OS-issues issueshttps://source.puri.sm/Librem5/OS-issues/-/issues2024-03-13T11:02:48Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/328Mobile data stops working, outgoing packets still sent but incoming packets n...2024-03-13T11:02:48ZElias RudbergMobile data stops working, outgoing packets still sent but incoming packets no longer arriveLibrem 5 running PureOS.
It happens quite often (maybe about once a day on average) that the mobile data connection suddenly stops working, while calls and SMS still work.
Mobile data seems to stop working while it is being used, for e...Librem 5 running PureOS.
It happens quite often (maybe about once a day on average) that the mobile data connection suddenly stops working, while calls and SMS still work.
Mobile data seems to stop working while it is being used, for example today I was playing a video clip on a web page in Firefox and that video suddenly stopped playing, because mobile data had stopped working.
Trying to find out what goes wrong I have looked at `mmcli -m any` and also `mmcli -m any -b x` with x being bearer number, and things look normal there. As far as I can tell there is no error indication anywhere. Also `nmcli con show` shows the connection as working, and `ip route` and `ip addr` output looks normal, it looks the same as when things are working. So both ModemManager and NetworkManager seem to think that everything is fine. But things are not fine, I can no longer communicate using the mobile data connection.
Trying to ping something in the outside world fails, but when I tried pinging my own server I could see the ping request packets from the Librem 5 arriving at the server, and the server sent an echo reply packet back each time. So in this situation the Librem 5 can send ping request packets, but the replies to not arrive. So the mobile data connection is not totally broken, it works in the outgoing direction but not in the incoming direction.
Trying to ping the gateway IP also fails. (Pinging the phone's own IP works though.)
Doing `mmcli -m any --reset` followed by `service NetworkManager restart` makes things work again.
Ideas on how to troubleshoot this further? One thing that would be interesting it to get some more low-level info from the kernel driver(s) involved, to see if there is any activity at all when incoming packets arrive.
Could it be related to suspend functionality?https://source.puri.sm/Librem5/OS-issues/-/issues/327Prepare crimson - package updates2023-06-21T21:39:42ZEvangelos Ribeiro TzarasPrepare crimson - package updatesThere are a number of packages we need to unblock things.
The [depcheck](http://master.scratch.pureos.net/depcheck/pureos/landing/binary/amd64/1) list should be empty :)
We have a number of patched packages (mostly L5 team), and the...There are a number of packages we need to unblock things.
The [depcheck](http://master.scratch.pureos.net/depcheck/pureos/landing/binary/amd64/1) list should be empty :)
We have a number of patched packages (mostly L5 team), and the team should handle those (or at least evaluate which patches are still needed - if any).
/cc @matthias.klumpp @carsten.schoenerthttps://source.puri.sm/Librem5/OS-issues/-/issues/325Cell Broadcast (CBS) is according to bm818-tool always disabled after restart2023-05-29T14:20:52ZJan VlugCell Broadcast (CBS) is according to bm818-tool always disabled after restartSteps to reproduce:
1. Enable CBS in bm818-tool
2. Exit the bm818-tool
3. Shut down the Librem 5
4. Start the Librem 5
5. Open the bm818-tool
Actual behavior:
bm818-tool shows that CBS is disabled.
Expected behavior:
bm818-tool shows t...Steps to reproduce:
1. Enable CBS in bm818-tool
2. Exit the bm818-tool
3. Shut down the Librem 5
4. Start the Librem 5
5. Open the bm818-tool
Actual behavior:
bm818-tool shows that CBS is disabled.
Expected behavior:
bm818-tool shows that CBS is enabled.https://source.puri.sm/Librem5/OS-issues/-/issues/324L5 goes into suspend w/o any warning message2023-05-18T16:05:16ZMatthias ApitzL5 goes into suspend w/o any warning messageWhen suspend is configured, the L5 goes into suspend mode w/o any warning message short before. For example, when you type some stuff, and one has to think about the words, then it is when the screen goes off.
This seems to be a regress...When suspend is configured, the L5 goes into suspend mode w/o any warning message short before. For example, when you type some stuff, and one has to think about the words, then it is when the screen goes off.
This seems to be a regression, because I saw such warning before.https://source.puri.sm/Librem5/OS-issues/-/issues/323Unable to send SMS on 4G with VoLTE enabled2023-06-17T13:39:30ZJan VlugUnable to send SMS on 4G with VoLTE enabledI cannot send SMS messages any more with Chatty. This used to work fine in the past.
I see this in the logging when sending an SMS message:
```
May 10 20:24:47 avalon mmsdtng[840]: ../plugins/modemmanager.c:cb_dbus_signal_sms_added() Go...I cannot send SMS messages any more with Chatty. This used to work fine in the past.
I see this in the logging when sending an SMS message:
```
May 10 20:24:47 avalon mmsdtng[840]: ../plugins/modemmanager.c:cb_dbus_signal_sms_added() Got new SMS
May 10 20:24:47 avalon mmsdtng[840]: ../plugins/modemmanager.c:mmsd_check_pdu_type() This is not an SMS being received, do not care
```
Because I had to send an important message, I put the SIM-card back in my Android phone, where sending worked fine.
What could be wrong? How can I get more details on what goes wrong?
Receiving SMS messages still works fine.
Another interesting observation is that there appears a little red cross after approximately 25 seconds next to the SMS messages. So, somehow Chatty knows that something went wrong. But I do not know how to get any additional information, like an error message. In the logging is nothing else than the lines above.
Now I’m thinking of it, the issue of not being able to send SMS messages might have started after a modem firmware update that I did a while ago. But it might also be totally unrelated, it is just a hypothesis.
See also [this forum post](https://forums.puri.sm/t/sending-sms-messages-stopped-working-how-to-debug/20233/3).
Chatty version: 0.7.2-1pureos1https://source.puri.sm/Librem5/OS-issues/-/issues/322Cannot install dbgsym packages2023-06-01T14:55:34ZElias RudbergCannot install dbgsym packagesI added a `/etc/apt/sources.list.d/debug.list` file as described in https://source.puri.sm/Librem5/developer.puri.sm/-/issues/181 hoping that this would let me install *-dbgsym packages with debug symbols, to see more useful info from st...I added a `/etc/apt/sources.list.d/debug.list` file as described in https://source.puri.sm/Librem5/developer.puri.sm/-/issues/181 hoping that this would let me install *-dbgsym packages with debug symbols, to see more useful info from stack traces, coredumps etc.
So my /etc/apt/sources.list.d/debug.list file looks as follows:
```
root@pureos:~# cat /etc/apt/sources.list.d/debug.list
deb https://repo.pureos.net/pureos-debug/ byzantium-debug main
deb https://repo.pureos.net/pureos-debug/ landing-debug main
deb http://debug.mirrors.debian.org/debian-debug/ bullseye-debug main
```
and I ran `apt update` after adding that file.
But it does not work; there are *-dbgsym packages, but trying to install them fails due to dependency problems.
Example:
```
root@pureos:~# apt install modemmanager-dbgsym
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
modemmanager-dbgsym : Depends: modemmanager (= 1.18.6-1pureos4) but 1.18.6-1pureos3 is to be installed
E: Unable to correct problems, you have held broken packages.
root@pureos:~#
```
There are two variants of the package:
```
root@pureos:~# apt list -a modemmanager-dbgsym
Listing... Done
modemmanager-dbgsym/landing-debug 1.18.6-1pureos4 arm64
modemmanager-dbgsym/stable-debug 1.14.12-0.2 arm64
```
But neither of them can be installed:
```
root@pureos:~# apt install modemmanager-dbgsym/landing-debug
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '1.18.6-1pureos4' (PureOS Debug:landing-debug [arm64]) for 'modemmanager-dbgsym'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
modemmanager-dbgsym : Depends: modemmanager (= 1.18.6-1pureos4) but 1.18.6-1pureos3 is to be installed
E: Unable to correct problems, you have held broken packages.
```
```
root@pureos:~# apt install modemmanager-dbgsym/stable-debug
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '1.14.12-0.2' (Debian debug:11.7/stable-debug [arm64]) for 'modemmanager-dbgsym'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
modemmanager-dbgsym : Depends: modemmanager (= 1.14.12-0.2) but 1.18.6-1pureos3 is to be installed
E: Unable to correct problems, you have held broken packages.
root@pureos:~#
```
What to do, how to make this work?https://source.puri.sm/Librem5/OS-issues/-/issues/321package m4 core firmware for PureOS2023-05-09T15:00:05ZMartin Kepplingerpackage m4 core firmware for PureOSI think we need a Debian binary package that includes the (zephyr-built) m4 firmware and installs it to /lib/firmware. And make sure the licensing is correct, sources available and so on. (not sure how a source-package would look like). ...I think we need a Debian binary package that includes the (zephyr-built) m4 firmware and installs it to /lib/firmware. And make sure the licensing is correct, sources available and so on. (not sure how a source-package would look like). I'd keep it as simple as possible.https://source.puri.sm/Librem5/OS-issues/-/issues/320Make all apps adhere to users feedback level choice2023-04-17T09:11:49ZJan VlugMake all apps adhere to users feedback level choiceI have Signal installed as a flatpak. When I set the notification profile of the L5 to silent or quiet, the L5 still plays a sound when a Signal notification appears.
Probably related to: https://github.com/flatpak/xdg-desktop-portal/is...I have Signal installed as a flatpak. When I set the notification profile of the L5 to silent or quiet, the L5 still plays a sound when a Signal notification appears.
Probably related to: https://github.com/flatpak/xdg-desktop-portal/issues/929
EDIT (by guido): I've moved that here since it's not feedbackd specific and add the gist to the description:
Applications that have the pulseaudiosocket or access to the alsa device can play sound. To make apps not become noisy in silent mode:
- Flatpaked: Don't expose the pulseaudio socket by default and use feedbackd. For apps that don't want to change this could be done transparently by wrapping libcanberra/gsound or similar
- non-flatpaked apps have so many ways that it would have to be done on a per app basis (e.g. app armor profile) and also a wrap
- migrating to feedbackd API is IMHO preferred. Work on the portal would be good for that to make it transparent for app developers
/cc @agx
/cc @julian.sparber as it would affect runtimeshttps://source.puri.sm/Librem5/OS-issues/-/issues/318losing mobile data connection while idle2023-10-12T09:08:18ZMartin Kepplingerlosing mobile data connection while idleI left the phone lying around - only enabled and disabled wifi a few times. On 17:05 I noted that "mobile data is still working". Next time I checked it was not working anymore. Here's the default journal logs only for now. I wanted to c...I left the phone lying around - only enabled and disabled wifi a few times. On 17:05 I noted that "mobile data is still working". Next time I checked it was not working anymore. Here's the default journal logs only for now. I wanted to create this issue because this is happening on a regular basis. The modem itself can still communicate! In this case, placing a call worked still. Only no mobile data anymore:
```
Mär 26 17:05:24 pureos NetworkManager[448]: <info> [1679843124.5035] manager: rfkill: Wi-Fi now disabled by radio killswitch
Mär 26 17:05:24 pureos NetworkManager[448]: <info> [1679843124.5186] device (wlan0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Mär 26 17:05:24 pureos NetworkManager[448]: <info> [1679843124.5525] dhcp4 (wlan0): canceled DHCP transaction
Mär 26 17:05:24 pureos NetworkManager[448]: <info> [1679843124.5539] dhcp4 (wlan0): state changed bound -> terminated
Mär 26 17:05:24 pureos NetworkManager[448]: <info> [1679843124.5825] dhcp6 (wlan0): canceled DHCP transaction
Mär 26 17:05:24 pureos NetworkManager[448]: <info> [1679843124.5890] dhcp6 (wlan0): state changed bound -> terminated
Mär 26 17:05:24 pureos kernel: brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
Mär 26 17:05:24 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mär 26 17:05:24 pureos systemd-logind[471]: Power key pressed.
Mär 26 17:05:24 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mär 26 17:05:24 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mär 26 17:05:24 pureos kernel: brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-110
Mär 26 17:05:24 pureos kernel: brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_cfg80211_get_channel: chanspec failed (-110)
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_fil_cmd_data: bus is down. we have nothing to do.
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_cfg80211_get_tx_power: error (-5)
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_fil_cmd_data: bus is down. we have nothing to do.
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_cfg80211_disconnect: error (-5)
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_fil_cmd_data: bus is down. we have nothing to do.
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: send_key_to_dongle: wsec_key error (-5)
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: brcmf_fil_cmd_data: bus is down. we have nothing to do.
Mär 26 17:05:24 pureos kernel: ieee80211 phy2: send_key_to_dongle: wsec_key error (-5)
Mär 26 17:05:24 pureos wpa_supplicant[488]: wlan0: CTRL-EVENT-DISCONNECTED bssid=78:d2:94:52:25:d0 reason=3 locally_generated=1
Mär 26 17:05:25 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:05:25 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:05:25 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 17:05:25 pureos avahi-daemon[443]: Interface wlan0.IPv6 no longer relevant for mDNS.
Mär 26 17:05:25 pureos systemd-networkd[347]: wlan0: Link DOWN
Mär 26 17:05:25 pureos avahi-daemon[443]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fdbe:c468:7df7:0:3c12:a84e:4c4c:75fe.
Mär 26 17:05:25 pureos systemd-networkd[347]: wlan0: Lost carrier
Mär 26 17:05:25 pureos avahi-daemon[443]: Interface wlan0.IPv4 no longer relevant for mDNS.
Mär 26 17:05:25 pureos avahi-daemon[443]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.18.
Mär 26 17:05:25 pureos avahi-daemon[443]: Withdrawing address record for fdbe:c468:7df7::5bb on wlan0.
Mär 26 17:05:25 pureos avahi-daemon[443]: Withdrawing address record for fdbe:c468:7df7:0:3c12:a84e:4c4c:75fe on wlan0.
Mär 26 17:05:25 pureos avahi-daemon[443]: Withdrawing address record for 192.168.1.18 on wlan0.
Mär 26 17:05:25 pureos kernel: brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -123
Mär 26 17:05:25 pureos kernel: brcmfmac: brcmf_sdio_bus_stop: Failed to force clock for F2: err -123
Mär 26 17:05:25 pureos NetworkManager[448]: <info> [1679843125.3187] policy: set '0677-web' (wwan0) as default for IPv4 routing and DNS
Mär 26 17:05:25 pureos NetworkManager[448]: <info> [1679843125.3482] radio killswitch /sys/devices/platform/soc@0/30800000.bus/30b50000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy2/rfkill6 disappeared
Mär 26 17:05:25 pureos kernel: brcmfmac_cyw: brcmf_cyw_detach: executing
Mär 26 17:05:25 pureos NetworkManager[448]: <info> [1679843125.3603] device (wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Mär 26 17:05:25 pureos NetworkManager[448]: <info> [1679843125.3700] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Mär 26 17:05:25 pureos dbus-daemon[446]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=448 comm="/usr/sbin/NetworkManager --no-daemon ")
Mär 26 17:05:25 pureos kernel: mmc1: card 0001 removed
Mär 26 17:05:25 pureos wpa_supplicant[488]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Mär 26 17:05:25 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
Mär 26 17:05:25 pureos dbus-daemon[446]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mär 26 17:05:25 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
Mär 26 17:05:27 pureos phoc[586]: [libinput] event3 - EP0700M09: client bug: event processing lagging behind by 13ms, your system is too slow
Mär 26 17:05:28 pureos phoc[586]: [libinput] event3 - EP0700M09: client bug: event processing lagging behind by 12ms, your system is too slow
Mär 26 17:05:30 pureos systemd[1]: systemd-rfkill.service: Succeeded.
Mär 26 17:05:35 pureos systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mär 26 17:05:36 pureos systemd-logind[471]: Power key pressed.
Mär 26 17:05:36 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Mär 26 17:05:37 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:05:37 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:05:38 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 17:15:29 pureos systemd-logind[471]: Power key pressed.
Mär 26 17:15:29 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:15:29 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:15:29 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 17:15:31 pureos systemd-logind[471]: Power key pressed.
Mär 26 17:15:31 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Mär 26 17:15:31 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:15:31 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 17:15:31 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 17:17:01 pureos CRON[8703]: pam_unix(cron:account): account root has expired (account expired)
Mär 26 17:17:01 pureos CRON[8703]: Fehler bei Authentifizierung
Mär 26 17:17:01 pureos cron[8703]: Fehler bei Authentifizierung
Mär 26 17:31:59 pureos Tor[570]: Your system clock just jumped 3613 seconds forward; assuming established circuits no longer work.
Mär 26 17:32:49 pureos systemd-timesyncd[415]: Timed out waiting for reply from [2001:858:2:4:887d:c7ff:fef8:d02d]:123 (2.debian.pool.ntp.org).
Mär 26 17:32:59 pureos systemd-timesyncd[415]: Timed out waiting for reply from [2a02:1748:0:1500:3::2005]:123 (2.debian.pool.ntp.org).
Mär 26 17:33:09 pureos systemd-timesyncd[415]: Timed out waiting for reply from [2a00:63c1:13:217::2]:123 (2.debian.pool.ntp.org).
Mär 26 17:33:20 pureos systemd-timesyncd[415]: Timed out waiting for reply from [2a02:60:1:500::149]:123 (2.debian.pool.ntp.org).
Mär 26 17:33:30 pureos systemd-timesyncd[415]: Timed out waiting for reply from 151.236.30.71:123 (2.debian.pool.ntp.org).
Mär 26 17:33:40 pureos systemd-timesyncd[415]: Timed out waiting for reply from 86.59.80.170:123 (2.debian.pool.ntp.org).
Mär 26 17:33:50 pureos systemd-timesyncd[415]: Timed out waiting for reply from 85.237.30.84:123 (2.debian.pool.ntp.org).
Mär 26 17:34:01 pureos systemd-timesyncd[415]: Timed out waiting for reply from 91.206.8.36:123 (2.debian.pool.ntp.org).
Mär 26 18:10:30 pureos systemd[1]: Starting Daily apt download activities...
Mär 26 18:10:49 pureos systemd[1]: apt-daily.service: Succeeded.
Mär 26 18:10:49 pureos systemd[1]: Finished Daily apt download activities.
Mär 26 18:10:49 pureos systemd[1]: apt-daily.service: Consumed 17.973s CPU time.
Mär 26 18:14:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:14:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:15:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:15:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:15:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:15:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:15:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:15:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:16:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:17:01 pureos CRON[9039]: pam_unix(cron:account): account root has expired (account expired)
Mär 26 18:17:01 pureos CRON[9039]: Fehler bei Authentifizierung
Mär 26 18:17:01 pureos cron[9039]: Fehler bei Authentifizierung
Mär 26 18:17:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:17:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:17:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:17:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:17:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:17:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:18:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:18:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:18:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:18:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:18:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:18:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:19:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:19:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:19:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:19:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:19:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:19:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:20:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:20:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:20:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:20:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:20:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:20:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:21:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:22:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:22:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:22:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:22:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:22:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:22:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:23:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:23:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:23:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:23:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:23:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:23:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:24:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:24:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:24:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:24:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:24:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:24:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:25:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:25:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:25:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:25:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:25:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:25:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:26:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:27:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:27:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:27:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:27:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:27:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:27:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:28:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:28:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:28:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:28:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:28:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:28:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:29:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:29:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:29:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:29:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:29:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:29:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:30:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:30:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:30:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:30:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:30:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:30:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:31:59 pureos Tor[570]: Tor has been idle for 3600 seconds; assuming established circuits no longer work.
Mär 26 18:32:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:32:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:32:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:32:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:32:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:32:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:33:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:33:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:33:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:33:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:33:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:33:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:34:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:34:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:34:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:34:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:34:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:34:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:35:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:35:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:35:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:35:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:35:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:35:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:36:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:37:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:37:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:37:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:37:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:37:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:37:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:38:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:38:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:38:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:38:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:38:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:38:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:39:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:39:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:39:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:39:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:39:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:39:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:40:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:40:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:40:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:40:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:40:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:40:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:41:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:42:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:42:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:42:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:42:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:42:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:42:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:43:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:43:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:43:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:43:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:43:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:43:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:44:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:44:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:44:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:44:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:44:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:44:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:45:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:45:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:45:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:45:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:45:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:45:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:46:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:47:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:47:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:47:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:47:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:47:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:47:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:48:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:48:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:48:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:48:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:48:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:48:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:49:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:49:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:49:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:49:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:49:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:49:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:50:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:50:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:50:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:50:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:50:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:50:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:51:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:18 pureos systemd-logind[471]: Power key pressed.
Mär 26 18:52:19 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 18:52:19 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 18:52:19 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:52:46 pureos phoc[586]: [libinput] event3 - EP0700M09: client bug: event processing lagging behind by 17ms, your system is too slow
Mär 26 18:52:48 pureos dbus-daemon[726]: [session uid=1000 pid=726] Activating service name='org.gnome.zbrown.KingsCross' requested by ':1.29' (uid=1000 pid=907 comm="/usr/libexec/phosh ")
Mär 26 18:52:49 pureos dbus-daemon[726]: [session uid=1000 pid=726] Successfully activated service 'org.gnome.zbrown.KingsCross'
Mär 26 18:52:49 pureos systemd[677]: Started VTE child process 9303 launched by org.gnome.zbrown.KingsCross process 9291.
Mär 26 18:52:50 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:52:50 pureos sm.puri.OSK0.desktop[1119]: Warning: Failed to load layout from Resource: terminal/de: Missing resource, skipping
Mär 26 18:52:50 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:52:50 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: terminal/us
Mär 26 18:53:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:53:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:53:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:53:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:53:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:53:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:53:37 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:37 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: de
Mär 26 18:53:39 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:39 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: de
Mär 26 18:53:47 pureos phoc[586]: [libinput] event3 - EP0700M09: client bug: event processing lagging behind by 11ms, your system is too slow
Mär 26 18:53:49 pureos dbus-daemon[726]: [session uid=1000 pid=726] Activating service name='org.gnome.Weather' requested by ':1.29' (uid=1000 pid=907 comm="/usr/libexec/phosh ")
Mär 26 18:53:49 pureos dbus-daemon[726]: [session uid=1000 pid=726] Successfully activated service 'org.gnome.Weather'
Mär 26 18:53:52 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:52 pureos sm.puri.OSK0.desktop[1119]: Warning: Failed to load layout from Resource: terminal/de: Missing resource, skipping
Mär 26 18:53:52 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:52 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: terminal/us
Mär 26 18:53:53 pureos org.gnome.Weath[9390]: JS LOG: Timeout during model load, perhaps the network is not available?
Mär 26 18:53:53 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:53 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: de
Mär 26 18:53:56 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:56 pureos sm.puri.OSK0.desktop[1119]: Warning: Failed to load layout from Resource: terminal/de: Missing resource, skipping
Mär 26 18:53:56 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:53:56 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: terminal/us
Mär 26 18:54:03 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:54:03 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: de
Mär 26 18:54:07 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/de.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:54:07 pureos sm.puri.OSK0.desktop[1119]: Warning: Failed to load layout from Resource: terminal/de: Missing resource, skipping
Mär 26 18:54:07 pureos sm.puri.OSK0.desktop[1119]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: Datei oder Verzeichnis nicht gefunden (os error 2)
Mär 26 18:54:07 pureos sm.puri.OSK0.desktop[1119]: Info: Loaded layout Resource: terminal/us
Mär 26 18:54:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:54:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:54:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:54:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:54:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:54:14 pureos systemd[1]: Starting Load/Save RF Kill Switch Status...
Mär 26 18:54:14 pureos systemd[1]: Started Load/Save RF Kill Switch Status.
Mär 26 18:54:14 pureos NetworkManager[448]: <info> [1679849654.6997] manager: rfkill: Wi-Fi now enabled by radio killswitch
Mär 26 18:54:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:54:15 pureos kernel: mmc1: new ultra high speed SDR104 SDIO card at address 0001
Mär 26 18:54:15 pureos kernel: brcmfmac: F1 signature read @0x18000000=0x1042aae8
Mär 26 18:54:15 pureos kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
Mär 26 18:54:15 pureos kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43752-sdio.purism,librem5r4.bin failed with error -2
Mär 26 18:54:15 pureos systemd[1]: Started Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:15 pureos btattach[9455]: Failed to set protocol: Protocol not supported
Mär 26 18:54:15 pureos btattach[9455]: No controller attached
Mär 26 18:54:15 pureos btattach[9455]: Attaching Primary controller to /dev/ttymxc3
Mär 26 18:54:15 pureos btattach[9455]: Switched line discipline from 0 to 15
Mär 26 18:54:15 pureos systemd[1]: brcmfmac-bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Mär 26 18:54:15 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:15 pureos systemd[1]: Started Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:15 pureos btattach[9458]: Failed to set protocol: Protocol not supported
Mär 26 18:54:15 pureos btattach[9458]: No controller attached
Mär 26 18:54:15 pureos btattach[9458]: Attaching Primary controller to /dev/ttymxc3
Mär 26 18:54:15 pureos btattach[9458]: Switched line discipline from 0 to 15
Mär 26 18:54:15 pureos systemd[1]: brcmfmac-bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Mär 26 18:54:15 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:15 pureos systemd[1]: Started Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:15 pureos btattach[9459]: Failed to set protocol: Protocol not supported
Mär 26 18:54:15 pureos btattach[9459]: No controller attached
Mär 26 18:54:15 pureos btattach[9459]: Attaching Primary controller to /dev/ttymxc3
Mär 26 18:54:15 pureos btattach[9459]: Switched line discipline from 0 to 15
Mär 26 18:54:15 pureos systemd[1]: brcmfmac-bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Mär 26 18:54:15 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:15 pureos kernel: brcmfmac_cyw: brcmf_cyw_attach: executing
Mär 26 18:54:16 pureos kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
Mär 26 18:54:16 pureos systemd[1]: Started Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:16 pureos btattach[9461]: Failed to set protocol: Protocol not supported
Mär 26 18:54:16 pureos btattach[9461]: No controller attached
Mär 26 18:54:16 pureos btattach[9461]: Attaching Primary controller to /dev/ttymxc3
Mär 26 18:54:16 pureos btattach[9461]: Switched line discipline from 0 to 15
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:16 pureos systemd-udevd[9451]: Using default interface naming scheme 'v247'.
Mär 26 18:54:16 pureos systemd[1]: Started Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:16 pureos btattach[9464]: Failed to set protocol: Protocol not supported
Mär 26 18:54:16 pureos systemd-udevd[9451]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mär 26 18:54:16 pureos systemd-timesyncd[415]: Network configuration changed, trying to establish connection.
Mär 26 18:54:16 pureos NetworkManager[448]: <info> [1679849656.1672] device (wlan0): driver supports Access Point (AP) mode
Mär 26 18:54:16 pureos NetworkManager[448]: <info> [1679849656.1692] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/10)
Mär 26 18:54:16 pureos btattach[9464]: No controller attached
Mär 26 18:54:16 pureos btattach[9464]: Attaching Primary controller to /dev/ttymxc3
Mär 26 18:54:16 pureos btattach[9464]: Switched line discipline from 0 to 15
Mär 26 18:54:16 pureos NetworkManager[448]: <info> [1679849656.1741] rfkill7: found Wi-Fi radio killswitch (at /sys/devices/platform/soc@0/30800000.bus/30b50000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy3/rfkill7) (driver brcmfmac)
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Start request repeated too quickly.
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:16 pureos systemd[1]: Failed to start Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:16 pureos NetworkManager[448]: <info> [1679849656.2292] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mär 26 18:54:16 pureos systemd[1]: Condition check resulted in Bluetooth attachment for brcmfmac driver being skipped.
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Start request repeated too quickly.
Mär 26 18:54:16 pureos systemd[1]: brcmfmac-bluetooth.service: Failed with result 'exit-code'.
Mär 26 18:54:16 pureos systemd[1]: Failed to start Start btattach, needed to enable Bluetooth for brcmfmac.
Mär 26 18:54:16 pureos systemd-networkd[347]: wlan0: Link UP
Mär 26 18:54:16 pureos systemd-networkd[347]: wlan0: Link DOWN
Mär 26 18:54:16 pureos NetworkManager[448]: <info> [1679849656.8179] device (wlan0): set-hw-addr: set MAC address to A2:EF:45:00:5A:AA (scanning)
Mär 26 18:54:16 pureos systemd-networkd[347]: wlan0: Link UP
Mär 26 18:54:18 pureos kernel: ieee80211 phy3: brcmf_p2p_create_p2pdev: timeout occurred
Mär 26 18:54:18 pureos kernel: ieee80211 phy3: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
Mär 26 18:54:18 pureos wpa_supplicant[488]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error)
Mär 26 18:54:18 pureos wpa_supplicant[488]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0
Mär 26 18:54:18 pureos wpa_supplicant[488]: P2P: Failed to enable P2P Device interface
Mär 26 18:54:18 pureos wpa_supplicant[488]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4740] device (wlan0): supplicant interface state: internal-starting -> disconnected
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4744] Wi-Fi P2P device controlled by interface wlan0 created
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4759] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/11)
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4775] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4807] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4854] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4980] device (wlan0): supplicant interface state: disconnected -> scanning
Mär 26 18:54:18 pureos NetworkManager[448]: <info> [1679849658.4982] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Mär 26 18:54:18 pureos wpa_supplicant[488]: wlan0: Reject scan trigger since one is already pending
Mär 26 18:54:18 pureos NetworkManager[448]: <warn> [1679849658.5386] sup-iface[6c328fab05d54673,3,wlan0]: call-p2p-cancel: failed with P2P cancel failed
Mär 26 18:54:18 pureos ModemManager[548]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/soc@0/30800000.bus/30b50000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1': not supported by any plugin
Mär 26 18:54:21 pureos systemd[1]: systemd-rfkill.service: Succeeded.
Mär 26 18:54:21 pureos NetworkManager[448]: <info> [1679849661.5595] device (wlan0): supplicant interface state: scanning -> disconnected
Mär 26 18:54:21 pureos NetworkManager[448]: <info> [1679849661.5612] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
Mär 26 18:54:21 pureos NetworkManager[448]: <info> [1679849661.5720] policy: auto-activating connection 'Internet' (1220cb6b-8dd5-49bd-94b8-8ed0b3d6a6d3)
Mär 26 18:54:21 pureos NetworkManager[448]: <info> [1679849661.5752] device (wlan0): Activation: starting connection 'Internet' (1220cb6b-8dd5-49bd-94b8-8ed0b3d6a6d3)
Mär 26 18:54:21 pureos NetworkManager[448]: <info> [1679849661.5769] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:22 pureos systemd-networkd[347]: wlan0: Link DOWN
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.0992] device (wlan0): set-hw-addr: reset MAC address to 10:2C:6B:99:5E:68 (preserve)
Mär 26 18:54:22 pureos systemd-networkd[347]: wlan0: Link UP
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1030] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1044] device (wlan0): Activation: (wifi) access point 'Internet' has security, but secrets are required.
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1048] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1154] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1155] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1342] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1372] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1401] device (wlan0): Activation: (wifi) connection 'Internet' has security, and secrets exist. No new secrets needed.
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1453] Config: added 'ssid' value 'Internet'
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1454] Config: added 'scan_ssid' value '1'
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1454] Config: added 'bgscan' value 'simple:30:-70:86400'
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1456] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1456] Config: added 'auth_alg' value 'OPEN'
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1456] Config: added 'psk' value '<hidden>'
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1554] device (wlan0): supplicant interface state: interface_disabled -> inactive
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1555] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1822] device (wlan0): supplicant interface state: inactive -> scanning
Mär 26 18:54:22 pureos NetworkManager[448]: <info> [1679849662.1823] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Mär 26 18:54:25 pureos wpa_supplicant[488]: wlan0: Trying to associate with SSID 'Internet'
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.2501] device (wlan0): supplicant interface state: scanning -> associating
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.2502] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Mär 26 18:54:25 pureos wpa_supplicant[488]: wlan0: Associated with 78:d2:94:52:25:d0
Mär 26 18:54:25 pureos wpa_supplicant[488]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mär 26 18:54:25 pureos wpa_supplicant[488]: wlan0: WPA: Key negotiation completed with 78:d2:94:52:25:d0 [PTK=CCMP GTK=CCMP]
Mär 26 18:54:25 pureos wpa_supplicant[488]: wlan0: CTRL-EVENT-CONNECTED - Connection to 78:d2:94:52:25:d0 completed [id=0 id_str=]
Mär 26 18:54:25 pureos systemd-networkd[347]: wlan0: Gained carrier
Mär 26 18:54:25 pureos kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.4538] device (wlan0): supplicant interface state: associating -> completed
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.4540] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Internet"
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.4541] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.4570] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:25 pureos systemd-networkd[347]: wlan0: Connected WiFi access point: Internet (78:d2:94:52:25:d0)
Mär 26 18:54:25 pureos NetworkManager[448]: <info> [1679849665.4649] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mär 26 18:54:25 pureos avahi-daemon[443]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::721b:917a:2d5e:cd79.
Mär 26 18:54:25 pureos avahi-daemon[443]: New relevant interface wlan0.IPv6 for mDNS.
Mär 26 18:54:25 pureos avahi-daemon[443]: Registering new address record for fe80::721b:917a:2d5e:cd79 on wlan0.*.
Mär 26 18:54:26 pureos systemd-networkd[347]: wlan0: Gained IPv6LL
Mär 26 18:54:26 pureos NetworkManager[448]: <info> [1679849666.7999] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mär 26 18:54:26 pureos avahi-daemon[443]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::721b:917a:2d5e:cd79.
Mär 26 18:54:26 pureos avahi-daemon[443]: Joining mDNS multicast group on interface wlan0.IPv6 with address fdbe:c468:7df7:0:3c12:a84e:4c4c:75fe.
Mär 26 18:54:26 pureos avahi-daemon[443]: Registering new address record for fdbe:c468:7df7:0:3c12:a84e:4c4c:75fe on wlan0.*.
Mär 26 18:54:26 pureos avahi-daemon[443]: Withdrawing address record for fe80::721b:917a:2d5e:cd79 on wlan0.
Mär 26 18:54:26 pureos NetworkManager[448]: <info> [1679849666.8093] dhcp6 (wlan0): state changed unknown -> bound, address=fdbe:c468:7df7::5bb
Mär 26 18:54:26 pureos avahi-daemon[443]: Registering new address record for fdbe:c468:7df7::5bb on wlan0.*.
Mär 26 18:54:26 pureos dbus-daemon[446]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=448 comm="/usr/sbin/NetworkManager --no-daemon ")
Mär 26 18:54:26 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
Mär 26 18:54:26 pureos dbus-daemon[446]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mär 26 18:54:26 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
Mär 26 18:54:27 pureos NetworkManager[448]: <info> [1679849667.5077] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.1.18
Mär 26 18:54:27 pureos avahi-daemon[443]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.18.
Mär 26 18:54:27 pureos avahi-daemon[443]: New relevant interface wlan0.IPv4 for mDNS.
Mär 26 18:54:27 pureos avahi-daemon[443]: Registering new address record for 192.168.1.18 on wlan0.IPv4.
Mär 26 18:54:27 pureos NetworkManager[448]: <info> [1679849667.5210] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:27 pureos NetworkManager[448]: <info> [1679849667.5407] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:27 pureos NetworkManager[448]: <info> [1679849667.5417] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mär 26 18:54:27 pureos NetworkManager[448]: <info> [1679849667.5494] policy: set 'Internet' (wlan0) as default for IPv4 routing and DNS
Mär 26 18:54:27 pureos NetworkManager[448]: <info> [1679849667.5578] device (wlan0): Activation: successful, device activated.
Mär 26 18:54:28 pureos PackageKit[1310]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Mär 26 18:54:28 pureos PackageKit[1310]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Mär 26 18:54:31 pureos PackageKit[1310]: refresh-cache transaction /2060_ceaeddeb from uid 1000 finished with success after 2893ms
Mär 26 18:54:31 pureos PackageKit[1310]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Mär 26 18:54:31 pureos PackageKit[1310]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Mär 26 18:54:36 pureos PackageKit[1310]: refresh-cache transaction /2061_bebecbea from uid 1000 finished with success after 5517ms
Mär 26 18:54:36 pureos PackageKit[1310]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Mär 26 18:54:36 pureos PackageKit[1310]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Mär 26 18:54:37 pureos systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mär 26 18:54:42 pureos PackageKit[1310]: refresh-cache transaction /2062_dcbbedca from uid 1000 finished with success after 5606ms
Mär 26 18:54:56 pureos systemd-timesyncd[415]: Initial synchronization to time server 178.251.64.52:123 (1.debian.pool.ntp.org).
Mär 26 18:55:01 pureos geoclue[1091]: Failed to query location: Error resolving “location.services.mozilla.com”: Der Name oder der Dienst ist nicht bekannt
Mär 26 18:55:08 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Mär 26 18:55:08 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 18:55:08 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 18:55:08 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:55:15 pureos rtkit-daemon[728]: Supervising 10 threads of 4 processes of 1 users.
Mär 26 18:55:15 pureos rtkit-daemon[728]: Supervising 10 threads of 4 processes of 1 users.
Mär 26 18:56:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:16 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:56:35 pureos sshd[10369]: Accepted password for purism from 192.168.1.228 port 37486 ssh2
Mär 26 18:56:35 pureos sshd[10369]: pam_unix(sshd:session): session opened for user purism(uid=1000) by (uid=0)
Mär 26 18:56:36 pureos systemd-logind[471]: New session 7 of user purism.
Mär 26 18:56:36 pureos systemd[1]: Started Session 7 of user purism.
Mär 26 18:57:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:57:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:57:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:57:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:57:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:57:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:58:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:58:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:58:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:58:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:58:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:58:15 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:12 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:13 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:14 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:27 pureos systemd-logind[471]: Power key pressed.
Mär 26 18:59:27 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 18:59:27 pureos gsd-xsettings[1014]: Failed to get current UI legacy scaling factor
Mär 26 18:59:27 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:27 pureos phosh-session[10409]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Mär 26 18:59:27 pureos phosh-session[10409]: > Warning: Unsupported maximum keycode 569, clipping.
Mär 26 18:59:27 pureos phosh-session[10409]: > X11 cannot support keycodes above 255.
Mär 26 18:59:27 pureos phosh-session[10409]: Errors from xkbcomp are not fatal to the X server
Mär 26 18:59:33 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mär 26 18:59:34 pureos gsd-color[991]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
```https://source.puri.sm/Librem5/OS-issues/-/issues/316Prefer IPv4 over IPv62023-08-16T14:55:20ZSebastian KrzyszkowiakPrefer IPv4 over IPv6Even though WiFi is given priority over mobile data (see #130), people can still fall under opposite impression when WiFi connection provides IPv4 only and mobile connection does IPv6, in which case anything that happens to be resolved o...Even though WiFi is given priority over mobile data (see #130), people can still fall under opposite impression when WiFi connection provides IPv4 only and mobile connection does IPv6, in which case anything that happens to be resolved over IPv6 will use mobile connection even if IPv4 address is also available and could be used over WiFi.
Adding `precedence ::ffff:0:0/96 100` to `/etc/gai.conf` (belonging to package `libc-bin`) is supposed to make getaddrinfo prefer IPv4 over IPV6.https://source.puri.sm/Librem5/OS-issues/-/issues/315Please provide an adaptive screenshot GUI2023-06-02T18:04:33ZGuido GuntherPlease provide an adaptive screenshot GUIScreenshots in the default setup are more complicated than need be as it either needs command line or l5-goodies which then can't copy to the clipboard right away. https://source.puri.sm/guido.gunther/gnome-screenshot makes gnome-screens...Screenshots in the default setup are more complicated than need be as it either needs command line or l5-goodies which then can't copy to the clipboard right away. https://source.puri.sm/guido.gunther/gnome-screenshot makes gnome-screenshot adaptive so could help in that situation.https://source.puri.sm/Librem5/OS-issues/-/issues/314Coredump in plymouthd2023-01-21T10:50:19ZJan VlugCoredump in plymouthdWhen running `coredumpctl` I see several `plymouthd` coredumps:
```
# coredumpctl
TIME PID UID GID SIG COREFILE EXE
Tue 2023-01-10 10:28:26 CET 275 0 0 6 missing /usr/sbin/plymouthd
Tue 202...When running `coredumpctl` I see several `plymouthd` coredumps:
```
# coredumpctl
TIME PID UID GID SIG COREFILE EXE
Tue 2023-01-10 10:28:26 CET 275 0 0 6 missing /usr/sbin/plymouthd
Tue 2023-01-10 16:53:46 CET 1404 1000 1000 6 missing /usr/bin/gnome-calls
Sun 2023-01-15 13:00:58 CET 26768 1000 1000 6 missing /app/bin/zypak-helper
Mon 2023-01-16 09:15:25 CET 1445 1000 1000 6 missing /usr/bin/gnome-calls
Tue 2023-01-17 14:30:20 CET 1470 1000 1000 6 missing /usr/bin/gnome-calls
Tue 2023-01-17 16:20:37 CET 10874 1000 1000 6 missing /usr/bin/gnome-calls
Wed 2023-01-18 10:25:32 CET 255 0 0 6 missing /usr/sbin/plymouthd
Wed 2023-01-18 11:06:44 CET 1554 1000 1000 6 missing /usr/bin/gnome-calls
Thu 2023-01-19 14:33:56 CET 250 0 0 6 missing /usr/sbin/plymouthd
Fri 2023-01-20 12:13:26 CET 3636 1000 1000 5 missing /usr/libexec/tracker-store
Fri 2023-01-20 12:18:22 CET 277 0 0 6 missing /usr/sbin/plymouthd
Sat 2023-01-21 10:48:22 CET 250 0 0 6 present /usr/sbin/plymouthd
```
I think the coredump happens for each boot.
Here is the output of `coredumpctl info`: [plymouthd-coredump-info.txt](/uploads/b6edc827991980cc52ecee2bbc54cdee/plymouthd-coredump-info.txt)https://source.puri.sm/Librem5/OS-issues/-/issues/313Please build PureOS with frame pointers2023-06-01T14:54:25ZGuido GuntherPlease build PureOS with frame pointersWanted to file this since some time but lwn has an article now that reminded me: https://lwn.net/Articles/919940/, fedora's discussion: https://lwn.net/ml/fedora-devel/CA+voJeXhBPph9R2nzV9UCiMOU4Tpo0s0NtA26HcJccTwFad25w@mail.gmail.com/ ....Wanted to file this since some time but lwn has an article now that reminded me: https://lwn.net/Articles/919940/, fedora's discussion: https://lwn.net/ml/fedora-devel/CA+voJeXhBPph9R2nzV9UCiMOU4Tpo0s0NtA26HcJccTwFad25w@mail.gmail.com/ . It simplifies system tracing and profiling a lot as e.g. sysprof can work out of the box. There is a performance cost but I think the usefulness compensates for that.
This would be good to do from crimson onward especially if PureOS starts rebuilding compoinents that come from Debian.
I didn't file at tracker.pureos.net as that looks dormant.
@matthias.klumpp we could pass those on via dpkg's buildflags by default from crimson on.https://source.puri.sm/Librem5/OS-issues/-/issues/312Bad audio quality during call2023-03-21T13:27:56ZJan VlugBad audio quality during callI called someone. The first time they could not hear me at all, the second time, I heard an echo of myself, and the other end complained about the bad audio quality.
I noticed that the phone kept the 4G icon in the status bar, but did h...I called someone. The first time they could not hear me at all, the second time, I heard an echo of myself, and the other end complained about the bad audio quality.
I noticed that the phone kept the 4G icon in the status bar, but did have the exclamation mark in the mobile connection icon (see https://source.puri.sm/Librem5/linux/-/issues/454).
Here is the log file: [bad_audio_quality_during_call.log](/uploads/c46ca3332e785f1e8653266dab69b469/bad_audio_quality_during_call.log)
Note these lines in the log (from `cat bad_audio_quality_during_call.log | grep -i audio`):
```
Jan 06 16:11:22 avalon pulseaudio[867]: Configured maximum latency is smaller than latency, using latency instead
Jan 06 16:11:23 avalon pulseaudio[867]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:11:23 avalon pulseaudio[867]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:11:39 avalon pulseaudio[867]: Configured maximum latency is smaller than latency, using latency instead
Jan 06 16:11:39 avalon pulseaudio[867]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:11:39 avalon pulseaudio[867]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:11:39 avalon pulseaudio[867]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:11:39 avalon pulseaudio[867]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:11:39 avalon pulseaudio[867]: Doing resync
Jan 06 16:11:39 avalon pulseaudio[867]: Playback too far ahead (9907), drop source 1900
Jan 06 16:11:40 avalon pulseaudio[867]: Playback too far ahead (8990), drop source 1724
Jan 06 16:11:41 avalon pulseaudio[867]: Playback too far ahead (10065), drop source 1932
Jan 06 16:11:42 avalon pulseaudio[867]: Playback too far ahead (10344), drop source 1984
Jan 06 16:11:43 avalon pulseaudio[867]: Playback too far ahead (10195), drop source 1956
Jan 06 16:11:44 avalon pulseaudio[867]: Playback too far ahead (9790), drop source 1876
Jan 06 16:11:45 avalon pulseaudio[867]: Playback too far ahead (10049), drop source 1928
Jan 06 16:11:46 avalon pulseaudio[867]: Playback too far ahead (10050), drop source 1928
Jan 06 16:11:47 avalon pulseaudio[867]: Playback too far ahead (9900), drop source 1900
Jan 06 16:11:48 avalon pulseaudio[867]: Playback too far ahead (9926), drop source 1904
Jan 06 16:11:49 avalon pulseaudio[867]: Playback too far ahead (10239), drop source 1964
Jan 06 16:11:50 avalon pulseaudio[867]: Playback too far ahead (9945), drop source 1908
Jan 06 16:11:51 avalon pulseaudio[867]: Playback too far ahead (10370), drop source 1988
Jan 06 16:11:52 avalon pulseaudio[867]: Playback too far ahead (9632), drop source 1848
Jan 06 16:11:53 avalon pulseaudio[867]: Playback too far ahead (10115), drop source 1940
Jan 06 16:11:54 avalon pulseaudio[867]: Playback too far ahead (10179), drop source 1952
Jan 06 16:12:05 avalon pulseaudio[867]: Configured maximum latency is smaller than latency, using latency instead
Jan 06 16:12:05 avalon pulseaudio[867]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:12:05 avalon pulseaudio[867]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:12:11 avalon pulseaudio[867]: Configured maximum latency is smaller than latency, using latency instead
Jan 06 16:12:11 avalon pulseaudio[867]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:12:11 avalon pulseaudio[867]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:12:11 avalon pulseaudio[867]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:12:11 avalon pulseaudio[867]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 06 16:12:11 avalon pulseaudio[867]: Doing resync
Jan 06 16:12:11 avalon pulseaudio[867]: Playback after capture (-5410), drop sink 2152
Jan 06 16:12:12 avalon pulseaudio[867]: Playback after capture (-822), drop sink 392
```
See also [this forum item](https://forums.puri.sm/t/audio-defaults-to-speaker-built-in-audio-on-reboot/18829/11?u=janvlug).https://source.puri.sm/Librem5/OS-issues/-/issues/311Secondary call disconnecting kills audio on established/primary call2023-04-12T10:01:22ZEvangelos Ribeiro TzarasSecondary call disconnecting kills audio on established/primary callCurrently calls will autoreject secondary calls, because it does not implement [call waiting](https://gitlab.gnome.org/GNOME/calls/-/issues/209) yet.
Once the second call gets disconnected the audio for the existing call is broken (both...Currently calls will autoreject secondary calls, because it does not implement [call waiting](https://gitlab.gnome.org/GNOME/calls/-/issues/209) yet.
Once the second call gets disconnected the audio for the existing call is broken (both from and to the network).
Note that the broken audio is **not** due to calls autorejecting the call: Even if the call get's disconnected from the caller audio gets broken but is still fine **while** ringing.
Some observations:
- Audio continues to works just fine on the PinePhone when the second
- I've disabled auto hangup in calls to test if it makes any difference who hangs up on the second call: Audio also dies if the caller hangs up.
- I tried using older MM (`1.14.12-0.2pureos1`) which did not use QMI voice call management to see if that makes any difference, but any additional call gets routed to voicemail irrespective of the call waiting status.
- Once the second call is disconnected the modem audio card does not produce any more audio samples. When running `parecord` on the modems audio card: The instant the second call is disconnected the recording **stops** (as opposed to continuing but recording silence).
As the modem audio simply stops it would point to an issue with the modem (firmware), but another opinion or ideas about how to further narrow it down would be welcome /cc @angus.ainslie @sebastian.krzyszkowiak @martin.kepplinger
## Workaround
A possible workaround would be to `mmcli -m any --voice-disable-call-waiting`. In this case extra calls go straight to voicemail (or rejected as "busy") and I get notified of the missed call by SMS from my network operator.
We could disable call waiting entirely in Calls for the time being to prevent audio getting killed.https://source.puri.sm/Librem5/OS-issues/-/issues/309Programs like Calls are allowed to crash silently without any journalctl erro...2023-01-09T09:39:35ZElias RudbergPrograms like Calls are allowed to crash silently without any journalctl error messageUntil now, I have been assuming that if a program crashes (segmentation fault, assertion failure or similar), then there would always be some kind of error message in the `journalctl` log saying that something crashed. Now, to my surpris...Until now, I have been assuming that if a program crashes (segmentation fault, assertion failure or similar), then there would always be some kind of error message in the `journalctl` log saying that something crashed. Now, to my surprise, I found that it seems programs can crash without anything being logged about it.
The example below is about the Calls program `gnome-calls` which handles phone calls, but I think there is a more general issue to consider here, the way programs are run, there should be ways of configuring things so that an error message is logged whenever there is a crash.
I think that when `systemd-coredump` is installed, there will always be something logged for each crash, but that package is not installed by default.
Here is an example of what `journalctl` shows when Calls crashed on a Librem 5 that did not have `systemd-coredump` installed, so this is default behavior:
```
Jan 06 12:17:15 pureos pulseaudio[822]: Playback too far ahead (9959), drop source 1912
Jan 06 12:17:16 pureos pulseaudio[822]: Playback too far ahead (9986), drop source 1916
Jan 06 12:17:17 pureos pulseaudio[822]: Playback too far ahead (9892), drop source 1896
Jan 06 12:17:18 pureos pulseaudio[822]: Playback too far ahead (10183), drop source 1952
Jan 06 12:17:19 pureos ModemManager[768]: <info> [modem0/call3] call state changed: active -> terminated (unknown)
Jan 06 12:17:30 pureos dbus-daemon[826]: [session uid=1000 pid=826] Activating service name='org.gnome.Contacts' requested by ':1.207' (uid=1000 pid=4433 comm="gnome-calls ")
Jan 06 12:17:30 pureos dbus-daemon[826]: [session uid=1000 pid=826] Successfully activated service 'org.gnome.Contacts'
Jan 06 12:17:30 pureos gnome-session[963]: gnome-session-binary[963]: WARNING: App 'org.gnome.Calls-daemon.desktop' respawning too quickly
Jan 06 12:17:30 pureos gnome-session-binary[963]: WARNING: App 'org.gnome.Calls-daemon.desktop' respawning too quickly
Jan 06 12:17:30 pureos gnome-session[963]: gnome-session-binary[963]: WARNING: Error on restarting session managed app: Component 'org.gnome.Calls-daemon.desktop' crashing too quickly
Jan 06 12:17:30 pureos gnome-session-binary[963]: WARNING: Error on restarting session managed app: Component 'org.gnome.Calls-daemon.desktop' crashing too quickly
```
In that case there was an ongoing phonecall resulting in some pulseaudio log entries, then ModemManager notes that the call was terminated and dbus-daemon says something about Contacts. Nothing of that indicates any error. Then comes a line saying "respawning too quickly" which I think is because Calls has crashed, but there is nothing logged about the crash itself. Maybe Calls crashed several times in a short timespan, causing the "respawning too quickly" message. Then there is also a line saying Calls was "crashing too quickly".
It does not sound good that something is "crashing too quickly", I think there should be an error message each time something crashed, regardless of how quickly it was. Presumably there may have been many other crashes about which there is nothing at all logged, because those crashes did not happen in quick succession.
I suspect that a lot of issues with various kinds of weird behavior on the Librem 5 may be related to programs having crashed silently in this way. At least for me, troubleshooting when something strange happened involves looking at what `journalctl` says at the time of the problem. If something has crashed then that is very important information, troubleshooting will be much easier if all crashes are logged.
So, it would seem like a good idea to change the way programs are run such that silent crashes are no longer allowed, so that something is seen in the log each time a program has crashed. In case of Calls I think the file `/etc/xdg/autostart/org.gnome.Calls-daemon.desktop` may have something to do with this, but I'm not sure. That file has lines saying things like `Exec=gnome-calls --daemon` and `X-GNOME-AutoRestart=true`, perhaps it is possible to control error logging behavior from there?
Another suggestion is to have `systemd-coredump` installed by default, or at least to recommend installing that as a standard troubleshooting step. Or maybe there are better ways to make crashes visible.https://source.puri.sm/Librem5/OS-issues/-/issues/308Incoming call switches and leaves mobile data from 4G to 3G (according to ico...2022-12-27T11:42:50ZJan VlugIncoming call switches and leaves mobile data from 4G to 3G (according to icon in status bar)I had the Librem 5 up and running with a 4G mobile data connection (according to the status bar icon).
I received a call, and I saw an exclamation mark in the mobile data icon, and the 4G icon changed into a 3G icon.
After the call, th...I had the Librem 5 up and running with a 4G mobile data connection (according to the status bar icon).
I received a call, and I saw an exclamation mark in the mobile data icon, and the 4G icon changed into a 3G icon.
After the call, the exclamation mark disappeared after a while, but the connection stayed in 3G (according to the icon in the status bar).
This might be related to the fact that my provider does not support MMS. See [this bug in mobile-broadband-provider-info](https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info/-/issues/14).
Here are two log files. In this first one the call came in and the mobile data connection changed from 4G to 3G. There are some comments in the log file too:
[back_to_3G.log](/uploads/8b7c3bba996675f94be374a7006e0288/back_to_3G.log)
This is the log file of when I changed the mobile data settings a bit in GNOME Settings, and in the end got the 4G connection icon back.
[mobile_settings_changed.log](/uploads/374a73fa13494f110eff1d413a2c7c21/mobile_settings_changed.log)
The above described issue is a description from the user perspective. I would not be surprised if there are actually a few separate issues that cause this behavior, like:
* phone switching back to 3G on incoming call
* modem not switching back to 4G after call
* incorrect handling of providers that do not support MMS
* incorrect representation of mobile data state in GNOME settings
* incorrect representation of mobile data state in status bar
Please let me know when you need any more additional information or testing.
Edit: After closing and opening GNOME settings, I saw that the mobile settings were indeed changed in GNOME settings. So it seems that they are not correctly refreshed.https://source.puri.sm/Librem5/OS-issues/-/issues/306Rescue system (jumpdrive), chroot, luks and kernel updates2023-02-23T22:13:34ZPirate PraveenRescue system (jumpdrive), chroot, luks and kernel updatesCurrently jumpdrive provides a rescue system via usb-c cable (and telnet from a laptop), if the phone does not boot. This allows us to chroot into the phone and fix any issues. But jumpdrive does not support luks yet and this reported up...Currently jumpdrive provides a rescue system via usb-c cable (and telnet from a laptop), if the phone does not boot. This allows us to chroot into the phone and fix any issues. But jumpdrive does not support luks yet and this reported upstream https://github.com/dreemurrs-embedded/Jumpdrive/issues/79. Alternative option is to use qemu on the laptop to get a chroot environment on the phone as jumpdrive shares the emmc as a block device and this allows us to use luks support on the laptop to get a chroot.
This brings up the issue of flash-kernel failing if the kernel package is updated or reinstalled via chroot (details in the issue linked above). Though on mobian the kernel updates works in the chroot also because it does not use flash-kernel and it expects uboot to be handled independently, for example using tow boot.
So I was wondering if pureos should also consider this approach for crimson. Do you think it is reasonable expectation to be able to update a kernel using a chroot (just with the storage device and not connected with the phone)? Also it may be beneficial to everyone if pureos and mobian follows a common approach to bootloader. May be pureos is targeting only Librem 5 right now, do you plan to support pinephone or other devices with pureos? Answer to this question may decide if it is worthwhile to follow the tow boot approach here.https://source.puri.sm/Librem5/OS-issues/-/issues/305Limit journalctl log size on Librem 52024-02-14T20:21:42ZJoao AzevedoLimit journalctl log size on Librem 5Because it can take quite an amount of space in the L5 storage unit.
We use the defaults for Journalctl from upstream Debian, which for many use cases use larger storage units.
With the Librem 5 we have 32GB emmc.
We have had report...Because it can take quite an amount of space in the L5 storage unit.
We use the defaults for Journalctl from upstream Debian, which for many use cases use larger storage units.
With the Librem 5 we have 32GB emmc.
We have had reports of users with journalctl logs when unchecked, and using the current defaults, taking 2,9GB and in some cases 4GB of storage space. making in some cases more than 10% of the storage unit occupied with logs.
Some users have resorted to: `sudo journalctl --vacuum-size=200M` to reclaim storage space.
**suggestion:** Limit by defaults log to 500MB - 1GB, as it can still provide data from previous days/week, to prevent too much storage space to be filled on a L5.https://source.puri.sm/Librem5/OS-issues/-/issues/304Implement org.freedesktop.ScreenSaver2022-12-11T13:19:34ZDorota CzaplejewiczImplement org.freedesktop.ScreenSaverThe Phosh session exposes 2 dbus services for the screen saver, with differing behaviour (see https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/355#note_1613814 ).
However, both services expose pretty much identical functionalit...The Phosh session exposes 2 dbus services for the screen saver, with differing behaviour (see https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/355#note_1613814 ).
However, both services expose pretty much identical functionality, compare: https://lists.freedesktop.org/archives/xdg/2006-June/006523.html and https://lists.freedesktop.org/archives/xdg/2007-March/009187.html .
The "freedesktop" service seems to be dead.
This means that applications binding to the general (freedesktop) one first will successfuly find it and try to use it, but will not actually be connected to any behaviour they expected.
Filing in os-issues because I don't know better.