OS-issues issueshttps://source.puri.sm/Librem5/OS-issues/-/issues2024-01-26T10:03:24Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/346Road to crimson2024-01-26T10:03:24ZGuido GuntherRoad to crimsonAs discussed with @evangelos.tzaras let's have a meta issue (this only lists the things still todo, not all the things that have already been done):
- [ ] Switch image build to debos (https://source.puri.sm/pureos/infra/pureos-image-rec...As discussed with @evangelos.tzaras let's have a meta issue (this only lists the things still todo, not all the things that have already been done):
- [ ] Switch image build to debos (https://source.puri.sm/pureos/infra/pureos-image-recipes/-/merge_requests/2)
- [ ] Continuously build *recent* unencrypted images using debos (replacine [our vmdebootstrap ones for landing](https://arm01.puri.sm/job/Images/job/Image%20Builds%20landing/))
- [ ] complete gtk3 patches (https://source.puri.sm/Librem5/debs/gtk/-/issues/38)
- [ ] Use u-boot via deb (from there on we can deprecate arm01)
- [ ] crimson artwork (https://source.puri.sm/Librem5/OS-issues/-/issues/334)
- [ ] backport core libs
- [ ] [gtk 1.12](https://source.puri.sm/Librem5/debs/gtk4/-/issues/9)
- [ ] [libadwaita 1.4](https://source.puri.sm/Librem5/debs/libadwaita/-/issues/1)
- [ ] wlroots 0.17.0 (no issue yet)
- [ ] Sort out pulseaudio vs pipewire
- [ ] pipewire echo cancellation
- [ ] continuously build encrypted images too
- [ ] here we could release an alpha/beta variant (depending from what's still open from the issues below):
Issues tagged crimson:
- [Librem5 space](https://source.puri.sm/groups/Librem5/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=crimson&first_page_size=100)
- [PureOS core](https://source.puri.sm/groups/pureos/core/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=crimson&first_page_size=100)
- [PureOS packages](https://source.puri.sm/groups/pureos/packages/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=crimson&first_page_size=100)
Other bits:
- [ ] Test upgrade path from Byzantium
- [ ] [sync issues](https://master.pureos.net/sync/7/issues)https://source.puri.sm/Librem5/OS-issues/-/issues/162VoLTE support2022-04-14T12:20:34ZGuido GuntherVoLTE supportdiscussed in several places but lets have a bug: We need to support Voice Over LTE with the L5 modems. This involves both the modem and MM.
Upstream issue: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/378discussed in several places but lets have a bug: We need to support Voice Over LTE with the L5 modems. This involves both the modem and MM.
Upstream issue: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/378https://source.puri.sm/Librem5/OS-issues/-/issues/65Unlock gnome-keyring2023-02-24T19:17:45ZGuido GuntherUnlock gnome-keyringthe default keyring is not unlocked on login like on desktop gnome. Seems we're missing something in pam there - namely the session setup part.the default keyring is not unlocked on login like on desktop gnome. Seems we're missing something in pam there - namely the session setup part.https://source.puri.sm/Librem5/OS-issues/-/issues/252Librem 5 - Teseo-LIV3 GNSS Module reports weak carrier to noise ratio - proba...2023-01-15T15:52:10ZPavel PisaLibrem 5 - Teseo-LIV3 GNSS Module reports weak carrier to noise ratio - probably HW/design problem# What problem did you encounter
No GNSS lock in reasonable time only occasional in specially well condition (hour on roof of building)
Notice: problem is probably related to the Librem5 mainboard V1.03 and earlier. More users and deve...# What problem did you encounter
No GNSS lock in reasonable time only occasional in specially well condition (hour on roof of building)
Notice: problem is probably related to the Librem5 mainboard V1.03 and earlier. More users and developers feedback suggests that actual production Librem 5 phones with the mainboard version 1.6.0.1 achieve better signal to noise ratio and position fix is reached in 2 to 4 minutes...
## What is the actual behaviour?
GNSS is not functional al least on given single Librem 5 Evergreen L5v1-05 (in the battery compartment), shipped at November 5 2021.
According to the forum discussion in the thread [Librem 5 GPS/Location Tracking](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153) much more often problem, probably design level
## What is the expected behaviour?
GNSS fix in reasonable time and accuracy around 20 meters, even after self repair attempt the lock takes long and weak signal results in imprecise location
Performance should be comparable at least to low end consumer grade phones. Teseo-LIV3 GNSS Module is considered by ESA expert as one from the best compact modules. For sure incomparable to picosecond timing resolution of the HW which he design for ESA or the devices like Septentrio PolaRx5 or other geodetic GPSs.
## How to reproduce
Use ``gnss_test`` or log
```
socat unix-client:/var/run/gnss-share.sock -
```
and check ``$GPGSV`` lines for Carrier to Noise Ratio for satellite SatxCN0
# What hardware are you running on?
Librem 5 Evergreen L5v1-05 (in the battery compartment), shipped at November 5 2021. Mainboard V1.03, production date/number H 210726.
# More information
Actual tested device, Librem 5 Evergreen L5v1-05 (in the battery compartment), shipped at November 5 2021.
The values reported by ``$GPGSV`` - GNSS Satellites in View never better than 25 dB in the state of delivery and in ideal condition. Lock only sometimes after hour on the company roof above all other buildings and obstacles.
After self tune/repair attempt of earth pin contact enhance of the sensitivity by 5 dB but. Some satellites reach over 30 dB. Self repair and analysis reported in the forum thread [Librem 5 GPS/Location Tracking](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153/).
Problem is not probably only single unit production deviation.
[Thoughts of Galileo/ESA expert](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153/154)
[Some thoughts about GPGSV values interpretation](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153/156?u=ppisa)
[More about the issue](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153/158?u=ppisa)
[Confirmation of expected performance and required levels backed by expert clarification](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153/159)
[Report of Enhancement after Earthing Tune](https://forums.puri.sm/t/librem-5-gps-location-tracking/14153/163?u=ppisa)
After uncompleted reply without any answer of numbered points attempt to reach somebody supportive ad competent at Purism
[Librem 5 Hardware](https://forums.puri.sm/t/librem-5-hardware/16339)https://source.puri.sm/Librem5/OS-issues/-/issues/138Mobile data traffic counter2022-06-03T08:35:16ZSebastian KrzyszkowiakMobile data traffic counterApparently I've already managed to use all of my 10GB pre-paid plan of mobile data with my Birch, which I realized only when it stopped working due to lack of funds. A way to monitor (and limit) mobile data usage would be very helpful in...Apparently I've already managed to use all of my 10GB pre-paid plan of mobile data with my Birch, which I realized only when it stopped working due to lack of funds. A way to monitor (and limit) mobile data usage would be very helpful in keeping the expenses tamed.https://source.puri.sm/Librem5/OS-issues/-/issues/120Boot the OS when a wakeup alarm rings2021-08-20T15:09:33ZDorota CzaplejewiczBoot the OS when a wakeup alarm ringsBackground: some phones can activate the alarm even if they were turned "off". Some users expressed the wish to have this feature on the Librem 5: https://forums.puri.sm/t/will-alarm-clock-apps-be-able-to-wake-up-the-phone-when-its-off/4...Background: some phones can activate the alarm even if they were turned "off". Some users expressed the wish to have this feature on the Librem 5: https://forums.puri.sm/t/will-alarm-clock-apps-be-able-to-wake-up-the-phone-when-its-off/4916/19
Cast:
- The SNVS Real-Time clock aka SVNS_HI RTC. It is able to tigger alarms that wake up the SoC when powered on (6.4.2.2.2 in *i.MX 8M Dual/8M QuadLite/8M Quad Applications Processors Reference Manual*). Minimal power state "is the lowest power on state for the SoC so IIRC it draws in the uA on nA range"
- The PMIC BD71837 which controls the SVNS domain
- The on-board, accurate RTC
- The kernel
Plot:
- The SVNS RTC was disabled already in https://source.puri.sm/Librem5/linux-next/commit/491f04c6d5039294a7f818f87b22caf49e32c541
- Editing the power state via PMIC is tricky, as exemplified by https://source.puri.sm/Librem5/linux-next/commit/232aba9abca61da4ce67f11f8dd7caf41f3bfd62
- The challenge is in making sure the correct RTC is being used:
> You likely want to look into what happens when "rohm,reset-snvs-powered;" is in the pmic stanza. I think SNVS is enabled during powerdown right now so it would be more about re-enabling the SNVS RTC and getting it not to interfere with the RTC chip we have on board
> IIRC the "interference" was that Linux was trying to use the SNVS RTC for clock while we wanted it to use the on-board one
- There is a light at the end of the tunnel:
> I'm pretty sure the HW is capable it's will just be a matter of having the correct congiguration
- The OS would have to be appropriately notified, and run the alarm app right after boothttps://source.puri.sm/Librem5/OS-issues/-/issues/282don't suspend when wireless hotspot is active and devices connected2023-02-14T22:09:01ZPirate Praveendon't suspend when wireless hotspot is active and devices connectedI am sharing internet connection from my phone with laptop using wireless tethering. I have connected charger and suspend is selected only when using battery, but once charge reaches 100% it goes to suspend and hotpot is disconnected. Th...I am sharing internet connection from my phone with laptop using wireless tethering. I have connected charger and suspend is selected only when using battery, but once charge reaches 100% it goes to suspend and hotpot is disconnected. There should at least be a setting not to suspend when hotpsot is on.https://source.puri.sm/Librem5/OS-issues/-/issues/245squeekboard opens on phosh overview when not needed2022-07-08T18:20:04ZMartin Kepplingersqueekboard opens on phosh overview when not neededSince squeekboard 1.15.0-1pureos1 it opens very briefly when opening the phosh overview. It's like a very short glitch - it opens and closes again - at least most of the time. It happened 2 or 3 times to me that it would not close anymor...Since squeekboard 1.15.0-1pureos1 it opens very briefly when opening the phosh overview. It's like a very short glitch - it opens and closes again - at least most of the time. It happened 2 or 3 times to me that it would not close anymore. I captured one here. I only opened the phosh overview:
![2022-01-03-212806](/uploads/4cb9960529942424cb9fc12dd398cc73/2022-01-03-212806.png)https://source.puri.sm/Librem5/OS-issues/-/issues/237create and implement a policy for system suspend to RAM2023-11-15T19:31:19ZMartin Kepplingercreate and implement a policy for system suspend to RAMOur goal in the kernel is to support suspend to RAM and incoming (cellular) phone calls and SMS waking up the system. Exactly that. Currently we can't sensibly wake up the system based on any data packets.
But the above could be enough ...Our goal in the kernel is to support suspend to RAM and incoming (cellular) phone calls and SMS waking up the system. Exactly that. Currently we can't sensibly wake up the system based on any data packets.
But the above could be enough to not only let users manually suspend the system, but implement a policy that does not change UX (much) and saves power.
Something like suspend on "no internet connection", "no activity (whatever that means)" AND "display off for X seconds" is what comes to my mind.https://source.puri.sm/Librem5/OS-issues/-/issues/148Use a display manager2023-10-02T06:40:56ZGuido GuntherUse a display managerWe could use a custom lightdm greater reusing parts of phosh. This would allow to
- logout/switch users
- run through the whole pam stack privileged so e.g. gnome-keyring gets properly unlocked (#65)
- do away with the custom systemd un...We could use a custom lightdm greater reusing parts of phosh. This would allow to
- logout/switch users
- run through the whole pam stack privileged so e.g. gnome-keyring gets properly unlocked (#65)
- do away with the custom systemd unit
Downsides
- automatic after e.g. compositor or shell crashes wouldn't be that nice anymore
- uses x11https://source.puri.sm/Librem5/OS-issues/-/issues/350Consider adding a small swapfile to rootfs to avoid excessive zram pagefile n...2024-02-15T13:11:23ZJC StaudtConsider adding a small swapfile to rootfs to avoid excessive zram pagefile negotiationsAs described in [this forum thread](https://forums.puri.sm/t/improve-your-librem-5s-performance-with-this-one-weird-trick/22598), a small swapfile in rootfs has been observed to aid system responsiveness and stability by alleviating exce...As described in [this forum thread](https://forums.puri.sm/t/improve-your-librem-5s-performance-with-this-one-weird-trick/22598), a small swapfile in rootfs has been observed to aid system responsiveness and stability by alleviating excessive pagefile negotiations in zram. My personal anecdote it that even a swapfile of 512MiB was shown to be helpful but, of course, a larger swapfile is beneficial as disk space requirements allow.
This ticket serves as an argument in favor of the default L5 PureOS configuration mitigating performance/stability issues derived from the relatively limited disk space in the 32GB L5.https://source.puri.sm/Librem5/OS-issues/-/issues/349Return from suspend locks the OS2024-02-01T17:33:29ZMatthias ApitzReturn from suspend locks the OSPackage: phosh
Version: 0.32.0-1pureos1~byz1
vmlinuz-6.6.0-1-librem5
I do use my L5 as daily driver with enabled suspend to 2 minutes idle time on battery and 2 hours on AC. From “time to time” (say once a day) I face the problem that ...Package: phosh
Version: 0.32.0-1pureos1~byz1
vmlinuz-6.6.0-1-librem5
I do use my L5 as daily driver with enabled suspend to 2 minutes idle time on battery and 2 hours on AC. From “time to time” (say once a day) I face the problem that the L5 does not work correctly after coming back from suspend, mostly when the AC is plugged into the suspended phone, or when it is disconnected from AC and it was in suspend after 2h.
does not work correctly means:
1. the lock screen comes up
2. phone can be unlocked
3. terminal app echoes chars but no command starts and Ctrl-C has no visible effect
4. upper bar can be pulled down, but changing Wifi has no reaction
5. reboot or power from the menu dims the display, but does not shutdown the phone
Only long press on power button and an additional press bring it fully back to life.
I've done in the forum an exact log when and in which situation this has happened:
https://forums.puri.sm/t/status-of-suspend-for-librem-5/13918/510
and it turns out that these locks only happen when the phone is in suspend (logically) and I plug something in into it's USB-C port, either the AC or a laptop for tethering. Since I always wake it up before with a short press on power button no locks happen anymore.https://source.puri.sm/Librem5/OS-issues/-/issues/336crimson: Needs newer xdg-desktop-portal2023-10-19T17:01:26ZGuido Gunthercrimson: Needs newer xdg-desktop-portalWe should update to 1.18.0 to support `/usr/share/xdg-desktop-portal/portals` otherwise portal configuration is a complete hit and miss depending on what the user installed
/cc @ChriChriWe should update to 1.18.0 to support `/usr/share/xdg-desktop-portal/portals` otherwise portal configuration is a complete hit and miss depending on what the user installed
/cc @ChriChrihttps://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/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/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/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/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.