Librem 5 receive SMS fail

[marcux]

Hi all,
I have a strange problem with receiving SMS.
At first everything worked fine and I could both send/receive SMS (calls working as well).
I have had the problem from start with that the modem reset and both SMS and calls stopped working, but after a reboot everything worked fine again.
Two days ago all of a sudden I stopped receiving SMS, I can still send SMS:es and calls are working fine.
A reboot does not make any difference and everything I have tried still ends up in the same situation (double checking settings for mobile network and SMS/MMS settings in Chatty and trying different settings).
As I have read in other posts the APN for both network and SMS/MMS must be the same DNS name as it is not supported with different APNs.
MMS does not work as it requires another APN, this is Telia in Sweden, they have different APN for data and MMS.
I can not find anything useful that points me in any direction in the logs.

What should I do to figure out this problem?
What should I look for? What can I test?

Many thanks in advance!

[Skalman]

Hello and welcome to the forum!

My first suggestion would be to look at the output from journalctl to see if there are any error messages there that could give clues to what is happening when an SMS arrives.

Another thing to try is to run chatty with the debug option, to do that you first need to kill the autostarted chatty which can be done with killall chatty (need to do that twice because it starts again after the first kill), then when there is no longer any running chatty process, start it manually by doing “chatty --debug” which should produce debug messages, hopefully you can see something happening there when an SMS arrives, and some explanation to why it will not show you the SMS.

A third thing you can try is to use mmcli to see what things look like at the ModemManager level. If chatty is not running, then incoming SMS messages should be stored by ModemManager and you can then list them using mmcli with some option, see man mmcli to figure that out. Something like this could be interesting:

killall chatty
killall chatty
killall chatty
mmcli -m any --messaging-list-sms
# then send an sms to the L5, then check again
mmcli -m any --messaging-list-sms

Good luck, please let us know how it goes. Telia in Sweden should work (just not for MMS as you said).

[marcux]

Thank you Skalman!
First of all, I have tripled checked Telia modem settings so they shoud be correct.
APN: online.telia.se
In chatty I have removed all settings for APN in preferences ->SMS and MMS Settings -> MMS Carrier Settings
It was empty there from the beginning and then SMS was working so I assumed that I should leave it that way.

After

killall chatty
mmcli -m any --messaging-list-sms

The listing frpm mmcli is the same before and after sending SMS, the listing does not change.
It looks like this:

    /org/freedesktop/ModemManager1/SMS/23 (receiving)
    /org/freedesktop/ModemManager1/SMS/22 (receiving)
    /org/freedesktop/ModemManager1/SMS/21 (receiving)
    /org/freedesktop/ModemManager1/SMS/20 (receiving)
    /org/freedesktop/ModemManager1/SMS/19 (receiving)
    /org/freedesktop/ModemManager1/SMS/18 (receiving)
    /org/freedesktop/ModemManager1/SMS/17 (receiving)
    /org/freedesktop/ModemManager1/SMS/16 (receiving)
    /org/freedesktop/ModemManager1/SMS/15 (receiving)
    /org/freedesktop/ModemManager1/SMS/14 (receiving)
    /org/freedesktop/ModemManager1/SMS/13 (receiving)
    /org/freedesktop/ModemManager1/SMS/12 (receiving)

I put my SIM in my old Android to get all queued messages.
After I put the SIM back in my librem5 there has been sent 4 SMS to my phone.

Running chatty --debug:

(06:55:00) prefs: Reading /home/purism/.purple/prefs.xml
(06:55:00) prefs: Finished reading /home/purism/.purple/prefs.xml
(06:55:00) dbus: okkk
(06:55:00) plugins: probing /usr/lib/purple-2/joinpart.so
(06:55:00) plugins: probing /usr/lib/purple-2/perl.so
(06:55:00) plugins: probing /usr/lib/purple-2/newline.so
(06:55:00) plugins: probing /usr/lib/purple-2/liboscar.so
(06:55:00) plugins: /usr/lib/purple-2/liboscar.so is not usable because the 'purple_init_plugin' symbol could not be found.  Does the plugin call the PURPLE_INIT_PLUGIN() macro?
(06:55:00) plugins: probing /usr/lib/purple-2/ssl-nss.so
(06:55:00) plugins: probing /usr/lib/purple-2/libirc.so
(06:55:00) plugins: probing /usr/lib/purple-2/libjabber.so
(06:55:00) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found.  Does the plugin call the PURPLE_INIT_PLUGIN() macro?
(06:55:00) plugins: probing /usr/lib/purple-2/lurch.so
(06:55:00) plugins: probing /usr/lib/purple-2/libicq.so
(06:55:00) plugins: probing /usr/lib/purple-2/nss-prefs.so
(06:55:00) plugins: probing /usr/lib/purple-2/offlinemsg.so
(06:55:00) plugins: probing /usr/lib/purple-2/dbus-example.so
(06:55:00) plugins: probing /usr/lib/purple-2/psychic.so
(06:55:00) plugins: probing /usr/lib/purple-2/autoaccept.so
(06:55:00) plugins: probing /usr/lib/purple-2/libnovell.so
(06:55:00) plugins: probing /usr/lib/purple-2/jabber_http_file_upload.so
(06:55:00) plugins: probing /usr/lib/purple-2/carbons.so
(06:55:00) plugins: probing /usr/lib/purple-2/statenotify.so
(06:55:00) plugins: probing /usr/lib/purple-2/buddynote.so
(06:55:00) plugins: probing /usr/lib/purple-2/libzephyr.so
(06:55:00) plugins: probing /usr/lib/purple-2/libsametime.so
(06:55:00) plugins: /usr/lib/purple-2/libsametime.so has a prefs_info, but is a prpl. This is no longer supported.
(06:55:00) plugins: probing /usr/lib/purple-2/libaim.so
(06:55:00) plugins: probing /usr/lib/purple-2/libgg.so
(06:55:00) plugins: probing /usr/lib/purple-2/log_reader.so
(06:55:00) plugins: probing /usr/lib/purple-2/libsimple.so
(06:55:00) plugins: probing /usr/lib/purple-2/tcl.so
(06:55:00) plugins: /usr/lib/purple-2/tcl.so is not loadable: libtcl8.6.so: cannot open shared object file: No such file or directory
(06:55:00) plugins: probing /usr/lib/purple-2/idle.so
(06:55:00) plugins: probing /usr/lib/purple-2/libbonjour.so
(06:55:00) plugins: probing /usr/lib/purple-2/libxmpp.so
(06:55:00) plugins: probing /usr/lib/purple-2/ssl.so
(06:55:00) gg: Loading Gadu-Gadu protocol plugin with libgadu 1.12.2...
(06:55:01) mediamanager: Registered Audio/Source device Built-in Audio Headset Microphone + Stereo Microphones + Handset Microphone
(06:55:01) mediamanager: Registered Audio/Source device Modem Stereo
(06:55:01) mediamanager: Registered Audio/Sink device Built-in Audio Headphones + Speaker + Handset
(06:55:01) mediamanager: Registered Audio/Sink device Modem Stereo
(06:55:01) util: Reading file xmpp-caps.xml from directory /home/purism/.purple
(06:55:01) util: File /home/purism/.purple/xmpp-caps.xml does not exist (this is not necessarily an error)
(06:55:01) jabber: creating hash tables for data objects
(06:55:01) prefs: /purple/status/scores/offline changed, scheduling save.
(06:55:01) prefs: /purple/status/scores/available changed, scheduling save.
(06:55:01) prefs: /purple/status/scores/invisible changed, scheduling save.
(06:55:01) prefs: /purple/status/scores/away changed, scheduling save.
(06:55:01) prefs: /purple/status/scores/extended_away changed, scheduling save.
(06:55:01) prefs: /purple/status/scores/idle changed, scheduling save.
(06:55:01) prefs: /purple/status/scores/offline_msg changed, scheduling save.
(06:55:01) util: Reading file accounts.xml from directory /home/purism/.purple
(06:55:01) util: File /home/purism/.purple/accounts.xml does not exist (this is not necessarily an error)
(06:55:01) util: Reading file status.xml from directory /home/purism/.purple
(06:55:01) certificate: CertificateVerifier x509, singleuse requested but not found.
(06:55:01) certificate: CertificateVerifier singleuse registered
(06:55:01) certificate: CertificatePool x509, ca requested but not found.
(06:55:01) certificate: CertificateScheme x509 requested but not found.
(06:55:01) certificate/x509/ca: Lazy init failed because an X.509 Scheme is not yet registered. Maybe it will be better later.
(06:55:01) certificate/x509/ca: Init failed, probably because a dependency is not yet registered. It has been deferred to later.
(06:55:01) certificate: CertificatePool ca registered
(06:55:01) certificate: CertificatePool x509, tls_peers requested but not found.
(06:55:01) certificate: CertificatePool tls_peers registered
(06:55:01) certificate: CertificateVerifier x509, tls_cached requested but not found.
(06:55:01) certificate: CertificateVerifier tls_cached registered
(06:55:01) prefs: /purple/logging/format changed, scheduling save.
(06:55:01) prefs: /purple/logging/format changed, scheduling save.
(06:55:01) prefs: /purple/proxy/type changed, scheduling save.
(06:55:01) prefs: /purple/proxy/host changed, scheduling save.
(06:55:01) prefs: /purple/proxy/port changed, scheduling save.
(06:55:01) prefs: /purple/proxy/username changed, scheduling save.
(06:55:01) prefs: /purple/proxy/password changed, scheduling save.
(06:55:01) nss: Cipher - TLS_AES_128_GCM_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_CHACHA20_POLY1305_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_AES_256_GCM_SHA384: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_RC4_128_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_RC4_128_SHA: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_AES_128_GCM_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_AES_128_GCM_SHA256: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_AES_256_GCM_SHA384: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_AES_256_GCM_SHA384: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_AES_128_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_AES_128_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_AES_128_CBC_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_AES_128_CBC_SHA256: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_AES_256_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_AES_256_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_AES_256_CBC_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_AES_256_CBC_SHA256: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_RC4_128_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_RSA_WITH_AES_128_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_RSA_WITH_AES_256_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_ECDSA_WITH_RC4_128_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_RSA_WITH_RC4_128_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_AES_128_GCM_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_AES_256_GCM_SHA384: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_AES_128_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_AES_128_CBC_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_CAMELLIA_128_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_AES_256_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_AES_256_CBC_SHA256: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_CAMELLIA_256_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_SEED_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_3DES_EDE_CBC_SHA: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_RC4_128_SHA: Enabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_RC4_128_MD5: Enabled
(06:55:01) nss: Cipher - TLS_DHE_RSA_WITH_DES_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_DHE_DSS_WITH_DES_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_DES_CBC_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_ECDSA_WITH_NULL_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDHE_RSA_WITH_NULL_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_RSA_WITH_NULL_SHA: Disabled
(06:55:01) nss: Cipher - TLS_ECDH_ECDSA_WITH_NULL_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_NULL_SHA: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_NULL_SHA256: Disabled
(06:55:01) nss: Cipher - TLS_RSA_WITH_NULL_MD5: Disabled
(06:55:01) nss: TLS supported versions: 0x0301 through 0x0304
(06:55:01) nss: TLS versions allowed by default: 0x0301 through 0x0304
(06:55:01) certificate: CertificateScheme x509 requested but not found.
(06:55:01) certificate: CertificateScheme x509 registered
(06:55:01) util: Reading file smileys.xml from directory /home/purism/.purple
(06:55:01) util: File /home/purism/.purple/smileys.xml does not exist (this is not necessarily an error)
(06:55:01) stun: using server 
(06:55:01) prefs: /purple/savedstatus/default changed, scheduling save.
(06:55:01) prefs: Reading /home/purism/.purple/prefs.xml
(06:55:01) prefs: /purple/savedstatus/default changed, scheduling save.
(06:55:01) prefs: /plugins/core/nss_prefs/cipher_list changed, scheduling save.
(06:55:01) prefs: /chatty/plugins/loaded changed, scheduling save.
(06:55:01) prefs: Finished reading /home/purism/.purple/prefs.xml
(06:55:01) util: Reading file blist.xml from directory /home/purism/.purple
(06:55:01) util: File /home/purism/.purple/blist.xml does not exist (this is not necessarily an error)
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/ssl-nss.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/ssl.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/jabber_http_file_upload.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/lurch.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/ssl-nss.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/ssl.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/jabber_http_file_upload.so
(06:55:01) plugins: Loading saved plugin /usr/lib/purple-2/lurch.so
(06:55:01) plugins: probing /usr/lib/purple-2/joinpart.so
(06:55:01) plugins: probing /usr/lib/purple-2/perl.so
(06:55:01) plugins: probing /usr/lib/purple-2/newline.so
(06:55:01) plugins: probing /usr/lib/purple-2/liboscar.so
(06:55:01) plugins: /usr/lib/purple-2/liboscar.so is not usable because the 'purple_init_plugin' symbol could not be found.  Does the plugin call the PURPLE_INIT_PLUGIN() macro?
(06:55:01) plugins: probing /usr/lib/purple-2/ssl-nss.so
(06:55:01) plugins: probing /usr/lib/purple-2/libirc.so
(06:55:01) plugins: probing /usr/lib/purple-2/libjabber.so
(06:55:01) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found.  Does the plugin call the PURPLE_INIT_PLUGIN() macro?
(06:55:01) plugins: probing /usr/lib/purple-2/lurch.so
(06:55:01) plugins: probing /usr/lib/purple-2/libicq.so
(06:55:01) plugins: probing /usr/lib/purple-2/nss-prefs.so
(06:55:01) plugins: probing /usr/lib/purple-2/offlinemsg.so
(06:55:01) plugins: probing /usr/lib/purple-2/dbus-example.so
(06:55:01) plugins: probing /usr/lib/purple-2/psychic.so
(06:55:01) plugins: probing /usr/lib/purple-2/autoaccept.so
(06:55:01) plugins: probing /usr/lib/purple-2/libnovell.so
(06:55:01) plugins: probing /usr/lib/purple-2/jabber_http_file_upload.so
(06:55:01) plugins: probing /usr/lib/purple-2/carbons.so
(06:55:01) plugins: probing /usr/lib/purple-2/statenotify.so
(06:55:01) plugins: probing /usr/lib/purple-2/buddynote.so
(06:55:01) plugins: probing /usr/lib/purple-2/libzephyr.so
(06:55:01) plugins: probing /usr/lib/purple-2/libsametime.so
(06:55:01) plugins: probing /usr/lib/purple-2/libaim.so
(06:55:01) plugins: probing /usr/lib/purple-2/libgg.so
(06:55:01) plugins: probing /usr/lib/purple-2/log_reader.so
(06:55:01) plugins: probing /usr/lib/purple-2/libsimple.so
(06:55:01) plugins: probing /usr/lib/purple-2/tcl.so
(06:55:01) plugins: /usr/lib/purple-2/tcl.so is not loadable: libtcl8.6.so: cannot open shared object file: No such file or directory
(06:55:01) plugins: probing /usr/lib/purple-2/idle.so
(06:55:01) plugins: probing /usr/lib/purple-2/libbonjour.so
(06:55:01) plugins: probing /usr/lib/purple-2/libxmpp.so
(06:55:01) plugins: probing /usr/lib/purple-2/ssl.so
(06:55:01) pounce: Error reading pounces: Failed to open file “/home/purism/.purple/pounces.xml”: No such file or directory
(06:55:02) mediamanager: Registered Audio/Source device Built-in Audio Headset Microphone + Stereo Microphones + Handset Microphone
(06:55:02) mediamanager: Registered Audio/Source device Modem Stereo
(06:55:02) mediamanager: Registered Audio/Sink device Built-in Audio Headphones + Speaker + Handset
(06:55:02) mediamanager: Registered Audio/Sink device Modem Stereo
(06:55:06) util: Writing file prefs.xml to directory /home/purism/.purple
(06:55:06) util: Writing file /home/purism/.purple/prefs.xml
(06:55:06) util: Writing file status.xml to directory /home/purism/.purple
(06:55:06) util: Writing file /home/purism/.purple/status.xml

Here is also the latest 30 mins of the log:

mar 13 08:07:31 pureos NetworkManager[701]: <info>  [1678691251.4952] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
mar 13 08:07:39 pureos systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mar 13 08:14:21 pureos systemd-networkd[562]: wlan0: Link DOWN
mar 13 08:14:21 pureos NetworkManager[701]: <info>  [1678691661.3308] device (wlan0): set-hw-addr: set MAC address to BE:C1:14:DF:91:EE (scanning)
mar 13 08:14:21 pureos systemd-networkd[562]: wlan0: Link UP
mar 13 08:14:21 pureos NetworkManager[701]: <info>  [1678691661.3824] device (wlan0): supplicant interface state: disconnected -> interface_disabled
mar 13 08:14:21 pureos NetworkManager[701]: <info>  [1678691661.3835] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
mar 13 08:14:21 pureos NetworkManager[701]: <info>  [1678691661.3886] device (wlan0): supplicant interface state: interface_disabled -> inactive
mar 13 08:14:21 pureos NetworkManager[701]: <info>  [1678691661.3891] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
mar 13 08:14:45 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:14:45 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:14:45 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:14:45 pureos phosh-session[2894]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mar 13 08:14:45 pureos phosh-session[2894]: > Warning:          Unsupported maximum keycode 569, clipping.
mar 13 08:14:45 pureos phosh-session[2894]: >                   X11 cannot support keycodes above 255.
mar 13 08:14:45 pureos phosh-session[2894]: Errors from xkbcomp are not fatal to the X server
mar 13 08:15:03 pureos systemd[1]: Starting Load/Save RF Kill Switch Status...
mar 13 08:15:03 pureos NetworkManager[701]: <info>  [1678691703.5010] manager: rfkill: Wi-Fi now disabled by radio killswitch
mar 13 08:15:03 pureos NetworkManager[701]: <info>  [1678691703.5019] device (wlan0): state change: disconnected -> unavailable (reason 'none', sys-iface-state: 'managed')
mar 13 08:15:03 pureos systemd[1]: Started Load/Save RF Kill Switch Status.
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-110
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
mar 13 08:15:03 pureos kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
mar 13 08:15:03 pureos kernel: ieee80211 phy0: brcmf_cfg80211_get_channel: chanspec failed (-110)
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -123
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-123
mar 13 08:15:03 pureos kernel: brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
mar 13 08:15:03 pureos kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -123
mar 13 08:15:03 pureos kernel: ieee80211 phy0: brcmf_cfg80211_get_tx_power: error (-123)
mar 13 08:15:04 pureos systemd-networkd[562]: wlan0: Link DOWN
mar 13 08:15:04 pureos NetworkManager[701]: <info>  [1678691704.1543] device (wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
mar 13 08:15:04 pureos NetworkManager[701]: <info>  [1678691704.1629] manager: NetworkManager state is now CONNECTED_GLOBAL
mar 13 08:15:04 pureos NetworkManager[701]: <info>  [1678691704.1659] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
mar 13 08:15:04 pureos systemd[1]: Stopping Bluetooth attachment for brcmfmac driver...
mar 13 08:15:04 pureos NetworkManager[701]: <info>  [1678691704.1846] radio killswitch /sys/devices/platform/soc@0/30800000.bus/30b50000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill4 disappeared
mar 13 08:15:04 pureos kernel: Bluetooth: hci0: sending frame failed (-49)
mar 13 08:15:04 pureos kernel: mmc1: card 0001 removed
mar 13 08:15:04 pureos kernel: Bluetooth: hci0: Opcode 0x c03 failed: -49
mar 13 08:15:04 pureos wpa_supplicant[777]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
mar 13 08:15:04 pureos phoc[948]: [libinput] event4  - generic ft5x06 (f0): client bug: event processing lagging behind by 17ms, your system is too slow
mar 13 08:15:04 pureos bluetoothd[1172]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc
mar 13 08:15:04 pureos bluetoothd[1172]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc
mar 13 08:15:04 pureos systemd[979]: Stopped target Bluetooth.
mar 13 08:15:04 pureos dbus-daemon[699]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=701 comm="/usr/sbin/NetworkManager --no-daemon ")
mar 13 08:15:04 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
mar 13 08:15:04 pureos systemd[1]: bluetooth-brcmfmac.service: Succeeded.
mar 13 08:15:04 pureos systemd[1]: Stopped Bluetooth attachment for brcmfmac driver.
mar 13 08:15:04 pureos systemd[1]: Stopped target Bluetooth.
mar 13 08:15:04 pureos dbus-daemon[699]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mar 13 08:15:04 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
mar 13 08:15:09 pureos systemd[1]: systemd-rfkill.service: Succeeded.
mar 13 08:15:14 pureos systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mar 13 08:15:37 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
mar 13 08:15:37 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:15:37 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:15:37 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:17:01 pureos CRON[2964]: pam_unix(cron:account): account root has expired (account expired)
mar 13 08:17:01 pureos CRON[2964]: Authentication failure
mar 13 08:17:01 pureos cron[2964]: Authentication failure
mar 13 08:22:33 pureos systemd-timesyncd[626]: Initial synchronization to time server 193.182.111.14:123 (2.debian.pool.ntp.org).
mar 13 08:25:53 pureos ModemManager[902]: <warn>  [modem0] network reject indication received
mar 13 08:25:53 pureos ModemManager[902]: <warn>  [modem0]   service domain: ps
mar 13 08:25:53 pureos ModemManager[902]: <warn>  [modem0]   radio interface: umts
mar 13 08:25:53 pureos ModemManager[902]: <warn>  [modem0]   reject cause: implicitly-detached
mar 13 08:25:53 pureos ModemManager[902]: <info>  [modem0/bearer1] verbose call end reason (3,1009): [cm] implicitly-detached
mar 13 08:25:53 pureos ModemManager[902]: <info>  [modem0] state changed (connected -> registered)
mar 13 08:25:53 pureos ModemManager[902]: <info>  [modem0/bearer1] connection #3 finished: duration 4208s, tx: 364 bytes, rx: 203 bytes
mar 13 08:25:53 pureos mmsdtng[1030]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 11 New State: 8, Reason: 1
mar 13 08:25:53 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 8
mar 13 08:25:53 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
mar 13 08:25:53 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
mar 13 08:25:53 pureos mmsdtng[1030]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaab0b0f1ba0 handler 0xaaaaea595a20
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.4317] modem["cdc-wdm0"]: modem state changed, 'connected' --> 'registered' (reason: user-requested)
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.4333] device (cdc-wdm0): state change: activated -> failed (reason 'modem-no-carrier', sys-iface-state: 'managed')
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.4427] manager: NetworkManager state is now DISCONNECTED
mar 13 08:25:53 pureos NetworkManager[701]: <warn>  [1678692353.4895] device (cdc-wdm0): Activation: failed for connection 'Telia 3G'
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.5168] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.6167] policy: auto-activating connection 'Telia 3G' (d5091d21-4151-4b68-a214-52717ca7e307)
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.6428] device (cdc-wdm0): Activation: starting connection 'Telia 3G' (d5091d21-4151-4b68-a214-52717ca7e307)
mar 13 08:25:53 pureos systemd-timesyncd[626]: No network connectivity, watching for changes.
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.6625] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
mar 13 08:25:53 pureos NetworkManager[701]: <info>  [1678692353.6809] manager: NetworkManager state is now CONNECTING
mar 13 08:25:53 pureos dbus-daemon[699]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=701 comm="/usr/sbin/NetworkManager --no-daemon ")
mar 13 08:25:53 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
mar 13 08:25:54 pureos dbus-daemon[699]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mar 13 08:25:54 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
mar 13 08:25:54 pureos ModemManager[902]: <info>  [modem0] simple connect started...
mar 13 08:25:54 pureos ModemManager[902]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
mar 13 08:25:54 pureos ModemManager[902]: <info>  [modem0] simple connect state (5/8): register
mar 13 08:25:54 pureos ModemManager[902]: <info>  [modem0] simple connect state (6/8): bearer
mar 13 08:25:54 pureos ModemManager[902]: <info>  [modem0] simple connect state (7/8): connect
mar 13 08:25:54 pureos ModemManager[902]: <info>  [modem0] state changed (registered -> connecting)
mar 13 08:25:54 pureos NetworkManager[701]: <info>  [1678692354.4660] modem["cdc-wdm0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
mar 13 08:25:54 pureos mmsdtng[1030]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 8 New State: 10, Reason: 1
mar 13 08:25:54 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 10
mar 13 08:25:54 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
mar 13 08:25:54 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
mar 13 08:25:54 pureos mmsdtng[1030]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaab0b0f1ba0 handler 0xaaaaea595a20
mar 13 08:25:58 pureos ModemManager[902]: <info>  [modem0/bearer1] QMI IPv4 Settings:
mar 13 08:25:58 pureos ModemManager[902]: <info>  [modem0/bearer1]     address: 10.13.229.179/29
mar 13 08:25:58 pureos ModemManager[902]: <info>  [modem0/bearer1]     gateway: 10.13.229.180
mar 13 08:25:58 pureos ModemManager[902]: <info>  [modem0/bearer1]     DNS #1: 2.248.248.101
mar 13 08:25:58 pureos ModemManager[902]: <info>  [modem0/bearer1]     DNS #2: 2.248.248.100
mar 13 08:25:58 pureos ModemManager[902]: <info>  [modem0/bearer1]        MTU: 1500
mar 13 08:26:00 pureos ModemManager[902]: <info>  [modem0/bearer1] couldn't start network: QMI protocol error (14): 'CallFailed'
mar 13 08:26:00 pureos ModemManager[902]: <info>  [modem0/bearer1] verbose call end reason (6,50): [3gpp] ipv4-only-allowed
mar 13 08:26:00 pureos ModemManager[902]: <info>  [modem0] state changed (connecting -> connected)
mar 13 08:26:00 pureos ModemManager[902]: <info>  [modem0] simple connect state (8/8): all done
mar 13 08:26:00 pureos mmsdtng[1030]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 10 New State: 11, Reason: 1
mar 13 08:26:00 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 11
mar 13 08:26:00 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
mar 13 08:26:00 pureos mmsdtng[1030]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
mar 13 08:26:00 pureos mmsdtng[1030]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaab0b0f1ba0 handler 0xaaaaea595a20
mar 13 08:26:00 pureos mmsdtng[1030]: ../plugins/modemmanager.c:process_mms_process_message_queue() Processing any unsent/unreceived MMS messages.
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.4000] modem["cdc-wdm0"]: modem state changed, 'connecting' --> 'connected' (reason: user-requested)
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.4753] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.4974] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5032] modem["cdc-wdm0"]: IPv6 configuration disabled
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5053] modem-broadband[cdc-wdm0]: IPv4 static configuration:
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5065] modem-broadband[cdc-wdm0]:   address 10.13.229.179/29
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5067] modem-broadband[cdc-wdm0]:   gateway 10.13.229.180
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5069] modem-broadband[cdc-wdm0]:   DNS 2.248.248.101
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5070] modem-broadband[cdc-wdm0]:   DNS 2.248.248.100
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5070] modem-broadband[cdc-wdm0]:   MTU 1500
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.5620] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
mar 13 08:26:00 pureos systemd-timesyncd[626]: Network configuration changed, trying to establish connection.
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.6561] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.6635] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.6742] manager: NetworkManager state is now CONNECTED_LOCAL
mar 13 08:26:00 pureos systemd-timesyncd[626]: Initial synchronization to time server 193.182.111.14:123 (2.debian.pool.ntp.org).
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.6961] manager: NetworkManager state is now CONNECTED_SITE
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.6984] policy: set 'Telia 3G' (wwx0e8e33e3f256) as default for IPv4 routing and DNS
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.7183] device (cdc-wdm0): Activation: successful, device activated.
mar 13 08:26:00 pureos NetworkManager[701]: <info>  [1678692360.7361] manager: NetworkManager state is now CONNECTED_GLOBAL
mar 13 08:26:01 pureos mmsdtng[1030]: ../src/service.c:activate_bearer() service 0xaaab0b0f1ba0 setup 0 active 0
mar 13 08:26:01 pureos mmsdtng[1030]: ../src/service.c:activate_bearer() service 0xaaab0b0f1ba0 waiting for 20 seconds
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:set_context() Setting Context...
mar 13 08:26:01 pureos mmsdtng[1030]: ../src/service.c:mms_service_set_mmsc() service 0xaaab0b0f1ba0 mmsc NULL
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:set_context() Max number of bearers: 1
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:set_context() Current Context APN: online.telia.se, mmsd-tng settings MMS APN: NULL
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:set_context() Current Context APN: online.telia.se, mmsd-tng settings MMS APN: NULL
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:set_context() Current Context APN: online.telia.se, mmsd-tng settings MMS APN: NULL
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/0 active 1 context_active 0
mar 13 08:26:01 pureos mmsdtng[1030]: ../plugins/modemmanager.c:bearer_handler() Error activating context!
mar 13 08:26:01 pureos mmsdtng[1030]: ../src/service.c:mms_service_bearer_notify() service=0xaaab0b0f1ba0 active=0 iface=(null) proxy=(null)
mar 13 08:26:11 pureos systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mar 13 08:26:43 pureos ModemManager[902]: <info>  [modem0] 3GPP registration state changed (home -> searching)
mar 13 08:26:43 pureos ModemManager[902]: <warn>  [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
mar 13 08:26:43 pureos ModemManager[902]: <warn>  [modem0] couldn't load operator name: Current operator id is still unknown
mar 13 08:26:48 pureos ModemManager[902]: <info>  [modem0] 3GPP registration state changed (searching -> idle)
mar 13 08:26:48 pureos ModemManager[902]: <info>  [modem0] 3GPP registration state changed (idle -> registering)
mar 13 08:26:48 pureos ModemManager[902]: <info>  [modem0] 3GPP registration state changed (registering -> home)
mar 13 08:29:40 pureos systemd-logind[755]: Power key pressed.
mar 13 08:29:40 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:29:40 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:29:41 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:29:41 pureos phosh-session[3018]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mar 13 08:29:41 pureos phosh-session[3018]: > Warning:          Unsupported maximum keycode 569, clipping.
mar 13 08:29:41 pureos phosh-session[3018]: >                   X11 cannot support keycodes above 255.
mar 13 08:29:41 pureos phosh-session[3018]: Errors from xkbcomp are not fatal to the X server
mar 13 08:29:46 pureos phosh[1306]: ../../../gobject/gsignal.c:3479: invalid unclassed object pointer for value type 'PhoshNotification'
mar 13 08:29:51 pureos sm.puri.OSK0.desktop[1512]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/se.yaml", but it's missing: No such file or directory (os error 2)
mar 13 08:29:51 pureos sm.puri.OSK0.desktop[1512]: Info: Loaded layout Resource: se
mar 13 08:29:53 pureos phoc[948]: [libinput] event4  - generic ft5x06 (f0): client bug: event processing lagging behind by 19ms, your system is too slow
mar 13 08:29:54 pureos phosh[1306]: get_toplevel_from_activity: assertion 'PHOSH_IS_ACTIVITY (activity)' failed
mar 13 08:29:54 pureos phosh[1306]: phosh_toplevel_activate: assertion 'PHOSH_IS_TOPLEVEL (self)' failed
mar 13 08:29:54 pureos phosh[1306]: gtk_widget_has_focus: assertion 'GTK_IS_WIDGET (widget)' failed
mar 13 08:29:54 pureos phosh[1306]: gtk_widget_grab_focus: assertion 'GTK_IS_WIDGET (widget)' failed
mar 13 08:29:55 pureos systemd-logind[755]: Power key pressed.
mar 13 08:29:55 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
mar 13 08:29:55 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:29:55 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:29:55 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:33:49 pureos systemd-logind[755]: Power key pressed.
mar 13 08:33:50 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:33:50 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:33:50 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:34:57 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
mar 13 08:34:57 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:34:57 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:34:57 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:36:13 pureos systemd-logind[755]: Power key pressed.
mar 13 08:36:14 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:36:14 pureos gsd-xsettings[1407]: Failed to get current UI legacy scaling factor
mar 13 08:36:14 pureos gsd-color[1391]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
mar 13 08:36:23 pureos dbus-daemon[1039]: [session uid=1000 pid=1039] Activating service name='org.gnome.zbrown.KingsCross' requested by ':1.28' (uid=1000 pid=1306 comm="/usr/libexec/phosh ")
mar 13 08:36:23 pureos dbus-daemon[1039]: [session uid=1000 pid=1039] Successfully activated service 'org.gnome.zbrown.KingsCross'
mar 13 08:36:23 pureos systemd[979]: Started VTE child process 3093 launched by org.gnome.zbrown.KingsCross process 3084.
mar 13 08:36:24 pureos sm.puri.OSK0.desktop[1512]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/se.yaml", but it's missing: No such file or directory (os error 2)
mar 13 08:36:24 pureos sm.puri.OSK0.desktop[1512]: Warning: Failed to load layout from Resource: terminal/se: Missing resource, skipping
mar 13 08:36:24 pureos sm.puri.OSK0.desktop[1512]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
mar 13 08:36:24 pureos sm.puri.OSK0.desktop[1512]: Info: Loaded layout Resource: terminal/us
mar 13 08:36:31 pureos sm.puri.Chatty-daemon.desktop[3122]: [1:23:09.689833887] [3122]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0
mar 13 08:36:31 pureos sm.puri.Chatty-daemon.desktop[3122]: Oops, secure memory pool already initialized
mar 13 08:36:31 pureos mmsdtng[1030]: ../src/service.c:handle_method_call_manager() At Get Services Method Call
mar 13 08:36:31 pureos mmsdtng[1030]: ../src/service.c:handle_method_call_service() Retrieving all Messages...
mar 13 08:36:31 pureos mmsdtng[1030]: ../src/service.c:handle_method_call_service() No Messages!
mar 13 08:36:32 pureos gnome-session[1255]: gnome-session-binary[1255]: WARNING: App 'sm.puri.Chatty-daemon.desktop' respawning too quickly
mar 13 08:36:32 pureos gnome-session[1255]: gnome-session-binary[1255]: WARNING: Error on restarting session managed app: Component 'sm.puri.Chatty-daemon.desktop' crashing too quickly
mar 13 08:36:32 pureos gnome-session-binary[1255]: WARNING: App 'sm.puri.Chatty-daemon.desktop' respawning too quickly
mar 13 08:36:32 pureos gnome-session-binary[1255]: WARNING: Error on restarting session managed app: Component 'sm.puri.Chatty-daemon.desktop' crashing too quickly
mar 13 08:38:00 pureos systemd[979]: vte-spawn-4be356fe-e8d6-457e-9f8c-07581504622a.scope: Succeeded.
mar 13 08:38:00 pureos sm.puri.OSK0.desktop[1512]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/se.yaml", but it's missing: No such file or directory (os error 2)
mar 13 08:38:00 pureos sm.puri.OSK0.desktop[1512]: Info: Loaded layout Resource: se
mar 13 08:38:04 pureos dbus-daemon[1039]: [session uid=1000 pid=1039] Activating service name='org.gnome.zbrown.KingsCross' requested by ':1.28' (uid=1000 pid=1306 comm="/usr/libexec/phosh ")
mar 13 08:38:04 pureos dbus-daemon[1039]: [session uid=1000 pid=1039] Successfully activated service 'org.gnome.zbrown.KingsCross'
mar 13 08:38:05 pureos systemd[979]: Started VTE child process 3176 launched by org.gnome.zbrown.KingsCross process 3167.
mar 13 08:38:05 pureos sm.puri.OSK0.desktop[1512]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/se.yaml", but it's missing: No such file or directory (os error 2)
mar 13 08:38:05 pureos sm.puri.OSK0.desktop[1512]: Warning: Failed to load layout from Resource: terminal/se: Missing resource, skipping
mar 13 08:38:05 pureos sm.puri.OSK0.desktop[1512]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
mar 13 08:38:05 pureos sm.puri.OSK0.desktop[1512]: Info: Loaded layout Resource: terminal/us

I would appreciate some hael to find the reason, I do not seem to be able to figure out what is going on.

Many thanks!!!

[marcux]

Haaa!!
I got my SMS working again!!
I found this post:

Librem 5: can no longer receive SMS messages or calls

I had a related issue very recently. This was the only discussion I could find on the topic, so I’ll post my experience and solution here for posterity. It’s looking like mms support is around the corner, though, so hopefully this won’t be needed soon. A friend had shared with me a list from their text app (some samsung note taking app), and his phone sent it as an mms - at least that’s what it appeared to be initially. I didn’t receive it, so he sent it again. I suggested breaking it up, and t…

As soon as I have removed SMS:es stuck(?) in the modem with:
mmcli -m any --messaging-delete-sms=[index]
It all started working again!!

Thanks for your help Skalman!!

I love my Librem5, it is the way a phone should be!!

[Skalman]

Good job solving it!

If you enjoyed this exercise, then you will probably have much fun with your Librem 5

Do you know what caused it to end up in the state is was in – can you reproduce it somehow? It would be a good deed to solve the bug properly. The question is why chatty did not collect all those old sms messages, chatty should have done that by itself, you should not need to do the --messaging-delete-sms manually. Although I do understand it was fun.

[marcux]

You are right Skalman, it would be great to fix that bug properly.

I am not sure, but it seems that if the modem is reset and it reconnects with the network and you try to send an SMS before connection is up (chatty reports failure with the red X), it seems to get stuck in the modem with the text (receiving).

I will report back in this post if I can figure out a pattern.

Even if librem5 has small glitches here and there, I still can enjoy the freedom and privacy that we all deserve!!

[Zimmy]

@marcux

Two days ago all of a sudden I stopped receiving SMS, I can still send SMS:es and calls are working fine.
A reboot does not make any difference and everything I have tried still ends up in the same situation

I’ve been plagued by this problem. I’d go for a couple of days without receiving any SMS, not knowing anything was wrong. People then began asking me if I received their texts. Put SIM card back into iPhone and all the messages not received on the L5 immediately dumped onto the iPhone. I was using the L5 as my main phone for the last few months. Missing many SMSs, and unaware that anything was amiss, is unacceptable for me, so I switched back to the iPhone. Sad. This is a major problem.

[marcux]

Hi Zimmy,
I am sorry to hear that you had to go back to a harvesting phone.
I see you problem as this is a major need for me to. Most info in my world is exchanged through SMS, with wife, friends, children, parents of other children, server down from work aso…
I though hope that I have a solution working for me as the value of Free software and privacy is of great value to me I think it is worth walking the extra mile.
I found this post on a script (watchmodem) that gives you a notification when the modem is interupted:

Reseting mobile connection - Librem 5

This is how I remember I did it: Put the scripts into /home/purism/bin (watch-modem.sh, recover-modem.sh): purism@pureos:~$ ls -l bin/*modem* -rwxr-xr-x 1 root root 310 2. Jun 11:00 bin/recover-modem.sh -rwxr-xr-x 1 purism purism 1404 2. Jun 10:56 bin/watch-modem.sh recover-modem.sh is called as root (using sudo) - make it belong to root (like shown above) using this command: sudo chmod 775 /home/purism/bin/recover-modem.sh; sudo chown root:root /home/purism/bin/recover-modem.sh Edi…

I put it up as a systemd service (as described in the post) and it works well, I get a notification when the modem is interuped.
I usually wait for a bit to see that the modem is online again, then I check the SMS in the modem with:
mmcli -m any --messaging-list-sms
After this I send an SMS to my self to verify that it is still working.
This is a quick operation and do not take long. If you can see this as a temporary solution, please go ahead and bring your librem5 back to life.
As said before the pattern I see so far is that SMS that fails to be sent out are stuck in the modem and eventually gives you this problem. I will post again when I am able to verify if this is the case.

[ChriChri]

This information is deprecated (I’ll try to place a hint on the target url).

• @dos fixed an underlying problem and it looks like there’ll arrive soon a kernel and some udev rules that will make it unlikely that the modem vanishes from the bus and that the bus will get lost. My workaround might be deprecated.
• To follow up on the first versions and maybe improve them or add other workarounds/watch scripts for the modem in the Librem5 I made this repo. It is still active and I try to update the README.md according to what I learn about the modem.

There’s not a debian/PureOS (nor pmOS) package, yet, but for practice I’ll probably make one anyway . You could try to build it from the cloned repositories directory by calling dpkg-buildpackage -b --no-sign, but this is still work in progress.

FYI: @marcux, @Zimmy

Update: typo

[OpojOJirYAlG]

So, I’m having this same symptom of sms not being received with sending working, however there are no messages stuck in receiving on the modem and as best I can tell the modem itself is just not receiving sms messages.

If I put the sim back in my android device sms receive works though the messages that were sent when the sim was in the L5 don’t come through which seems to indicate from the carriers perspective they were delivered.

I’ve gone through the solutions in this thread to no avail, if anyone has any suggestions I’m looking for ideas that aren’t go back to android

[jalibster]

Your latest update applied 2 days ago has killed my SMS receiving message and even delete the message queue no longer fixes this. You need to get this fixed. I’m now afraid to update my phone anymore as this is 3 times an update has done this to me and now this one I cannot fix. Until this is fixed properly, it is unsuitable for anything but an experiment.

[Dlonk]

I’ve never had an update kill my SMS, but I have had SMS break and need me to delete “receiving” messages, and after I delete them I don’t start receiving again sometimes for a couple of minutes. Maybe restarting makes it happen faster.

How were you able to tell that it was the updates that killed your SMS? Obviously I probably have a different cellular service provider, so my situation might be different. But I never felt like the updates were actually what killed it for me – it seemed to just die sometimes from normal use. So I was curious.

[jalibster]

I used to think it was just coincidence and you may be right. My only problem with this is the only time my receiving messages stops is after a execute an update. BTW the provider is “Freedom Mobile”. Also, after clearing and restarting my phone 3 times the messages finally started coming in. I don’t know why no other phone OS experiences this yet but for people to accept this phone as a mainstream product someone needs to figure this out. Maybe I’ll take a crack at it. Thanks for your additional information.

[FranklyFlawless]

@jalibster

BTW the provider is “Freedom Mobile”.

I do not experience any issues like yours on Freedom Mobile, so it is more likely that the problem lies elsewhere.

[dos]

There were no updates that could influence SMS reception in recent months.