OS-issues issueshttps://source.puri.sm/Librem5/OS-issues/-/issues2021-03-19T20:18:48Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/203Byzantum - Window manager wrong behaviors2021-03-19T20:18:48Zfralb5Byzantum - Window manager wrong behaviors# What problem did you encounter
## What is the actual behaviour?
I don't know If I should put this in Phosh or not
I'm currently adapting one of my GTK2 software to GTK3+libhandy in the Librem 5 VM and I found 2 misbehaviors of the Win...# What problem did you encounter
## What is the actual behaviour?
I don't know If I should put this in Phosh or not
I'm currently adapting one of my GTK2 software to GTK3+libhandy in the Librem 5 VM and I found 2 misbehaviors of the Window Manager :
- The first one is a minor problem : a useless spamming of the event GDK_CONFIGURE, when I'm only moving the cursor on phosh GUI
It's a minor problem, but it could probably intensively use the CPU if many open softwares are getting spam by this event until focus is given
It happens only after changing the Scale in the Display settings
The spamming stop only if I put the focus on my window again
- The second one is a more critical problem : the scale change from 200% to 100% doesn't trigger the problem, but from 100% to 200% triggers it
The configure event (GDK_CONFIGURE) is not updating correctly the width information
My software is rendering a view depending on the dimensions of the window, but it can't do it properly because of that misbehavior from the Window Manager
## How to reproduce
1) Launching a software
2) Changing the scale from 100% to 200%
3) Displaying the values given in the event->configure structure
Here is a video showing the entire process:
The left panel is the standard output of my software printing some values from the event->configure structure
I added a count of event to see the spam for the first problem
![2021-03-19_20-46-22](/uploads/c8b3816019e69ab98b72dbe4f5044117/2021-03-19_20-46-22.mp4)
# What hardware are you running on?
- [X] amd64 qemu image (Librem5 VM)
# Relevant OS information
## Which kernel are you using?
Linux pureos 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64 GNU/Linux
## Which OS are you using?
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
VERSION_ID=10.0
VERSION_CODENAME=byzantium
HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"
LOGO=pureos-logo-icon
## Any other information that may be helpful?
I did 'apt update && apt upgrade' todayhttps://source.puri.sm/Librem5/OS-issues/-/issues/204jitterentropy-rngd process taking 100% CPU on byzantium2021-03-30T10:53:26ZElias Rudbergjitterentropy-rngd process taking 100% CPU on byzantiumJust reflashed a Librem 5 Birch with the latest byzantium image, like this:
./scripts/librem5-flash-image --board librem5r2 --dist byzantium
Things seem to work, but it seemed a bit busy when I thought it should be idle and looking...Just reflashed a Librem 5 Birch with the latest byzantium image, like this:
./scripts/librem5-flash-image --board librem5r2 --dist byzantium
Things seem to work, but it seemed a bit busy when I thought it should be idle and looking at `top` shows that there is a `jitterentropy-rngd` process taking 100% CPU.
```
top - 19:39:11 up 6 min, 2 users, load average: 2.00, 1.65, 0.84
Tasks: 192 total, 2 running, 190 sleeping, 0 stopped, 0 zombie
%Cpu(s): 25.2 us, 1.0 sy, 0.0 ni, 73.5 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
MiB Mem : 2991.9 total, 1934.7 free, 453.2 used, 604.0 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 2400.8 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
423 root 20 0 2156 492 420 R 100.0 0.0 6:21.11 jitterentropy-r
5 root 20 0 0 0 0 I 1.5 0.0 0:07.42 kworker/0:0-events
1509 purism 20 0 13000 2912 2376 R 1.5 0.1 0:00.10 top
```
purism@pureos:~$ ps -eF | grep jitter
root 423 1 99 539 492 1 19:32 ? 00:07:01 /usr/sbin/jitterentropy-rngd
There is a `jitterentropy-rngd` package installed:
jitterentropy-rngd/byzantium,now 1.2.1-1 arm64 [installed,automatic]
The man page says: "jitterentropy-rngd - CPU Jitter Random Number Generator Daemon".
But there must be something wrong with it, certainly it is not supposed to use 100% CPU all the time?https://source.puri.sm/Librem5/OS-issues/-/issues/205dpkg-architecture: command not found (happens on ssh login on byzantium)2021-07-28T14:15:35ZElias Rudbergdpkg-architecture: command not found (happens on ssh login on byzantium)Librem 5 Birch running byzatium, installed using `./scripts/librem5-flash-image --board librem5r2 --dist byzantium`
Each time I login using ssh there is an error message like this:
-bash: dpkg-architecture: command not found
Here ...Librem 5 Birch running byzatium, installed using `./scripts/librem5-flash-image --board librem5r2 --dist byzantium`
Each time I login using ssh there is an error message like this:
-bash: dpkg-architecture: command not found
Here is what the whole login looks like:
```
$ ssh purism@$LOCAL_IP
[... password prompt ...]
Linux pureos 5.11.0-1-librem5 #1 SMP PREEMPT Mon Mar 22 14:21:27 PDT 2021 aarch64
The programs included with the PureOS system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
PureOS comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Mar 30 10:59:35 2021 from [...]
-bash: dpkg-architecture: command not found
purism@pureos:~$
```
Then the ssh session seem to work fine anyway as far as I can tell, but I'm not sure if that command being missing could lead to some other problems.
I figured out that the `dpkg-architecture` command is part of the `dpkg-dev` package, and after doing `sudo apt install dpkg-dev` the error message no longer comes.
What happens at an ssh login that makes it try to use the `dpkg-architecture` command?
Should the `dpkg-dev` package be installed already by default to avoid the problem?https://source.puri.sm/Librem5/OS-issues/-/issues/207Byzantium: Welcome screen does not fit2021-04-09T09:47:55ZElias RudbergByzantium: Welcome screen does not fitHere is what the welcome screen looks on first startup like after flashing the most recent Byzantium image:
![WP_20210409_005](/uploads/c239c83b1d8dc2b191297070532b6d4f/WP_20210409_005.jpg)
Look to the right, where the names of countri...Here is what the welcome screen looks on first startup like after flashing the most recent Byzantium image:
![WP_20210409_005](/uploads/c239c83b1d8dc2b191297070532b6d4f/WP_20210409_005.jpg)
Look to the right, where the names of countries are supposed to be, those names are cut off a lot. It looks like the welcome screen has the wrong idea about the screen size.
The specific image flashed in this case was "'plain librem5r2 byzantium image' from Fri Apr 9 05:23:45 2021" but it has been like this for earlier Byzantium images also.
The next screen that comes up, "Typing", has the same problem.
After that comes the "Wi-Fi" screen, but that one is shown correctly.
This is on Librem 5 Birch in case that matters.https://source.puri.sm/Librem5/OS-issues/-/issues/208Replace passwordless sudo o user by `sudo` group membership2021-08-30T12:16:37ZGuido GuntherReplace passwordless sudo o user by `sudo` group membershipI'm running this on byzantium since some time since i'm not a fan of root privileges with the only requirement being having a tty.
It would mean scripts either use sudo (when run in shell) or polkit/`pkexec` when using GUI.
/cc @kyle.r...I'm running this on byzantium since some time since i'm not a fan of root privileges with the only requirement being having a tty.
It would mean scripts either use sudo (when run in shell) or polkit/`pkexec` when using GUI.
/cc @kyle.rankinhttps://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/211Error on ssh login2021-06-07T09:18:17ZDorota CzaplejewiczError on ssh loginOn my first login I noticed an error as a welcome message that I can't immediately fix:
```
$ ssh purism@10.42.0.42
[...]
Linux pureos 5.12.0-1-librem5 #1 SMP PREEMPT Tue May 25 08:16:08 PDT 2021 aarch64
[...]
Last login: Sun Jun 6 10:...On my first login I noticed an error as a welcome message that I can't immediately fix:
```
$ ssh purism@10.42.0.42
[...]
Linux pureos 5.12.0-1-librem5 #1 SMP PREEMPT Tue May 25 08:16:08 PDT 2021 aarch64
[...]
Last login: Sun Jun 6 10:19:27 2021
-bash: dpkg-architecture: command not found
purism@pureos:~$
```https://source.puri.sm/Librem5/OS-issues/-/issues/212Luks image does not resize2021-06-07T07:54:32ZDorota CzaplejewiczLuks image does not resize# What problem did you encounter
Luks Byzantium image does not seem to resize the root partition, leading to low memory.
Note that I use an image from last week.
Using Evergreen.
```
# df -h
/dev/dm-0 3.6G 3.1G 370M 90% /
```# What problem did you encounter
Luks Byzantium image does not seem to resize the root partition, leading to low memory.
Note that I use an image from last week.
Using Evergreen.
```
# df -h
/dev/dm-0 3.6G 3.1G 370M 90% /
```https://source.puri.sm/Librem5/OS-issues/-/issues/216OSK-sdl gives feedback on missed presses2021-08-27T14:49:48ZDorota CzaplejewiczOSK-sdl gives feedback on missed pressesUsing an encrypted Byzantium and entering the password multiple times a day due to reboots, I'm getting a lot of failed attempts due to imprecise feedback.
Currently, it buzzes on any touch, even if it doesn't cause any other interacti...Using an encrypted Byzantium and entering the password multiple times a day due to reboots, I'm getting a lot of failed attempts due to imprecise feedback.
Currently, it buzzes on any touch, even if it doesn't cause any other interaction. It would be better to buzz only on accepted presses.
I'm not sure how closely we are tracking upstream, so in case it's already solved there, I'm only filing here.https://source.puri.sm/Librem5/OS-issues/-/issues/217Add sound feedback at boot2021-09-10T15:50:51ZDorota CzaplejewiczAdd sound feedback at bootThere are two cases where extra sound feedback would be useful.
The first one is when the button is being pressed. There is the light, but when the phone is on the charger, the color change feels somewhat unclear: "is it the phone turni...There are two cases where extra sound feedback would be useful.
The first one is when the button is being pressed. There is the light, but when the phone is on the charger, the color change feels somewhat unclear: "is it the phone turning on or a change of charging status?". Making the motor run would suggest that the phone is more "alive" now, that is, the button press was accepted.
The second case is related to the boot password entry. It's necessary every time the phone is rebooted, meaning when rebooting while hacking on the OS, or when rebooting to do updates. Shutdown is not instant, therefore I usually put the phone aside, and I find that I often forget about it (especially when using the reinstall+reboot script). Some audio feedback would be very useful there.https://source.puri.sm/Librem5/OS-issues/-/issues/219Wish: toggle boot animation on button press2021-09-11T07:53:22ZDorota CzaplejewiczWish: toggle boot animation on button pressCurrently, there's no way to dismiss the boot animation and see the console. I think it would be useful:
- for debugging
- I sometimes flip it to check if the system is completely hung when waiting for upgrades
and also for marketing. ...Currently, there's no way to dismiss the boot animation and see the console. I think it would be useful:
- for debugging
- I sometimes flip it to check if the system is completely hung when waiting for upgrades
and also for marketing. Every Linux phone I had, someone was shocked/impressed to see the boot process in the terminal. Being able to "look under the hood" underscores how the phone holds no secrets and for whose benefit it's working, so it's not just the "linux nerd" angle. But ofc shwing off to nerds is an important benefit :)https://source.puri.sm/Librem5/OS-issues/-/issues/220sdcard reader going crazy2021-09-08T08:14:34ZGuido Gunthersdcard reader going crazyI had this in dmesg
```
[...many more of these...]
Sep 07 11:48:43 qwark pcscd[3204]: 00003221 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:48:43 qwark pcscd[3204]: 00153525 winscard.c:286:SCardConnect() Error Reader E...I had this in dmesg
```
[...many more of these...]
Sep 07 11:48:43 qwark pcscd[3204]: 00003221 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:48:43 qwark pcscd[3204]: 00153525 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:11 qwark pcscd[3204]: 27425605 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:11 qwark pcscd[3204]: 00002173 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:33 qwark pcscd[3204]: 22800482 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:33 qwark pcscd[3204]: 00002232 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:38 qwark pcscd[3204]: 05088978 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:38 qwark pcscd[3204]: 00002216 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:40 qwark pcscd[3204]: 02005644 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:49:40 qwark pcscd[3204]: 00002288 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:00 qwark pcscd[3204]: 19093702 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:00 qwark pcscd[3204]: 00002455 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:30 qwark pcscd[3204]: 30125936 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:30 qwark pcscd[3204]: 00002488 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:48 qwark pcscd[3204]: 18078614 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:48 qwark pcscd[3204]: 00002347 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:48 qwark pcscd[3204]: 00150329 winscard.c:286:SCardConnect() Error Reader Exclusive
Sep 07 11:50:59 qwark gpg-agent[4827]: scdaemon[4827]: ccid open error: skip
Sep 07 11:50:59 qwark gpg-agent[4827]: scdaemon[4827]: ccid open error: skip
Sep 07 11:50:59 qwark gpg-agent[4827]: scdaemon[4827]: ccid open error: skip
Sep 07 11:50:59 qwark gpg-agent[4825]: detected card with S/N D27600012401030300050000877F0000
```
and i don't even have a smart card inserted.
/cc @angus.ainsliehttps://source.puri.sm/Librem5/OS-issues/-/issues/222ssh stalls on IPv62021-10-03T17:55:59ZDorota Czaplejewiczssh stalls on IPv6Using a link-local connection from NetworkManager over USB:
```
ssh purism@fe80::18be:46be:45d6:951c%enp0s20u1i2
```
It works for a while, at least 15 seconds, and then it waits (for a lack of activity?) to stall. I'm not sure if anyth...Using a link-local connection from NetworkManager over USB:
```
ssh purism@fe80::18be:46be:45d6:951c%enp0s20u1i2
```
It works for a while, at least 15 seconds, and then it waits (for a lack of activity?) to stall. I'm not sure if anything else but SSH is affected, and not sure yet what's happening on the TCP level. New connections can be established no problem.https://source.puri.sm/Librem5/OS-issues/-/issues/225TECHGEAR Active Strike Pro Bluetooth keyboard - wrong char mappings2021-10-15T12:17:57ZMatthias ApitzTECHGEAR Active Strike Pro Bluetooth keyboard - wrong char mappings
I use a `TECHGEAR Active Strike Pro` BT keyboard which paires fine with my L5 and my Ubuntu mobile phone BQ E4.5, but the key layout does not work on the L5, mostly for upper case chars. I have here what the both devices give when typin...
I use a `TECHGEAR Active Strike Pro` BT keyboard which paires fine with my L5 and my Ubuntu mobile phone BQ E4.5, but the key layout does not work on the L5, mostly for upper case chars. I have here what the both devices give when typing the upper row of physical keys with SHIFT:
```
BQ device: ! " £ $ % ^ & * ( ) _ +
L5 device: ! " # $ % & / ( ) = ? ¡
```
With the Ubuntu devices it gives as chars what is printed on the physical keys.
I investigated a bit:
I used the X11 tool `xev` to sniff what the keys are generating, here only for the physical key which is labeled with `=` (lowercase) and `+` (uppercase):
```
DISPLAY=:0 xev | tee -a xev.out
```
This gives for the key `=` / `+`:
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 230474, (39,35), root:(39,67),
state 0x0, keycode 21 (keysym 0xbf, questiondown), same_screen YES,
XLookupString gives 2 bytes: (c2 bf) "¿"
XmbLookupString gives 2 bytes: (c2 bf) "¿"
XFilterEvent returns: False
```
and together with SHIFT:
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 269343, (39,35), root:(39,67),
state 0x1, keycode 21 (keysym 0xa1, exclamdown), same_screen YES,
XLookupString gives 2 bytes: (c2 a1) "¡"
XmbLookupString gives 2 bytes: (c2 a1) "¡"
XFilterEvent returns: False
```
If I now run:
```
DISPLAY=:0 xmodmap -e "keycode 21 = equal plus"
```
it gives:
```
KeyPress event, serial 32, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 348519, (39,35), root:(39,67),
state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
XLookupString gives 1 bytes: (3d) "="
XmbLookupString gives 1 bytes: (3d) "="
XFilterEvent returns: False
```
and togethet with SHIFT
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 376107, (39,35), root:(39,67),
state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
XKeysymToKeycode returns keycode: 35
XLookupString gives 1 bytes: (2b) "+"
XmbLookupString gives 1 bytes: (2b) "+"
XFilterEvent returns: False
```
i.e. the physical key gives what it has as labels on it. Ofc, this works only in any X11 application, for example, I tested the (new installed) xterm, but not in the terminal app of the L5.
So, the question (or bug) is: where in Debian / PureOS is the mapping of such BT keyboard (wrong)defined?https://source.puri.sm/Librem5/OS-issues/-/issues/231App launch splash missing for some apps2021-11-30T03:00:49ZElias RudbergApp launch splash missing for some appsReally appreciate the new app launch splash screen in phosh that is nowadays shown while an app is starting!
However there are some apps for which there is no splash, instead the default background is shown while they start.
Among the ...Really appreciate the new app launch splash screen in phosh that is nowadays shown while an app is starting!
However there are some apps for which there is no splash, instead the default background is shown while they start.
Among the default apps in Byzantium, the following seem to get no launch splash:
- Contacts
- Backups
- Chess
- Disks
- Files
- Geary
- King's Cross (the terminal app)
- Megapixels
- Text editor
- Weather
For the above I have never seen any launch splash. Then there are also a couple of apps for which the splash sometimes comes up briefly but most of the startup time is anyway without splash:
- PureOS Store
- Maps
I'm guessing these are two different cases, the first case where there is never any splash being due to some configuration missing for those apps, whereas in the second case there is a splash in principle but there is a timing problem. But that is just a guess.
Is there something that each app needs to do, in order to have a launch splash? (It looks like the splash is made from the app's icon and all the apps above have nice icons so in that way it seems possible to construct a splash from the existing info.)https://source.puri.sm/Librem5/OS-issues/-/issues/235calls' phone-call-GUI exits during a phone call2021-12-09T12:02:01ZMartin Kepplingercalls' phone-call-GUI exits during a phone callDuring a recent phone call, I noticed calls had closed the "ongoing phone call" GUI, the backlight went on (didn't turn off when near anymore) showning the calls app, but just the recent calls GUI - no indication that a phone call is act...During a recent phone call, I noticed calls had closed the "ongoing phone call" GUI, the backlight went on (didn't turn off when near anymore) showning the calls app, but just the recent calls GUI - no indication that a phone call is active - but I want still talking on the active call in this situation. After saying "bye" I rebooted because I couldn't hang up.
```
Dez 08 16:25:30 pureos ModemManager[739]: <info> [modem9/call2] user request to start call
Dez 08 16:25:30 pureos ModemManager[739]: <info> [modem9/call2] call state changed: unknown -> dialing (outgoing-started)
Dez 08 16:25:30 pureos ModemManager[739]: <info> [modem9/call2] call is started
Dez 08 16:25:32 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:32 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:34 pureos ModemManager[739]: <info> [modem9/call2] call state changed: dialing -> ringing-out (unknown)
Dez 08 16:25:34 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:34 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:34 pureos pulseaudio[801]: Configured maximum latency is smaller than latency, using latency instead
Dez 08 16:25:34 pureos pulseaudio[801]: Cannot set requested sink latency of 50,00 ms, adjusting to 100,00 ms
Dez 08 16:25:34 pureos pulseaudio[801]: Cannot set requested source latency of 50,00 ms, adjusting to 100,00 ms
Dez 08 16:25:36 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:36 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:38 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:38 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:40 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:40 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:42 pureos ModemManager[739]: <info> [modem9/call2] call state changed: ringing-out -> active (unknown)
Dez 08 16:25:42 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:42 pureos ModemManager[739]: <warn> [modem9] unexpected incoming call to number 'n/a' reported in call list: state active
Dez 08 16:25:42 pureos pulseaudio[801]: Configured maximum latency is smaller than latency, using latency instead
Dez 08 16:25:42 pureos pulseaudio[801]: Cannot set requested sink latency of 50,00 ms, adjusting to 100,00 ms
Dez 08 16:25:42 pureos pulseaudio[801]: Cannot set requested source latency of 50,00 ms, adjusting to 100,00 ms
Dez 08 16:25:42 pureos pulseaudio[801]: Configured latency of 200,00 ms is smaller than minimum latency, using minimum instead
Dez 08 16:25:42 pureos pulseaudio[801]: Cannot set requested source latency of 60,75 ms, adjusting to 100,00 ms
Dez 08 16:25:42 pureos pulseaudio[801]: Cannot set requested sink latency of 50,00 ms, adjusting to 100,00 ms
Dez 08 16:25:42 pureos pulseaudio[801]: Doing resync
Dez 08 16:25:42 pureos pulseaudio[801]: Playback too far ahead (7847), drop source 1504
Dez 08 16:25:42 pureos callaudiod[983]: no available input found!
Dez 08 16:25:42 pureos callaudiod[983]: no available output found!
Dez 08 16:25:42 pureos callaudiod[983]: no available input found!
Dez 08 16:25:43 pureos pulseaudio[801]: Playback too far ahead (9542), drop source 1832
Dez 08 16:25:44 pureos pulseaudio[801]: Playback too far ahead (9905), drop source 1900
Dez 08 16:25:45 pureos pulseaudio[801]: Playback too far ahead (9933), drop source 1904
Dez 08 16:25:46 pureos pulseaudio[801]: Playback too far ahead (10237), drop source 1964
Dez 08 16:25:47 pureos pulseaudio[801]: Playback too far ahead (9984), drop source 1916
Dez 08 16:25:48 pureos pulseaudio[801]: Playback too far ahead (9881), drop source 1896
Dez 08 16:25:49 pureos pulseaudio[801]: Playback too far ahead (9854), drop source 1888
Dez 08 16:25:50 pureos pulseaudio[801]: Playback too far ahead (10035), drop source 1924
Dez 08 16:25:51 pureos pulseaudio[801]: Playback too far ahead (10179), drop source 1952
Dez 08 16:25:52 pureos pulseaudio[801]: Playback too far ahead (10207), drop source 1956
Dez 08 16:25:53 pureos pulseaudio[801]: Playback too far ahead (9968), drop source 1912
Dez 08 16:25:54 pureos pulseaudio[801]: Playback too far ahead (9927), drop source 1904
Dez 08 16:25:55 pureos pulseaudio[801]: Playback too far ahead (9979), drop source 1912
Dez 08 16:25:56 pureos pulseaudio[801]: Playback too far ahead (9872), drop source 1892
Dez 08 16:25:57 pureos pulseaudio[801]: Playback too far ahead (9857), drop source 1892
Dez 08 16:25:58 pureos pulseaudio[801]: Playback too far ahead (10194), drop source 1956
Dez 08 16:25:59 pureos pulseaudio[801]: Playback too far ahead (10074), drop source 1932
Dez 08 16:26:00 pureos pulseaudio[801]: Playback too far ahead (9981), drop source 1916
Dez 08 16:26:01 pureos pulseaudio[801]: Playback too far ahead (9921), drop source 1904
Dez 08 16:26:02 pureos pulseaudio[801]: Playback too far ahead (9982), drop source 1916
Dez 08 16:26:03 pureos pulseaudio[801]: Playback too far ahead (10231), drop source 1964
Dez 08 16:26:04 pureos pulseaudio[801]: Playback too far ahead (9803), drop source 1880
Dez 08 16:26:05 pureos pulseaudio[801]: Playback too far ahead (10028), drop source 1924
Dez 08 16:26:06 pureos pulseaudio[801]: Playback too far ahead (9943), drop source 1908
Dez 08 16:26:07 pureos pulseaudio[801]: Playback too far ahead (10138), drop source 1944
Dez 08 16:26:08 pureos pulseaudio[801]: Playback too far ahead (9867), drop source 1892
Dez 08 16:26:09 pureos pulseaudio[801]: Playback too far ahead (10208), drop source 1956
Dez 08 16:26:10 pureos pulseaudio[801]: Playback too far ahead (9860), drop source 1892
Dez 08 16:26:11 pureos pulseaudio[801]: Playback too far ahead (10053), drop source 1928
Dez 08 16:26:12 pureos pulseaudio[801]: Playback too far ahead (10032), drop source 1924
Dez 08 16:26:13 pureos pulseaudio[801]: Playback too far ahead (10109), drop source 1940
Dez 08 16:26:14 pureos pulseaudio[801]: Playback too far ahead (10228), drop source 1960
Dez 08 16:26:15 pureos pulseaudio[801]: Playback too far ahead (9810), drop source 1880
Dez 08 16:26:16 pureos pulseaudio[801]: Playback too far ahead (9890), drop source 1896
Dez 08 16:26:17 pureos pulseaudio[801]: Playback too far ahead (9974), drop source 1912
Dez 08 16:26:18 pureos pulseaudio[801]: Playback too far ahead (9820), drop source 1884
Dez 08 16:26:19 pureos pulseaudio[801]: Playback too far ahead (10132), drop source 1944
Dez 08 16:26:20 pureos pulseaudio[801]: Playback too far ahead (10091), drop source 1936
Dez 08 16:26:21 pureos pulseaudio[801]: Playback too far ahead (10310), drop source 1976
Dez 08 16:26:22 pureos pulseaudio[801]: Playback too far ahead (9959), drop source 1912
Dez 08 16:26:23 pureos pulseaudio[801]: Playback too far ahead (9839), drop source 1888
Dez 08 16:26:24 pureos pulseaudio[801]: Playback too far ahead (10215), drop source 1960
Dez 08 16:26:25 pureos pulseaudio[801]: Playback too far ahead (9978), drop source 1912
Dez 08 16:26:26 pureos pulseaudio[801]: Playback too far ahead (9811), drop source 1880
Dez 08 16:26:27 pureos pulseaudio[801]: Playback too far ahead (10006), drop source 1920
Dez 08 16:26:35 pureos pulseaudio[801]: Playback after capture (-21), drop sink 88
Dez 08 16:40:31 pureos kernel: usb 1-1.2: reset high-speed USB device number 12 using xhci-hcd
Dez 08 16:40:31 pureos kernel: usb 1-1.2: USB disconnect, device number 12
Dez 08 16:40:31 pureos kernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Dez 08 16:40:31 pureos kernel: option 1-1.2:1.0: device disconnected
Dez 08 16:40:31 pureos kernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Dez 08 16:40:31 pureos kernel: option 1-1.2:1.1: device disconnected
Dez 08 16:40:31 pureos kernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Dez 08 16:40:31 pureos kernel: option 1-1.2:1.2: device disconnected
Dez 08 16:40:31 pureos kernel: option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Dez 08 16:40:31 pureos kernel: option 1-1.2:1.3: device disconnected
Dez 08 16:40:31 pureos kernel: qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device
Dez 08 16:40:31 pureos ModemManager[739]: Cannot read from istream: connection broken
Dez 08 16:40:31 pureos systemd-networkd[393]: wwan0: Link DOWN
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] QMI endpoint hangup: removed
Dez 08 16:40:31 pureos systemd-networkd[393]: wwan0: Lost carrier
Dez 08 16:40:31 pureos ModemManager[739]: <info> [modem9] connection to qmi-proxy for /dev/cdc-wdm0 lost, reprobing
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'wds' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'wds' client with ID '2'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'wds' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'wds' client with ID '1'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'voice' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'voice' client with ID '2'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'pdc' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'pdc' client with ID '1'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'loc' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'loc' client with ID '1'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'uim' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'uim' client with ID '1'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'wms' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'wms' client with ID '1'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'nas' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'nas' client with ID '1'
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'dms' client with flags 'release-cid'...
Dez 08 16:40:31 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'dms' client with ID '1'
Dez 08 16:40:31 pureos NetworkManager[512]: <info> [1638978031.8642] device (cdc-wdm0): state change: activated -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Dez 08 16:40:31 pureos NetworkManager[512]: <info> [1638978031.8775] manager: NetworkManager state is now DISCONNECTED
Dez 08 16:40:31 pureos upowerd[888]: treating change event as add on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
Dez 08 16:40:31 pureos NetworkManager[512]: <warn> [1638978031.9310] dns-sd-resolved[e60865f5b37d4772]: send-updates SetLinkDomains@11 failed: GDBus.Error:org.freedesktop.resolve1.NoSuchLink: Link 11 not known
Dez 08 16:40:31 pureos ModemManager[739]: <info> [base-manager] port ttyUSB2 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Dez 08 16:40:31 pureos ModemManager[739]: <info> [base-manager] port ttyUSB1 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Dez 08 16:40:31 pureos ModemManager[739]: <info> [base-manager] port ttyUSB0 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Dez 08 16:40:31 pureos kernel: usb 1-1.2: new high-speed USB device number 13 using xhci-hcd
Dez 08 16:40:31 pureos ModemManager[739]: <info> [base-manager] port ttyUSB3 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Dez 08 16:40:32 pureos ModemManager[739]: <info> [base-manager] port cdc-wdm0 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Dez 08 16:40:32 pureos dbus-daemon[511]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=512 comm="/usr/sbin/NetworkManager --no-daemon ")
Dez 08 16:40:32 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
Dez 08 16:40:32 pureos kernel: usb 1-1.2: New USB device found, idVendor=2020, idProduct=2060, bcdDevice= 0.00
Dez 08 16:40:32 pureos kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Dez 08 16:40:32 pureos kernel: usb 1-1.2: Product: Qualcomm CDMA Technologies MSM
Dez 08 16:40:32 pureos kernel: usb 1-1.2: Manufacturer: Qualcomm, Incorporated
Dez 08 16:40:32 pureos ModemManager[739]: <info> [base-manager] port wwan0 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Dez 08 16:40:32 pureos NetworkManager[512]: <warn> [1638978032.0956] modem-broadband[cdc-wdm0]: failed to disconnect modem: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.ModemManager1.Modem.Simple” on object at path /org/freedesktop/ModemManager1/Modem/9
Dez 08 16:40:32 pureos kernel: option 1-1.2:1.0: GSM modem (1-port) converter detected
Dez 08 16:40:32 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
Dez 08 16:40:32 pureos kernel: option 1-1.2:1.1: GSM modem (1-port) converter detected
Dez 08 16:40:32 pureos dbus-daemon[511]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dez 08 16:40:32 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
Dez 08 16:40:32 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
Dez 08 16:40:32 pureos kernel: option 1-1.2:1.2: GSM modem (1-port) converter detected
Dez 08 16:40:32 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
Dez 08 16:40:32 pureos kernel: option 1-1.2:1.3: GSM modem (1-port) converter detected
Dez 08 16:40:32 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
Dez 08 16:40:32 pureos kernel: qmi_wwan 1-1.2:1.4: cdc-wdm0: USB WDM device
Dez 08 16:40:32 pureos kernel: qmi_wwan 1-1.2:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.4.auto-1.2, WWAN/QMI device, ea:e0:5a:59:fb:14
Dez 08 16:40:32 pureos upowerd[888]: treating change event as add on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
Dez 08 16:40:32 pureos mtp-probe[5658]: checking bus 1, device 13: "/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2"
Dez 08 16:40:32 pureos mtp-probe[5658]: bus: 1, device: 13 was not an MTP device
Dez 08 16:40:32 pureos upowerd[888]: treating change event as add on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
Dez 08 16:40:32 pureos systemd-udevd[5641]: Using default interface naming scheme 'v247'.
Dez 08 16:40:32 pureos systemd-udevd[5641]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dez 08 16:40:32 pureos gnome-calls[1203]: Error hanging up ModemManager call to `+43XXXXXXXXX': GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.ModemManager1.Call” on object at path /org/freedesktop/ModemManager1/Call/2
Dez 08 16:40:32 pureos mtp-probe[5694]: checking bus 1, device 13: "/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2"
Dez 08 16:40:32 pureos mtp-probe[5694]: bus: 1, device: 13 was not an MTP device
Dez 08 16:40:33 pureos goa-daemon[859]: goa_http_client_check() failed: 2 — Fehler beim Auflösen von »cloud.puri.sm«: Der Name oder der Dienst ist nicht bekannt
Dez 08 16:40:33 pureos goa-daemon[859]: /org/gnome/OnlineAccounts/Accounts/account_1638277513_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: Ungültiges Passwort für Benutzer »martin.kepplinger@puri.sm« (goa-error-quark, 0): Rechnername konnte nicht aufgelöst werden (goa-error-quark, 4)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] Opening device with flags 'version-info, proxy'...
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] created endpoint
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] Checking version info (25 retries)...
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] QMI Device supports 27 services:
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] ctl (1.5)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] wds (1.67)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] dms (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] nas (1.25)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] qos (1.12)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] wms (1.10)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] auth (1.3)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] at (1.4)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] voice (2.1)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] cat2 (2.24)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] uim (1.46)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] pbm (1.4)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] test (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] loc (2.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] sar (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] csd (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] ts (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] tmd (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] wda (1.16)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] csvt (1.1)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] coex (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] pdc (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] rfrpe (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] dsd (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] unknown [0x2d] (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] unknown [0x30] (1.0)
Dez 08 16:40:33 pureos ModemManager[739]: [/dev/cdc-wdm0] unknown [0x36] (1.0)
Dez 08 16:40:34 pureos goa-daemon[859]: goa_http_client_check() failed: 2 — Fehler beim Auflösen von »cloud.puri.sm«: Der Name oder der Dienst ist nicht bekannt
Dez 08 16:40:34 pureos ModemManager[739]: <info> [device /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2] creating modem with plugin 'broadmobi' and '6' ports
Dez 08 16:40:34 pureos ModemManager[739]: <info> [base-manager] modem for device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2' successfully created
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Opening device with flags 'version-info, proxy'...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] created endpoint
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Checking version info (25 retries)...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] QMI Device supports 27 services:
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] ctl (1.5)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] wds (1.67)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] dms (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] nas (1.25)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] qos (1.12)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] wms (1.10)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] auth (1.3)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] at (1.4)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] voice (2.1)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] cat2 (2.24)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] uim (1.46)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] pbm (1.4)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] test (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] loc (2.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] sar (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] csd (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] ts (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] tmd (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] wda (1.16)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] csvt (1.1)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] coex (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] pdc (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] rfrpe (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] dsd (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] unknown [0x2d] (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] unknown [0x30] (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] unknown [0x36] (1.0)
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'wda' (version 1.16) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'wda' client with flags 'release-cid'...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'wda' client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'dms' (version 1.0) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'nas' (version 1.25) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'wms' (version 1.10) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'uim' (version 1.46) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'loc' (version 2.0) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'pdc' (version 1.0) client with ID '1'
Dez 08 16:40:34 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'voice' (version 2.1) client with ID '2'
Dez 08 16:40:35 pureos ModemManager[739]: <warn> [modem10/sim9] couldn't load list of emergency numbers: uninitialized emergency numbers list
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] state changed (unknown -> disabled)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3078] modem["cdc-wdm0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3100] manager: (cdc-wdm0): new Broadband device (/org/freedesktop/NetworkManager/Devices/12)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3130] device (cdc-wdm0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3188] device (cdc-wdm0): modem state 'enabling'
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3262] device (cdc-wdm0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3300] policy: auto-activating connection 'HoT' (c9aa442f-4ae3-4752-974d-6208792de208)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3343] device (cdc-wdm0): Activation: starting connection 'HoT' (c9aa442f-4ae3-4752-974d-6208792de208)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3360] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.3402] manager: NetworkManager state is now CONNECTING
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] state changed (disabled -> enabling)
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] simple connect started...
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] simple connect state (4/8): wait to get fully enabled
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'wds' (version 1.67) client with ID '1'
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Releasing 'wds' client with flags 'release-cid'...
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Unregistered 'wds' client with ID '1'
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] state changed (enabling -> enabled)
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] simple connect state (5/8): register
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] simple connect state (6/8): bearer
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] simple connect state (7/8): connect
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] state changed (enabled -> connecting)
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.7407] modem["cdc-wdm0"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested)
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] 3GPP registration state changed (unknown -> registering)
Dez 08 16:40:35 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'wds' (version 1.67) client with ID '1'
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] 3GPP registration state changed (registering -> home)
Dez 08 16:40:35 pureos ModemManager[739]: <info> [modem10] state changed (connecting -> registered)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.7538] modem["cdc-wdm0"]: modem state changed, 'enabled' --> 'connecting' (reason: user-requested)
Dez 08 16:40:35 pureos NetworkManager[512]: <info> [1638978035.7796] modem["cdc-wdm0"]: modem state changed, 'connecting' --> 'registered' (reason: unknown)
Dez 08 16:40:37 pureos ModemManager[739]: <info> [modem10/bearer8] QMI IPv4 Settings:
Dez 08 16:40:37 pureos ModemManager[739]: <info> [modem10/bearer8] address: 10.72.154.218/30
Dez 08 16:40:37 pureos ModemManager[739]: <info> [modem10/bearer8] gateway: 10.72.154.217
Dez 08 16:40:37 pureos ModemManager[739]: <info> [modem10/bearer8] DNS #1: 213.162.70.25
Dez 08 16:40:37 pureos ModemManager[739]: <info> [modem10/bearer8] DNS #2: 213.162.70.9
Dez 08 16:40:37 pureos ModemManager[739]: <info> [modem10/bearer8] MTU: 1500
Dez 08 16:40:37 pureos ModemManager[739]: [/dev/cdc-wdm0] Allocating new client ID...
Dez 08 16:40:38 pureos ModemManager[739]: [/dev/cdc-wdm0] Registered 'wds' (version 1.67) client with ID '2'
Dez 08 16:40:40 pureos ModemManager[739]: <info> [modem10/bearer8] couldn't start network: QMI protocol error (14): 'CallFailed'
Dez 08 16:40:40 pureos ModemManager[739]: <info> [modem10/bearer8] call end reason (1): generic-unspecified
Dez 08 16:40:40 pureos ModemManager[739]: <info> [modem10/bearer8] verbose call end reason (6,50): [3gpp] ipv4-only-allowed
Dez 08 16:40:40 pureos ModemManager[739]: <info> [modem10] state changed (registered -> connected)
Dez 08 16:40:40 pureos ModemManager[739]: <info> [modem10] simple connect state (8/8): all done
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1484] modem["cdc-wdm0"]: modem state changed, 'registered' --> 'connected' (reason: user-requested)
Dez 08 16:40:40 pureos systemd-networkd[393]: wwan0: Link UP
Dez 08 16:40:40 pureos systemd-networkd[393]: wwan0: Gained carrier
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1688] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1715] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1727] modem["cdc-wdm0"]: IPv6 configuration disabled
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1729] modem-broadband[cdc-wdm0]: IPv4 static configuration:
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1730] modem-broadband[cdc-wdm0]: address 10.72.154.218/30
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1731] modem-broadband[cdc-wdm0]: gateway 10.72.154.217
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1731] modem-broadband[cdc-wdm0]: DNS 213.162.70.25
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1732] modem-broadband[cdc-wdm0]: DNS 213.162.70.9
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1732] modem-broadband[cdc-wdm0]: MTU 1500
Dez 08 16:40:40 pureos systemd-timesyncd[478]: Network configuration changed, trying to establish connection.
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.1966] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2183] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2197] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2308] manager: NetworkManager state is now CONNECTED_LOCAL
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2425] manager: NetworkManager state is now CONNECTED_SITE
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2445] policy: set 'HoT' (wwan0) as default for IPv4 routing and DNS
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2495] device (cdc-wdm0): Activation: successful, device activated.
Dez 08 16:40:40 pureos NetworkManager[512]: <info> [1638978040.2537] manager: NetworkManager state is now CONNECTED_GLOBAL
Dez 08 16:40:40 pureos geoclue[1109]: Failed to query location: Error resolving “location.services.mozilla.com”: Der Name oder der Dienst ist nicht bekannt
Dez 08 16:40:44 pureos goa-daemon[859]: /org/gnome/OnlineAccounts/Accounts/account_1638277513_0: Setting AttentionNeeded to FALSE because EnsureCredentials() succeded
```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/243Telegram-deskop will not sign in due to old version (2.6)2021-12-29T22:18:42ZChris TalbotTelegram-deskop will not sign in due to old version (2.6)PureOS Byzantium has version Telegram-desktop 2.6, which Telegram considers "Old". Telegram will not allow it to sign in due to this.
Please update Telegram-Desktop to 3.1. Debian has it backported for Bullseye (which I think Byzantium ...PureOS Byzantium has version Telegram-desktop 2.6, which Telegram considers "Old". Telegram will not allow it to sign in due to this.
Please update Telegram-Desktop to 3.1. Debian has it backported for Bullseye (which I think Byzantium targets).https://source.puri.sm/Librem5/OS-issues/-/issues/250Autoremove old kernels2022-02-22T13:15:59ZGuido GuntherAutoremove old kernelsIf we don't `/boot` will run out of space at some point.If we don't `/boot` will run out of space at some point.https://source.puri.sm/Librem5/OS-issues/-/issues/255Please update libc-ares2 to 1.18.12022-07-08T03:05:18ZChris TalbotPlease update libc-ares2 to 1.18.1PureOS has `1.17` of libc-ares2 (which is in line with Debian Bullseye). However, there is a particularly annnoying bug in it that makes it not able to resolve DNS issues for `mmsd-tng`, the error looks like:
```
** (mmsdtng:1853): CRIT...PureOS has `1.17` of libc-ares2 (which is in line with Debian Bullseye). However, there is a particularly annnoying bug in it that makes it not able to resolve DNS issues for `mmsd-tng`, the error looks like:
```
** (mmsdtng:1853): CRITICAL **: 16:04:19.376: Failed to resolve host: Misformatted domain name
** (mmsdtng:1853): WARNING **: 16:04:19.376: Failed to resolve 'proxy.mobile.att.net'
```
I would like to move to the default DNS backend to c-ares for `mmsd-tng`, but this would break MMS for PureOS due to this bug. This bug looks to be fixed in `1.18.1` (as I installed it from Debian Bookworm and the bug did not occur.).
lib-cares2 is pretty self-contained, so no other packages need to be updated for it.
As such, could we update `lib-cares` to `1.18.1`?https://source.puri.sm/Librem5/OS-issues/-/issues/257Enable zram by default2022-04-13T07:27:04ZJan VlugEnable zram by defaultI set up the L5 with a docking station with an external display and tried to use a browser.
The browser did not work however, probably because lack of memory.
When I enabled zram as described in this [blog](https://puri.sm/posts/my-first...I set up the L5 with a docking station with an external display and tried to use a browser.
The browser did not work however, probably because lack of memory.
When I enabled zram as described in this [blog](https://puri.sm/posts/my-first-year-of-librem-5-convergence/), the browser worked fine.
I suggest to enable zram by default to improve the user experience and usability of the L5.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)https://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/277No Bluetooth Found in GNOME Settings2022-07-04T17:01:58ZJan VlugNo Bluetooth Found in GNOME SettingsOn my fully up-to-date Librem 5 Bluetooth is not found in GNOME Settings:
![2022-07-03-144658](/uploads/3aace50705647a9e7265e95343df3c93/2022-07-03-144658.png)
I had a quick look at this [forum thread](https://forums.puri.sm/t/bluetoot...On my fully up-to-date Librem 5 Bluetooth is not found in GNOME Settings:
![2022-07-03-144658](/uploads/3aace50705647a9e7265e95343df3c93/2022-07-03-144658.png)
I had a quick look at this [forum thread](https://forums.puri.sm/t/bluetooth-support-for-librem-5/14965).
This is the content of my /lib/firmware directory:
```
root@avalon:~# ls -l /lib/firmware
total 16
lrwxrwxrwx 1 root root 31 Sep 11 2021 regulatory.db -> /etc/alternatives/regulatory.db
-rw-r--r-- 1 root root 3764 Jun 30 2020 regulatory.db-debian
-rw-r--r-- 1 root root 3764 Jun 30 2020 regulatory.db-upstream
lrwxrwxrwx 1 root root 35 Sep 11 2021 regulatory.db.p7s -> /etc/alternatives/regulatory.db.p7s
-rw-r--r-- 1 root root 1249 Jun 30 2020 regulatory.db.p7s-debian
-rw-r--r-- 1 root root 1182 Jun 30 2020 regulatory.db.p7s-upstream
```
Here is the output of `dmesg | grep redpine`: [redpine_dmesg.txt](/uploads/8527209cec1ea78f3f817d28b285fa3b/redpine_dmesg.txt). I disabled Wifi/Bluetooth and enabled it again with the kill switch in the time span covered by this file.https://source.puri.sm/Librem5/OS-issues/-/issues/278Images installed with librem5-flash-image do not include systemd-timesyncd2022-07-07T13:38:26ZChris TalbotImages installed with librem5-flash-image do not include systemd-timesyncdThe images installed with: https://source.puri.sm/Librem5/librem5-flash-image do not include `systemd-timesyncd`. As a result, the phone does not sync to an NTP server and `Automatic Time & Date` does not appear in g-c-c as an option. It...The images installed with: https://source.puri.sm/Librem5/librem5-flash-image do not include `systemd-timesyncd`. As a result, the phone does not sync to an NTP server and `Automatic Time & Date` does not appear in g-c-c as an option. It alsso makes for a frustrating experience as many things e.g. apt depend on the corrrect date and time, else one gets errors related to expired certs.
Once installed, the time and date sync and `Automatic Time & Date` appears in g-c-c as an option
Please install `systemd-timesyncd` as a default.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/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/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/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/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/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/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/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/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/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.