Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2023-01-17T13:05:08Zhttps://source.puri.sm/Librem5/wys/-/issues/12Audio disappearing when secondary call is being rejected2023-01-17T13:05:08ZEvangelos Ribeiro TzarasAudio disappearing when secondary call is being rejectedWith the latest ModemManager (specifically https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/580 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/568) having multiple calls bec...With the latest ModemManager (specifically https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/580 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/568) having multiple calls becomes possible.
Calls currently does not support this however and autorejects any incoming calls if a call is already active.
While testing the latest MM I noticed the audio disappearing on the L5 when the secondary call was being rejected.
See this log from wys (starting wys -> starting a call -> receiving and rejecting an incoming call:
```
** (wys:3701): DEBUG: 14:08:21.269: Watching for ModemManager
Wys started with modem `(none)'
** (wys:3701): DEBUG: 14:08:21.271: Found card 'alsa_card.platform-sound-wwan', alsa: 'Modem'
** (wys:3701): DEBUG: 14:08:21.314: ModemManager appeared on D-Bus
** (wys:3701): DEBUG: 14:08:21.377: ModemManager interface `org.freedesktop.ModemManager1.Modem.Firmware' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.378: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.ProfileManager' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.378: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.378: ModemManager interface `org.freedesktop.ModemManager1.Modem.Simple' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.378: ModemManager interface `org.freedesktop.ModemManager1.Modem.Time' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.378: ModemManager interface `org.freedesktop.ModemManager1.Modem.Voice' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.378: Adding new voice-capable modem `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.380: ModemManager interface `org.freedesktop.ModemManager1.Modem' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.380: ModemManager interface `org.freedesktop.ModemManager1.Modem.Messaging' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.380: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.380: ModemManager interface `org.freedesktop.ModemManager1.Modem.Signal' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:21.380: ModemManager interface `org.freedesktop.ModemManager1.Modem.Location' found on object `/org/freedesktop/ModemManager1/Modem/2'
** (wys:3701): DEBUG: 14:08:56.140: Call `/org/freedesktop/ModemManager1/Call/12' added, state: 0
** (wys:3701): DEBUG: 14:08:56.208: Call `/org/freedesktop/ModemManager1/Call/12' state changed, new: 1, old: 0
** (wys:3701): DEBUG: 14:09:01.680: Call `/org/freedesktop/ModemManager1/Call/12' state changed, new: 2, old: 1
** (wys:3701): DEBUG: 14:09:01.680: Call `/org/freedesktop/ModemManager1/Call/12' gained audio from network
** (wys:3701): DEBUG: 14:09:01.680: Modem `/org/freedesktop/ModemManager1/Modem/2' audio from network now present
** (wys:3701): DEBUG: 14:09:01.680: Audio from network now present
** (wys:3701): DEBUG: 14:09:01.680: Finding ALSA card `Modem' source output
** (wys:3701): DEBUG: 14:09:01.681: End of source output list reached
** (wys:3701): DEBUG: 14:09:01.682: Instantiating loopback module for ALSA card `Modem' source
** (wys:3701): DEBUG: 14:09:01.682: Finding source for ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:01.683: The source 0 `alsa_output.platform-sound.HiFi__hw_L5_0__sink.monitor' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:01.683: The source 1 `alsa_input.platform-sound.HiFi__hw_L5_0__source' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:01.684: The source 2 `alsa_output.platform-sound-wwan.stereo-fallback.monitor' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:01.684: The source 3 `alsa_input.platform-sound-wwan.stereo-fallback' is ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:01.684: End of source list reached
** (wys:3701): DEBUG: 14:09:01.684: Instantiating loopback module with source `alsa_input.platform-sound-wwan.stereo-fallback' (ALSA card `Modem')
** (wys:3701): DEBUG: 14:09:01.853: Instantiated loopback module 47 with source `alsa_input.platform-sound-wwan.stereo-fallback' (ALSA card `Modem')
** (wys:3701): DEBUG: 14:09:04.746: Call `/org/freedesktop/ModemManager1/Call/12' state changed, new: 4, old: 2
** (wys:3701): DEBUG: 14:09:04.747: Call `/org/freedesktop/ModemManager1/Call/12' gained audio to network
** (wys:3701): DEBUG: 14:09:04.747: Modem `/org/freedesktop/ModemManager1/Modem/2' audio to network now present
** (wys:3701): DEBUG: 14:09:04.747: Audio to network now present
** (wys:3701): DEBUG: 14:09:04.747: Finding ALSA card `Modem' sink input
** (wys:3701): DEBUG: 14:09:04.748: Getting sink 0 of sink input 22 `Voice call audio (to speaker)'
** (wys:3701): DEBUG: 14:09:04.748: End of sink input list reached
** (wys:3701): DEBUG: 14:09:04.751: Sink 0 `alsa_output.platform-sound.HiFi__hw_L5_0__sink' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:04.751: Instantiating loopback module for ALSA card `Modem' sink
** (wys:3701): DEBUG: 14:09:04.751: Finding sink for ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:04.753: The sink 0 `alsa_output.platform-sound.HiFi__hw_L5_0__sink' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:04.754: The sink 1 `alsa_output.platform-sound-wwan.stereo-fallback' is ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:04.754: End of sink list reached
** (wys:3701): DEBUG: 14:09:04.754: Instantiating loopback module with sink `alsa_output.platform-sound-wwan.stereo-fallback' (ALSA card `Modem')
** (wys:3701): DEBUG: 14:09:04.781: Instantiated loopback module 48 with sink `alsa_output.platform-sound-wwan.stereo-fallback' (ALSA card `Modem')
** (wys:3701): DEBUG: 14:09:29.027: Call `/org/freedesktop/ModemManager1/Call/13' added, state: 6
** (wys:3701): DEBUG: 14:09:29.101: Call `/org/freedesktop/ModemManager1/Call/13' state changed, new: 7, old: 6
** (wys:3701): DEBUG: 14:09:29.161: Removing call `/org/freedesktop/ModemManager1/Call/13'
** (wys:3701): DEBUG: 14:09:29.162: Call `/org/freedesktop/ModemManager1/Call/13' removed
** (wys:3701): DEBUG: 14:09:38.269: Call `/org/freedesktop/ModemManager1/Call/12' state changed, new: 7, old: 4
** (wys:3701): DEBUG: 14:09:38.270: Call `/org/freedesktop/ModemManager1/Call/12' lost audio from network
** (wys:3701): DEBUG: 14:09:38.270: Modem `/org/freedesktop/ModemManager1/Modem/2' audio now absent
** (wys:3701): DEBUG: 14:09:38.270: Audio from network now absent
** (wys:3701): DEBUG: 14:09:38.270: Finding ALSA card `Modem' source output
** (wys:3701): DEBUG: 14:09:38.270: Call `/org/freedesktop/ModemManager1/Call/12' lost audio to network
** (wys:3701): DEBUG: 14:09:38.270: Modem `/org/freedesktop/ModemManager1/Modem/2' audio now absent
** (wys:3701): DEBUG: 14:09:38.270: Audio to network now absent
** (wys:3701): DEBUG: 14:09:38.270: Finding ALSA card `Modem' sink input
** (wys:3701): DEBUG: 14:09:38.273: Getting source 3 of source output 20 `Loopback to Built-in Audio Headphones + Speaker + Handset (echo cancelled with Built-in Audio Headset Microphone + Internal Microphone)'
** (wys:3701): DEBUG: 14:09:38.273: Getting source 16 of source output 21 `Voice call audio (from mic)'
** (wys:3701): DEBUG: 14:09:38.273: Getting source 1 of source output 22 `Echo-Cancel Source Stream'
** (wys:3701): DEBUG: 14:09:38.273: End of source output list reached
** (wys:3701): DEBUG: 14:09:38.273: Getting sink 8 of sink input 22 `Voice call audio (to speaker)'
** (wys:3701): DEBUG: 14:09:38.274: Getting sink 1 of sink input 23 `Loopback of Built-in Audio Headset Microphone + Internal Microphone (echo cancelled with Built-in Audio Headphones + Speaker + Handset)'
** (wys:3701): DEBUG: 14:09:38.274: Getting sink 0 of sink input 24 `Echo-Cancel Sink Stream'
** (wys:3701): DEBUG: 14:09:38.276: End of sink input list reached
** (wys:3701): DEBUG: 14:09:38.294: Checking whether module 47 for ALSA card `Modem' source output is a loopback module
** (wys:3701): DEBUG: 14:09:38.294: Source 16 `alsa_input.platform-sound.HiFi__hw_L5_0__source.echo-cancel' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:38.294: Source 1 `alsa_input.platform-sound.HiFi__hw_L5_0__source' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:38.294: Sink 8 `alsa_output.platform-sound.HiFi__hw_L5_0__sink.echo-cancel' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:38.295: Checking whether module 48 for ALSA card `Modem' sink input is a loopback module
** (wys:3701): DEBUG: 14:09:38.295: Sink 0 `alsa_output.platform-sound.HiFi__hw_L5_0__sink' is not ALSA card `Modem'
** (wys:3701): DEBUG: 14:09:38.299: Removing call `/org/freedesktop/ModemManager1/Call/12'
** (wys:3701): DEBUG: 14:09:38.300: Call `/org/freedesktop/ModemManager1/Call/12' removed
** (wys:3701): DEBUG: 14:09:38.301: Module 47 for ALSA card `Modem' source output is a loopback module
** (wys:3701): DEBUG: 14:09:38.302: Deinstantiating loopback modules for ALSA card `Modem' source
** (wys:3701): DEBUG: 14:09:38.303: Deinstantiating loopback module 47
** (wys:3701): DEBUG: 14:09:38.303: Module 48 for ALSA card `Modem' sink input is a loopback module
** (wys:3701): DEBUG: 14:09:38.303: Deinstantiating loopback modules for ALSA card `Modem' sink
** (wys:3701): DEBUG: 14:09:38.304: Deinstantiating loopback module 48
** (wys:3701): DEBUG: 14:09:38.304: Successfully deinstantiated loopback module 47
** (wys:3701): DEBUG: 14:09:38.305: Successfully deinstantiated loopback module 48
```https://source.puri.sm/Librem5/millipixels/-/issues/16Pictures from front cam are horizontally mirrored2022-06-25T21:22:01ZEvangelos Ribeiro TzarasPictures from front cam are horizontally mirroredHey there,
I've just noticed that pictures taken from the front camera (with megapixels)
appear to be mirrored.
Observe the tree, cars and road markings in the following pictures:
Rear camera (matches what my eyes tell me):
![back](/u...Hey there,
I've just noticed that pictures taken from the front camera (with megapixels)
appear to be mirrored.
Observe the tree, cars and road markings in the following pictures:
Rear camera (matches what my eyes tell me):
![back](/uploads/f670c8c28fe1f22994771bb08ac83b24/back.jpg)
Front camera (from mirror land):
![front](/uploads/14f62e5883e5b8c8788344e79fecae37/front.jpg)https://source.puri.sm/Librem5/image-builder/-/issues/64Swich to luks2 format?2021-04-21T17:24:50ZGuido GuntherSwich to luks2 format?We currently do
`cryptsetup luksFormat ...`
but could rather do
`cryptsetup luksFormat --type=luks2`
since that seems to be more clever regarding reencryption and is more flexible regardin PBKDF.We currently do
`cryptsetup luksFormat ...`
but could rather do
`cryptsetup luksFormat --type=luks2`
since that seems to be more clever regarding reencryption and is more flexible regardin PBKDF.https://source.puri.sm/Librem5/geary/-/issues/16"Accounts" view doesn't fit the screen when there's long account name2021-08-24T05:15:37ZSebastian Krzyszkowiak"Accounts" view doesn't fit the screen when there's long account nameAs seen on the screenshot:
![geary-fit](/uploads/8e8ad1908ccd5c1252c8134204d70361/geary-fit.png)
Editing the account name to be shorter makes it fit again.As seen on the screenshot:
![geary-fit](/uploads/8e8ad1908ccd5c1252c8134204d70361/geary-fit.png)
Editing the account name to be shorter makes it fit again.https://source.puri.sm/Librem5/geary/-/issues/15Erratic touch input2023-06-17T01:02:11ZSebastian KrzyszkowiakErratic touch inputSometimes (not sure what's the trigger) Geary stops to react to touches in a sane way - it starts to behave as if the new touch was happening in the place of the previous one (even if the widget that was touched the last time isn't visib...Sometimes (not sure what's the trigger) Geary stops to react to touches in a sane way - it starts to behave as if the new touch was happening in the place of the previous one (even if the widget that was touched the last time isn't visible on screen anymore).
![geary-touch](/uploads/879cfd0fe28e33e67004fc039c2bdef5/geary-touch.mp4)
![MVI_1962.MP4](/uploads/938f7069269851f2a5b8818f570c43bc/MVI_1962.MP4.webm)
I don't know the exact reproducer, but it seems like I can eventually trigger it when I play with changing views a lot (going to and back from message view, folder view, trying to quickly scroll the list of messages before switching happens etc.). When it happens, the only way to recover seems to be to kill and restart geary.
Possible libhandy issue? /cc @alexander.mikhaylenko @adrien.plazas @julian.sparberhttps://source.puri.sm/Librem5/linux/-/issues/239etnaviv: Fix too early gem unmap2023-02-17T09:57:22ZGuido Guntheretnaviv: Fix too early gem unmapWith !233 we can unmap BOs too early. This of mitigated by !249 and can happen on external screen unplug (there are other scenarios but this is the most likely one). I have that on my todo list but there wasn't a bug so far. Trase looks...With !233 we can unmap BOs too early. This of mitigated by !249 and can happen on external screen unplug (there are other scenarios but this is the most likely one). I have that on my todo list but there wasn't a bug so far. Trase looks somewhat like
```
[ 488.735126] Call trace:
[ 488.735132] etnaviv_gem_close_object+0xc8/0xd0
[ 488.735136] drm_gem_object_release_handle+0x40/0xa8
[ 488.735140] drm_gem_handle_delete+0x70/0xc8
[ 488.735144] drm_gem_close_ioctl+0x38/0x50
[ 488.735148] drm_ioctl_kernel+0xcc/0x120
[ 488.735151] drm_ioctl+0x250/0x4a0
```https://source.puri.sm/Librem5/user-personas/-/issues/9User persona: Martin2023-10-12T09:06:48ZMartin KepplingerUser persona: Martini.e. what's missing for the L5 to really become my only phone:
| missing | references |
| ------ | ------ |
| 100% reliably being online and reachable | https://source.puri.sm/Librem5/OS-issues/-/issues/318 https://source.puri.sm/Librem...i.e. what's missing for the L5 to really become my only phone:
| missing | references |
| ------ | ------ |
| 100% reliably being online and reachable | https://source.puri.sm/Librem5/OS-issues/-/issues/318 https://source.puri.sm/Librem5/OS-issues/-/issues/328 https://source.puri.sm/Librem5/linux/-/issues/423 |
| chatty contact rx/tx (MMS) | https://source.puri.sm/Librem5/chatty/-/issues/677 |
| gnome Clocks alarm wakeup from suspend | https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/100 |
| encrypted root partition | https://source.puri.sm/Librem5/image-builder/-/issues/63 https://source.puri.sm/Librem5/librem5-flash-image/-/issues/2 |
| xmpp/jingle voip calls (with SRTP / compatible with the conversations.im app) | https://gitlab.gnome.org/GNOME/calls/-/issues/151 |
| alarm sound independent of used profile | https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/28 |
| Offline OSM maps with turn-by-turn GNSS navi | https://developer.puri.sm/Librem5/Development_Environment/Phone/Troubleshooting/Testing_GNSS.html https://gpsd.gitlab.io/gpsd/gpsd.html and https://www.navit-project.org/ https://github.com/navit-gps/navit/releases or https://github.com/rinigus/pure-maps/releases |
workarounds:
| what | workaround |
| ------ | ------ |
| caldav / carddav sync on random servers | https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/3 ? evolution |
apply the workarounds:
```
git clone https://source.puri.sm/martin.kepplinger/addons.git && cd addons
./prepare.sh
```https://source.puri.sm/Librem5/purple-mm-sms/-/issues/17Duplicate messages when remove recieved messages is off2020-08-24T18:50:20ZAren MoynihanDuplicate messages when remove recieved messages is offWhen removing received sms messages is set to off via `/mm-sms rm_r off` purple-mm-sms duplicates messages that have already been received.
This seems to happen when purple-mm-sms polls ModemManager for messages (I believe this happens ...When removing received sms messages is set to off via `/mm-sms rm_r off` purple-mm-sms duplicates messages that have already been received.
This seems to happen when purple-mm-sms polls ModemManager for messages (I believe this happens when it starts up). I'm guessing purple-mm-sms gets a full list of messages and doesn't check for duplicates of messages it already knows about.
I think this may be related to chatty#287, but it's not quite the same bug.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/feedbackd/-/issues/19create a libfeedback-rs2020-06-04T12:14:49ZGuido Gunthercreate a libfeedback-rsFor squeekboard and others having rust bindings would be useful. I'm open to whether that would better be done using gir or building a native library using the `dbus` crate.For squeekboard and others having rust bindings would be useful. I'm open to whether that would better be done using gir or building a native library using the `dbus` crate.https://source.puri.sm/Librem5/OS-issues/-/issues/146Shutdown when long-pressing the Power Button2020-06-22T12:17:35ZMartin KepplingerShutdown when long-pressing the Power ButtonWe actually already do this, but out-of-band in librem5-devkit-tools' power_key.py script. In order to get rid of that script in the long run, could this be done in phoc?We actually already do this, but out-of-band in librem5-devkit-tools' power_key.py script. In order to get rid of that script in the long run, could this be done in phoc?https://source.puri.sm/Librem5/gnome-software/-/issues/31Packagekit eats cpu for breakfast2022-03-30T09:07:06ZGuido GuntherPackagekit eats cpu for breakfastRelated to #20 we should also cut down on packagekit activity in general. Having top running on the devkit shows packagekit coming up hogging one cpu at 100% several times. This burns battery.Related to #20 we should also cut down on packagekit activity in general. Having top running on the devkit shows packagekit coming up hogging one cpu at 100% several times. This burns battery.https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/21Alarm alert should appear above lock screen2021-10-25T12:05:56ZKyle RankinAlarm alert should appear above lock screenAny alarm intended to wake a user up will sound after the phone is idle and in a locked state. Instead of requiring the user to fumble with their phone to unlock it and then dismiss their alarm, the alarm should provide a basic dismiss/s...Any alarm intended to wake a user up will sound after the phone is idle and in a locked state. Instead of requiring the user to fumble with their phone to unlock it and then dismiss their alarm, the alarm should provide a basic dismiss/snooze option above/on the lock screen.https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/19Timer should repeat (like alarm) or be loud and longer2020-01-26T13:51:44ZTodd WeaverTimer should repeat (like alarm) or be loud and longerThe timer 'ding' is very quiet and very short
Reproduction
1. Clocks - Timer
2. Set to 1 second
3. Start
4. Hear tiny ding through earpiece
(now imagine your cookies burning from the other room because you missed this sound)
I could s...The timer 'ding' is very quiet and very short
Reproduction
1. Clocks - Timer
2. Set to 1 second
3. Start
4. Hear tiny ding through earpiece
(now imagine your cookies burning from the other room because you missed this sound)
I could see this either being like the alarm (continuous), or being much louder (through speaker) and much longer (at least 15 seconds). This probably needs @design to chime in :)
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1911+git9afed36-1pureos0
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/image-builder/-/issues/53Expired root account causes troubles with some postinsts2021-10-14T10:22:39ZSebastian KrzyszkowiakExpired root account causes troubles with some postinstsThe way we disable the root account causes troubles with configuration of some packages, like gpsd:
```
Setting up gpsd (3.17-7) ...
Creating/updating gpsd user account...
Your account has expired; please contact your system administrat...The way we disable the root account causes troubles with configuration of some packages, like gpsd:
```
Setting up gpsd (3.17-7) ...
Creating/updating gpsd user account...
Your account has expired; please contact your system administrator
chfn: PAM: Authentication failure
adduser: `/bin/chfn -f GPSD system user gpsd' returned error code 1. Exiting.
Non-system user gpsd found. I will not overwrite a non-system
user. Remove the user and reinstall gpsd.
dpkg: error processing package gpsd (--configure):
installed gpsd package post-installation script subprocess returned error exit status 1
```
gpsd's postinst script looks like this:
```
#!/bin/bash
# postinst script for gpsd
set -e
if [ "$1" = "configure" ] ; then
echo "Creating/updating gpsd user account..."
adduser --system --ingroup dialout --home /run/gpsd \
--gecos "GPSD system user" --shell /bin/false \
--quiet --disabled-password gpsd || {
# adduser failed. Why?
if getent passwd gpsd >/dev/null ; then
echo "Non-system user gpsd found. I will not overwrite a non-system" >&2
echo "user. Remove the user and reinstall gpsd." >&2
exit 1
fi
# unknown adduser error, simply exit
exit 1
}
fi
#DEBHELPER#
exit 0
```
It also causes some commonly used patterns, like `sudo su`, to not work. AFAIK other systems, like Ubuntu, tend to disable root account just by disabling its password without expiring the account.https://source.puri.sm/Librem5/gnome-software/-/issues/20Only install updates when connected to usb-c power.2022-06-21T07:23:11ZGuido GuntherOnly install updates when connected to usb-c power.To avoid running out of battery it'd be good to make gnome-software only install updates when connected to usb-c power. Possibe implementation:
- download updates but then only restart the phone when connected to usb-c
- during the up...To avoid running out of battery it'd be good to make gnome-software only install updates when connected to usb-c power. Possibe implementation:
- download updates but then only restart the phone when connected to usb-c
- during the update step check if we're still charging.https://source.puri.sm/Librem5/OS-issues/-/issues/85Adjust display brightness to ambient light level2023-03-18T17:54:34ZDorota CzaplejewiczAdjust display brightness to ambient light levelThe brightness of the display is not automatically adjusted, leading to nasty issues like
- blinding the user at night
- more power draw than necessaryThe brightness of the display is not automatically adjusted, leading to nasty issues like
- blinding the user at night
- more power draw than necessaryhttps://source.puri.sm/Librem5/OS-issues/-/issues/84Language selection doesn't work2022-06-03T20:29:34ZDorota CzaplejewiczLanguage selection doesn't workSwitching the language only changes the language inside the initial setup window, but doesn't affect the system. A restart doesn't fix this.
I'm not sure exactly where to look, but:
```
$ env | grep LANG
LANG=C.UTF-8
```Switching the language only changes the language inside the initial setup window, but doesn't affect the system. A restart doesn't fix this.
I'm not sure exactly where to look, but:
```
$ env | grep LANG
LANG=C.UTF-8
```Evg++https://source.puri.sm/Librem5/Apps_Issues/-/issues/167Have an IVR system2019-11-22T11:12:56ZBob HamHave an IVR systemFrom David Hamner's [comment on a Calls issue](https://source.puri.sm/Librem5/calls/issues/26#note_68404):
"Auto answer the phone and ask for input:
* Press one (or enter pre-setup pin) to ring phone
* Press two to leave a message
* PI...From David Hamner's [comment on a Calls issue](https://source.puri.sm/Librem5/calls/issues/26#note_68404):
"Auto answer the phone and ask for input:
* Press one (or enter pre-setup pin) to ring phone
* Press two to leave a message
* PIN Code to start phone alarm and or IM GPS (lost phones)
* Custom greeting (Custom menu options/audio)
Give known callers a PIN that lets them ring straight through to your phone. They can then input your number into their contacts as \[number\]\[pause pause pause\]\[PIN\] to make it seamless."
This is a full [IVR](https://en.wikipedia.org/wiki/Interactive_voice_response) system, beyond the scope of just Calls really. Probably [Asterisk](https://www.asterisk.org) would be needed.https://source.puri.sm/Librem5/Apps_Issues/-/issues/141night light / red shift not working on devkit2020-03-31T22:41:01ZGuido Gunthernight light / red shift not working on devkitThe shell supports this and my laptop does it, the devkit does not. Have to check if it's a userspace issue or if the dcss driver even support the gamma ramps.The shell supports this and my laptop does it, the devkit does not. Have to check if it's a userspace issue or if the dcss driver even support the gamma ramps.