Guido Günther @agx@librem.one

@drewdevault @martijnbraam something as simple as `coredumpctl gdb` plus a debuginfod server would be totally awesome. (not complaining, just trying to learn something I can *remember*) 😃

@drewdevault @martijnbraam To get core files at all, but then you need to set /proc/sys/kernel/core_pattern to have it in a fixed location (and not what the process changed to), then grab dbgsym packages, ... and do all that on all devices you care about

@martijnbraam For me the the alpine "trouble" is mostly debug tooling. It severely miss coredumpctl and reliable backtraces. Are there replacements I should be looking at?

@Phaserune @dos @craftyguy so want you link to it here so others can follow along?

@Phaserune @dos @craftyguy I'm not following PureOS Kernel development in detail atm so can't help here, sorry.

@joshfowler I think the best thing is to have phosh running nested on your desktop and then use gtk-inspector to modify e.g. CSS at runtime. That's easier (and faster) than pocking at the phone directly.

@joshfowler I'm not familiar with the regulations in UK but there's https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/904 - basically for the bits in calls to land.

@joshfowler Generally speaking: while we try to take higher resolution devices into account when developing phosh it's not continuously tested (e.g. phosh's CI tests 360x720) so it needs people to step up to send patches for those devices and to get rid of the papercuts (and we can then make sure we don't regress via CI).

@joshfowler Ah regarding lock screen, you want to send patches to allow for more spacing between the keys and maybe even scale up a bit.

Regarding switching keyboards:
That depends on your distro. In Debian it's just `update-alternatives`. On pmOS building from source and installing to `/usr/local/` should do the trick. That's at least how I run it there for testing. Note that phosh-osk-stub is experimental so make sure you have ssh access.

@joshfowler But lockscreen is fixed?

Your screenshot show's squeekboard so I assume you're hitting https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/338 . I'm using phosh-osk-stub instead as I rely on some of it's features and that ones scales according to the screenshot I posted.

@joshfowler hmm...seems my reply somehow vanished: pmOS tweaks sets CSS which likely causes your problem. Basically if you add additional CSS you got to keep the pieces.
There's some other caveats with fractinal scaling atm but phosh itself should render correctly at scale 2.5 (it does here on current main).

@joshfowler I assume you apply some custom CSS then? Both #phosh's lockscreen and #phosh-osk-stub look right here at scale 2.5 (got myself temporary access to a Oneplus 6T to check that)

I've tagged an initial version 0.0.1 of gmobile, a small supporting library used by #phosh, #feedbackd and soon #phoc for notches/cutouts, timers and the like: https://gitlab.gnome.org/guidog/gmobile/-/releases/v0.0.1

This is in early stages but maybe there's some stuff useful for other projects.

#linuxmobile #mobilelinux

@dos causality vs correlation strikes again.

As the last component of the 0.23.0 release set #phoc 0.23.0 is out, fixing the pixman renderer to help #CI testing, running in #qemu and platforms that can't or don't want to use GLES2. If you don't need any of these it's safe to wait for 0.24.0.

Release notes at: https://gitlab.gnome.org/World/Phosh/phoc/-/releases/v0.23.0

#phosh #wayland #wlroots #linuxonmobile #mobile #gnome #gnomeonmobile #librem5

@gnumdk I certainly appreciate any help to get the top panel flow around notches nicely once the groundwork landed (my #librem5 doesn't even need notches /cutout support). I hope we get some design input from @snwh how things could look like.

@hemish read thw whole thing: https://social.librem.one/@agx/109682949493890985