Show more

can leverage @exalm@floss.social 's work on theme preferences to at least guess whether the system intends to use dark-mode and color the launch splash accordingly:

@postmarketOS @linmob @danctnix that's reasonable to keep the maintenance burden under control. It should be merged soon though (there was review already if you look through the comments).

@linmob @danctnix @postmarketOS The patch has design blessing, is approved by upstream and will be merged after 41 is branched, that's as close as it gets when GNOME is about to release. Can't help here sorry. ( carries the patch since some time)

@joshfowler Also locate all sm.puri.OSK0.desktop and make sure none conatins "Exec=/usr/local/bin/phosh-osk-stub"

@joshfowler that says the keyboard isn't there when phosh wants to talk to it, that's not necessarily a problem but indicates that something is wrong (e.g. your distro calls it differently) - . Look at `gnome-session` in the logs. Phosh itself (the shell bianry) isn't really involved here (it's just that the git repo also contains the session file that lists the session components).

@joshfowler so check

- which session file is invoked
- which component in the session file refers to the keyboard
- which dektop files match that (can be duplicate ones in multiple directories)
- which one is invoked
- what is wrong with that one

(assuming you're *not* using systemd) If you dont' want to debug further just drop a desktop file to launch squeeboard into `/etc/xdg/autostart/` for the moment and let your distro figure out the details.

@joshfowler if i had to debug this i'd look first what desktop (or systemd unit) is invoked to for the OSK on session startup and then see why it doesn't happen (e.g. wrong path in desktop file, ...). The journal should tell you too (journalctl -b 0).

@joshfowler having it both in /usr/local/bin/ ans /usr/bin looks odd. The binary is likely in `/u/lib/phosh` in your case then (try `file` it needs to be an elf executable)

@joshfowler you can also just replace the /usr/bin/libexec/phosh binary and keep everything else as is from 0.12.1 - nothing important changed in the surroundings.

@joshfowler well if you can start squeekboard manually then something is wrong with your session. Are yo maybe using systemd activation while manjaro uses builtin session (see meson_options.txt)?

@joshfowler gnome-session brings up the required components in `phosh.session.desktop`. The OSK one is named `sm.puri.OSK0`

@joshfowler squeekboard is not affected/changed by this release, likely it's "just" not running in your session? Squeekboard startup is still snowflaky: source.puri.sm/Librem5/librem5 . Or maybe you're running `phosh-osk-stub` (which is just for tests).

phosh 0.13.1 is out 🚀 :
gitlab.gnome.org/World/Phosh/p

Feedback quick setting cycles through all modes, "Close all" notifications button, improved encrypted media handling and fractional scaling improvements.

The #Debian Janitor now automatically produces updated packages with the latest upstream Git commit for about 8k out of the 30k packages in the archive. Instructions on how to add the apt repo and which packages are included at janitor.debian.net/fresh / jelmer.uk/fresh-builds.html

@chrichri gitlab.gnome.org/World/Phosh/p - scale to fit users should think about sending patches to improve this (it's not that complicated and confined to the compositor)

@carlosgonz@mastodon.social video is already accelerated for fullscreen see https://source.puri.brem5/debs/epiphany/-/issues/32 and gitlab.gnome.org/Teams/Design/

Encrypted USB sticks are now automounted too in , no need to go via nautilus (thanks to GMountOperation):

Show more
image/svg+xml Librem Chat image/svg+xml