Incoming call results in screen lighting up, but otherwise ignored: no ringing and no button to answer call
This happened several times today: my Librem 5 (running PureOS byzantium) is locked with the screen off, someone calls me, then I see that the screen turns on (so in that way the phone is reacting to the incoming call) but that's all that happens, it does not ring and it does not show the usual buttons to reject or answer the call. Meanwhile the person calling me (in one case myself from another phone) hears signals as if it was ringing.
journalctl shows the following:
feb 23 10:58:56 pureos ModemManager[597]: <info> [modem0/call3] call state changed: unknown -> ringing-in (incoming-new)
feb 23 10:58:56 pureos gsd-xsettings[925]: Failed to get current UI legacy scaling factor
feb 23 10:58:56 pureos gsd-xsettings[925]: Failed to get current UI legacy scaling factor
feb 23 10:58:56 pureos gsd-color[908]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
feb 23 10:58:58 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:58:58 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:00 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:00 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:02 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:02 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:04 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:04 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:06 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:06 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:08 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:08 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:10 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:10 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:12 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:12 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:14 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:14 pureos ModemManager[597]: <warn> [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
feb 23 10:59:16 pureos ModemManager[597]: <info> [modem0/call3] call state changed: ringing-in -> terminated (unknown)What could be going wrong here?
How to troubleshoot further? One idea is to turn on ModemManager debug output, I'll try that when I have time.
Are the "Failed to get current UI legacy scaling factor" and "unable to get EDID for xrandr-DSI-1: unable to get EDID for output" messages anything to worry about?
What about the "unexpected incoming call to number 'n/a' reported in call list: state active" message that comes twice every other second, what do those mean?