OS-issues issueshttps://source.puri.sm/Librem5/OS-issues/-/issues2023-04-12T10:01:22Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/311Secondary call disconnecting kills audio on established/primary call2023-04-12T10:01:22ZEvangelos Ribeiro TzarasSecondary call disconnecting kills audio on established/primary callCurrently calls will autoreject secondary calls, because it does not implement [call waiting](https://gitlab.gnome.org/GNOME/calls/-/issues/209) yet.
Once the second call gets disconnected the audio for the existing call is broken (both...Currently calls will autoreject secondary calls, because it does not implement [call waiting](https://gitlab.gnome.org/GNOME/calls/-/issues/209) yet.
Once the second call gets disconnected the audio for the existing call is broken (both from and to the network).
Note that the broken audio is **not** due to calls autorejecting the call: Even if the call get's disconnected from the caller audio gets broken but is still fine **while** ringing.
Some observations:
- Audio continues to works just fine on the PinePhone when the second
- I've disabled auto hangup in calls to test if it makes any difference who hangs up on the second call: Audio also dies if the caller hangs up.
- I tried using older MM (`1.14.12-0.2pureos1`) which did not use QMI voice call management to see if that makes any difference, but any additional call gets routed to voicemail irrespective of the call waiting status.
- Once the second call is disconnected the modem audio card does not produce any more audio samples. When running `parecord` on the modems audio card: The instant the second call is disconnected the recording **stops** (as opposed to continuing but recording silence).
As the modem audio simply stops it would point to an issue with the modem (firmware), but another opinion or ideas about how to further narrow it down would be welcome /cc @angus.ainslie @sebastian.krzyszkowiak @martin.kepplinger
## Workaround
A possible workaround would be to `mmcli -m any --voice-disable-call-waiting`. In this case extra calls go straight to voicemail (or rejected as "busy") and I get notified of the missed call by SMS from my network operator.
We could disable call waiting entirely in Calls for the time being to prevent audio getting killed.https://source.puri.sm/Librem5/OS-issues/-/issues/308Incoming call switches and leaves mobile data from 4G to 3G (according to ico...2022-12-27T11:42:50ZJan VlugIncoming call switches and leaves mobile data from 4G to 3G (according to icon in status bar)I had the Librem 5 up and running with a 4G mobile data connection (according to the status bar icon).
I received a call, and I saw an exclamation mark in the mobile data icon, and the 4G icon changed into a 3G icon.
After the call, th...I had the Librem 5 up and running with a 4G mobile data connection (according to the status bar icon).
I received a call, and I saw an exclamation mark in the mobile data icon, and the 4G icon changed into a 3G icon.
After the call, the exclamation mark disappeared after a while, but the connection stayed in 3G (according to the icon in the status bar).
This might be related to the fact that my provider does not support MMS. See [this bug in mobile-broadband-provider-info](https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info/-/issues/14).
Here are two log files. In this first one the call came in and the mobile data connection changed from 4G to 3G. There are some comments in the log file too:
[back_to_3G.log](/uploads/8b7c3bba996675f94be374a7006e0288/back_to_3G.log)
This is the log file of when I changed the mobile data settings a bit in GNOME Settings, and in the end got the 4G connection icon back.
[mobile_settings_changed.log](/uploads/374a73fa13494f110eff1d413a2c7c21/mobile_settings_changed.log)
The above described issue is a description from the user perspective. I would not be surprised if there are actually a few separate issues that cause this behavior, like:
* phone switching back to 3G on incoming call
* modem not switching back to 4G after call
* incorrect handling of providers that do not support MMS
* incorrect representation of mobile data state in GNOME settings
* incorrect representation of mobile data state in status bar
Please let me know when you need any more additional information or testing.
Edit: After closing and opening GNOME settings, I saw that the mobile settings were indeed changed in GNOME settings. So it seems that they are not correctly refreshed.https://source.puri.sm/Librem5/OS-issues/-/issues/306Rescue system (jumpdrive), chroot, luks and kernel updates2023-02-23T22:13:34ZPirate PraveenRescue system (jumpdrive), chroot, luks and kernel updatesCurrently jumpdrive provides a rescue system via usb-c cable (and telnet from a laptop), if the phone does not boot. This allows us to chroot into the phone and fix any issues. But jumpdrive does not support luks yet and this reported up...Currently jumpdrive provides a rescue system via usb-c cable (and telnet from a laptop), if the phone does not boot. This allows us to chroot into the phone and fix any issues. But jumpdrive does not support luks yet and this reported upstream https://github.com/dreemurrs-embedded/Jumpdrive/issues/79. Alternative option is to use qemu on the laptop to get a chroot environment on the phone as jumpdrive shares the emmc as a block device and this allows us to use luks support on the laptop to get a chroot.
This brings up the issue of flash-kernel failing if the kernel package is updated or reinstalled via chroot (details in the issue linked above). Though on mobian the kernel updates works in the chroot also because it does not use flash-kernel and it expects uboot to be handled independently, for example using tow boot.
So I was wondering if pureos should also consider this approach for crimson. Do you think it is reasonable expectation to be able to update a kernel using a chroot (just with the storage device and not connected with the phone)? Also it may be beneficial to everyone if pureos and mobian follows a common approach to bootloader. May be pureos is targeting only Librem 5 right now, do you plan to support pinephone or other devices with pureos? Answer to this question may decide if it is worthwhile to follow the tow boot approach here.https://source.puri.sm/Librem5/OS-issues/-/issues/304Implement org.freedesktop.ScreenSaver2022-12-11T13:19:34ZDorota CzaplejewiczImplement org.freedesktop.ScreenSaverThe Phosh session exposes 2 dbus services for the screen saver, with differing behaviour (see https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/355#note_1613814 ).
However, both services expose pretty much identical functionalit...The Phosh session exposes 2 dbus services for the screen saver, with differing behaviour (see https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/355#note_1613814 ).
However, both services expose pretty much identical functionality, compare: https://lists.freedesktop.org/archives/xdg/2006-June/006523.html and https://lists.freedesktop.org/archives/xdg/2007-March/009187.html .
The "freedesktop" service seems to be dead.
This means that applications binding to the general (freedesktop) one first will successfuly find it and try to use it, but will not actually be connected to any behaviour they expected.
Filing in os-issues because I don't know better.https://source.puri.sm/Librem5/OS-issues/-/issues/303Cell broadcast: report from Germany during CB test2023-11-24T18:34:50ZJonathan BrielmaierCell broadcast: report from Germany during CB testToday (2022-12-08) at 11:00 am (local time) there was a test run of the cell broadcast system in Germany. I installed [Angus' bm818-tool](https://source.puri.sm/angus.ainslie/bm818-tools/-/blob/tool-app/usr/bin/bm818-tool) and enabled CB...Today (2022-12-08) at 11:00 am (local time) there was a test run of the cell broadcast system in Germany. I installed [Angus' bm818-tool](https://source.puri.sm/angus.ainslie/bm818-tools/-/blob/tool-app/usr/bin/bm818-tool) and enabled CBS yesterday on my Librem 5.
The phone was in Baden-Württemberg and I use the Deutsche Telekom network. An iPhone SE 2nd Gen in the Deutsche Telekom network sitting next to the Librem 5 did received the CB.
Here is what ModemManager did logged. I can provide the full log if needed, just not sure if there are any private information included...
```
Dez 08 10:59:17 claudii ModemManager[785]: [/dev/cdc-wdm0] Received message...
[...]
Dez 08 10:59:19 claudii ModemManager[785]: [/dev/cdc-wdm0] Received generic indication (translated)...
<<<<<< QMUX:
<<<<<< length = 17
<<<<<< flags = 0x80
<<<<<< service = "nas"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "indication"
<<<<<< transaction = 8
<<<<<< tlv_length = 5
<<<<<< message = "Event Report" (0x0002)
<<<<<< TLV:
<<<<<< type = "Signal Strength" (0x10)
<<<<<< length = 2
<<<<<< value = B5:08
<<<<<< translated = [ strength = '-75' radio_interface = 'lte' ]
Dez 08 10:59:19 claudii ModemManager[785]: <debug> [modem3] signal strength indication (lte): -75 dBm --> 62%
Dez 08 10:59:19 claudii ModemManager[785]: <debug> [modem3] signal quality updated (62)
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3/ttyUSB2/at] <-- '<CR><LF>+CBM: 88<CR><LF>40C0111F0113D4E2940A0A328B522A0BE40C52934FE735492C8282CCA2940A2206B320194C260351D175900C2693BD62B2170C076A8162305D2D070AB7412D10B53CA783C2ECB29C0E6A81CC6F398858AED3E763343BEC06<CR><LF>'
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3/ttyUSB2/at] <-- '<CR><LF>+CBM: 88<CR><LF>40C0111F012364500B444597E565507A0E72BF41E4B0FB5C96BB402D90B12EA7A3CB7250DA6D7ECBDB617AFAEDD681D0743A7CAE7BBDEE61B9BBEE3EBBC47537D9452EBFDA6536B9EE3E97DDA016085A17B3D37374990C02<CR><LF><CR><LF>+CBM: 84<CR><LF>40C0111F0133E2BC0E24ACBBC9E579B84D0799FD7290B06CE7B3D76579DD7D9ECFC7E83A5D0FAABBC9A065981E9ED3E56F38BAEC46A7D9E6320BE40CD3D36F77985D065DC372B7BEECA6CBC3EC32280612BEDDEE<CR><LF>'
Dez 08 10:59:21 claudii ModemManager[785]: [/dev/cdc-wdm0] Received message...
<<<<<< RAW:
<<<<<< length = 116
<<<<<< data = 01:73:00:80:05:01:04:01:00:01:00:67:00:11:60:00:01:FF:FF:FF:FF:07:58:00:40:C0:11:1F:01:13:D4:E2:94:0A:0A:32:8B:52:2A:0B:E4:0C:52:93:4F:E7:35:49:2C:82:82:CC:A2:94:0A:22:06:B3:20:19:4C:26:03:51:D1:75:90:0C:26:93:BD:62:B2:17:0C:07:6A:81:62:30:5D:2D:07:0A:B7:41:2D:10:B5:3C:A7:83:C2:EC:B2:9C:0E:6A:81:CC:6F:39:88:58:AE:D3:E7:63:34:3B:EC:06:16:01:00:00
Dez 08 10:59:21 claudii ModemManager[785]: [/dev/cdc-wdm0] Received generic indication (translated)...
<<<<<< QMUX:
<<<<<< length = 115
<<<<<< flags = 0x80
<<<<<< service = "wms"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "indication"
<<<<<< transaction = 1
<<<<<< tlv_length = 103
<<<<<< message = "Event Report" (0x0001)
<<<<<< TLV:
<<<<<< type = "Transfer Route MT Message" (0x11)
<<<<<< length = 96
<<<<<< value = 01:FF:FF:FF:FF:07:58:00:40:C0:11:1F:01:13:D4:E2:94:0A:0A:32:8B:52:2A:0B:E4:0C:52:93:4F:E7:35:49:2C:82:82:CC:A2:94:0A:22:06:B3:20:19:4C:26:03:51:D1:75:90:0C:26:93:BD:62:B2:17:0C:07:6A:81:62:30:5D:2D:07:0A:B7:41:2D:10:B5:3C:A7:83:C2:EC:B2:9C:0E:6A:81:CC:6F:39:88:58:AE:D3:E7:63:34:3B:EC:06
<<<<<< translated = [ ack_indicator = 'do-not-send' transaction_id = '4294967295' format = 'gsm-wcdma-broadcast' raw_data = '{ [0] = '64 ' [1] = '192 ' [2] = '17 ' [3] = '31 ' [4] = '1 ' [5] = '19 ' [6] = '212 ' [7] = '226 ' [8] = '148 ' [9] = '10 ' [10] = '10 ' [11] = '50 ' [12] = '139 ' [13] = '82 ' [14] = '42 ' [15] = '11 ' [16] = '228 ' [17] = '12 ' [18] = '82 ' [19] = '147 ' [20] = '79 ' [21] = '231 ' [22] = '53 ' [23] = '73 ' [24] = '44 ' [25] = '130 ' [26] = '130 ' [27] = '204 ' [28] = '162 ' [29] = '148 ' [30] = '10 ' [31] = '34 ' [32] = '6 ' [33] = '179 ' [34] = '32 ' [35] = '25 ' [36] = '76 ' [37] = '38 ' [38] = '3 ' [39] = '81 ' [40] = '209 ' [41] = '117 ' [42] = '144 ' [43] = '12 ' [44] = '38 ' [45] = '147 ' [46] = '189 ' [47] = '98 ' [48] = '178 ' [49] = '23 ' [50] = '12 ' [51] = '7 ' [52] = '106 ' [53] = '129 ' [54] = '98 ' [55] = '48 ' [56] = '93 ' [57] = '45 ' [58] = '7 ' [59] = '10 ' [60] = '183 ' [61] = '65 ' [62] = '45 ' [63] = '16 ' [64] = '181 ' [65] = '60 ' [66] = '167 ' [67] = '131 ' [68] = '194 ' [69] = '236 ' [70] = '178 ' [71] = '156 ' [72] = '14 ' [73] = '106 ' [74] = '129 ' [75] = '204 ' [76] = '111 ' [77] = '57 ' [78] = '136 ' [79] = '88 ' [80] = '174 ' [81] = '211 ' [82] = '231 ' [83] = '99 ' [84] = '52 ' [85] = '59 ' [86] = '236 ' [87] = '6 '}' ]
<<<<<< TLV:
<<<<<< type = "SMS on IMS" (0x16)
<<<<<< length = 1
<<<<<< value = 00
<<<<<< translated = no
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3] Got transfer-route MT message
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3] parsing PDU (0)...
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3] This is a transfer-route message
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3] deliver type PDU detected
Dez 08 10:59:21 claudii ModemManager[785]: <debug> [modem3] error parsing PDU (0): PDU too short, cannot read number: 88 < 98
Dez 08 10:59:21 claudii ModemManager[785]: [/dev/cdc-wdm0] Received message...
<<<<<< RAW:
<<<<<< length = 116
<<<<<< data = 01:73:00:80:05:01:04:02:00:01:00:67:00:11:60:00:01:FF:FF:FF:FF:07:58:00:40:C0:11:1F:01:23:64:50:0B:44:45:97:E5:65:50:7A:0E:72:BF:41:E4:B0:FB:5C:96:BB:40:2D:90:B1:2E:A7:A3:CB:72:50:DA:6D:7E:CB:DB:61:7A:FA:ED:D6:81:D0:74:3A:7C:AE:7B:BD:EE:61:B9:BB:EE:3E:BB:C4:75:37:D9:45:2E:BF:DA:65:36:B9:EE:3E:97:DD:A0:16:08:5A:17:B3:D3:73:74:99:0C:02:16:01:00:00
Dez 08 10:59:21 claudii ModemManager[785]: [/dev/cdc-wdm0] Received generic indication (translated)...
[...]
<<<<<< translated = [ ack_indicator = 'do-not-send' transaction_id = '4294967295' format = 'gsm-wcdma-broadcast'
[...]
Dez 08 10:59:21 claudii ModemManager[785]: [/dev/cdc-wdm0] Received generic indication (translated)...
[...]
<<<<<< translated = [ ack_indicator = 'do-not-send' transaction_id = '4294967295' format = 'gsm-wcdma-broadcast'
[...]
Dez 08 10:59:43 claudii ModemManager[785]: <debug> [modem3/bearer7] got QMI WDS event report
Dez 08 10:59:44 claudii ModemManager[785]: <debug> [modem3/ttyUSB0/qcdm] <-- 60 26 00 46 26 18 51 76 2e f7 4c fc 00 07 46 26 7f 74 91 2e f7 4c fc 00 01 46 26 27 74 9d 2e f7 4c fc 00 02 46 a6 74 9d 02 c0 4b 7e
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3/ttyUSB2/at] <-- '<CR><LF>+CBM: 88<CR><LF>41301112001450E95358BC06A5CEAAF3C80209AB4E62717A2D26A94529E81A943AA9C123480693C940C4B70B04C3B96232970C2693815AA0184C57CB81AA6839A80582CADFE2F23D2C77D7DD67500B64F6CB41C4729D3E07<CR><LF><CR><LF>+CBM: 88<CR><LF>41301112002463343BEC26835AA0E21C242ECFE965341DB42EA7DD65D0B16C0EA3E52E500B742DA7E965791994749BDF7350B86E06A1E974F85CF77ADDC37277DD7D7689EB6EB28B5C7EB5CB6C72DD7D2EBB412D10B22C07<CR><LF>'
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3/ttyUSB2/at] <-- '<CR><LF>+CBM: 88<CR><LF>413011120034E1FAFC5C3E97C56537C8FE76EB40C2BA9B5C9E87DB7490D92F0709CB763E7B5D96D7DDE7F97C8CAED3F5A0BA9B0C5A86E9E1395DFE86A3CB6E749A6D2EB340CE303DFD7687D965D0352C77EBCB6EBA3CCC06<CR><LF>'
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3/ttyUSB2/at] <-- '<CR><LF>+CBM: 13<CR><LF>41301112004465500C247CBBDD<CR><LF>'
[...]
<<<<<< translated = [ ack_indicator = 'do-not-send' transaction_id = '4294967295' format = 'gsm-wcdma-broadcast' raw_data = '{ [0] = '65 ' [1] = '48 ' [2] = '17 ' [3] = '18 ' [4] = '0 ' [5] = '20 ' [6] = '80 ' [7] = '233 ' [8] = '83 ' [9] = '88 ' [10] = '188 ' [11] = '6 ' [12] = '165 ' [13] = '206 ' [14] = '170 ' [15] = '243 ' [16] = '200 ' [17] = '2 ' [18] = '9 ' [19] = '171 ' [20] = '78 ' [21] = '98 ' [22] = '113 ' [23] = '122 ' [24] = '45 ' [25] = '38 ' [26] = '169 ' [27] = '69 ' [28] = '41 ' [29] = '232 ' [30] = '26 ' [31] = '148 ' [32] = '58 ' [33] = '169 ' [34] = '193 ' [35] = '35 ' [36] = '72 ' [37] = '6 ' [38] = '147 ' [39] = '201 ' [40] = '64 ' [41] = '196 ' [42] = '183 ' [43] = '11 ' [44] = '4 ' [45] = '195 ' [46] = '185 ' [47] = '98 ' [48] = '50 ' [49] = '151 ' [50] = '12 ' [51] = '38 ' [52] = '147 ' [53] = '129 ' [54] = '90 ' [55] = '160 ' [56] = '24 ' [57] = '76 ' [58] = '87 ' [59] = '203 ' [60] = '129 ' [61] = '170 ' [62] = '104 ' [63] = '57 ' [64] = '168 ' [65] = '5 ' [66] = '130 ' [67] = '202 ' [68] = '223 ' [69] = '226 ' [70] = '242 ' [71] = '61 ' [72] = '44 ' [73] = '119 ' [74] = '215 ' [75] = '221 ' [76] = '103 ' [77] = '80 ' [78] = '11 ' [79] = '100 ' [80] = '246 ' [81] = '203 ' [82] = '65 ' [83] = '196 ' [84] = '114 ' [85] = '157 ' [86] = '62 ' [87] = '7 '}' ]
<<<<<< TLV:
<<<<<< type = "SMS on IMS" (0x16)
<<<<<< length = 1
<<<<<< value = 00
<<<<<< translated = no
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] Got transfer-route MT message
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] parsing PDU (0)...
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] This is a transfer-route message
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] submit type PDU detected
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] message reference: 48
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] number parsed: 0041059c3585a#605*
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] PID: 206
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] user data encoding is GSM7
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] user data length: 243 elements
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] user data length: 213 bytes
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] error parsing PDU (0): PDU too short, cannot read TP-UD: 88 < 229
Dez 08 10:59:47 claudii ModemManager[785]: [/dev/cdc-wdm0] Received message...
<<<<<< RAW:
<<<<<< length = 116
<<<<<< data = 01:73:00:80:05:01:04:05:00:01:00:67:00:11:60:00:01:FF:FF:FF:FF:07:58:00:41:30:11:12:00:24:63:34:3B:EC:26:83:5A:A0:E2:1C:24:2E:CF:E9:65:34:1D:B4:2E:A7:DD:65:D0:B1:6C:0E:A3:E5:2E:50:0B:74:2D:A7:E9:65:79:19:94:74:9B:DF:73:50:B8:6E:06:A1:E9:74:F8:5C:F7:7A:DD:C3:72:77:DD:7D:76:89:EB:6E:B2:8B:5C:7E:B5:CB:6C:72:DD:7D:2E:BB:41:2D:10:B2:2C:07:16:01:00:00
Dez 08 10:59:47 claudii ModemManager[785]: [/dev/cdc-wdm0] Received generic indication (translated)...
[...]
<<<<<< translated = [ ack_indicator = 'do-not-send' transaction_id = '4294967295' format = 'gsm-wcdma-broadcast'
[...]
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] Got transfer-route MT message
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] parsing PDU (0)...
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] This is a transfer-route message
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] submit type PDU detected
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] message reference: 48
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] number parsed: 00423643#3ac6238*5
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] PID: 160
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] user data encoding is UCS2
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] user data length: 28 elements
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] user data length: 28 bytes
Dez 08 10:59:47 claudii ModemManager[785]: <debug> [modem3] decoding SMS text with 4294967287 elements
Dez 08 10:59:48 claudii systemd[1]: ModemManager.service: Main process exited, code=dumped, status=11/SEGV
Dez 08 10:59:48 claudii systemd[1]: ModemManager.service: Failed with result 'core-dump'.
Dez 08 10:59:48 claudii systemd[1]: ModemManager.service: Consumed 13.395s CPU time.
Dez 08 10:59:48 claudii systemd[1]: ModemManager.service: Scheduled restart job, restart counter is at 1.
Dez 08 10:59:48 claudii systemd[1]: Stopped Modem Manager.
Dez 08 10:59:48 claudii systemd[1]: ModemManager.service: Consumed 13.395s CPU time.
Dez 08 10:59:48 claudii systemd[1]: Starting Modem Manager...
```
And the coredump of ModemManager. I can provide the full coredump if required. Just tell me :)
```
sudo coredumpctl info
PID: 785 (ModemManager)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Thu 2022-12-08 10:59:47 CET (1h 40min ago)
Command Line: /usr/sbin/ModemManager --log-level=DEBUG
Executable: /usr/sbin/ModemManager
Control Group: /system.slice/ModemManager.service
Unit: ModemManager.service
Slice: system.slice
Boot ID: 3f15b684700c48cab9c105ce788da100
Machine ID: 08f1e8fd07b64070b01c039ebcc520f8
Hostname: claudii
Storage: /var/lib/systemd/coredump/core.ModemManager.0.3f15b684700c48cab9c105ce788da100.785.1670493587000000.zst
Message: Process 785 (ModemManager) of user 0 dumped core.
Stack trace of thread 785:
#0 0x0000ffffba04a630 n/a (libc.so.6 + 0x85630)
#1 0x0000ffffba4dd11c g_array_append_vals (libglib-2.0.so.0 + 0x2011c)
#2 0x0000ffffba4debe4 g_byte_array_append (libglib-2.0.so.0 + 0x21be4)
#3 0x0000aaaada595cdc sms_decode_text (ModemManager + 0x145cdc)
#4 0x0000aaaada54132c add_new_read_sms_part (ModemManager + 0xf132c)
#5 0x0000aaaada5414f8 messaging_event_report_indication_cb (ModemManager + 0xf14f8)
#6 0x0000ffffba9a3520 g_cclosure_marshal_VOID__BOXEDv (libgobject-2.0.so.0 + 0x18520)
#7 0x0000ffffba9a0274 n/a (libgobject-2.0.so.0 + 0x15274)
#8 0x0000ffffba9b9c34 g_signal_emit_valist (libgobject-2.0.so.0 + 0x2ec34)
#9 0x0000ffffba9b9e90 g_signal_emit (libgobject-2.0.so.0 + 0x2ee90)
#10 0x0000ffffba787a64 n/a (libqmi-glib.so.5 + 0x187a64)
#11 0x0000ffffba698c64 n/a (libqmi-glib.so.5 + 0x98c64)
#12 0x0000ffffba510ab4 g_main_context_dispatch (libglib-2.0.so.0 + 0x53ab4)
#13 0x0000ffffba510e5c n/a (libglib-2.0.so.0 + 0x53e5c)
#14 0x0000ffffba5111b0 g_main_loop_run (libglib-2.0.so.0 + 0x541b0)
#15 0x0000aaaada4a7574 main (ModemManager + 0x57574)
#16 0x0000ffffb9fe5e18 __libc_start_main (libc.so.6 + 0x20e18)
#17 0x0000aaaada4a77c8 $x (ModemManager + 0x577c8)
#18 0x0000aaaada4a77c8 $x (ModemManager + 0x577c8)
```
~Jonathanhttps://source.puri.sm/Librem5/OS-issues/-/issues/300Tapping url link does not switch to browser2022-12-02T10:22:55ZTomas ÖqvistTapping url link does not switch to browser# What problem did you encounter
When tapping a url link (e.g. in Geary, Telegram, Tootle) on the Librem 5 the link opens a new tab in the Firefox but L5 will not switch to FF.
Is there a way to make L5 always switch to the browser when...# What problem did you encounter
When tapping a url link (e.g. in Geary, Telegram, Tootle) on the Librem 5 the link opens a new tab in the Firefox but L5 will not switch to FF.
Is there a way to make L5 always switch to the browser when opening a url link?
## What is the actual behaviour?
When tapping a url link (e.g. in Geary, Telegram, Tootle) on the Librem 5 the link opens as a new tab in Firefox (my default browser). L5 also switches to FF, if it is not open in the background, which is what I want. However, if FF is already open, the link opens as a new tab but L5 will not switch to FF. I have to open the app switcher and manually go to FF to see the url I just opened.
## What is the expected behaviour?
Tapping a url link would switch to Firefox and show the requested url
## How to reproduce
Open Firefox and switch to e.g. Tootle
Tap a url link
Wait for the Firefox app to come into focus
# What hardware are you running on?
- [ ] amd64 qemu image
- [x] Librem5 Evergreen
- [ ] other (please elaborate)
# Relevant OS information
Linux pureos 6.0.0-1-librem5
## Which kernel are you using?
Linux pureos 6.0.0-1-librem5 #1 SMP PREEMPT Tue Nov 15 21:27:04 UTC 2022 aarch64 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?
Depending on the nature of the issue, you may consider adding the output of:
* lsblk (for mounting issues)
* lsusb (for usb attachment issues)
* any journalctl logs that look suspicious
* etc.https://source.puri.sm/Librem5/OS-issues/-/issues/299VoLTE does not work with Deutsche Telekom2022-12-14T20:17:17ZJonathan BrielmaierVoLTE does not work with Deutsche Telekom## What problem did you encounter
VoLTE does not work with my Librem 5 in the Deutsche Telekom network in Germany.
### What is the actual behaviour?
VoLTE does not work. When doing or receiving a call the network drops from 4G to 2G du...## What problem did you encounter
VoLTE does not work with my Librem 5 in the Deutsche Telekom network in Germany.
### What is the actual behaviour?
VoLTE does not work. When doing or receiving a call the network drops from 4G to 2G during the call. There is no 3G network in Germany anymore...
* I'm on newest byzantinum. All patches applied.
* The problem exist since I received the Librem 5. VoLTE never worked with Deutsche Telekom (so its not a regression).
* I asked my MVNO (PennyMobil via Congstar), if I'm on a VoLTE "block list". They said no and I should check my APN (see below) settings. It doesn't make any difference using this one or `internet.t-mobile`...
```
Name: Congstar Internet
APN: internet.v6.telekom
Proxy: keine Eingabe
Port: keine Eingabe
Benutzername: telekom
Passwort: tm
MCC: 262
MNC: 01
Authentifizierungstyp: PAP
APN-typ: default,supl
```
* I updated the modem firmware together with Joao, it did not helped. My current firmware:
```
$ sudo socat - /dev/ttyUSB3,crnl
AT+BMSWVER
+BMSWVER: M100E_YCSN0_1.0.0_220926,YCSN0_M100E_1BAD_3117_V1.0.0.2_20220930,M100E_1.0.4_200715
```
* When using a Vodafone Deutschland SIM-card VoLTE does work out of the box with the currently installed firmware.https://source.puri.sm/Librem5/OS-issues/-/issues/297No option to have on incoming call only ringtone, but no vibration2022-11-25T11:16:00ZMatthias ApitzNo option to have on incoming call only ringtone, but no vibrationThis is on a Librem 5 with Byzantium and the latest updates. The subject says it all: no way unconfigure vibration on incoming calls.This is on a Librem 5 with Byzantium and the latest updates. The subject says it all: no way unconfigure vibration on incoming calls.https://source.puri.sm/Librem5/OS-issues/-/issues/295Qt's tlwRect.size() reports ~16 GByte2022-11-20T11:47:39ZMatthias ApitzQt's tlwRect.size() reports ~16 GByteWhile trying to run the app `Stellarium` on the L5, this fails with a message
```
qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17179344900
```
The maintainer of stellarium reports that this comes out of Qt from `tlwRect....While trying to run the app `Stellarium` on the L5, this fails with a message
```
qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17179344900
```
The maintainer of stellarium reports that this comes out of Qt from `tlwRect.size() ` in `qwidgetrepaintmanager.cpp` reporting this size of "top-level window". See also the thread https://github.com/Stellarium/stellarium/discussions/2831#
It seems not to be exactly 16 GByte;
```
$ echo '16*1024*1024*1024' | bc
17179869184
```https://source.puri.sm/Librem5/OS-issues/-/issues/294Manual mobile network selection always fail with 'Timeout was reached'2022-11-10T04:54:45ZPirate PraveenManual mobile network selection always fail with 'Timeout was reached'Under Settings -> Mobile -> Network -> Automatic, when disabling the toggle, it always fail with 'Timeout was reached' error. This could be one reason why we are not able to register on a network most of the time when traveling and tower...Under Settings -> Mobile -> Network -> Automatic, when disabling the toggle, it always fail with 'Timeout was reached' error. This could be one reason why we are not able to register on a network most of the time when traveling and towers are changed.
I'm using pureos byzantium.
Originally reported upstream at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2129 but upstream no longer supports this version of gnome.https://source.puri.sm/Librem5/OS-issues/-/issues/293Please include `phosh-antispam` into the repos2022-11-20T22:15:45ZChris TalbotPlease include `phosh-antispam` into the repos`phosh-antispam` is now in the Deb repos, so this should be a straight port.`phosh-antispam` is now in the Deb repos, so this should be a straight port.https://source.puri.sm/Librem5/OS-issues/-/issues/291For Discussion: Carrying a patch for curl to get Visual Voicemail to work2022-11-03T01:07:23ZChris TalbotFor Discussion: Carrying a patch for curl to get Visual Voicemail to workHello!
T-Mobile USA has modified their servers to no longer advertise a method of authentication (PLAIN) for Visual Voicemail. However, the IMAP RFC allows for the method to be used as a fallback. I suspect since T-mobile only tests the...Hello!
T-Mobile USA has modified their servers to no longer advertise a method of authentication (PLAIN) for Visual Voicemail. However, the IMAP RFC allows for the method to be used as a fallback. I suspect since T-mobile only tests their servers against iOS and Android, they see whatever update they did not breaking anything.
However for curl, it does NOT handle this, so to access the IMAP server, this patch is required: https://github.com/curl/curl/pull/8986 . I have asked a few times how to get this merged, but really haven't hear anything back.
Ideally, I would like this to be merged so there are no issues, but I have no idea how to move that forward. In the mean time, it would be nice to carry the patch in PureOS so folks with T-Mobile can keep using Visual Voicemail.
Also, any feedback on how to move that patch forward would be welcome too.
Thank you!https://source.puri.sm/Librem5/OS-issues/-/issues/290smartcard: Don't list two readers when there's only ne2022-10-24T13:36:03ZGuido Gunthersmartcard: Don't list two readers when there's only ne```
$ opensc-tool -l
# Detected readers (pcsc)
Nr. Card Features Name
0 Yes L5 built-in SmartCard Reader 00 01 00 00
1 Yes L5 built-in SmartCard Reader 00 01 00 01
```
Similar things happen with [pcsc_sc...```
$ opensc-tool -l
# Detected readers (pcsc)
Nr. Card Features Name
0 Yes L5 built-in SmartCard Reader 00 01 00 00
1 Yes L5 built-in SmartCard Reader 00 01 00 01
```
Similar things happen with [pcsc_scan](https://source.puri.sm/firmware/ttxs-firmware/-/blob/purism/PURISM.md#testing-the-smartcard). We can limit slots in config but I have no idea yet what the right fix for the problem is.https://source.puri.sm/Librem5/OS-issues/-/issues/289Cannot move inside directory in Files app2022-10-17T08:34:36ZElias RudbergCannot move inside directory in Files appIn the Files app, I think it was earlier possible to move inside a directory by tapping on it. However, that no longer works.
Steps to reproduce:
- Open the "Files" app
- Try to go inside a directory, for example "Downloads" or "Picture...In the Files app, I think it was earlier possible to move inside a directory by tapping on it. However, that no longer works.
Steps to reproduce:
- Open the "Files" app
- Try to go inside a directory, for example "Downloads" or "Pictures", by tapping on it
- Nothing happens
Long-press leads to a context menu being shown, including a "Open" option that looks promising, but it does not seem possible to select anything in that menu, it disappears when you lift your finger.
I think this has worked earlier, not sure when it stopped working.
This is on a Librem 5 with PureOS byzantium with the most recent updates installed.https://source.puri.sm/Librem5/OS-issues/-/issues/284Please port phosh-antispam into PureOS2022-11-20T22:15:47ZChris TalbotPlease port phosh-antispam into PureOSIt is already ported into Debian and should be a straight port:
https://salsa.debian.org/DebianOnMobile-team/phosh-antispam
https://tracker.debian.org/pkg/phosh-antispamIt is already ported into Debian and should be a straight port:
https://salsa.debian.org/DebianOnMobile-team/phosh-antispam
https://tracker.debian.org/pkg/phosh-antispamEvangelos Ribeiro TzarasEvangelos Ribeiro Tzarashttps://source.puri.sm/Librem5/OS-issues/-/issues/283sharing files to laptop via data cable2022-08-18T19:51:10ZPirate Praveensharing files to laptop via data cableIn android, when a data cable is connected, a notification comes to choose how to use the cable. By default it is just charging and there is an option to share files and this exposes the storage as a block device/usb storage to laptop. I...In android, when a data cable is connected, a notification comes to choose how to use the cable. By default it is just charging and there is an option to share files and this exposes the storage as a block device/usb storage to laptop. I think this should be enabled in Librem 5 as well. Jumpdrive has that functionality already, so it may be easy to integrate. Though mounting same disk in both places can be tricky.https://source.puri.sm/Librem5/OS-issues/-/issues/281Settings -> Regional & Language does not actually change the interface langua...2022-08-10T12:29:17ZPirate PraveenSettings -> Regional & Language does not actually change the interface language when the locale is not generatedI have selected Malayalam as the language but the interface is still in English and locale command shows en_US.UTF-8 as locale. I assume the locale need to be generated using dpkg-reconfigure locales command for this to work. May be ther...I have selected Malayalam as the language but the interface is still in English and locale command shows en_US.UTF-8 as locale. I assume the locale need to be generated using dpkg-reconfigure locales command for this to work. May be there is a better way to do it via systemd as well. But currently this is broken.https://source.puri.sm/Librem5/OS-issues/-/issues/279[Contacts] Unable to create new entry2022-07-26T22:39:51ZMladen Pejakovic[Contacts] Unable to create new entry# Contacts app
### Problem description
Unable to create/save a contact in the contact app. Error message is “Unable to create new contacts: Persona store has not yet been prepared.” Trying to use a local address book and not sync it wi...# Contacts app
### Problem description
Unable to create/save a contact in the contact app. Error message is “Unable to create new contacts: Persona store has not yet been prepared.” Trying to use a local address book and not sync it with any cloud/internet based services.
### Steps to reproduce
1. Open the app
2. Tap `ADD` to create new entry
3. "lets me type in a name, there are no fields to put in a phone #, but there are fields for birthday and url which I leave blank, and when I try to save the contact is when I get the error message."
### Logs
**Journal:** [logs.txt](/uploads/70e01042d3605c0b02a5c76bfc4c8886/logs.txt)
## PureOS
**Version:** PureOS 10, up to datehttps://source.puri.sm/Librem5/OS-issues/-/issues/276make bluetooth tethering easy and include by default2022-11-09T18:04:36ZPirate Praveenmake bluetooth tethering easy and include by defaultOnly blueman has support from bluetooth tethering (Netwrok Access Point), so it should be made adaptive and installed by default or we should add this feature directly to gnome's bluetooth support.
Though pairing with another laptop run...Only blueman has support from bluetooth tethering (Netwrok Access Point), so it should be made adaptive and installed by default or we should add this feature directly to gnome's bluetooth support.
Though pairing with another laptop running Debian sid took quite a lot of tries. The device was detected by both devices but pairing was not happening.
Once blueman is installed we can run blueman-services and turn on Network Access Point (NAP support). This works for getting an IP address. But internet connection does not work by default. Probably it has to be configured manually now (sysctl and iptables).https://source.puri.sm/Librem5/OS-issues/-/issues/275wifi tethering breaks roughly once a day and need a reboot2022-07-01T22:11:55ZPirate Praveenwifi tethering breaks roughly once a day and need a rebootWhen wifi tethering is on for a long time, the wifi device vanishes and turns tethering off. It comes back after some time but tethering needs to be turned on, but if goes off again if tethering is turned on and any clients are connected...When wifi tethering is on for a long time, the wifi device vanishes and turns tethering off. It comes back after some time but tethering needs to be turned on, but if goes off again if tethering is turned on and any clients are connected and using internet. Even many restarts or hks cycle does not help. Only a reboot fixes things. It keeps working until next day and it breaks again. I noticed this for 3+ days already. I use wifi tethering heavily as my main internet connection for laptop.