Sebastian Krzyszkowiak @dos@librem.one

"me in the morning, right after I turned the switches on"

This may not be the most impressive winter selfie (it's a 8M sensor outputting 0.3M after all), but you got to start somewhere :) #librem5

I did nothing but taking the photo (looped in a script with v4l2-ctl and dcraw; then displayed on screen using Eye of GNOME) - all the credit goes to Dorota and Martin, and the work continues there: https://source.puri.sm/Librem5/linux-next/-/issues/43

@Alexmitter @bleakgrey Thankfully it's not the underlying tech that makes it hard - it's just a matter of tooling and culture around it, so fortunately it does seem like it's just a matter of time and maturity.

@Alexmitter @bleakgrey Yeah, I find the fact that it's super hard even for the *user* to patch libraries used by Flatpak apps to be its huge problem. For you and me it's the scrolling bug, someone else may need a quick hack to improve accessibility, someone else may want to test their patch on real apps before contributing upstream... Flatpak makes this hard for no good reason. I hope this will get better with time as power user needs get recognized and proper documentation gets written.

@thelinuxexperiment Looks like the animations in GTK are disabled - is this Manjaro's default?

@dylanvanassche @agx Yes, you can even do it right from the GUI in GNOME Settings now.

@scops Dumping the systemd journal from the previous boot would do it. Make sure to skim it for personal data though before sharing :)

@scops Would be nice to gather some logs then. Do you have the latest kernel installed? We used to have very unreliable battery meter that could lead to unexpected shutdowns too, but that should be fixed by now.

@scops If the compositor crashes, the screen goes blank for a few seconds. Then people tend to press the power button instead of waiting for phosh to come up again (which, well, is a natural reaction to screen suddenly going blank), which in turn triggers a full shutdown as that's what systemd does when it notices the power button being pressed and there's no compositor to intercept it.

I'll take a look whether we can block that power button behavior when the compositor isn't up.

@scops Does your Librem 5 shut down unexpectedly? That shouldn't happen and doesn't happen for me here. Are you sure it's not just a compositor crash? (asking since people very often confuse those) Which hardware batch is it?

@satur @niboe FYI Movim is pretty much a self-hostable server-side XMPP client.

@linmobnet ...and Giara has migrated now as well :)

@linmobnet FYI Tootle has already arrived in amber-phone yesterday, and Giara has been available in amber-phone-staging for more than two weeks now (seems there's some issue with its migration, it should have migrated by now - well, it likely just needs some manual encouragement ;))

@vancha @linmobnet People use to call it "random reboot", but in fact it's a compositor crash and then a manual reboot triggered by a power button when the compositor wasn't running. Unfortunately we still have a notorious crash in phoc that isn't sorted out yet :(

Spent some time on getting my old Librem 5 port of Jumpdrive into shape, so it can get upstreamed. It's a super useful little recovery utility to have in your tool belt :) https://github.com/dreemurrs-embedded/Jumpdrive/pull/24 #librem5 #gnu #linux #mobile