29 May 2021 |
panioluka | Now it's ok | 17:04:38 |
panioluka | Tho at right scaling I have some overlaps | 17:04:53 |
3 Jun 2021 |
plfiorini | In reply to @panioluka:matrix.org i am back here wb | 07:37:28 |
plfiorini | In reply to @panioluka:matrix.org And can i use https://github.com/neochapay/qt5-qpa-hwcomposer-plugin without mods? this should be usable instead of eglfs. in the future it would be cool to make an eglfs extension from it | 07:39:46 |
plfiorini | panioluka: i have a spare nexus 5 phone, how can i install manjaro arm on it and test liri myself? | 07:40:20 |
plfiorini | that way i could see if i can improve the UI for that form factor | 07:40:56 |
21 Jun 2021 |
Jack Works | Hi I've tried Liri with a newly installed arch Linux install | 16:19:03 |
Jack Works | I found those problems: 1. After I enter the password, the screen becomes dark and only a x-shaped cursor available. | 16:20:08 |
Jack Works | If I not use SDDM but type liri-session directly, I can open the session. | 16:20:46 |
Jack Works | 2. It seems like many icon is missing and showing a transparent empty icon in taskbar, app center, etc... | 16:21:34 |
Jack Works | 3. When there is a modal opening, like the app list, cursor will be invisible and it's hard to navigate around | 16:22:19 |
Jack Works | 4. When inside app list, after I typing the search item, using Tab cannot navigate me to the app list. | 16:23:17 |
Jack Works | 5. It will crash back to TTY and says "The Wayland connection broke. Did the Wayland compositor die?" randomly within 10 minutes | 16:24:18 |
Jack Works | I'm running this on a real machine, with AMD GPU. Not a laptop | 16:25:50 |
23 Jun 2021 |
panioluka | In reply to @plfiorini:matrix.org panioluka: i have a spare nexus 5 phone, how can i install manjaro arm on it and test liri myself? You need to port halium | 12:10:57 |
2 Jul 2021 |
| b4d_tR1p changed their profile picture. | 08:44:00 |
3 Jul 2021 |
| @lionirdeadman:gnome.org joined the room. | 05:31:40 |
@lionirdeadman:gnome.org | Hi, should the applications on Flathub be marked as EOL since you ship it on your own repository? Otherwise, it'd be good to update them away from EOL runtimes. | 05:33:36 |
@lionirdeadman:gnome.org | I'd be willing to do that work. It seems upstream you've stopped using a BaseApp so maybe that should still be EOLed once the applications are updated. | 05:35:15 |
plfiorini | apps in the liri repository are built from the continuous integration, the flathub apps are the official ones | 07:08:49 |
plfiorini | some apps are only in the liri repository for a reason: for example terminal needs an integration with flatpak to be usable otherwise it will only have access to the filesystem inside its flatpak package | 07:11:28 |
plfiorini | * some apps are only in the liri repository for a reason: for example terminal needs an integration with flatpak to be usable otherwise it will only have access to the filesystem inside its flatpak image | 07:11:32 |
plfiorini | the file manager too | 07:11:47 |
@lionirdeadman:gnome.org | An integration with flatpak? You mean a minimal flatpak version? | 07:12:19 |
@lionirdeadman:gnome.org | I think I misunderstood that. You meant that they're shipped there because they don't currently work, right? | 07:20:09 |
@lionirdeadman:gnome.org | Anyhow, I'll look into updating the flatpaks on Flathub tomorrow then. Would EOLing the BaseApp be wanted if upstream CI already doesn't use it? | 07:22:01 |
| * @lionirdeadman:gnome.org goes to sleep | 07:22:22 |
plfiorini | no no BaseApp is fine | 07:26:59 |
plfiorini | it's not used in the CI for semplicity | 07:27:21 |
plfiorini | but updating the flatpaks on flathub is very welcome, just don't EOL the base app :) | 07:28:12 |