Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2020-07-06T06:46:18Zhttps://source.puri.sm/Librem5/gnome-software/-/issues/35provide update information similar to `apt-listchanges`2020-07-06T06:46:18ZGuido Guntherprovide update information similar to `apt-listchanges`it'd be nice to also (optionally) display chanelogs and news files past download and prior to installation/reboot preparationit'd be nice to also (optionally) display chanelogs and news files past download and prior to installation/reboot preparationhttps://source.puri.sm/Librem5/OS-issues/-/issues/154screenshot app icon not appearing for GNOME-20482020-07-04T13:32:15ZTodd Weaverscreenshot app icon not appearing for GNOME-2048
# What problem did you encounter
One app, GNOME-2048, shows an icon on the app screen, but not the app-screenshot area.
## What is the actual behaviour?
App icon missing
## What is the expected behaviour?
App icon showing
## How t...
# What problem did you encounter
One app, GNOME-2048, shows an icon on the app screen, but not the app-screenshot area.
## What is the actual behaviour?
App icon missing
## What is the expected behaviour?
App icon showing
## How to reproduce
Install gnome-2048
see the app icon in the apps available
launch it
don't see the app icon in the app-screenshot list
![purism-librem-5-birch-gnome-2048-icon-2020-07-03](/uploads/aa5d54f2a876d6a92e27669ad73b448d/purism-librem-5-birch-gnome-2048-icon-2020-07-03.webm)
# What hardware are you running on?
Librem 5 Birch
# Relevant OS information
```
purism@l5b:~$ dpkg -s phosh | grep Version
Version: 0.4.0
purism@l5b:~$ dpkg -s gnome-2048 | grep Version
Version: 3.34.2+487+git436f4bf-1pureos0
purism@l5b:~$ dpkg -s phoc | grep Version
Version: 0.4.0
purism@l5b:~$ uname -a
Linux l5b 5.7.0-1-librem5 #1 SMP PREEMPT Wed Jun 24 08:36:30 UTC 2020 aarch64 GNU/Linux
purism@l5b:~$
```https://source.puri.sm/Librem5/OS-issues/-/issues/153Low disk space on "boot"2023-03-31T13:52:07ZTodd WeaverLow disk space on "boot"# What problem did you encounter
Low disk space on "boot" during upgrade
## What is the actual behaviour?
Warning (and failure to finish update) of "Low disk space on "boot""
## What is the expected behaviour?
that boot has enough s...# What problem did you encounter
Low disk space on "boot" during upgrade
## What is the actual behaviour?
Warning (and failure to finish update) of "Low disk space on "boot""
## What is the expected behaviour?
that boot has enough space for upgrades
## How to reproduce
Do enough upgrades to fill up /boot
try to upgrade
# What hardware are you running on?
Librem 5 Birch
# Relevant OS information
## Which kernel are you using?
```
Linux l5b 5.6.0-2-librem5 #1 SMP PREEMPT Fri Apr 17 15:20:46 UTC 2020 aarch64 GNU/Linux
purism@l5b:~$ cat /etc/os-release
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
VERSION_ID=9.0
VERSION_CODENAME=amber
HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"
LOGO=pureos-logo-icon
purism@l5b:~$
```
## Any other information that may be helpful?
![birch-full-boot-disk-2020-07-03](/uploads/40aee0006590568160b2325b39e76901/birch-full-boot-disk-2020-07-03.jpeg)
```
purism@l5b:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1330760 0 1330760 0% /dev
tmpfs 300108 1272 298836 1% /run
/dev/mmcblk0p2 29804304 11161724 17385560 40% /
tmpfs 1500528 24 1500504 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 1500528 0 1500528 0% /sys/fs/cgroup
/dev/mmcblk0p1 179489 179487 0 100% /boot
tmpfs 300104 8108 291996 3% /run/user/1000
purism@l5b:~$ ls -l /boot
total 177595
-rw-r--r-- 1 root root 2311 Jun 18 13:33 boot.scr
-rw-r--r-- 1 root root 2312 Mar 13 15:27 boot.scr.bak
-rw-r--r-- 1 root root 158849 Nov 29 2019 config-5.3.0-librem5-g24b9d535b
-rw-r--r-- 1 root root 158849 Nov 26 2019 config-5.3.0-librem5-gaca00a721
-rw-r--r-- 1 root root 163512 Mar 4 00:49 config-5.3.0-librem5-h1
-rw-r--r-- 1 root root 170194 Apr 9 03:54 config-5.6.0-2-librem5
-rw-r--r-- 1 root root 169992 Jun 23 11:31 config-5.7.0-1-librem5
lrwxrwxrwx 1 root root 41 Jun 18 13:33 dtb -> dtbs/5.6.0-2-librem5/./imx8mq-librem5.dtb
lrwxrwxrwx 1 root root 50 Dec 3 2019 dtb-5.3.0-librem5-g24b9d535b -> dtbs/5.3.0-librem5-g24b9d535b/./imx8mq-librem5.dtb
lrwxrwxrwx 1 root root 50 Dec 3 2019 dtb-5.3.0-librem5-gaca00a721 -> dtbs/5.3.0-librem5-gaca00a721/./imx8mq-librem5.dtb
lrwxrwxrwx 1 root root 42 Mar 13 15:27 dtb-5.3.0-librem5-h1 -> dtbs/5.3.0-librem5-h1/./imx8mq-librem5.dtb
lrwxrwxrwx 1 root root 41 Jun 18 13:33 dtb-5.6.0-2-librem5 -> dtbs/5.6.0-2-librem5/./imx8mq-librem5.dtb
drwxr-xr-x 7 root root 1024 Jul 3 16:05 dtbs
-rw-r--r-- 1 root root 17377792 Jun 18 13:33 Image
-rw-r--r-- 1 root root 8245248 Jul 3 16:05 Image.tmp
-rw-r--r-- 1 root root 11095791 Jun 18 13:33 initrd.img
-rw-r--r-- 1 root root 10928763 Dec 3 2019 initrd.img-5.3.0-librem5-g24b9d535b
-rw-r--r-- 1 root root 10928861 Nov 27 2019 initrd.img-5.3.0-librem5-gaca00a721
-rw-r--r-- 1 root root 10132662 Mar 13 15:27 initrd.img-5.3.0-librem5-h1
-rw-r--r-- 1 root root 11095791 Jun 18 13:33 initrd.img-5.6.0-2-librem5
-rw-r--r-- 1 root root 10132662 Mar 13 15:27 initrd.img.bak
drwx------ 2 root root 12288 Nov 26 2019 lost+found
-rw-r--r-- 1 root root 3721945 Nov 29 2019 System.map-5.3.0-librem5-g24b9d535b
-rw-r--r-- 1 root root 3721945 Nov 26 2019 System.map-5.3.0-librem5-gaca00a721
-rw-r--r-- 1 root root 3909700 Mar 4 00:49 System.map-5.3.0-librem5-h1
-rw-r--r-- 1 root root 4512954 Apr 9 03:54 System.map-5.6.0-2-librem5
-rw-r--r-- 1 root root 4519422 Jun 23 11:31 System.map-5.7.0-1-librem5
-rw-r--r-- 1 root root 17377792 Jun 18 13:33 vmlinuz
-rw-r--r-- 1 root root 6779212 Nov 29 2019 vmlinuz-5.3.0-librem5-g24b9d535b
-rw-r--r-- 1 root root 6779201 Nov 26 2019 vmlinuz-5.3.0-librem5-gaca00a721
-rw-r--r-- 1 root root 7168658 Mar 4 00:49 vmlinuz-5.3.0-librem5-h1
-rw-r--r-- 1 root root 7589897 Apr 9 03:54 vmlinuz-5.6.0-2-librem5
-rw-r--r-- 1 root root 7631112 Jun 23 11:31 vmlinuz-5.7.0-1-librem5
-rw-r--r-- 1 root root 16611840 Mar 13 15:27 vmlinuz.bak
purism@l5b:~$
```https://source.puri.sm/Librem5/linux/-/issues/199dwc3 hangs in dwc3_gadget_exit2020-07-06T06:12:06ZAngus Ainslieangus.ainslie@puri.smdwc3 hangs in dwc3_gadget_exitThe gadget driver hangs the dwc3 on exit
```
[ 242.643914] INFO: task kworker/3:1:38 blocked for more than 120 seconds.
[ 242.650815] Not tainted 5.7.5-librem5-00029-g90e07e6bedfb-dirty #217
[ 242.657971] "echo 0 > /proc/sys/k...The gadget driver hangs the dwc3 on exit
```
[ 242.643914] INFO: task kworker/3:1:38 blocked for more than 120 seconds.
[ 242.650815] Not tainted 5.7.5-librem5-00029-g90e07e6bedfb-dirty #217
[ 242.657971] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 242.665909] kworker/3:1 D 0 38 2 0x00000028
[ 242.666156] Workqueue: events_freezable __dwc3_set_mode [dwc3]
[ 242.666189] Call trace:
[ 242.666273] __switch_to+0xf4/0x148
[ 242.666332] __schedule+0x2c0/0x658
[ 242.666345] schedule+0x50/0x110
[ 242.666432] gserial_free_port+0xb0/0x100 [u_serial]
[ 242.666449] gserial_free_line+0x70/0xb8 [u_serial]
[ 242.666506] acm_free_instance+0x24/0x40 [usb_f_acm]
[ 242.666724] usb_put_function_instance+0x2c/0x48 [libcomposite]
[ 242.666784] multi_unbind+0x40/0x70 [g_multi]
[ 242.666808] __composite_unbind+0x90/0xf0 [libcomposite]
[ 242.666834] composite_unbind+0x1c/0x28 [libcomposite]
[ 242.666994] usb_gadget_remove_driver+0x44/0xa0 [udc_core]
[ 242.667018] usb_del_gadget_udc+0x70/0xe0 [udc_core]
[ 242.667060] dwc3_gadget_exit+0x24/0x78 [dwc3]
[ 242.667081] __dwc3_set_mode+0xd0/0x264 [dwc3]
[ 242.667136] process_one_work+0x1c8/0x488
[ 242.667149] worker_thread+0x54/0x430
[ 242.667182] kthread+0x11c/0x150
[ 242.667203] ret_from_fork+0x10/0x1c
```https://source.puri.sm/Librem5/linux/-/issues/198redpine: Bluetooth and wifi exclusive2020-07-05T12:59:00ZGuido Guntherredpine: Bluetooth and wifi exclusiveit seems i can only have one, when i turn on BT the wifi connection drops when i turn it off wifi comes back.it seems i can only have one, when i turn on BT the wifi connection drops when i turn it off wifi comes back.https://source.puri.sm/Librem5/OS-issues/-/issues/152Clipboard paste notifications2020-07-03T02:08:21ZSebastian KrzyszkowiakClipboard paste notificationsThe newest iOS version has introduced a notification bubble that tells the user when some application reaches for the clipboard's content - in turn, some popular apps have been caught on using the clipboard's content for no apparent reas...The newest iOS version has introduced a notification bubble that tells the user when some application reaches for the clipboard's content - in turn, some popular apps have been caught on using the clipboard's content for no apparent reason.
In might be good to consider adding a similar feature to phoc and phosh.https://source.puri.sm/Librem5/purple-mm-sms/-/issues/15Incoming SMS not handled, PDU type "cdma-deliver"2020-10-02T07:39:33ZSalem ElrahalIncoming SMS not handled, PDU type "cdma-deliver"I have a 4G connection with Verizon in US, am getting the following logs and no SMS message in chatty:
```
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.247: pur_mm_get_new_sms path /org/freedesktop/ModemManager1/SMS/10
(sm.puri.Chatty:...I have a 4G connection with Verizon in US, am getting the following logs and no SMS message in chatty:
```
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.247: pur_mm_get_new_sms path /org/freedesktop/ModemManager1/SMS/10
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.247: cb_dbus_signal_sms_added: New SMS at /org/freedesktop/ModemManager1/SMS/10
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.306: PDU type not handled
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.307: pur_mm_check_pdu_type: pdu type cdma-deliver
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.307: cb_sms_list_new_ready
```
I guess this PDU type is not mapped/supported here:
https://source.puri.sm/Librem5/purple-mm-sms/-/blob/master/mm-sms.c#L585https://source.puri.sm/Librem5/debs/ModemManager/-/issues/38please move to https://source.puri.sm/Librem5/debs/ModemManager2020-07-14T15:14:01ZGuido Guntherplease move to https://source.puri.sm/Librem5/debs/ModemManagerthe intention is to separate things that are clean Debian backports (plus occasional patches in `debian/patches`) from our upstream work and from the sloppy build (mostly used by for GNOME stuff) this makes it easier to track things
Sa...the intention is to separate things that are clean Debian backports (plus occasional patches in `debian/patches`) from our upstream work and from the sloppy build (mostly used by for GNOME stuff) this makes it easier to track things
Same goes for libqmi/mbim. Moving the repo and adjusting `deb-build-jobs` should do the trick (jenkins sometimes fails to recognize the repo move but i can handle that once done)https://source.puri.sm/Librem5/debs/ModemManager/-/issues/37Failed to place phone call2021-01-11T17:05:45ZGuido GuntherFailed to place phone callThis is MM from `1.14.0+6935+gitac0606d2-1pureos0`
placing a phone call did not get the ring tone (while previous MM version worked), hanging up gave
This is MM from `1.14.0+6935+gitac0606d2-1pureos0`
placing a phone call with that ve...This is MM from `1.14.0+6935+gitac0606d2-1pureos0`
placing a phone call did not get the ring tone (while previous MM version worked), hanging up gave
This is MM from `1.14.0+6935+gitac0606d2-1pureos0`
placing a phone call with that version gave
```
placing a phone call did not get the ring tone (while previous MM version worked), hanging up gave
ul 02 10:36:08 pureos ModemManager[496]: <info> [modem1/call0] call state changed: unknown -> dialing (outgoing-started)
Jul 02 10:36:08 pureos calls[829]: ########################################################
Jul 02 10:36:08 pureos calls[829]: ########################################################
Jul 02 10:36:08 pureos calls[829]: ############ THIS CALLS CONTAINS UGLY HACKS ############
Jul 02 10:36:08 pureos calls[829]: ########################################################
Jul 02 10:36:08 pureos calls[829]: ########################################################
Jul 02 10:36:12 pureos wpa_supplicant[475]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-46 noise=9999 txrate=1000
Jul 02 10:36:33 pureos calls[829]: Error starting outgoing call ModemManager call to `017610246822': Zeitüberschreitung wurde erreicht
Jul 02 10:36:38 pureos ModemManager[496]: <info> [modem1/call0] user request to hangup call
Jul 02 10:36:41 pureos ModemManager[496]: <info> [modem1/call0] user request to hangup call
Jul 02 10:37:38 pureos ModemManager[496]: <warn> [modem1/call0] couldn't start call: Serial command timed out
Jul 02 10:37:38 pureos ModemManager[496]: <info> [modem1/call0] call state changed: dialing -> terminated (unknown)
Jul 02 10:37:38 pureos ModemManager[496]: <warn> [modem1] port ttyUSB1 timed out 2 consecutive times
Jul 02 10:37:38 pureos kernel: etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
Jul 02 10:37:55 pureos ModemManager[496]: <warn> [modem1] port ttyUSB1 timed out 9 consecutive times
Jul 02 10:37:57 pureos ModemManager[496]: <warn> [modem1/call1] couldn't start call: AT command was cancelled
Jul 02 10:37:57 pureos ModemManager[496]: <info> [modem1/call1] call state changed: dialing -> terminated (error)
Jul 02 10:37:57 pureos ModemManager[496]: <warn> [modem1] cannot update in-call state: missing internal call list
Jul 02 10:37:57 pureos ModemManager[496]: <warn> [modem1] couldn't load call list: AT command was cancelled
Jul 02 10:37:57 pureos calls[829]: Error starting outgoing call ModemManager call to `017610246822': GDBus.Error:org.freedesktop.ModemManager1.Error.Connection.NoDialtone: No dialtone
```
Modemmanager then gave up
```
# mmcli -L
No modems were found
```
although the device is still on the bus
```
# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 2020:2060
Bus 001 Device 003: ID 0424:4041 Standard Microsystems Corp. Hub and media card controller
Bus 001 Device 002: ID 0424:2640 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
i'm using the default hub suspend we currently ship.https://source.puri.sm/Librem5/Apps_Issues/-/issues/191Automount sdcard and add it to bookmarks/locations in GTK file dialog2023-06-27T03:43:26ZGuido GuntherAutomount sdcard and add it to bookmarks/locations in GTK file dialogWe can ship a systemd automount unit to to e.g. automount to `/sdcard` writeable by user purism and add it to the gtk file choser locations (add least that used to be possible) so it becomes visible/usable in GTK all apps right way.
Th...We can ship a systemd automount unit to to e.g. automount to `/sdcard` writeable by user purism and add it to the gtk file choser locations (add least that used to be possible) so it becomes visible/usable in GTK all apps right way.
The upside over just using file-choser's mount is that we unount when not in use.https://source.puri.sm/Librem5/purple-mm-sms/-/issues/14Crash in pur_mm_get_sms_properties on ModemManager restart2020-07-13T15:26:15ZSebastian KrzyszkowiakCrash in pur_mm_get_sms_properties on ModemManager restart```
(gdb) bt
#0 0x0000ffff91a70a08 in () at /lib/aarch64-linux-gnu/libc.so.6
#1 0x0000ffff88f7b728 in pur_mm_get_sms_properties (sms_props=0xaaab0577a6f0) at mm-sms.c:498
#2 0x0000ffff88f7aeec in cb_sms_state_change (sms=0xffff8000ab...```
(gdb) bt
#0 0x0000ffff91a70a08 in () at /lib/aarch64-linux-gnu/libc.so.6
#1 0x0000ffff88f7b728 in pur_mm_get_sms_properties (sms_props=0xaaab0577a6f0) at mm-sms.c:498
#2 0x0000ffff88f7aeec in cb_sms_state_change (sms=0xffff8000ab60 [MMSms], pspec=0xaaab05a64730 [GParamUInt], sms_props=0xaaab0577a6f0) at mm-sms.c:274
#6 0x0000ffff92bc9b98 in <emit signal notify:state on instance 0xffff8000ab60 [MMSms]> (instance=instance@entry=0xffff8000ab60, signal_id=signal_id@entry=1, detail=<optimized out>)
at ../../../gobject/gsignal.c:3447
#3 0x0000ffff92bac9f8 in g_closure_invoke (closure=0xaaab0577a760, return_value=0x0, n_param_values=2, param_values=0xffffc439ecf0, invocation_hint=0xffffc439ecb8) at ../../../gobject/gclosure.c:810
#4 0x0000ffff92bc12b8 in signal_emit_unlocked_R (node=node@entry=0xaaab0533ab40, detail=1636, detail@entry=0, instance=0xffff8000ab60,
instance@entry=0x0, emission_return=emission_return@entry=0x0, instance_and_params=0xffffc439ecf0, instance_and_params@entry=0xffff92af4b00 <valid_format_string+272>) at ../../../gobject/gsignal.c:3635
#5 0x0000ffff92bc962c in g_signal_emit_valist (instance=instance@entry=0xffff8000ab60, signal_id=signal_id@entry=1, detail=<optimized out>, var_args=...) at ../../../gobject/gsignal.c:3391
#7 0x0000ffff92bb1808 in g_object_dispatch_properties_changed (object=0xffff8000ab60 [MMSms], n_pspecs=<optimized out>, pspecs=<optimized out>) at ../../../gobject/gobject.c:1088
#8 0x0000ffff92bb3f10 in g_object_notify_by_spec_internal (pspec=<optimized out>, object=0xffff8000ab60 [MMSms]) at ../../../gobject/gobject.c:1181
#9 0x0000ffff92bb3f10 in g_object_notify (object=0xffff8000ab60 [MMSms], property_name=<optimized out>) at ../../../gobject/gobject.c:1229
#10 0x0000ffff88b4e27c in mm_gdbus_sms_proxy_g_properties_changed (_proxy=<optimized out>, changed_properties=<optimized out>, invalidated_properties=0xaaab05a450b0) at mm-gdbus-sms.c:1772
#11 0x0000ffff91878dcc in ffi_call_SYSV () at /lib/aarch64-linux-gnu/libffi.so.6
#12 0x0000ffff918796f4 in ffi_call () at /lib/aarch64-linux-gnu/libffi.so.6
#17 0x0000ffff92bc9b98 in <emit signal ??? on instance 0xffff8000ab60 [MMSms]> (instance=instance@entry=0xffff8000ab60, signal_id=signal_id@entry=20, detail=detail@entry=0) at ../../../gobject/gsignal.c:3447
#13 0x0000ffff92bad224 in g_cclosure_marshal_generic
(closure=0xffff92c00000, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x1) at ../../../gobject/gclosure.c:1496
#14 0x0000ffff92bac9f8 in g_closure_invoke (closure=0xaaab05355b30, return_value=0x0, n_param_values=3, param_values=0xffffc439f7a0, invocation_hint=0xffffc439f768) at ../../../gobject/gclosure.c:810
#15 0x0000ffff92bc0b30 in signal_emit_unlocked_R (node=node@entry=0xaaab05355b60, detail=detail@entry=0, instance=0xffff8000ab60,
instance@entry=0x0, emission_return=emission_return@entry=0x0, instance_and_params=0xffffc439f7a0, instance_and_params@entry=0xffff92afdeec <g_variant_type_info_get+476>) at ../../../gobject/gsignal.c:3673
#16 0x0000ffff92bc962c in g_signal_emit_valist (instance=instance@entry=0xffff8000ab60, signal_id=signal_id@entry=20, detail=detail@entry=0, var_args=...) at ../../../gobject/gsignal.c:3391
#18 0x0000ffff92d16754 in on_name_owner_changed
(connection=<optimized out>, sender_name=<optimized out>, object_path=<optimized out>, interface_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>, user_data=<optimized out>)
at ../../../gio/gdbusproxy.c:1344
#19 0x0000ffff92d04658 in emit_signal_instance_in_idle_cb (data=0xffff7c057b10) at ../../../gio/gdbusconnection.c:3711
#20 0x0000ffff92ab851c in g_main_dispatch (context=0xaaab0534a9a0) at ../../../glib/gmain.c:3182
#21 0x0000ffff92ab851c in g_main_context_dispatch (context=context@entry=0xaaab0534a9a0) at ../../../glib/gmain.c:3847
#22 0x0000ffff92ab88e8 in g_main_context_iterate (context=context@entry=0xaaab0534a9a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:3920
#23 0x0000ffff92ab8984 in g_main_context_iteration (context=context@entry=0xaaab0534a9a0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3981
#24 0x0000ffff92cdcc7c in g_application_run (application=0xaaab053490e0 [ChattyApplication], argc=2, argv=0xffffc439ff38) at ../../../gio/gapplication.c:2470
#25 0x0000aaaae828a304 in main ()
(gdb)
```https://source.puri.sm/Librem5/linux/-/issues/197Modem and SD card inaccessible after failed USB resume2023-03-23T20:18:16ZSebastian KrzyszkowiakModem and SD card inaccessible after failed USB resumeIt just happened to me after a few hours of the device sitting there doing nothing. When I picked it up, I noticed that the modem was inaccessible despite of it being turned on.
```
[ 3025.568529] xhci-hcd xhci-hcd.4.auto: xHCI host not...It just happened to me after a few hours of the device sitting there doing nothing. When I picked it up, I noticed that the modem was inaccessible despite of it being turned on.
```
[ 3025.568529] xhci-hcd xhci-hcd.4.auto: xHCI host not responding to stop endpoint command.
[ 3025.568586] xhci-hcd xhci-hcd.4.auto: USBSTS:
[ 3025.576712] xhci-hcd xhci-hcd.4.auto: xHCI host controller not responding, assume dead
[ 3025.584983] xhci-hcd xhci-hcd.4.auto: HC died; cleaning up
[ 3025.595358] usb 1-1: USB disconnect, device number 2
[ 3025.595435] usb 1-1.1: USB disconnect, device number 3
[ 3025.595534] device: 'ep_02': device_unregister
[ 3025.596165] PM: Removing info for No Bus:ep_02
[ 3025.596334] device: 'ep_82': device_unregister
[ 3025.596482] PM: Removing info for No Bus:ep_82
[ 3025.596794] bus: 'usb': remove device 1-1.1:1.0
[ 3025.597205] device: '0:0:0:0': device_unregister
[ 3025.598804] PM: Removing info for No Bus:0:0:0:0
[ 3025.599482] device: '0:0:0:0': device_create_release
[ 3025.599517] device: '0:0:0:0': device_unregister
[ 3025.599665] PM: Removing info for No Bus:0:0:0:0
[ 3025.600342] bus: 'scsi': remove device 0:0:0:0
[ 3025.600788] PM: Removing info for No Bus:0:0:0:0
[ 3025.602597] PM: Removing info for No Bus:sda1
[ 3025.604054] device: '8:0': device_unregister
[ 3025.604317] PM: Removing info for No Bus:8:0
[ 3025.604487] device: '8:0': device_create_release
[ 3025.606270] PM: Removing info for No Bus:sda
[ 3025.607201] PM: Removing info for scsi:0:0:0:0
[ 3025.611295] bus: 'scsi': remove device target0:0:0
[ 3025.611395] PM: Removing info for scsi:target0:0:0
[ 3025.612690] device: 'host0': device_unregister
[ 3025.613188] PM: Removing info for No Bus:host0
[ 3025.613587] bus: 'scsi': remove device host0
[ 3025.613610] PM: Removing info for scsi:host0
[ 3025.650821] PM: Removing info for usb:1-1.1:1.0
[ 3025.651488] device: 'ep_00': device_unregister
[ 3025.652117] PM: Removing info for No Bus:ep_00
[ 3025.653389] bus: 'usb': remove device 1-1.1
[ 3025.653778] PM: Removing info for usb:1-1.1
[ 3025.656351] usb 1-1.2: USB disconnect, device number 4
[ 3025.656422] device: 'ep_81': device_unregister
[ 3025.656608] PM: Removing info for No Bus:ep_81
[ 3025.656662] device: 'ep_01': device_unregister
[ 3025.656770] PM: Removing info for No Bus:ep_01
[ 3025.656987] bus: 'usb': remove device 1-1.2:1.0
[ 3025.658027] bus: 'usb-serial': remove device ttyUSB0
[ 3025.658811] device: 'ttyUSB0': device_unregister
[ 3025.659392] PM: Removing info for No Bus:ttyUSB0
[ 3025.660159] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 3025.660290] PM: Removing info for usb-serial:ttyUSB0
[ 3025.660572] option 1-1.2:1.0: device disconnected
[ 3025.660728] PM: Removing info for usb:1-1.2:1.0
[ 3025.660814] device: 'ep_82': device_unregister
[ 3025.660982] PM: Removing info for No Bus:ep_82
[ 3025.661030] device: 'ep_02': device_unregister
[ 3025.661146] PM: Removing info for No Bus:ep_02
[ 3025.661349] bus: 'usb': remove device 1-1.2:1.1
[ 3025.661954] bus: 'usb-serial': remove device ttyUSB1
[ 3025.662631] device: 'ttyUSB1': device_unregister
[ 3025.663200] PM: Removing info for No Bus:ttyUSB1
[ 3025.663592] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 3025.663691] PM: Removing info for usb-serial:ttyUSB1
[ 3025.664028] option 1-1.2:1.1: device disconnected
[ 3025.664179] PM: Removing info for usb:1-1.2:1.1
[ 3025.664286] device: 'ep_83': device_unregister
[ 3025.664464] PM: Removing info for No Bus:ep_83
[ 3025.664528] device: 'ep_84': device_unregister
[ 3025.664674] PM: Removing info for No Bus:ep_84
[ 3025.664734] device: 'ep_03': device_unregister
[ 3025.664891] PM: Removing info for No Bus:ep_03
[ 3025.665058] bus: 'usb': remove device 1-1.2:1.2
[ 3025.665615] bus: 'usb-serial': remove device ttyUSB2
[ 3025.666072] device: 'ttyUSB2': device_unregister
[ 3025.666478] PM: Removing info for No Bus:ttyUSB2
[ 3025.666771] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 3025.666844] PM: Removing info for usb-serial:ttyUSB2
[ 3025.666978] option 1-1.2:1.2: device disconnected
[ 3025.667056] PM: Removing info for usb:1-1.2:1.2
[ 3025.667124] device: 'ep_85': device_unregister
[ 3025.667265] PM: Removing info for No Bus:ep_85
[ 3025.667320] device: 'ep_86': device_unregister
[ 3025.667450] PM: Removing info for No Bus:ep_86
[ 3025.667494] device: 'ep_04': device_unregister
[ 3025.667612] PM: Removing info for No Bus:ep_04
[ 3025.668121] bus: 'usb': remove device 1-1.2:1.3
[ 3025.668323] bus: 'usb-serial': remove device ttyUSB3
[ 3025.668736] device: 'ttyUSB3': device_unregister
[ 3025.669045] PM: Removing info for No Bus:ttyUSB3
[ 3025.669309] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[ 3025.669384] PM: Removing info for usb-serial:ttyUSB3
[ 3025.669530] option 1-1.2:1.3: device disconnected
[ 3025.669589] PM: Removing info for usb:1-1.2:1.3
[ 3025.669652] device: 'ep_87': device_unregister
[ 3025.669781] PM: Removing info for No Bus:ep_87
[ 3025.669831] device: 'ep_88': device_unregister
[ 3025.670045] PM: Removing info for No Bus:ep_88
[ 3025.670097] device: 'ep_05': device_unregister
[ 3025.670225] PM: Removing info for No Bus:ep_05
[ 3025.670391] bus: 'usb': remove device 1-1.2:1.4
[ 3025.670550] qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device
[ 3025.681724] PM: Removing info for No Bus:wwan0
[ 3025.704449] device: 'cdc-wdm0': device_unregister
[ 3025.705193] PM: Removing info for No Bus:cdc-wdm0
[ 3025.705895] device: 'cdc-wdm0': device_create_release
[ 3025.705941] device class 'usbmisc': unregistering
[ 3025.706044] class 'usbmisc': release.
[ 3025.706061] class_create_release called for usbmisc
[ 3025.706638] PM: Removing info for usb:1-1.2:1.4
[ 3025.707133] device: 'ep_00': device_unregister
[ 3025.707321] PM: Removing info for No Bus:ep_00
[ 3025.708510] bus: 'usb': remove device 1-1.2
[ 3025.708854] PM: Removing info for usb:1-1.2
[ 3025.715052] device: 'ep_81': device_unregister
[ 3025.715530] PM: Removing info for No Bus:ep_81
[ 3025.716192] bus: 'usb': remove device 1-1:1.0
[ 3025.716575] device: '1-1-port3': device_unregister
[ 3025.716842] PM: Removing info for No Bus:1-1-port3
[ 3025.716971] device: '1-1-port2': device_unregister
[ 3025.717143] PM: Removing info for No Bus:1-1-port2
[ 3025.717226] device: '1-1-port1': device_unregister
[ 3025.717374] PM: Removing info for No Bus:1-1-port1
[ 3025.717920] PM: Removing info for usb:1-1:1.0
[ 3025.718219] device: 'ep_00': device_unregister
[ 3025.718380] PM: Removing info for No Bus:ep_00
[ 3025.720155] bus: 'usb': remove device 1-1
[ 3025.720594] PM: Removing info for usb:1-1
```
This is on Birch using stock udev rules from current version of librem5-base.
/cc @martin.kepplinger /cc @guido.guntherMartin KepplingerMartin Kepplingerhttps://source.puri.sm/Librem5/linux/-/issues/196Suspend sd card reader even when mounted2020-08-02T11:11:39ZGuido GuntherSuspend sd card reader even when mountedThanks to @martin.kepplinger 's patch (!160) for sd the sd card works and hub can suspend while not mounted but it should also be able to suspend when mounted
https://lore.kernel.org/linux-scsi/20200623111018.31954-1-martin.kepplinger@...Thanks to @martin.kepplinger 's patch (!160) for sd the sd card works and hub can suspend while not mounted but it should also be able to suspend when mounted
https://lore.kernel.org/linux-scsi/20200623111018.31954-1-martin.kepplinger@puri.sm/T/#m72ef6a2fbf29957ed494fb125c8d3eb56f78e1ac
(just so we have a bug to track that as well)https://source.puri.sm/Librem5/OS-issues/-/issues/151Auto-brightness setting results in flickering on a white background, without ...2020-06-25T11:28:18ZMarek Lach BcAuto-brightness setting results in flickering on a white background, without it the flickering stopsNot really sure how the *automatically adjust display brightness* feature works now, but it seems to change a little every few seconds, particularly on a white background, which results in quite a noticeable screen-flickering.
I am not ...Not really sure how the *automatically adjust display brightness* feature works now, but it seems to change a little every few seconds, particularly on a white background, which results in quite a noticeable screen-flickering.
I am not really sure how many brightness levels the auto-brightness feature is switching between right now, but there should probably only be two: day - a brighter display, and night - a more dimmed display. Once one, or the other is set, it should most likely remain fixed at that level of shade/brightness.https://source.puri.sm/Librem5/linux/-/issues/195etnaviv-gpu doesn't suspend after recovering from hung GPU2020-09-15T15:48:43ZSebastian Krzyszkowiaketnaviv-gpu doesn't suspend after recovering from hung GPUAfter noticing higher power consumption that what I expected on my phone, I started looking to what could have caused it. Turned out that it was GPU that stopped suspending exactly at the same moment when it (successfully) recovered from...After noticing higher power consumption that what I expected on my phone, I started looking to what could have caused it. Turned out that it was GPU that stopped suspending exactly at the same moment when it (successfully) recovered from a hang:
```terminal
$ sudo dmesg | grep gpu
(...)
[10895.156683] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[10895.222051] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[10896.252101] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[10897.132155] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[10897.297011] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[10897.752986] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[10901.055271] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[10901.518826] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[10901.600051] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[10901.630306] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[10902.172021] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[10902.283058] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[10904.433489] etnaviv-gpu 38000000.gpu: recover hung GPU!
[10906.032050] etnaviv-gpu 38000000.gpu: recover hung GPU!
$
```https://source.puri.sm/Librem5/feedbackd/-/issues/20Add gtk-module2020-06-23T14:01:19ZGuido GuntherAdd gtk-modulesimilar to libcanberra to hook into gtk signals for emitting feedback.similar to libcanberra to hook into gtk signals for emitting feedback.https://source.puri.sm/Librem5/OS-issues/-/issues/150h-dog barking is audible (haptic motor makes a sound)2020-06-28T12:56:49ZTodd Weaverh-dog barking is audible (haptic motor makes a sound)# What problem did you encounter
h-dog barking is audible (haptic motor vibration makes a sound)
## What is the current behaviour?
h-dog barking is audible (haptic motor vibration makes a sound)
## What is the expected behaviour?
vi...# What problem did you encounter
h-dog barking is audible (haptic motor vibration makes a sound)
## What is the current behaviour?
h-dog barking is audible (haptic motor vibration makes a sound)
## What is the expected behaviour?
vibration without motor sound
## How to reproduce
1. turn on the haptic motor (test was done via Alarms)
2. hear a sound from the motor that is louder than the alarm sound
3. Note: the vibrating motor sound is pretty cute, like a hedgehog squeak.
# Which version did you encounter the bug in?
```
purism@pureos:~$ uname -a
Linux pureos 5.7.0-1-librem5 #1 SMP PREEMPT Fri Jun 5 00:52:56 UTC 2020 aarch64 GNU/Linux
purism@pureos:~$ dpkg -s phosh | grep Version
Version: 0.3.0
purism@pureos:~$ dpkg -s phoc | grep Version
Version: 0.1.8
purism@pureos:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1916+git01bf68a-1pureos0
purism@pureos:~$ dpkg -s feedbackd | grep Version
Version: 0.0.0+git20200527
purism@pureos:~$
```
# What hardware are you running phosh on?
- Chestnuthttps://source.puri.sm/Librem5/gnome-control-center/-/issues/120Phosh 'silent' silences h-dog (haptic motor) on alarms2020-07-05T11:26:18ZTodd WeaverPhosh 'silent' silences h-dog (haptic motor) on alarms# What problem did you encounter
Set an alarm in Clocks, turned to 'silent' in phosh, didn't hear alarm (proper); didn't feel vibration (improper)
## What is the current behaviour?
no h-dog barking. (no haptic motor vibration)
## Wha...# What problem did you encounter
Set an alarm in Clocks, turned to 'silent' in phosh, didn't hear alarm (proper); didn't feel vibration (improper)
## What is the current behaviour?
no h-dog barking. (no haptic motor vibration)
## What is the expected behaviour?
h-dog barks. (haptic motor vibrates)
## How to reproduce
1. set an alarm for 1 minute from now
2. turn phosh to 'silent' from quick menu
3. wait
4. hear/feel nothing
# Which version did you encounter the bug in?
```
purism@pureos:~$ uname -a
Linux pureos 5.7.0-1-librem5 #1 SMP PREEMPT Fri Jun 5 00:52:56 UTC 2020 aarch64 GNU/Linux
purism@pureos:~$ dpkg -s phosh | grep Version
Version: 0.3.0
purism@pureos:~$ dpkg -s phoc | grep Version
Version: 0.1.8
purism@pureos:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1916+git01bf68a-1pureos0
purism@pureos:~$
```
# What hardware are you running phosh on?
- Chestnuthttps://source.puri.sm/Librem5/debs/epiphany/-/issues/18black area during transition of keyboard (in Web browser)2020-09-22T08:59:29ZTodd Weaverblack area during transition of keyboard (in Web browser)# What problem did you encounter
black area of keyboard during transition
## What is the current behaviour?
black area
## What is the expected behaviour?
smooth app to full-screen
## How to reproduce
![phosh-black-area-keyboard-20...# What problem did you encounter
black area of keyboard during transition
## What is the current behaviour?
black area
## What is the expected behaviour?
smooth app to full-screen
## How to reproduce
![phosh-black-area-keyboard-2020-06-20](/uploads/f54bb9c530953a63a984c7e4db51b72a/phosh-black-area-keyboard-2020-06-20.webm)
# Which version did you encounter the bug in?
```
purism@pureos:~$ uname -a
Linux pureos 5.7.0-1-librem5 #1 SMP PREEMPT Fri Jun 5 00:52:56 UTC 2020 aarch64 GNU/Linux
purism@pureos:~$ dpkg -s phosh | grep Version
Version: 0.3.0
purism@pureos:~$ dpkg -s phoc | grep Version
Version: 0.1.8
purism@pureos:~$
```
# What hardware are you running phosh on?
- Chestnuthttps://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/26Clocks Timer Numpad seems useless (could just use the +/- keys)2020-12-07T10:09:50ZTodd WeaverClocks Timer Numpad seems useless (could just use the +/- keys)Reproduction
1. Open Clocks
2. Go to Timer
3. Click '+', numpad pops-up to get in the way
4. can't backspace, doesn't overwrite, have to refocus, or highlight to even use the numpad (quite useless IMHO)
5. +/- would suffice for my use ca...Reproduction
1. Open Clocks
2. Go to Timer
3. Click '+', numpad pops-up to get in the way
4. can't backspace, doesn't overwrite, have to refocus, or highlight to even use the numpad (quite useless IMHO)
5. +/- would suffice for my use cases
6. Have to toggle keyboard off to go to other clocks items.
Expected behavior would be no numpad.
![clock-numpad-useless-2020-06-20](/uploads/c20814912f78318505b5deebb3fa2c5b/clock-numpad-useless-2020-06-20.webm)
```
purism@pureos:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1916+git01bf68a-1pureos0
purism@pureos:~$
```Adrien PlazasAdrien Plazas