Guido Günther @agx@librem.one

@linmob Great! As a data point: I'm running #phosh on about a handful of different devices (#librem5, laptops, "media center" (which is basically a laptop attached to a TV) with #PureOS or #Debian and it's pretty stable there) so version comparisons and reviewing your distros patches may help).

@linmob if phosh (I assume you mean the session) crashes for you, you really want to check with you distro since it's fairly stable over here with PureOS for daily usage. Figuring out which component fails and gathering backtraces would be the first step (https://honk.sigxcpu.org/con/phosh_overview.html)

@cogitri @purism yes, it's a NexDock that provides keyboard/trackpad via usb and the librem5 feeds display via usb-pd alt-mode.

@joshfowler @purism send patches!

Besides the scaling from yesterday #phosh now also handles single / join display mode via GNOME Settings (arranging outputs, also changing resolution, rotation). There's bugs to be fixed in #phoc and #phosh to make this fully reliable but if you're careful it's already pretty useful:

#librem5 #gnomeonmobile @purism

Temporarily need more screen space with #phosh? Just scale to 100% instead of 200%:

@purism #librem5 #gnomeonmobile

@bart wonder how that happened, fixed now. Thanks!

#phosh in numbers 2020:

commits: 759
distinct authors (incl. i18n): 40
releases: 18

Thanks everyone!

While we had enabled power saving for the vivante gpu on the #librem5 since some time we couldn't power off the corresponding regulator (power supply) since the phone would hang then. Turns out we just didn't give it enough time to come back up. Fix is already merged into linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3b66e4a8e58a85af3212c7117d7a29c9ef6679a2

#etnaviv #librem5 #batterylife

I've put together a short overview on #phosh and closely related components and how they play together: https://honk.sigxcpu.org/con/phosh_overview.html

#gnomeonmobile #phoc #squeekboard

@ruff @x51@cybre.space https://gitlab.gnome.org/GNOME/gtk/-/blob/master/gtk/gtkapplication-dbus.c#L186

#phosh 0.7.1 is out 🚀 : https://source.puri.sm/Librem5/phosh/-/releases/v0.7.1

Bug fixes for keyboard navigation, monitor unplug, and modal dialog background rendering (@dos) but also new features like keygrabbing support (to make e.g media keys work) by @devrtz and initial logind support.

#librem5 @purism #gnomeonmobile

@ruff @x51@cybre.space did you look at the code? It is a well known DBus path abstacted by the toolkit (here GTK).

@ruff @x51@cybre.space you can do that today by looking at https://developer.gnome.org/gtk3/stable/GtkApplication.html#GtkApplication--screensaver-active and we have apps doing that already.

@ruff @x51@cybre.space that shpi;d't be hard to add but needs to happen in a DE agnostic way so we can hook it into e.g. GApplication.

@ruff @x51@cybre.space how do *you* define an inactive application? If you mean one that is not using CPU time then not yet. It's not a shell thing though #phosh would just talk to the daemon that handles this (e.g. by freezing a cgroup).
So we'd need to come up with the deamon first (maybe fits into the systemd project) and then hook the UI to it.

Here's a bit of doc how #phosh's session is set and what it interacts with: https://honk.sigxcpu.org/projects/phosh/docs/ch01.html

/cc @x51@cybre.space