OS-issues issueshttps://source.puri.sm/Librem5/OS-issues/-/issues2023-11-14T13:44:03Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/344irregular/vulnerable? early usb serial behavior2023-11-14T13:44:03Zinxirregular/vulnerable? early usb serial behaviorThe librem 5 allows login over a serial usb connection, using a user account on the phone.
However, with repeated connection attempts during early boot it's possible to eventually get into the device before it seems to have properly ini...The librem 5 allows login over a serial usb connection, using a user account on the phone.
However, with repeated connection attempts during early boot it's possible to eventually get into the device before it seems to have properly initialized, and one sees (without doing anything!) what seems to be AT (modem?) commands getting printed into the session, and causing errors:
```
$ picocom -b 115200 /dev/ttyACM0
picocom v3.1
port is : /dev/ttyACM0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no
Type [C-a] [C-h] to see available commands
Terminal ready
PureOS pureos ttyGS0
pureos login: ATPassword:
AT
Login incorrect
ATPasswort: AT
Login incorrect
pureos Login: ATPassword:
Login incorrect
pureos Login:
```
The device ttyGS0, seems to be a device on the phone.https://source.puri.sm/Librem5/OS-issues/-/issues/338crimson: USB tethering does not work at all2023-11-06T09:05:03ZMatthias Apitzcrimson: USB tethering does not work at allWhen I connect my Librem 11 via USB-C cable, I expect that on both devices network interfaces will come up, as it does with the Librem 5 (usb0 in L5 and en7 in MacOS).
The only visible reaction is in /var/log/syslog these lines:
```
202...When I connect my Librem 11 via USB-C cable, I expect that on both devices network interfaces will come up, as it does with the Librem 5 (usb0 in L5 and en7 in MacOS).
The only visible reaction is in /var/log/syslog these lines:
```
2023-11-03T09:34:49.131639+00:00 pureos kernel: [ 4049.766672] usb 1-7: USB disconnect, device number 29
2023-11-03T09:34:49.248747+00:00 pureos acpid: input device has been disconnected, fd 16
2023-11-03T09:34:49.291865+00:00 pureos acpid: input device has been disconnected, fd 17
2023-11-03T09:34:49.348458+00:00 pureos acpid: input device has been disconnected, fd 18
2023-11-03T09:34:50.051901+00:00 pureos kernel: [ 4050.683120] usb 1-7: new full-speed USB device number 30 using xhci_hcd
2023-11-03T09:34:50.203616+00:00 pureos kernel: [ 4050.835719] usb 1-7: New USB device found, idVendor=1018, idProduct=1008, bcdDevice= 1.00
2023-11-03T09:34:50.203651+00:00 pureos kernel: [ 4050.835740] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2023-11-03T09:34:50.207621+00:00 pureos kernel: [ 4050.840763] input: HID 1018:1008 as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:1018:1008.0025/input/input75
2023-11-03T09:34:50.210309+00:00 pureos mtp-probe: checking bus 1, device 30: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7"
2023-11-03T09:34:50.210646+00:00 pureos mtp-probe: bus: 1, device: 30 was not an MTP device
2023-11-03T09:34:50.267538+00:00 pureos kernel: [ 4050.901032] hid-generic 0003:1018:1008.0025: input,hidraw1: USB HID v1.11 Keyboard [HID 1018:1008] on usb-0000:00:14.0-7/input0
2023-11-03T09:34:50.271531+00:00 pureos kernel: [ 4050.906335] input: HID 1018:1008 System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:1018:1008.0026/input/input76
2023-11-03T09:34:50.331538+00:00 pureos kernel: [ 4050.963080] input: HID 1018:1008 Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:1018:1008.0026/input/input77
2023-11-03T09:34:50.331560+00:00 pureos kernel: [ 4050.963251] hid-generic 0003:1018:1008.0026: input,hiddev0,hidraw2: USB HID v1.11 Device [HID 1018:1008] on usb-0000:00:14.0-7/input1
2023-11-03T09:34:50.363106+00:00 pureos mtp-probe: checking bus 1, device 30: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7"
2023-11-03T09:34:50.363676+00:00 pureos mtp-probe: bus: 1, device: 30 was not an MTP device
```https://source.puri.sm/Librem5/OS-issues/-/issues/339crimson: device does not suspend with powerbutton2023-11-06T09:01:43ZMatthias Apitzcrimson: device does not suspend with powerbuttonThe Librem 11 suspends fine after the configured idle time when on battery or power supply. But it does not suspend on using the power button, even when configured that this should be its action. Only the display is switched off.The Librem 11 suspends fine after the configured idle time when on battery or power supply. But it does not suspend on using the power button, even when configured that this should be its action. Only the display is switched off.https://source.puri.sm/Librem5/OS-issues/-/issues/1Enable etnaviv in libdrm Debian package2023-10-10T19:45:13ZGuido GuntherEnable etnaviv in libdrm Debian packageNeeded for the devkits: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906915
Enabled in Debian upstream, needs to tickle through PureOS.Needed for the devkits: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906915
Enabled in Debian upstream, needs to tickle through PureOS.https://source.puri.sm/Librem5/OS-issues/-/issues/330apt update says "Could not connect to repo.pureos.net:443"2023-08-11T10:03:02ZElias Rudbergapt update says "Could not connect to repo.pureos.net:443"The last few days, the `apt update` command on my Librem 5 says: "`Could not connect to repo.pureos.net:443`"
Is something wrong with the repo.pureos.net server?The last few days, the `apt update` command on my Librem 5 says: "`Could not connect to repo.pureos.net:443`"
Is something wrong with the repo.pureos.net server?https://source.puri.sm/Librem5/OS-issues/-/issues/326Cannot scale-to-fit mumble2023-06-02T16:15:39ZEvangelos Ribeiro TzarasCannot scale-to-fit mumbleThe preferences window in Mumble overflows a lot.
p-m-s does not show a separate entry in the compositor panel.
It was previously suspected that the problem being that it's run through xwayland where scaling does not work,
however I've...The preferences window in Mumble overflows a lot.
p-m-s does not show a separate entry in the compositor panel.
It was previously suspected that the problem being that it's run through xwayland where scaling does not work,
however I've verified that it runs indeed under wayland (`WAYLAND_DEBUG=1` works).
See this video (with ~13MB too big to attach to gitlab directly):
https://fortysixandtwo.eu/upload/mumble1.webm
I will check wayland logs for what type of surface is being opened for the preferences window, but I wanted to share my initial findings already (so I won't forget to do it later).https://source.puri.sm/Librem5/OS-issues/-/issues/180My software is messing with the Window Manager and triggers crash and/or free...2023-05-27T10:49:54Zfralb5My software is messing with the Window Manager and triggers crash and/or freeze of GUI# What problem did you encounter
My software triggers some crash and/or freeze of GUI (Phosh ? Phoc? something else ?)
What is triggering the crash/freezes : my software is trying to move the main transparent window outside of the scre...# What problem did you encounter
My software triggers some crash and/or freeze of GUI (Phosh ? Phoc? something else ?)
What is triggering the crash/freezes : my software is trying to move the main transparent window outside of the screen again and again, with an other info window (when mouse is over an icon)
Sometimes, the GUI is freezing, probably due to the spamming of Update_info_position() with gtk_* calls inside
I put a printf in my configure callback for the main window : Callback_on_configure()
And a printf in a repositionning of the info window : Update_info_position()
The majority of times it end up like this :
```
Update_info_position()
updates-warner: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
```
where my software is killed and the GUI is left intact
But sometimes, the GUI is also killed and reset to the authentication screen, sometime it does not even reset and keep just a black screen
Sometimes gdk_screen_is_composited() returns false (if I remember after a GUI crash and reset)
## How to reproduce
Sadly, I don't have an easy way of triggering this
Last time I crashed it, it took 45 seconds and didnt reset to the authentication screen just no GUI anymore, while doing things on SSH still active
I was "lucky" because it can takes minutes and multiple attempts before it crashes
**EDIT** : I deleted the unpractical way of reproducing, I will provide the result of my tests (see comments)
# Which version did you encounter the bug in?
- [X] I used the precompiled Debian package (e.g. by running a prebuilt
image). Please paste the output oof ``dpkg -s phosh`` below.
```
Package: phosh
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 1400
Maintainer: PureOS Maintainers <pureos-project@puri.sm>
Architecture: amd64
Version: 0.8.0-1pureos0
Provides: notification-daemon, polkit-1-auth-agent
Depends: dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.17), libcairo2 (>= 1.2.4), libfeedback-0.0-0 (>= 0.0.0+git20200305), libgcr-base-3-1 (>= 3.8.0), libgcr-ui-3-1 (>= 3.8.0), libgdk-pixbuf-2.0-0 (>= 2.23.0), libglib2.0-0 (>= 2.59.2), libgnome-desktop-3-19 (>= 3.17.92), libgtk-3-0 (>= 3.21.5), libhandy-1-0 (>= 1.0.2), libnm0 (>= 1.0.0), libpam0g (>= 0.99.7.1), libpango-1.0-0 (>= 1.37.2), libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.94), libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libsecret-1-0 (>= 0.7), libsystemd0 (>= 217), libupower-glib3 (>= 0.99.4-3~), libwayland-client0 (>= 1.9.91), fonts-lato, gnome-shell-common, gsettings-desktop-schemas, phoc (>= 0.4.4)
Recommends: feedbackd, gnome-session-bin, gnome-session-common, gnome-settings-daemon, iio-sensor-proxy, phosh-mobile-tweaks, squeekboard | phosh-osk-stub
Description: Pure Wayland shell for mobile devices
Phosh is a graphical shell for Wayland compositors speaking the layer-surface
protocol and aimed at mobile devices like smart phones and tablets using touch
based inputs and small screens.
.
It's part of the Phosh Mobile Environment based on GNOME/GTK. For the full
stack see the phosh-full and phosh-core metapackages.
Homepage: https://source.puri.sm/Librem5/phosh
```
# What hardware are you running phosh on?
- [X] amd64 qemu image
I'm using the librem5.qcow2 (PureOS 10.0 byzantium) in kvm
I compile with gcc (Debian 10.2.1-6) 10.2.1 20210110 (provided by PureOs)
I did 'apt update && apt upgrade && reboot' and did trigger multiples crashes just before validating this report
# Releveant logfiles
I did a compilation of logs from 'journalctl -b 0'
[journalctl.log](/uploads/2529a50df8c55c59f59969e4bee37694/journalctl.log)https://source.puri.sm/Librem5/OS-issues/-/issues/12Crash in the wifi stack2023-05-03T16:56:01ZFabrice DesréCrash in the wifi stackNot sure if that's the right place to report this issue, but I got this crash in wpa_supplicant:
```
[ 14.377404] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.377548] rsi_91x: ===> Interface UP <===
[ 14.380304] IPv6: ...Not sure if that's the right place to report this issue, but I got this crash in wpa_supplicant:
```
[ 14.377404] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.377548] rsi_91x: ===> Interface UP <===
[ 14.380304] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.382107] rsi_91x: ===> Interface DOWN <===
[ 14.383350] rsi_91x: ===> Interface UP <===
[ 14.383527] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.514619] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.518723] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 14.563852] systemd-journald[1209]: File /var/log/journal/63404380c564418ea450ae1e9c33565b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 14.848121] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.043718] imx-sdma 30bd0000.sdma: load_address = 685
[ 15.043725] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 15.043729] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 15.043732] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 15.043735] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 15.043738] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 15.168250] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.487967] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.491849] imx-sdma 30bd0000.sdma: load_address = 749
[ 15.491856] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 15.491859] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 15.491862] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 15.491865] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 15.491868] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 15.808338] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.914723] imx-sdma 30bd0000.sdma: load_address = 685
[ 15.914732] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 15.914735] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 15.914738] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 15.914742] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 15.914745] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 16.127937] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 16.447777] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 16.629389] imx-sdma 30bd0000.sdma: load_address = 749
[ 16.629398] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 16.629401] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 16.629404] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 16.629407] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 16.629410] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 16.768979] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.075017] imx-sdma 30bd0000.sdma: sdma_prep_dma_cyclic channel: 1
[ 17.075027] imx-sdma 30bd0000.sdma: load_address = 749
[ 17.075033] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.075038] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 17.075042] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.075047] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 17.075051] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.075065] imx-sdma 30bd0000.sdma: entry 0: count: 2204 dma: 0xec180000 intr
[ 17.075071] imx-sdma 30bd0000.sdma: entry 1: count: 2204 dma: 0xec18089c intr
[ 17.075077] imx-sdma 30bd0000.sdma: entry 2: count: 2204 dma: 0xec181138 intr
[ 17.075083] imx-sdma 30bd0000.sdma: entry 3: count: 2204 dma: 0xec1819d4 wrap intr
[ 17.077780] imx-sdma 30bd0000.sdma: load_address = 685
[ 17.077786] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.077789] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 17.077792] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.077795] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 17.077798] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.087860] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.414001] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.522024] imx-sdma 30bd0000.sdma: sdma_prep_dma_cyclic channel: 2
[ 17.522033] imx-sdma 30bd0000.sdma: load_address = 685
[ 17.522036] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.522040] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 17.522043] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.522046] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 17.522049] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.522060] imx-sdma 30bd0000.sdma: entry 0: count: 2204 dma: 0xec200000 intr
[ 17.522065] imx-sdma 30bd0000.sdma: entry 1: count: 2204 dma: 0xec20089c intr
[ 17.522068] imx-sdma 30bd0000.sdma: entry 2: count: 2204 dma: 0xec201138 intr
[ 17.522072] imx-sdma 30bd0000.sdma: entry 3: count: 2204 dma: 0xec2019d4 wrap intr
[ 17.562311] imx-sdma 30bd0000.sdma: load_address = 749
[ 17.562319] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.562322] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 17.562325] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.562328] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 17.562331] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.727895] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.987421] imx-sdma 30bd0000.sdma: load_address = 749
[ 17.987429] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.987432] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 17.987436] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.987439] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 17.987442] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 18.048171] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 18.367875] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 18.410881] imx-sdma 30bd0000.sdma: load_address = 685
[ 18.410889] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 18.410893] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 18.410896] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 18.410899] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 18.410902] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 18.847953] imx-sdma 30bd0000.sdma: sdma_prep_dma_cyclic channel: 2
[ 18.847962] imx-sdma 30bd0000.sdma: load_address = 685
[ 18.847965] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 18.847968] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 18.847971] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 18.847974] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 18.847977] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 18.847989] imx-sdma 30bd0000.sdma: entry 0: count: 2204 dma: 0xec200000 intr
[ 18.847993] imx-sdma 30bd0000.sdma: entry 1: count: 2204 dma: 0xec20089c intr
[ 18.847997] imx-sdma 30bd0000.sdma: entry 2: count: 2204 dma: 0xec201138 intr
[ 18.848001] imx-sdma 30bd0000.sdma: entry 3: count: 2204 dma: 0xec2019d4 wrap intr
[ 18.862405] imx-sdma 30bd0000.sdma: load_address = 749
[ 18.862413] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 18.862416] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 18.862419] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 18.862423] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 18.862426] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 19.300079] imx-sdma 30bd0000.sdma: load_address = 749
[ 19.300087] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 19.300090] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 19.300094] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 19.300097] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 19.300100] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 19.716174] imx-sdma 30bd0000.sdma: load_address = 749
[ 19.716182] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 19.716185] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 19.716189] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 19.716192] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 19.716195] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 20.132651] imx-sdma 30bd0000.sdma: load_address = 749
[ 20.132658] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 20.132661] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 20.132664] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 20.132668] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 20.132671] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 20.550044] imx-sdma 30bd0000.sdma: load_address = 749
[ 20.550053] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 20.550058] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 20.550063] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 20.550067] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 20.550072] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 21.112810] imx-sdma 30bd0000.sdma: load_address = 749
[ 21.112819] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 21.112824] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 21.112829] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 21.112834] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 21.112838] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 21.544957] imx-sdma 30bd0000.sdma: load_address = 749
[ 21.544967] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 21.544972] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 21.544977] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 21.544981] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 21.544986] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 22.263948] imx-sdma 30bd0000.sdma: load_address = 749
[ 22.263956] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 22.263962] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 22.263966] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 22.263971] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 22.263976] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 22.755013] imx-sdma 30bd0000.sdma: load_address = 749
[ 22.755020] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 22.755024] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 22.755027] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 22.755030] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 22.755033] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 23.374749] imx-sdma 30bd0000.sdma: load_address = 749
[ 23.374758] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 23.374761] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 23.374764] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 23.374768] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 23.374771] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 24.902488] rsi_91x: ===> Interface DOWN <===
[ 24.904758] rsi_91x: ===> Interface UP <===
[ 24.904876] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 37.262605] wlan0: authenticate with b0:93:5b:c7:60:79
[ 37.262735] wlan0: send auth to b0:93:5b:c7:60:79 (try 1/3)
[ 37.266741] wlan0: authenticated
[ 37.271261] wlan0: associate with b0:93:5b:c7:60:79 (try 1/3)
[ 37.275740] wlan0: RX AssocResp from b0:93:5b:c7:60:79 (capab=0x1411 status=0 aid=6)
[ 37.277010] wlan0: associated
[ 37.293757] wlan0: Limiting TX power to 27 (30 - 3) dBm as advertised by b0:93:5b:c7:60:79
[ 37.302110] rsi_91x: EAPOL 4 confirm
[ 37.311680] rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 1 key_len: 16
[ 37.311697] rsi_91x: rsi_mac80211_set_key: RSI set_key
[ 37.314066] rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 2 key_len: 16
[ 37.314081] rsi_91x: rsi_mac80211_set_key: RSI set_key
[ 37.314356] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 56.239938] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
[ 56.248948] Mem abort info:
[ 56.251859] ESR = 0x96000004
[ 56.254912] Exception class = DABT (current EL), IL = 32 bits
[ 56.260944] SET = 0, FnV = 0
[ 56.264108] EA = 0, S1PTW = 0
[ 56.267307] Data abort info:
[ 56.270185] ISV = 0, ISS = 0x00000004
[ 56.274131] CM = 0, WnR = 0
[ 56.277107] user pgtable: 4k pages, 48-bit VAs, pgdp = 000000002d23c7d9
[ 56.283886] [00000000000000d0] pgd=0000000000000000
[ 56.288880] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 56.294451] Modules linked in: aes_ce_ccm bnep qmi_wwan cdc_wdm usbnet tcpci tcpm roles typec bq25890_charger rtc_m41t80 st_gyro_spi st_sensors_spi st_gyro_i2c ov5640 st_sensors_i2c st_gyro st_sensors xhci_plat_hcd xhci_hcd usbcore usb_f_acm u_serial dwc3 ulpi rsi_sdio rsi_91x bluetooth aes_ce_blk crypto_simd crc32_ce crct10dif_ce ghash_ce sha2_ce sha1_ce snd_soc_simple_card snd_soc_simple_card_utils dwc3_of_simple i2c_imx spi_imx imx_sdma imx2_wdt g_serial libcomposite udc_core ip_tables x_tables ipv6
[ 56.338995] CPU: 2 PID: 2333 Comm: wpa_supplicant Not tainted 4.18.11-g59f358aa #1
[ 56.346561] Hardware name: Purism Librem 5 devkit (DT)
[ 56.351697] pstate: 20000005 (nzCv daif -PAN -UAO)
[ 56.356503] pc : rsi_send_probe_request+0x16c/0x328 [rsi_91x]
[ 56.362256] lr : rsi_send_probe_request+0x158/0x328 [rsi_91x]
[ 56.367998] sp : ffff8000a20d37e0
[ 56.371310] x29: ffff8000a20d37e0 x28: ffff80008db52db8
[ 56.376622] x27: ffff8000a783f0c8 x26: ffff80008db52db8
[ 56.381933] x25: ffff8000a783e3d8 x24: 0000000000000000
[ 56.387244] x23: 0000000000000079 x22: ffff800086d8ac40
[ 56.392555] x21: 0000000000000001 x20: ffff8000a783e000
[ 56.397866] x19: 000000000000000d x18: ffff000008b76000
[ 56.403177] x17: 0000000000000000 x16: 0000000000000000
[ 56.408488] x15: ffff800086d8ac00 x14: 0100000000000000
[ 56.413800] x13: 00000000ff01006e x12: 1a2d6c6048302418
[ 56.419110] x11: 120c080100000000 x10: 0000000000000100
[ 56.424422] x9 : 0000000000000000 x8 : 0000ff01006e1a2d
[ 56.429733] x7 : 6c60483004322418 x6 : ffff8000a783e42a
[ 56.435043] x5 : ffff8000abf85e30 x4 : 0000000000000008
[ 56.440354] x3 : 0000000000000000 x2 : ffffffffffffffca
[ 56.445665] x1 : ffff800086d8ae4a x0 : ffff8000a783e3d8
[ 56.450978] Process wpa_supplicant (pid: 2333, stack limit = 0x000000005a0a93a7)
[ 56.458370] Call trace:
[ 56.460824] rsi_send_probe_request+0x16c/0x328 [rsi_91x]
[ 56.466228] rsi_mac80211_hw_scan_start+0x168/0x200 [rsi_91x]
[ 56.471978] __ieee80211_start_scan+0x260/0x818
[ 56.476507] ieee80211_request_scan+0x34/0x58
[ 56.480864] ieee80211_scan+0x58/0xd0
[ 56.484527] nl80211_trigger_scan+0x5ac/0x820
[ 56.488883] genl_family_rcv_msg+0x248/0x368
[ 56.493151] genl_rcv_msg+0x60/0xa8
[ 56.496638] netlink_rcv_skb+0xf0/0x138
[ 56.500471] genl_rcv+0x3c/0x50
[ 56.503610] netlink_unicast+0x198/0x218
[ 56.507531] netlink_sendmsg+0x274/0x340
[ 56.511453] sock_sendmsg+0x34/0x50
[ 56.514939] ___sys_sendmsg+0x28c/0x2b8
[ 56.518773] __sys_sendmsg+0x78/0xd0
[ 56.522346] sys_sendmsg+0x38/0x48
[ 56.525749] el0_svc_naked+0x30/0x34
[ 56.529324] Code: 54fffba1 110062f7 7101e2ff 540002c9 (f9406b00)
[ 56.535416] ---[ end trace 8d185367b2287175 ]---
```https://source.puri.sm/Librem5/OS-issues/-/issues/319Black screen when trying to add phosh UI to my desktop PureOS version2023-04-30T19:13:36ZOleg LightsBlack screen when trying to add phosh UI to my desktop PureOS versionI'd like to add a mobile interface on my desktop to test the mobile OS and see how close we are to convergence.
I'm using Librem mini v2 running Byzantium updated on March 18th, however I tried it with one of the older versions as well ...I'd like to add a mobile interface on my desktop to test the mobile OS and see how close we are to convergence.
I'm using Librem mini v2 running Byzantium updated on March 18th, however I tried it with one of the older versions as well as on a virtual machine and the result was the same. Specifics: Linux 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux.
When I log out of my desktop, click on my name, I see a settings gear allowing me to pick a UI. I choose phosh and get a black screen. The only way to exit it is to press the sleep button on my keyboard, then wake the machine up which brings back the login screen, from which I can choose another interface that works (GNOME).https://source.puri.sm/Librem5/OS-issues/-/issues/317Kernel upgrade with low space results in phone not booting2023-03-21T10:15:25ZDorota CzaplejewiczKernel upgrade with low space results in phone not booting# What problem did you encounter
When low on space in /boot, a failed initramfs generation results in the boot script pointing to the broken kernel.
## What is the actual behaviour?
1. Install kernel
2. Fail to install
3. Boot script ...# What problem did you encounter
When low on space in /boot, a failed initramfs generation results in the boot script pointing to the broken kernel.
## What is the actual behaviour?
1. Install kernel
2. Fail to install
3. Boot script points to the broken version
## What is the expected behaviour?
3. Boot script points to some good version
## How to reproduce
Starting with:
```
ls /boot/vmlinuz-* | cat
/boot/vmlinuz-5.19.0-1-librem5
/boot/vmlinuz-6.0.0-1-librem5
/boot/vmlinuz-6.1.0-1-librem5
/boot/vmlinuz-6.1.13-librem5-gd7c9aec13bf6
```
Trigger with:
```
sudo truncate -s 32M /boot/fill # adjust size until problem seen. If the kernel installs, increase. If it fails before initramfs generation, decrease.
sudo apt install linux-image-6.2.0-1-librem5
```
Result (notice missing initrd):
```
$ grep -a librem5 /boot/boot.scr
setenv fk_kvers '6.2.0-1-librem5'
purism@pureos:~$ ls /boot/initrd.* | cat
/boot/initrd.img-5.19.0-1-librem5
/boot/initrd.img-6.0.0-1-librem5
/boot/initrd.img-6.1.0-1-librem5
/boot/initrd.img-6.1.13-librem5-gd7c9aec13bf6
purism@pureos:~$ ls /boot/vmlinuz-* | cat
/boot/vmlinuz-5.19.0-1-librem5
/boot/vmlinuz-6.0.0-1-librem5
/boot/vmlinuz-6.1.0-1-librem5
/boot/vmlinuz-6.1.13-librem5-gd7c9aec13bf6
/boot/vmlinuz-6.2.0-1-librem5
```
Log:
```
Unpacking linux-image-6.2.0-1-librem5 (6.2.2pureos1) ...
Setting up linux-image-6.2.0-1-librem5 (6.2.2pureos1) ...
update-initramfs: Generating /boot/initrd.img-6.2.0-1-librem5
pigz: abort: write error on <stdout> (No space left on device)
E: mkinitramfs failure pigz 28
update-initramfs: failed for /boot/initrd.img-6.2.0-1-librem5 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Using DTB: freescale/imx8mq-librem5-r4.dtb
Installing /usr/lib/linux-image-6.2.0-1-librem5/freescale/imx8mq-librem5-r4.dtb into /boot/dtbs/6.2.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
Installing new imx8mq-librem5-r4.dtb.
Installing /usr/lib/linux-image-6.2.0-1-librem5/freescale/imx8mq-librem5-r4.dtb into /boot/dtbs/6.2.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
Taking backup of imx8mq-librem5-r4.dtb.
Installing new imx8mq-librem5-r4.dtb.
flash-kernel: deferring update (trigger activated)
dpkg: error processing package linux-image-6.2.0-1-librem5 (--configure):
installed linux-image-6.2.0-1-librem5 package post-installation script subprocess returned error exit status 1
Processing triggers for flash-kernel (3.102.0pureos6) ...
Using DTB: freescale/imx8mq-librem5-r4.dtb
Installing /usr/lib/linux-image-6.2.0-1-librem5/freescale/imx8mq-librem5-r4.dtb into /boot/dtbs/6.2.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
Taking backup of imx8mq-librem5-r4.dtb.
Installing new imx8mq-librem5-r4.dtb.
flash-kernel: installing version 6.2.0-1-librem5
Generating boot script u-boot image... done.
Taking backup of boot.scr.
Installing new boot.scr.
Errors were encountered while processing:
linux-image-6.2.0-1-librem5
E: Sub-process /usr/bin/dpkg returned an error code (1)
```
# What hardware are you running on?
L5
# Relevant OS information
## Which OS are you using?
Byzantiumhttps://source.puri.sm/Librem5/OS-issues/-/issues/130NetworkManager gives wwan0 DNS priority over wlan02023-03-19T21:42:56ZKyle RankinNetworkManager gives wwan0 DNS priority over wlan0# Problem
Network appears sluggish due to DNS being slow to resolve. DNS is slow to resolve because wwan0 DNS is taking precedence over the faster wlan0 network. If wwan0 has poor signal, then DNS resolution slows down as it must time ou...# Problem
Network appears sluggish due to DNS being slow to resolve. DNS is slow to resolve because wwan0 DNS is taking precedence over the faster wlan0 network. If wwan0 has poor signal, then DNS resolution slows down as it must time out the wwan0 DNS queries before moving on to wlan0.
Specifically, NetworkManager is giving wlan0 connections a dns-priority of 20. Per https://wiki.gnome.org/Projects/NetworkManager/DNS the default priority if not set seems to be 100. The end result is that when wwan0 data is enabled, its DNS servers always take precendence over wlan0, even though wlan0 takes routing precedence.
The config files for wwan0 interfaces under /etc/NetworkManager/system-connections/ appear to be dynamic, or at least changes made to dns-priority to wwan0 files directly seem to be overwritten when the interface changes.
## Complications From IPv6
This also produces a separate error in the case that wwan0 provides IPv6 but wlan0 doesn't. In that case, DNS queries will return (and prefer) IPv6 responses from wwan0, but may not be able to route to those addresses over wlan0. To the user this ends up looking like the network is down (web pages won't load etc) when in reality they are attempting to connect to an IPv6 address over an IPv4 network.
# Desired Behavior
DNS priority matches overall interface priority. In this case, wlan0 has routing precedence over wwan0 so it should also take DNS precedence.
# Steps to Reproduce
Connect both wlan0 and wwan0 to a network. Observe that wwan0 DNS servers appear first in /etc/resolv.conf.
# Temporary Workaround
Disable wwan0 data when on WiFi connection.https://source.puri.sm/Librem5/OS-issues/-/issues/236Bring vvmplayer / vvmd to PureOS2023-01-17T09:09:43ZGuido GuntherBring vvmplayer / vvmd to PureOSThey're up to date in Debian and wold be straight backports
there's discussion of moving the GUI into calls but until then having it would be great and we'd need vvmd anyway.
/cc @carsten.schoenert (syncing already existent stuff is ce...They're up to date in Debian and wold be straight backports
there's discussion of moving the GUI into calls but until then having it would be great and we'd need vvmd anyway.
/cc @carsten.schoenert (syncing already existent stuff is certainly more important, just in case you're bored and noone else picks it up til then)https://source.puri.sm/Librem5/OS-issues/-/issues/310Please update `mmsd-tng` to 1.13.02023-01-13T11:56:45ZChris TalbotPlease update `mmsd-tng` to 1.13.0Hello!
There is a bug in `1.12.1` where T-mobile will tell a user that an MMS is sent, but the MMSC silently dropped the MMS. This bug has been fixed and there is a new release for it. However, since PureOS does not package libsoup3, I ...Hello!
There is a bug in `1.12.1` where T-mobile will tell a user that an MMS is sent, but the MMSC silently dropped the MMS. This bug has been fixed and there is a new release for it. However, since PureOS does not package libsoup3, I tagged and released `1.13.0` specifically for PureOS:
https://gitlab.com/kop316/mmsd/-/tags/1.13.0
Aside from using libsoup3, the `1.x` releases are identical in features to the `2.x` version.https://source.puri.sm/Librem5/OS-issues/-/issues/301Update to Meson 0.592022-12-07T18:35:21ZChris TalbotUpdate to Meson 0.59Hello!
Many apps are updating to GTK-4.0 and Libadwaita. In doing this, many are also updating a lot of their meson scripts, and are making `0.59` the default minimum version. There is a way to maintain backwards compatibility to work i...Hello!
Many apps are updating to GTK-4.0 and Libadwaita. In doing this, many are also updating a lot of their meson scripts, and are making `0.59` the default minimum version. There is a way to maintain backwards compatibility to work in PureOS (I do so in `vvmplayer` and `phosh-antispam`), but one has to convince the upstream maintainers to do so.
It would be nice if PureOS could update to meson 0.59, as this would eliminate the pain point on Backwards compatibility.https://source.puri.sm/Librem5/OS-issues/-/issues/292Plase update `mmsd-tng`, `vvmd`, and `vvmplayer` to the latest packages2022-11-22T11:43:42ZChris TalbotPlase update `mmsd-tng`, `vvmd`, and `vvmplayer` to the latest packages`mmsd-tng`, `vvmd`, and `vvmplayer` look to be on versions that are at least 2 months out of date. The latest versions are in Debian Bookworm, so it should be easy to port over.`mmsd-tng`, `vvmd`, and `vvmplayer` look to be on versions that are at least 2 months out of date. The latest versions are in Debian Bookworm, so it should be easy to port over.https://source.puri.sm/Librem5/OS-issues/-/issues/209Auto-rotation icon unclear2022-10-07T07:16:22ZDorota CzaplejewiczAuto-rotation icon unclearThe button which controls automatic display orientation is a circular arrow. The meaning is hard to decode.
Usually this kind of icon is dedicated to verbs like restart, redo, reload, retry. Moreover, clicking it does not cause anything...The button which controls automatic display orientation is a circular arrow. The meaning is hard to decode.
Usually this kind of icon is dedicated to verbs like restart, redo, reload, retry. Moreover, clicking it does not cause anything to happen, making it not possible to understand the purpose without an external source of knowledge.
Here are some concepts that might be useful for creating a better icon:
- display
- that display orientation has only 4 cardinal directions
- that display has just 2 shapes: portrait and landscape
- lock
- gravity
The clearest icon I can immediately think of is something presenting the 2 possible display shapes, and an arrow connecting them.https://source.puri.sm/Librem5/OS-issues/-/issues/280Backport latest vvmd2022-08-18T11:57:57ZEvangelos Ribeiro TzarasBackport latest vvmd@kop316 pinged me about updating
We have 0.7 in the archive and 0.10 is about to hit bookworm in a couple days.
[Changelog](https://gitlab.com/kop316/vvmd/-/blob/main/ChangeLog)
it mentiones needing this (as of yet) unmerged [patch fo...@kop316 pinged me about updating
We have 0.7 in the archive and 0.10 is about to hit bookworm in a couple days.
[Changelog](https://gitlab.com/kop316/vvmd/-/blob/main/ChangeLog)
it mentiones needing this (as of yet) unmerged [patch for curl](https://github.com/curl/curl/pull/8986)
maybe we should also keep that on our radar,
but if I remember the upstream discussion that curl patch is only needed for a "full fix"
for (I believe) [this issue](https://gitlab.com/kop316/vvmd/-/issues/8)
and there might be some partial mitigation in place in 0.9 (I'm a bit hazy on the details currently)
Mostly putting this here as a reminder for myselfhttps://source.puri.sm/Librem5/OS-issues/-/issues/269PureOS Settings app2022-08-08T13:58:38ZGuido GuntherPureOS Settings appWe have a bunch of things that should be tweakable by the user but that isn't in GNOME Settings.
- ring tone and other sound profile settings
- per application feedback settings
`gsettings set org.sigxcpu.feedbackd.application:/org...We have a bunch of things that should be tweakable by the user but that isn't in GNOME Settings.
- ring tone and other sound profile settings
- per application feedback settings
`gsettings set org.sigxcpu.feedbackd.application:/org/sigxcpu/feedbackd/application/sm-puri-phosh/ profile quiet`
- scale-to-fit settings (select app from list of running applications)
`helpers/scale-to-fit org.gnome.Maps on`
- mark apps as adaptive (selectable from a list of installed applications
`$ gsettings set sm.puri.phosh force-adaptive "['chromium.desktop', 'firefox-esr.desktop', 'org.gnome.Dictionary.desktop', 'org.gnome.Maps.desktop', 'org.gnome.zbrown.KingsCross.desktop', 'yelp.desktop', 'org.gnome.TwentyFortyEight.desktop', 'org.gnome.eog.desktop', 'org.gnome.Reversi.desktop', 'org.gnome.LightsOff.desktop', 'com.github.bilelmoussaoui.Authenticator.desktop', 'org.gnome.DiskUtility.desktop']"`
- app filter settings (filter adaptive apps yes/no)
`$ gsettings set sm.puri.phosh app-filter-mode '[]'`
- map external touch screens (selectable from a list of attached touch devices)
`$ gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/27c0:0819/ output "['Unknown', 'NexDock', '8R33926O00Q']"`
- enable disable VoLTE (https://source.puri.sm/angus.ainslie/firmware-bm818-nonfree/-/commit/f48f9877f9a9866dddc224fe25a6be41e0f2bb6b)
- …
Until these things make it upstream (if ever) it would be good to have an app that makes it accessible to the user without resorting to GSettings.
maybe also:
- actions triggered on HKS toggle
- advanced suspend settings
- some relevant settings to report to support (could be merged with the upcoming l5-support app):
- current charging speed
- background tasks that drain the battery
- …
It would be good to have an app (or several) for that.
Related:
- https://gitlab.gnome.org/World/Phosh/phosh/-/issues/779
- https://gitlab.com/postmarketOS/postmarketos-tweaks
This would go a long way to make PureOS easier to use.
@francois.techene @tobias.bernard @sam.hewitt it would be good to have designs for that.https://source.puri.sm/Librem5/OS-issues/-/issues/273Package powersupply2022-08-02T11:52:37ZEvangelos Ribeiro TzarasPackage powersupplyhttps://gitlab.com/MartijnBraam/powersupply/
https://gitlab.com/mobian1/packages/powersupply
![powersupply](/uploads/5f1fb8a188f2da486cc349f3471c4400/powersupply.png)
![powersupply_charging](/uploads/feee7fc24ee7efa62a17ae463e9733f0/po...https://gitlab.com/MartijnBraam/powersupply/
https://gitlab.com/mobian1/packages/powersupply
![powersupply](/uploads/5f1fb8a188f2da486cc349f3471c4400/powersupply.png)
![powersupply_charging](/uploads/feee7fc24ee7efa62a17ae463e9733f0/powersupply_charging.png)https://source.puri.sm/Librem5/OS-issues/-/issues/264Dialect: Cannot close the preferences window2022-07-18T18:42:49ZÉloi RivardDialect: Cannot close the preferences windowThere is no way to close the preferences dialog in dialect with phosh on a L5. I don't know whose responsibility it is.
Related dialect issue: https://github.com/dialect-app/dialect/issues/255
![170329876-ed0b7258-ae83-4a9f-bd79-0f7e76...There is no way to close the preferences dialog in dialect with phosh on a L5. I don't know whose responsibility it is.
Related dialect issue: https://github.com/dialect-app/dialect/issues/255
![170329876-ed0b7258-ae83-4a9f-bd79-0f7e76b41e02](/uploads/0b8105e7a5aac5a90c1248072af55004/170329876-ed0b7258-ae83-4a9f-bd79-0f7e76b41e02.png)