Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2023-09-20T06:24:52Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/332upgrade to crimson removes gui2023-09-20T06:24:52ZChris Vogelupgrade to crimson removes guiI upgraded from an up-to-date byzantium to crimson and the gui has been removed as part of the `apt full-upgrade`.
After reboot without gui (but with graphical output of a login: prompt) the situation could be fixed by `apt-get install ...I upgraded from an up-to-date byzantium to crimson and the gui has been removed as part of the `apt full-upgrade`.
After reboot without gui (but with graphical output of a login: prompt) the situation could be fixed by `apt-get install librem5-gnome`.https://source.puri.sm/Librem5/millipixels/-/issues/91audio/video desync2023-09-06T23:14:40ZEvangelos Ribeiro Tzarasaudio/video desyncWhen I record videos the audio track is not fully in sync with video footage and audio **always** before the video is complete, leaving a couple of seconds of silence at the end of the video.
Possibly related: #90
I've not checked in...When I record videos the audio track is not fully in sync with video footage and audio **always** before the video is complete, leaving a couple of seconds of silence at the end of the video.
Possibly related: #90
I've not checked in detail if the amount of "no sound at the end of the video" is a (linear) function of the video duration,
but I may follow up with this information once I've done necessary research (but I may not actually get around to it, so don't wait on me :P )https://source.puri.sm/Librem5/millipixels/-/issues/90Long(ish) video capture produces stutters2023-10-02T09:02:18ZEvangelos Ribeiro TzarasLong(ish) video capture produces stuttersThis may actually be a kernel issue because the behaviour is different between PureOS (running 6.3) and Mobian (running 6.1).
The issue can be reproduced the following way:
- Start recording a video (rear camera in my case - I haven't c...This may actually be a kernel issue because the behaviour is different between PureOS (running 6.3) and Mobian (running 6.1).
The issue can be reproduced the following way:
- Start recording a video (rear camera in my case - I haven't checked with front camera)
- Observe the preview freezing every now and then for variable amounts of time (t \element [0.2; 3] seconds)
- These stutters are also in the video file (probably this is obvious)
- This even happens for relatively short videos of ~30s (so should be easy to reproduce)
- This also happens when not thermally throttled (i.e. coming out of suspend and starting to record shortly afterwards)
However on Mobian these issues do not seem to manifest (this strongly?)
If desired I can provide some video footage
/cc @martin.kepplinger because it may be a kernel issue (I believe millipixels in Mobian and PureOS is the same version - TODO need to recheck)https://source.puri.sm/Librem5/feedbackd/-/issues/74lfb: Don't assert when not inited2023-09-06T09:53:19ZGuido Guntherlfb: Don't assert when not initedWe should rather `g_return_if_fail` (and in the async case we can even return sensible errors). This makes it simpler for clients.We should rather `g_return_if_fail` (and in the async case we can even return sensible errors). This makes it simpler for clients.https://source.puri.sm/Librem5/feedbackd/-/issues/73feedbackd: Try harder to load a theme2023-10-01T22:12:36ZBoud Roukemafeedbackd: Try harder to load a themeDESCRIPTION:
A user may create a `custom.json` file with erroneous syntax; either
forget or not know about using `fbd-theme-validate` and `fbcli`; and
restart phosh with the un-parseable syntax. With the current code of
`feedbackd`, no f...DESCRIPTION:
A user may create a `custom.json` file with erroneous syntax; either
forget or not know about using `fbd-theme-validate` and `fbcli`; and
restart phosh with the un-parseable syntax. With the current code of
`feedbackd`, no fallback is available, so (at least in the case of
`phosh`) the user session will fail in the sense that clicking on any
gui will cause `phosh` to restart. The user will not have access to a
terminal in phosh to correct the syntax error.
COMMENT:
While a careful user will avoid this bug (especially as documentation
improves), it would be better to minimise situations where the user
becomes in some sense "locked out" of using basic tools - including an
on-touchscreen terminal - due to a minor error resulting from having some,
but not enough, experience of various nuances in using general tools
and tools specific to this software. The open mobile phone ecosystem especially needs
to encourage people who are in between experts and novices, and if
we can make things a bit more robust for the in-between people, then that would
help to encourage activity in the bridge between the active people (few) and
the novices (many). Having a safe fallback is a low-cost, high-benefit policy.
REPRODUCE BUG:
1. Backup the file `~/.config/feedbackd/themes/custom.json` if you have it (and similarly shift out of place/backup files in other user-level locations - see https://source.puri.sm/Librem5/feedbackd/-/blob/main/README.md for a current description of customisation)
````
cp -piv ~/.config/feedbackd/themes/custom.json ~/.config/feedbackd/themes/custom.json.bak
````
2. Create a file with wrong syntax and "forget" to check it with `fbd-theme-validate` and `fbcli` (the user's actual error is likely to be much less easy to spot by eye - the current upstream README.md template has a double-quote and two commas missing):
````
echo "{" > ~/.config/feedbackd/themes/custom.json
````
3. Check that you have the 'custom' theme selected:
````
gsettings set org.sigxcpu.feedbackd theme custom; gsettings get org.sigxcpu.feedbackd theme
````
This should give:
````
'custom'
````
4. Consider a user who tries to do things properly by searching for a `feedbackd` systemd service, and does not find any. The user instead guesses that killing the `feedbackd` process and restarting `phosh` is a sure way to force the process to be restarted. (A reboot would presumably give the same effect as this step.)
````
killall feedbackd
sudo systemctl restart phosh
````
5. `Phosh` should restart. Login and try to click open a terminal or other gui that uses the session, such as `foot`, `chatty`, `kgx` aka `gnome-console`, or `gnome-calls`.
Result:
`phosh` restarts each time one of these guis is restarted. The user does not have terminal access (apart from `ssh` over USB-C, or a `ttyN` through a docking bar + keyboard, or through a pine64 keyboard). If the user is e.g. travelling with no convenient access to this extra hardware, then the user's attempt to do a minor customisation of `feedbackd` ends up in effectively disabling the phone for the rest of the journey.
CONTEXT:
* Mobian/trixie
* PinePhone v1.2
````
$ dpkg -l |grep -E "feedbackd|phosh|gnome|foot"
ii feedbackd 0.2.0-2 arm64 DBus service for haptic/visual/audio feedback
ii feedbackd-common 0.2.0-2 all Shared files for feedbackd
ii feedbackd-device-themes 0.0.r3-1 all Device specific themes for Feedbackd
ii foot 1.15.3-1 arm64 Fast, lightweight and minimalistic Wayland terminal emulator
ii foot-terminfo 1.15.3-1 all Fast, lightweight and minimalistic Wayland terminal emulator (terminfo files)
ii foot-themes 1.15.3-1 all Fast, lightweight and minimalistic Wayland terminal emulator (theme files)
ii gir1.2-gnomedesktop-3.0:arm64 44.0-2 arm64 Introspection data for GnomeDesktop (GTK 3)
ii gnome-backgrounds 44.0-2 all Set of backgrounds packaged with the GNOME desktop
ii gnome-bluetooth-3-common 42.6-1 all GNOME Bluetooth 3 common files
ii gnome-bluetooth-sendto 42.6-1 arm64 GNOME Bluetooth Send To app
ii gnome-calculator 1:45.0-2 arm64 GNOME desktop calculator
ii gnome-calendar 44.1-2mobian1 arm64 Calendar application for GNOME
ii gnome-calls 45~alpha.0-4 arm64 Make and receive PSTN phone calls
ii gnome-clocks 44.0-2 arm64 Simple GNOME app with stopwatch, timer, and world clock support
ii gnome-console 44.0-2 arm64 Simple user-friendly terminal emulator for the GNOME desktop
ii gnome-contacts 44.0-2mobian1 arm64 Contacts manager for GNOME
ii gnome-control-center 1:44.3-3mobian1 arm64 utilities to configure the GNOME desktop
ii gnome-control-center-data 1:44.3-3mobian1 all configuration applets for GNOME - data files
ii gnome-desktop3-data 44.0-2 all Common files for GNOME desktop apps
ii gnome-initial-setup 45~beta-1 arm64 Initial GNOME system setup helper
ii gnome-keyring 42.1-1+b2 arm64 GNOME keyring services (daemon and tools)
ii gnome-maps 44.3-2 arm64 map application for GNOME
ii gnome-online-accounts 3.48.0-2 arm64 service to manage online accounts for the GNOME desktop
ii gnome-session-bin 44.0-2 arm64 GNOME Session Manager - Minimal runtime
ii gnome-session-canberra 0.30-10 arm64 GNOME session log in and log out sound events
ii gnome-session-common 44.0-2 all GNOME Session Manager - common files
ii gnome-settings-daemon 45~beta-1 arm64 daemon handling the GNOME session settings
ii gnome-settings-daemon-common 45~beta-1 all daemon handling the GNOME session settings - common files
ii gnome-shell-common 44.3-5 all common files for the GNOME graphical shell
ii gnome-sound-recorder 43~beta-1 all simple and modern sound recorder for GNOME
ii gnome-themes-extra-data 3.28-2 all Adwaita GTK 2 theme and Adwaita-dark GTK 3 theme — common files
ii gnome-todo 43.0-1 all minimalistic personal task manager - transitional package
ii gnome-usage 3.38.1-3mobian1 arm64 simple system monitor app for GNOME
ii gnome-weather 44.0-2 all access current conditions and forecasts
ii libgnome-bg-4-2:arm64 44.0-2 arm64 Utility library for background images - runtime files
ii libgnome-bluetooth-3.0-13:arm64 42.6-1 arm64 GNOME Bluetooth 3 support library
ii libgnome-bluetooth-ui-3.0-13:arm64 42.6-1 arm64 GNOME Bluetooth 3 UI support library
ii libgnome-desktop-3-20:arm64 44.0-2 arm64 Utility library for the GNOME desktop - GTK 3 version
ii libgnome-desktop-3-dev:arm64 44.0-2 arm64 Utility library for the GNOME desktop - development files (GTK 3)
ii libgnome-desktop-4-2:arm64 44.0-2 arm64 Utility library for the GNOME desktop - runtime files
ii libgnome-rr-4-2:arm64 44.0-2 arm64 Utility library for display information - runtime files
ii libjim0.81:arm64 0.81+dfsg0-2 arm64 small-footprint implementation of Tcl - shared library
ii libpam-gnome-keyring:arm64 42.1-1+b2 arm64 PAM module to unlock the GNOME keyring upon login
ii mobian-phosh 0.4.2 all Mobian -- full Phosh environment
ii mobian-phosh-base 0.4.2 all Mobian -- base Phosh environment
ii mobian-phosh-extras 0.4.2 all Mobian -- extra applications for the Phosh environment
ii mobian-phosh-phone 0.4.2 all Mobian -- telephony applications for the Phosh environment
ii mobian-tweaks-phosh 0.5.8 all Mobian -- Configuration settings for Phosh
ii network-manager-gnome 1.32.0-3 arm64 network management framework (GNOME frontend)
ii phosh 0.30.0-1 arm64 Pure Wayland shell for mobile devices
ii phosh-core 24 arm64 GNOME/Phosh mobile Environment -- essential components
ii phosh-full 24 arm64 GNOME/Phosh mobile Environment, with extra components
ii phosh-mobile-settings 0.30.0-1 arm64 Phosh and related settings for mobile
ii phosh-mobile-tweaks 0.30.0-1 all Pure Wayland shell for mobile devices - GSettings tweaks
ii phosh-phone 24 arm64 GNOME/Phosh mobile Environment -- phone components
ii phosh-plugins 0.30.0-1 arm64 Pure Wayland shell for mobile devices - Plugins
ii phosh-tour 0.24.0-2 arm64 Short introduction to phosh on smartphones
ii pinentry-gnome3 1.2.1-1 arm64 GNOME 3 PIN or pass-phrase entry dialog for GnuPG
````
LOG:
````
$ journalctl # from the deliberate restart of phosh in step 4, to the unwanted restart of phosh in step 5
Sep 03 00:49:36 mobian systemd[1]: systemd-localed.service: Deactivated successfully.
Sep 03 00:49:36 mobian sudo[34086]: mobian : TTY=pts/2 ; PWD=/home/mobian/.config/feedbackd/themes ; USER=root ; COMMAND=/usr/bin/systemctl restart phosh
Sep 03 00:49:36 mobian sudo[34086]: pam_unix(sudo:session): session opened for user root(uid=0) by mobian(uid=1000)
Sep 03 00:49:36 mobian systemd[1]: Stopping phosh.service - Phosh, a shell for mobile phones...
Sep 03 00:49:36 mobian systemd-logind[655]: Session 1183 logged out. Waiting for processes to exit.
Sep 03 00:49:36 mobian kernel: rfkill: input handler enabled
Sep 03 00:49:37 mobian xdg-desktop-por[33927]: Error reading events from display: Broken pipe
Sep 03 00:49:37 mobian systemd[829]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Sep 03 00:49:37 mobian systemd[829]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Sep 03 00:49:37 mobian systemd[1]: phosh.service: Deactivated successfully.
Sep 03 00:49:37 mobian phosh-session[34029]: could not connect to wayland server
Sep 03 00:49:37 mobian systemd[1]: Stopped phosh.service - Phosh, a shell for mobile phones.
Sep 03 00:49:37 mobian phosh-session[34029]: (EE)
Sep 03 00:49:37 mobian phosh-session[34029]: Fatal server error:
Sep 03 00:49:37 mobian phosh-session[34029]: (EE) Couldn't add screen
Sep 03 00:49:37 mobian phosh-session[34029]: (EE)
Sep 03 00:49:37 mobian systemd-logind[655]: Failed to restore VT, ignoring: Input/output error
Sep 03 00:49:37 mobian polkitd[650]: Unregistered Authentication Agent for unix-session:1183 (system bus name :1.553, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C.UTF-8) (disconnected from bus)
Sep 03 00:49:37 mobian systemd[1]: Started phosh.service - Phosh, a shell for mobile phones.
Sep 03 00:49:37 mobian sudo[34086]: pam_unix(sudo:session): session closed for user root
Sep 03 00:49:37 mobian systemd[1]: session-1183.scope: Deactivated successfully.
Sep 03 00:49:37 mobian systemd[1]: session-1183.scope: Consumed 57.214s CPU time.
Sep 03 00:49:37 mobian systemd-logind[655]: Removed session 1183.
Sep 03 00:49:37 mobian (-session)[34136]: pam_unix(login:session): session opened for user mobian(uid=1000) by mobian(uid=0)
Sep 03 00:49:37 mobian systemd-logind[655]: New session 1185 of user mobian.
Sep 03 00:49:37 mobian systemd[1]: Started session-1185.scope - Session 1185 of User mobian.
Sep 03 00:49:37 mobian phoc[34136]: [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
Sep 03 00:49:37 mobian phoc[34136]: [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
Sep 03 00:49:38 mobian phosh-session[34136]: Running compositor on wayland display 'wayland-0'
Sep 03 00:49:38 mobian phoc[34136]: Output 'DSI-1' added ('(null)'/'(null)'/'(null)'), 68mm x 136mm
Sep 03 00:49:40 mobian phoc[34136]: Enabling shell mode
Sep 03 00:49:41 mobian gnome-session[34157]: gnome-session-binary[34157]: WARNING: Desktop file /etc/xdg/autostart/pulseaudio.desktop for application pulseaudio.desktop could not be parsed or references a missing TryExec binary
Sep 03 00:49:41 mobian gnome-session-binary[34157]: WARNING: Desktop file /etc/xdg/autostart/pulseaudio.desktop for application pulseaudio.desktop could not be parsed or references a missing TryExec binary
Sep 03 00:49:41 mobian gnome-keyring-daemon[1017]: The PKCS#11 component was already initialized
Sep 03 00:49:41 mobian gnome-keyring-daemon[34200]: discover_other_daemon: 1
Sep 03 00:49:41 mobian gnome-keyring-pkcs11.desktop[34200]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 03 00:49:41 mobian gnome-keyring-pkcs11.desktop[34200]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Sep 03 00:49:41 mobian gnome-keyring-d[1017]: The PKCS#11 component was already initialized
Sep 03 00:49:41 mobian gnome-keyring-daemon[1017]: The Secret Service was already initialized
Sep 03 00:49:41 mobian gnome-keyring-d[1017]: The Secret Service was already initialized
Sep 03 00:49:41 mobian gnome-keyring-daemon[34203]: discover_other_daemon: 1
Sep 03 00:49:41 mobian gnome-keyring-secrets.desktop[34203]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 03 00:49:41 mobian gnome-keyring-secrets.desktop[34203]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Sep 03 00:49:41 mobian gnome-keyring-daemon[1017]: The SSH agent was already initialized
Sep 03 00:49:41 mobian gnome-keyring-daemon[34207]: discover_other_daemon: 1
Sep 03 00:49:41 mobian gnome-keyring-ssh.desktop[34207]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 03 00:49:41 mobian gnome-keyring-ssh.desktop[34207]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Sep 03 00:49:41 mobian gnome-keyring-d[1017]: The SSH agent was already initialized
Sep 03 00:49:42 mobian polkitd[650]: Registered Authentication Agent for unix-session:1185 (system bus name :1.574 [/usr/libexec/phosh], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C.UTF-8)
Sep 03 00:49:42 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activating service name='org.sigxcpu.Feedback' requested by ':1.790' (uid=1000 pid=34209 comm="/usr/libexec/phosh")
Sep 03 00:49:42 mobian feedbackd[34218]: Failed to load any theme: <data>:1:1: Parse error: unexpected character `{', expected string constant
Sep 03 00:49:42 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activated service 'org.sigxcpu.Feedback' failed: Process org.sigxcpu.Feedback received signal 5
Sep 03 00:49:42 mobian phosh[34209]: Failed to init libfeedback: Error calling StartServiceByName for org.sigxcpu.Feedback: Process org.sigxcpu.Feedback received signal 5
Sep 03 00:49:43 mobian phosh[34209]: Unable to toggle OSK: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name sm.puri.OSK0 was not provided by any .service files
Sep 03 00:49:44 mobian phosh[34209]: Disabling emergency calls
Sep 03 00:49:45 mobian kernel: rfkill: input handler disabled
Sep 03 00:49:46 mobian gsd-usb-protect[34372]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
Sep 03 00:49:46 mobian dbus-daemon[644]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.584' (uid=1000 pid=34365 comm="/usr/libexec/gsd-keyboard")
Sep 03 00:49:46 mobian systemd[1]: Starting systemd-localed.service - Locale Service...
Sep 03 00:49:47 mobian phosh-session[34527]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 03 00:49:47 mobian phosh-session[34527]: > Warning: Unsupported maximum keycode 708, clipping.
Sep 03 00:49:47 mobian phosh-session[34527]: > X11 cannot support keycodes above 255.
Sep 03 00:49:47 mobian phosh-session[34527]: Errors from xkbcomp are not fatal to the X server
Sep 03 00:49:47 mobian dbus-daemon[644]: [system] Successfully activated service 'org.freedesktop.locale1'
Sep 03 00:49:47 mobian systemd[1]: Started systemd-localed.service - Locale Service.
Sep 03 00:49:49 mobian gnome-session-binary[34157]: Entering running state
Sep 03 00:49:49 mobian phosh-session[34647]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 03 00:49:49 mobian phosh-session[34647]: > Warning: Unsupported maximum keycode 708, clipping.
Sep 03 00:49:49 mobian phosh-session[34647]: > X11 cannot support keycodes above 255.
Sep 03 00:49:49 mobian phosh-session[34647]: Errors from xkbcomp are not fatal to the X server
Sep 03 00:49:50 mobian libcanberra-login-sound.desktop[34631]: Failed to play sound: File or data not found
Sep 03 00:49:51 mobian chatty[34624]: Couldn't read the color-scheme setting: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Portal operation not allowed: Unable to open /proc/34624/root
Sep 03 00:49:51 mobian chatty[34624]: Couldn't read the color-scheme setting: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Portal operation not allowed: Unable to open /proc/34624/root
Sep 03 00:49:51 mobian chatty[34624]: Couldn't read the high-contrast setting: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Portal operation not allowed: Unable to open /proc/34624/root
Sep 03 00:49:51 mobian gnome-calls[34621]: Couldn't read the color-scheme setting: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Portal operation not allowed: Unable to open /proc/34621/root
Sep 03 00:49:51 mobian gnome-calls[34621]: Couldn't read the color-scheme setting: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Portal operation not allowed: Unable to open /proc/34621/root
Sep 03 00:49:51 mobian gnome-calls[34621]: Couldn't read the high-contrast setting: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Portal operation not allowed: Unable to open /proc/34621/root
Sep 03 00:49:52 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activating service name='org.sigxcpu.Feedback' requested by ':1.824' (uid=1000 pid=34624 comm="/usr/bin/chatty --daemon")
Sep 03 00:49:52 mobian feedbackd[34752]: Failed to load any theme: <data>:1:1: Parse error: unexpected character `{', expected string constant
Sep 03 00:49:52 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activated service 'org.sigxcpu.Feedback' failed: Process org.sigxcpu.Feedback received signal 5
Sep 03 00:49:52 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activating service name='org.sigxcpu.Feedback' requested by ':1.823' (uid=1000 pid=34621 comm="/usr/bin/gnome-calls --daemon")
Sep 03 00:49:52 mobian feedbackd[34779]: Failed to load any theme: <data>:1:1: Parse error: unexpected character `{', expected string constant
Sep 03 00:49:52 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activated service 'org.sigxcpu.Feedback' failed: Process org.sigxcpu.Feedback received signal 5
Sep 03 00:49:52 mobian gnome-calls[34621]: Failed to init libfeedback: Error calling StartServiceByName for org.sigxcpu.Feedback: Process org.sigxcpu.Feedback received signal 5
Sep 03 00:49:53 mobian NetworkManager[671]: <info> [1693694993.5854] agent-manager: agent[bc17f5944b4b7bd4,:1.574/sm.puri.phosh.NetworkAgent/1000]: agent registered
Sep 03 00:49:53 mobian sm.puri.Chatty-daemon.desktop[34817]: Xlib: extension "DRI2" missing on display ":0".
Sep 03 00:49:53 mobian sm.puri.Chatty-daemon.desktop[34817]: Xlib: extension "DRI2" missing on display ":0".
Sep 03 00:49:53 mobian org.gnome.Calls-daemon.desktop[34621]: su_source_port_create() returns 0x55ad3ac9f0
Sep 03 00:49:53 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activating service name='org.gnome.Contacts' requested by ':1.823' (uid=1000 pid=34621 comm="/usr/bin/gnome-calls --daemon")
Sep 03 00:49:54 mobian dbus-daemon[901]: [session uid=1000 pid=901] Successfully activated service 'org.gnome.Contacts'
Sep 03 00:49:54 mobian chatty[34624]: gst_element_message_full_with_details: assertion 'GST_IS_ELEMENT (element)' failed
Sep 03 00:49:54 mobian chatty[34624]: gst_element_message_full_with_details: assertion 'GST_IS_ELEMENT (element)' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian sm.puri.Chatty-daemon.desktop[34624]: Oops, secure memory pool already initialized
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian dbus-daemon[901]: [session uid=1000 pid=901] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.74' (uid=1000 pid=1707 comm="/usr/libexec/xdg-desktop-portal")
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian chatty[34624]: purple_presence_set_status_active: assertion 'status != NULL' failed
Sep 03 00:49:55 mobian systemd[829]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
Sep 03 00:50:00 mobian gsd-xsettings[34287]: Failed to get current UI legacy scaling factor
Sep 03 00:50:00 mobian gsd-xsettings[34287]: Failed to get current UI legacy scaling factor
Sep 03 00:50:00 mobian org.gnome.SettingsDaemon.XSettings.desktop[34879]: Failure: No such entity
Sep 03 00:50:00 mobian dbus-daemon[901]: [session uid=1000 pid=901] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
Sep 03 00:50:00 mobian systemd[829]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Sep 03 00:50:00 mobian gsd-xsettings[34287]: Failed to get current UI legacy scaling factor
Sep 03 00:50:00 mobian gsd-xsettings[34287]: Failed to get current UI legacy scaling factor
Sep 03 00:50:10 mobian gnome-session[34157]: gnome-session-binary[34157]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Sep 03 00:50:10 mobian gnome-session-binary[34157]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Sep 03 00:50:11 mobian phosh-session[34957]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 03 00:50:11 mobian phosh-session[34957]: > Warning: Unsupported maximum keycode 708, clipping.
Sep 03 00:50:11 mobian phosh-session[34957]: > X11 cannot support keycodes above 255.
Sep 03 00:50:11 mobian phosh-session[34957]: Errors from xkbcomp are not fatal to the X server
Sep 03 00:50:12 mobian gsd-xsettings[34939]: Failed to get current UI legacy scaling factor
Sep 03 00:50:12 mobian gsd-xsettings[34939]: Failed to get current UI legacy scaling factor
Sep 03 00:50:12 mobian org.gnome.SettingsDaemon.XSettings.desktop[34970]: Failure: No such entity
Sep 03 00:50:13 mobian gsd-xsettings[34939]: Failed to get current UI legacy scaling factor
Sep 03 00:50:13 mobian gsd-xsettings[34939]: Failed to get current UI legacy scaling factor
Sep 03 00:50:15 mobian phosh[34209]: You must call lfb_init() before triggering events.
Sep 03 00:50:15 mobian polkitd[650]: Unregistered Authentication Agent for unix-session:1185 (system bus name :1.574, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C.UTF-8) (disconnected from bus)
Sep 03 00:50:15 mobian gnome-session[34157]: gnome-session-binary[34157]: WARNING: Application 'sm.puri.Phosh.desktop' killed by signal 5
Sep 03 00:50:15 mobian gnome-session-binary[34157]: WARNING: Application 'sm.puri.Phosh.desktop' killed by signal 5
Sep 03 00:50:15 mobian gnome-session-binary[34157]: Unrecoverable failure in required component sm.puri.Phosh.desktop
Sep 03 00:50:15 mobian kernel: rfkill: input handler enabled
Sep 03 00:50:15 mobian gsd-color[34299]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian gsd-wacom[34276]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian gsd-power[34290]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian gsd-keyboard[34365]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian gsd-media-keys[34393]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian squeekboard[34559]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian xdg-desktop-por[34849]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian phosh-session[34951]: (EE) failed to read Wayland events: Broken pipe
Sep 03 00:50:15 mobian evolution-alarm[34616]: Error reading events from display: Broken pipe
Sep 03 00:50:15 mobian org.codeberg.dnkl.foot.desktop[35009]: err: wayland.c:1452: no compositor
Sep 03 00:50:15 mobian systemd[829]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Sep 03 00:50:15 mobian systemd[829]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Sep 03 00:50:15 mobian org.codeberg.dnkl.foot.desktop[35009]: err: wayland.c:1951: failed to flush wayland socket: Connection reset by peer
Sep 03 00:50:16 mobian systemd[829]: xdg-desktop-portal-gtk.service: Consumed 1.011s CPU time.
Sep 03 00:50:16 mobian systemd-logind[655]: Session 1185 logged out. Waiting for processes to exit.
Sep 03 00:50:16 mobian systemd[1]: phosh.service: Deactivated successfully.
Sep 03 00:50:16 mobian systemd[1]: session-1185.scope: Deactivated successfully.
Sep 03 00:50:16 mobian systemd[1]: session-1185.scope: Consumed 56.013s CPU time.
Sep 03 00:50:16 mobian systemd-logind[655]: Removed session 1185.
Sep 03 00:50:17 mobian systemd[1]: systemd-localed.service: Deactivated successfully.
Sep 03 00:50:21 mobian systemd[1]: phosh.service: Scheduled restart job, restart counter is at 1.
Sep 03 00:50:22 mobian systemd[1]: Started phosh.service - Phosh, a shell for mobile phones.
````
SUGGESTED FIX:
If the user has messed up the configuration, then falling back to the default profile seems wiser than letting the session (`phosh`) become unusable. A hack that works for me to do this is the following patch:
````
diff --git a/src/fbd-theme-expander.c b/src/fbd-theme-expander.c
index 3cce7af..1aedfcc 100644
--- a/src/fbd-theme-expander.c
+++ b/src/fbd-theme-expander.c
@@ -369,8 +369,19 @@ fbd_theme_expander_load_theme_files (FbdThemeExpander *self, GError **err)
g_info ("Loading theme file at '%s'", self->theme_file);
theme = fbd_feedback_theme_new_from_file (self->theme_file, err);
- if (theme == NULL)
+ if (theme == NULL){
+ /* Warn about error in user-level theme and fall back to default
+ * theme . */
+ g_critical ("Error loading user-level theme at '%s'", self->theme_file);
+ self->theme_name = g_strdup (DEFAULT_THEME_NAME);
+ theme_file = fbd_theme_expander_find_theme_path (self, self->theme_name);
+ self->theme_file = g_steal_pointer(&theme_file);
+ theme = fbd_feedback_theme_new_from_file (self->theme_file, err);
+ if (theme == NULL){
+ g_critical ("Error falling back to default theme");
return NULL;
+ }
+ }
/* Build a list of themes */
while (TRUE) {
````
The idea is that the system-level theme will normally be a lot better checked than one
modified by the user. An error at that level is the responsibility of developers and
OS distributions such as Debian GNU/Linux and Mobian.
I can propose this as a merge request if it looks like an acceptable solution.https://source.puri.sm/Librem5/millipixels/-/issues/89macro mode lost2023-10-02T12:16:22ZChris Vogelmacro mode lostI took (this picture)[https://social.librem.one/@chrichri/108142188504318062] in April 2022.
I didn't find a way to get a focus nearly as close as the picture is taken.
To me it looks like some change made it impossible to focus for ve...I took (this picture)[https://social.librem.one/@chrichri/108142188504318062] in April 2022.
I didn't find a way to get a focus nearly as close as the picture is taken.
To me it looks like some change made it impossible to focus for very close objects.https://source.puri.sm/Librem5/OS-issues/-/issues/331Backport xdg-desktop-portal 0.17.12023-08-31T13:30:35ZGuido GuntherBackport xdg-desktop-portal 0.17.1This allows for finer grained selection of which portal to use which phosh can make use of.This allows for finer grained selection of which portal to use which phosh can make use of.https://source.puri.sm/Librem5/debs/gnome-settings-daemon/-/issues/29USBGuard pops up seeming randomly2023-08-30T18:53:38ZDavid HamnerUSBGuard pops up seeming randomlyAfter flashing a fresh L5 image sometimes I get a popup about USBGuard.
![USB](/uploads/80431a43db441b5fb66f8b3e885b0824/USB.jpg)
It's rather rare I have only seen it perhaps 4-5 times out of countless flashes. As a workaround for the p...After flashing a fresh L5 image sometimes I get a popup about USBGuard.
![USB](/uploads/80431a43db441b5fb66f8b3e885b0824/USB.jpg)
It's rather rare I have only seen it perhaps 4-5 times out of countless flashes. As a workaround for the popup, Autoqa keeps a lookout for it after the first login and enters the password if it does come up:
https://source.puri.sm/david.hamner/autoqa/-/blob/main/verify_image/2.0_welcome_wizard/0_usb_guard.yamlhttps://source.puri.sm/Librem5/bm818-tools/-/issues/6bm818-tools doesn't show up in PureOS Store2023-10-02T07:00:28ZSteve Stevensbm818-tools doesn't show up in PureOS StoreIf you search for bm818 or bm818-tools in the software app, it doesn't show up.If you search for bm818 or bm818-tools in the software app, it doesn't show up.https://source.puri.sm/Librem5/linux/-/issues/491ethernet connection not activated when hoyoki dock is connected2023-08-29T09:41:13ZChris Vogelethernet connection not activated when hoyoki dock is connectedKernel version: 6.3.0-1-librem5 (PureOS Byzantium)
The ethernet connection is not activated when the hoyoki dock is connected.
Here's a dmesg of the dock being connected:
```
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream ...Kernel version: 6.3.0-1-librem5 (PureOS Byzantium)
The ethernet connection is not activated when the hoyoki dock is connected.
Here's a dmesg of the dock being connected:
```
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:51 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000000000010010
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: irq 208, io mem 0x38100000
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4
[Fr Aug 18 12:29:52 2023] xhci-hcd xhci-hcd.5.auto: Host supports USB 3.0 SuperSpeed
[Fr Aug 18 12:29:52 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:52 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:52 2023] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.03
[Fr Aug 18 12:29:52 2023] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Fr Aug 18 12:29:52 2023] usb usb3: Product: xHCI Host Controller
[Fr Aug 18 12:29:52 2023] usb usb3: Manufacturer: Linux 6.3.0-1-librem5 xhci-hcd
[Fr Aug 18 12:29:52 2023] usb usb3: SerialNumber: xhci-hcd.5.auto
[Fr Aug 18 12:29:52 2023] hub 3-0:1.0: USB hub found
[Fr Aug 18 12:29:52 2023] hub 3-0:1.0: 1 port detected
[Fr Aug 18 12:29:52 2023] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[Fr Aug 18 12:29:52 2023] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.03
[Fr Aug 18 12:29:52 2023] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Fr Aug 18 12:29:52 2023] usb usb4: Product: xHCI Host Controller
[Fr Aug 18 12:29:52 2023] usb usb4: Manufacturer: Linux 6.3.0-1-librem5 xhci-hcd
[Fr Aug 18 12:29:52 2023] usb usb4: SerialNumber: xhci-hcd.5.auto
[Fr Aug 18 12:29:52 2023] hub 4-0:1.0: USB hub found
[Fr Aug 18 12:29:52 2023] hub 4-0:1.0: 1 port detected
[Fr Aug 18 12:29:52 2023] bq25890-charger 3-006a: Upstream supply changed: 1.
[Fr Aug 18 12:29:52 2023] bq25890-charger 3-006a: Disabling OTG_EN pin
[Fr Aug 18 12:29:52 2023] cdns-mhdp-imx 32c00000.hdmi: Wait PLL Ack failed
[Fr Aug 18 12:29:52 2023] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[Fr Aug 18 12:29:52 2023] usb 3-1: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 7.04
[Fr Aug 18 12:29:52 2023] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Aug 18 12:29:52 2023] usb 3-1: Product: USB2.0 Hub
[Fr Aug 18 12:29:52 2023] usb 3-1: Manufacturer: VIA Labs, Inc.
[Fr Aug 18 12:29:52 2023] usb 3-1: SerialNumber: 000000001
[Fr Aug 18 12:29:52 2023] usb 3-1: Device is not authorized for usage
[Fr Aug 18 12:29:52 2023] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[Fr Aug 18 12:29:52 2023] hub 3-1:1.0: USB hub found
[Fr Aug 18 12:29:52 2023] hub 3-1:1.0: 4 ports detected
[Fr Aug 18 12:29:52 2023] usb 4-1: New USB device found, idVendor=2109, idProduct=0822, bcdDevice= 7.04
[Fr Aug 18 12:29:52 2023] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fr Aug 18 12:29:52 2023] usb 4-1: Product: USB3.1 Hub
[Fr Aug 18 12:29:52 2023] usb 4-1: Manufacturer: VIA Labs, Inc.
[Fr Aug 18 12:29:52 2023] usb 4-1: SerialNumber: 000000001
[Fr Aug 18 12:29:52 2023] usb 4-1: Device is not authorized for usage
[Fr Aug 18 12:29:53 2023] usb 3-1: authorized to connect
[Fr Aug 18 12:29:53 2023] hub 4-1:1.0: USB hub found
[Fr Aug 18 12:29:53 2023] hub 4-1:1.0: 4 ports detected
[Fr Aug 18 12:29:53 2023] usb 4-1: authorized to connect
[Fr Aug 18 12:29:53 2023] usb 3-1.4: new high-speed USB device number 3 using xhci-hcd
[Fr Aug 18 12:29:54 2023] usb 3-1.4: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[Fr Aug 18 12:29:54 2023] usb 3-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Fr Aug 18 12:29:54 2023] usb 3-1.4: Product: USB 2.0 Hub
[Fr Aug 18 12:29:54 2023] usb 3-1.4: Device is not authorized for usage
[Fr Aug 18 12:29:54 2023] imx-sdma 30bd0000.dma-controller: restart cyclic channel 3
[Fr Aug 18 12:29:54 2023] hub 3-1.4:1.0: USB hub found
[Fr Aug 18 12:29:54 2023] hub 3-1.4:1.0: 4 ports detected
[Fr Aug 18 12:29:54 2023] usb 3-1.4: authorized to connect
[Fr Aug 18 12:29:54 2023] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[Fr Aug 18 12:29:54 2023] usb 4-1.1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[Fr Aug 18 12:29:54 2023] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[Fr Aug 18 12:29:54 2023] usb 4-1.1: Product: USB 10/100/1000 LAN
[Fr Aug 18 12:29:54 2023] usb 4-1.1: Manufacturer: Realtek
[Fr Aug 18 12:29:54 2023] usb 4-1.1: SerialNumber: 000001000000
[Fr Aug 18 12:29:54 2023] r8152-cfgselector 4-1.1: Device is not authorized for usage
[Fr Aug 18 12:29:54 2023] imx-sdma 30bd0000.dma-controller: restart cyclic channel 3
[Fr Aug 18 12:29:54 2023] r8152-cfgselector 4-1.1: authorized to connect
[Fr Aug 18 12:29:54 2023] usb 3-1.4.1: new low-speed USB device number 4 using xhci-hcd
[Fr Aug 18 12:29:54 2023] usb 3-1.4.1: New USB device found, idVendor=099a, idProduct=7202, bcdDevice= 0.06
[Fr Aug 18 12:29:54 2023] usb 3-1.4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[Fr Aug 18 12:29:54 2023] usb 3-1.4.1: Product: Wireless Keyboard/Mouse
[Fr Aug 18 12:29:54 2023] usb 3-1.4.1: Device is not authorized for usage
[Fr Aug 18 12:29:54 2023] input: Wireless Keyboard/Mouse as /devices/platform/soc@0/38100000.usb/xhci-hcd.5.auto/usb3/3-1/3-1.4/3-1.4.1/3-1.4.1:1.0/0003:099A:7202.0015/input/input49
[Fr Aug 18 12:29:55 2023] hid-generic 0003:099A:7202.0015: input,hidraw0: USB HID v1.11 Keyboard [Wireless Keyboard/Mouse] on usb-xhci-hcd.5.auto-1.4.1/input0
[Fr Aug 18 12:29:55 2023] input: Wireless Keyboard/Mouse as /devices/platform/soc@0/38100000.usb/xhci-hcd.5.auto/usb3/3-1/3-1.4/3-1.4.1/3-1.4.1:1.1/0003:099A:7202.0016/input/input50
[Fr Aug 18 12:29:55 2023] input: Wireless Keyboard/Mouse Consumer Control as /devices/platform/soc@0/38100000.usb/xhci-hcd.5.auto/usb3/3-1/3-1.4/3-1.4.1/3-1.4.1:1.1/0003:099A:7202.0016/input/input51
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: new high-speed USB device number 5 using xhci-hcd
[Fr Aug 18 12:29:55 2023] hid-generic 0003:099A:7202.0016: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Wireless Keyboard/Mouse] on usb-xhci-hcd.5.auto-1.4.1/input1
[Fr Aug 18 12:29:55 2023] usb 3-1.4.1: authorized to connect
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: New USB device found, idVendor=05e3, idProduct=0751, bcdDevice=14.04
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: New USB device strings: Mfr=3, Product=4, SerialNumber=0
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: Product: USB Storage
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: Manufacturer: USB Storage
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: Device is not authorized for usage
[Fr Aug 18 12:29:55 2023] imx-sdma 30bd0000.dma-controller: restart cyclic channel 3
[Fr Aug 18 12:29:55 2023] usb-storage 3-1.4.3:1.0: USB Mass Storage device detected
[Fr Aug 18 12:29:55 2023] scsi host1: usb-storage 3-1.4.3:1.0
[Fr Aug 18 12:29:55 2023] usb 3-1.4.3: authorized to connect
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: new high-speed USB device number 6 using xhci-hcd
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: New USB device found, idVendor=05e3, idProduct=0751, bcdDevice=14.04
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: New USB device strings: Mfr=3, Product=4, SerialNumber=0
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: Product: USB Storage
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: Manufacturer: USB Storage
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: Device is not authorized for usage
[Fr Aug 18 12:29:55 2023] usb-storage 3-1.4.4:1.0: USB Mass Storage device detected
[Fr Aug 18 12:29:55 2023] scsi host2: usb-storage 3-1.4.4:1.0
[Fr Aug 18 12:29:55 2023] usb 3-1.4.4: authorized to connect
[Fr Aug 18 12:29:56 2023] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 1404 PQ: 0 ANSI: 6
[Fr Aug 18 12:29:56 2023] sd 1:0:0:0: [sdb] Media removed, stopped polling
[Fr Aug 18 12:29:56 2023] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[Fr Aug 18 12:29:56 2023] scsi 2:0:0:0: Direct-Access Generic STORAGE DEVICE 1404 PQ: 0 ANSI: 6
[Fr Aug 18 12:29:57 2023] sd 2:0:0:0: [sdc] Media removed, stopped polling
[Fr Aug 18 12:29:57 2023] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[Fr Aug 18 12:30:35 2023] edt_ft5x06 2-0038: Unable to fetch data, error: -6
```
While the dock is still connected the ethernet adapter can be resurrected by unloading and reloading its kernel module(s):
```
root@pureos:~# dmesg -W -T &
root@pureos:~# rmmod r8153_ecm r8152
[Fr Aug 18 12:38:18 2023] usbcore: deregistering interface driver r8153_ecm
[Fr Aug 18 12:38:18 2023] usbcore: deregistering interface driver r8152
[Fr Aug 18 12:38:18 2023] usbcore: deregistering device driver r8152-cfgselector
root@pureos:~# modprobe r8152
[Fr Aug 18 12:38:40 2023] usbcore: registered new device driver r8152-cfgselector
[Fr Aug 18 12:38:40 2023] r8152-cfgselector 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[Fr Aug 18 12:38:40 2023] r8152 4-1.1:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2
[Fr Aug 18 12:38:40 2023] r8152 4-1.1:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2)
[Fr Aug 18 12:38:40 2023] r8152 4-1.1:1.0 eth0: v1.12.13
[Fr Aug 18 12:38:40 2023] usbcore: registered new interface driver r8152
root@pureos:~# [Fr Aug 18 12:38:40 2023] usbcore: registered new interface driver r8153_ecm
[Fr Aug 18 12:38:41 2023] r8152 4-1.1:1.0 enxXXXXXXXXXX: renamed from eth0
```https://source.puri.sm/Librem5/image-builder/-/issues/70PureOS Fails to boot after flashed to SD card2023-08-18T16:58:34ZAlistairPureOS Fails to boot after flashed to SD cardI have a Librem5 currently running u-boot 2022.10 and pmOS.
After downloading plain (no LUKS) image from https://storage.puri.sm/librem5/images I run the following to flash it to an SD card
```shell
unxz ./librem5r4.img.xz
sudo dd if=....I have a Librem5 currently running u-boot 2022.10 and pmOS.
After downloading plain (no LUKS) image from https://storage.puri.sm/librem5/images I run the following to flash it to an SD card
```shell
unxz ./librem5r4.img.xz
sudo dd if=./librem5r4.img of=/dev/sdb bs=4M iflag=fullblock oflag=direct conv=fsync status=progress
```
I can then boot the image by holding volume down while powering on the Librem5.
I see the boot splash from PureOS, but it never completes the boot. I can then press the power down button and I see the log attached:
![IMG-2663](/uploads/34e49e098cbfb59d57f6813f03b6d58a/IMG-2663.jpg)
pmOS doesn't use systemd, so the PureOS rootFS is clearly being mounted, but it doesn't work correctly.
I have tried a range of different images yet still nothing works. I have tried both LUKS and plain images, from Jenkins and older PureOS releases. It's a brand new SD card, so it shouldn't be failing either.https://source.puri.sm/Librem5/geary/-/issues/27Undo delete pop-up blocks back button2023-08-28T16:25:00ZLee RiemenschneiderUndo delete pop-up blocks back buttonWhen deleting mail in the list view, the message about undoing the delete blocks the back button at the top of the view. This results in an annoying delay, before being allowed to go back to e.g., the mailboxes view.When deleting mail in the list view, the message about undoing the delete blocks the back button at the top of the view. This results in an annoying delay, before being allowed to go back to e.g., the mailboxes view.https://source.puri.sm/Librem5/librem5-flash-image/-/issues/15Need to verify that the downloaded u-boot file is correct size and has correc...2023-08-08T17:22:00ZAmos BattoNeed to verify that the downloaded u-boot file is correct size and has correct SHA256 checksumThe code of the librem5-flash-image/scripts/librem5_flash_image.py script verifies that the downloaded image file is the correct size in bytes and its SHA256 hashing checksum is correct. However, it doesn’t verify whether the downloaded ...The code of the librem5-flash-image/scripts/librem5_flash_image.py script verifies that the downloaded image file is the correct size in bytes and its SHA256 hashing checksum is correct. However, it doesn’t verify whether the downloaded u-boot file is correct. From a security point of view, the u-boot file is arguably just as important as the image.https://source.puri.sm/Librem5/linux/-/issues/490Kernel crash after ending phone call resulting in black screen2023-08-17T15:31:33ZGuido GuntherKernel crash after ending phone call resulting in black screen```
Aug 07 20:12:42 nn kernel: ------------[ cut here ]------------
Aug 07 20:12:42 nn kernel: NETDEV WATCHDOG: wwan0 (qmi_wwan): transmit queue 0 timed out
Aug 07 20:12:42 nn kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:525...```
Aug 07 20:12:42 nn kernel: ------------[ cut here ]------------
Aug 07 20:12:42 nn kernel: NETDEV WATCHDOG: wwan0 (qmi_wwan): transmit queue 0 timed out
Aug 07 20:12:42 nn kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x280/0x2a0
Aug 07 20:12:42 nn pulseaudio[904]: Playback too far ahead (46145), drop source 8856
Aug 07 20:12:43 nn kernel: Modules linked in: aes_ce_ccm uinput rfcomm algif_hash algif_skcipher af_alg bnep redpine_sdio redpine_91x bluetooth mac80211 cfg80211 usb_f_acm u_serial usb_f_ncm u_ether st_magn_i2c>
Aug 07 20:12:43 nn kernel: led_class_multicolor nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcomposite nf_tables libcrc32c ledtrig_timer nfnetlink fuse zram ip_tables x_tables ip>
Aug 07 20:12:43 nn kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -110
Aug 07 20:12:43 nn kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.3.0-1-librem5 #1
Aug 07 20:12:43 nn kernel: Hardware name: Purism Librem 5r4 (DT)
Aug 07 20:12:43 nn kernel: pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Aug 07 20:12:43 nn kernel: pc : dev_watchdog+0x280/0x2a0
Aug 07 20:12:43 nn kernel: imx-pgc imx-pgc-domain.5: failed to enable regulator: -ETIMEDOUT
Aug 07 20:12:43 nn kernel: lr : dev_watchdog+0x280/0x2a0
Aug 07 20:12:43 nn kernel: sp : ffff800008003e00
Aug 07 20:12:43 nn kernel: x29: ffff800008003e00 x28: ffff800009641d00 x27: 0000000000000002
Aug 07 20:12:43 nn kernel: x26: ffff8000096389e0 x25: ffff8000096389e0 x24: ffff8000092a9008
Aug 07 20:12:43 nn kernel: x23: ffff800009636000 x22: 0000000000000000 x21: ffff000006fe43dc
Aug 07 20:12:43 nn kernel: x20: ffff000006fe4000 x19: ffff000006fe4488 x18: 0000000000000000
Aug 07 20:12:43 nn kernel: x17: ffff8000b0ac1000 x16: ffff800008000000 x15: 0000000000000030
Aug 07 20:12:43 nn kernel: x14: 0000000000000000 x13: 74756f2064656d69 x12: 7420302065756575
Aug 07 20:12:43 nn kernel: x11: 00000000ffffdfff x10: 00000000ffffdfff x9 : ffff800008197f64
Aug 07 20:12:43 nn kernel: x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 0000000000017ff4
Aug 07 20:12:43 nn kernel: x5 : 0000000000000000 x4 : ffff0000b9d6ba08 x3 : ffff0000b9d77f30
Aug 07 20:12:43 nn kernel: x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff800009641d00
Aug 07 20:12:43 nn kernel: Call trace:
Aug 07 20:12:43 nn kernel: dev_watchdog+0x280/0x2a0
Aug 07 20:12:43 nn kernel: call_timer_fn+0x3c/0x1d0
Aug 07 20:12:43 nn kernel: expire_timers+0xcc/0x190
Aug 07 20:12:43 nn kernel: run_timer_softirq+0xfc/0x268
Aug 07 20:12:43 nn kernel: ------------[ cut here ]------------
Aug 07 20:12:43 nn kernel: __do_softirq+0x118/0x3a4
Aug 07 20:12:43 nn kernel: [CRTC:33:crtc-0] vblank wait timed out
Aug 07 20:12:43 nn kernel: ____do_softirq+0x18/0x30
Aug 07 20:12:43 nn kernel: call_on_irq_stack+0x24/0x58
Aug 07 20:12:43 nn kernel: WARNING: CPU: 3 PID: 6754 at drivers/gpu/drm/drm_atomic_helper.c:1618 drm_atomic_helper_wait_for_vblanks.part.0+0x280/0x2b0
Aug 07 20:12:43 nn kernel: do_softirq_own_stack+0x24/0x38
Aug 07 20:12:43 nn kernel: Modules linked in:
Aug 07 20:12:43 nn kernel: __irq_exit_rcu+0xac/0xf0
Aug 07 20:12:43 nn kernel: aes_ce_ccm
Aug 07 20:12:43 nn kernel: irq_exit_rcu+0x18/0x30
Aug 07 20:12:43 nn kernel: uinput
```
The effect is that blank/unblank still turns backlight on/off but the display stays dark. pgc 5 is the GPU power domain IIRC.https://source.puri.sm/Librem5/millipixels/-/issues/88Pipewire: Switching to front camera produces a Segmentation Fault and camera ...2023-08-02T21:51:16ZChris TalbotPipewire: Switching to front camera produces a Segmentation Fault and camera not available until reboot - L5From: https://salsa.debian.org/Mobian-team/packages/millipixels/-/issues/1
In L5 with Mobian staging and Trixie with kernel 6.1 or 6.4 and pipewire, opening Millipixels and switching to the front camera produces a segmentation fault and...From: https://salsa.debian.org/Mobian-team/packages/millipixels/-/issues/1
In L5 with Mobian staging and Trixie with kernel 6.1 or 6.4 and pipewire, opening Millipixels and switching to the front camera produces a segmentation fault and the camera is disabled until restart the phone.
The output from the console is shown in the picture below.
![millipixels_error_L5](/uploads/d6ba9a3a9a0eb3f42cca5286a57a9921/millipixels_error_L5.png)https://source.puri.sm/Librem5/OS-issues/-/issues/329Mobile Data automatically enabled (after reboot?)2023-08-16T13:16:23ZJan VlugMobile Data automatically enabled (after reboot?)I disabled the Mobile Data in Settings. After a reboot I noticed that it was enabled again.
Normally, I never disable Mobile Data, but because I'm abroad now, and Mobile Data is expensive, I disabled Mobile Data.
I'm not sure if there re...I disabled the Mobile Data in Settings. After a reboot I noticed that it was enabled again.
Normally, I never disable Mobile Data, but because I'm abroad now, and Mobile Data is expensive, I disabled Mobile Data.
I'm not sure if there really has been traffic over the Mobile Data connection.https://source.puri.sm/Librem5/millipixels/-/issues/87Mobian/Trixie: Saving/postprocessing does something strange with pictures2023-08-08T12:52:52ZChris TalbotMobian/Trixie: Saving/postprocessing does something strange with picturesHello!
When I upgraded to Trixie, saving pictures looks like it is broken with Millipixels.
The actual images in preview are fine. The thumbnail looks correct too:
![Screenshot_from_2023-07-23_10-56-28](/uploads/c96d7c2cc2bb500ba244f...Hello!
When I upgraded to Trixie, saving pictures looks like it is broken with Millipixels.
The actual images in preview are fine. The thumbnail looks correct too:
![Screenshot_from_2023-07-23_10-56-28](/uploads/c96d7c2cc2bb500ba244f3cd51fb3701/Screenshot_from_2023-07-23_10-56-28.png)
However, the dng images look like the following:
![Screenshot_2023-07-23_10-53-23](/uploads/0b8105a2b9c2b8ad9fdaeed7cf40053f/Screenshot_2023-07-23_10-53-23.jpg)
The outputted jpg looks like below:
![Screenshot_2023-07-23_10-28-18](/uploads/8d545e78b8998104768f987167294781/Screenshot_2023-07-23_10-28-18.png)https://source.puri.sm/Librem5/millipixels/-/issues/86Allow to select a custom directories for saving photos and videos2023-07-24T15:42:40ZJan VlugAllow to select a custom directories for saving photos and videosSuggestion: Allow to select a custom directories for saving photos and videos.
I've been using my Librem 5 as a daily driver for over a year. One of the most pressing issues nowadays is the continuous lack of space on the root partition...Suggestion: Allow to select a custom directories for saving photos and videos.
I've been using my Librem 5 as a daily driver for over a year. One of the most pressing issues nowadays is the continuous lack of space on the root partition. It would be a great improvement if I could save photos and videos in a custom directory on my largely unused micro SD card.
See also this discussion on the [forums](https://forums.puri.sm/t/millipixels-can-i-set-a-custom-directory-for-photos-and-videos/20887).
As a side note: Saving photos in the home directory of the user is also not what I expect, ~/Pictures or something like that seems more logical as a default to me.https://source.puri.sm/Librem5/librem5-base/-/issues/74Use Debian's mobile-tweaks2023-07-18T12:40:43ZGuido GuntherUse Debian's mobile-tweaksDebian's mobile-tweaks has device specific changes. E.g. `librem5-tweaks`. Basing on that would help us unclutter librem5-base and would also make PureOS approachable for people that want to use it on other devices.Debian's mobile-tweaks has device specific changes. E.g. `librem5-tweaks`. Basing on that would help us unclutter librem5-base and would also make PureOS approachable for people that want to use it on other devices.https://source.puri.sm/Librem5/zephyr/-/issues/3d/rules: use the proper debhelper cmake build instead of overrides2023-07-11T14:57:41ZMartin Kepplingerd/rules: use the proper debhelper cmake build instead of overridesinstead of calling cmake and ninja ourselves, It should be possible to do it the "dh" way and just define the variables.instead of calling cmake and ninja ourselves, It should be possible to do it the "dh" way and just define the variables.