Bug: infinite loop of connection errors
asked 2014-01-21 08:11:13 +0300
My office is mostly surrounded by steel-reinforced concrete, ensuring that all phone connectivity flickers between nothing and a single bar of 2G. One problem that occasionally gets triggered by this is a device-crippling flood of "Problem with connection" messages; the device takes a long time to respond to button presses and touch commands, while the "Problem with connection" notification popup is constantly spammed. During this, the CPU is consumed entirely by lipstick, connectionagent, timed-qt5 and msyncd.
Journalctl log is as follows:
Jan 21 13:26:01 localhost connmand[1607]: connman_inet_clear_address: Invalid argument
Jan 21 13:26:01 localhost connmand[1607]: connman_inet_clear_ipv6_address: Invalid argument
Jan 21 13:26:01 localhost lipstick[2131]: ---- errorReported: Operation aborted
Jan 21 13:26:01 localhost lipstick[2131]: ---- errorReported: connect-failed
Jan 21 13:26:01 localhost lipstick[2131]: ---- errorReported: Connection failure: vodafone AU
Jan 21 13:26:01 localhost lipstick[2131]: ---- errorReported: connect-failed
(repeat at a rate of about 5 times per second)
Killing the lipstick process stops the flood, at the expense of closing everything that was open.
I've encountered the same bug a few times.
mattikbk ( 2014-01-21 08:13:43 +0300 )editI've encountered the same bug a few times too in the past few days, had to hard reboot as the phone was not responding anymore (could just wake the screen - with a significant delay - and then chose to wait or close non-responding apps). In my case, it was not due to bad reception or steel concrete.
Kabouik ( 2014-01-21 11:13:55 +0300 )editI got that behavior several times. lipstick, connectionagent, timed-qt5 and msyncd, eating the whole CPU
corsarium ( 2014-01-21 12:46:37 +0300 )editSame here, related to this topic: https://together.jolla.com/question/11696/cant-get-out-of-lock-screen-repeating-connection-problem-banners-long-wakeup-delay/
damourti ( 2014-01-24 15:05:15 +0300 )editThis is a significant issue now for me and renders the phone useless. The solution below is not a solution, it is impossible to do anything with the phone until it is rebooted. This is a major bug.
bockersjv ( 2014-01-26 17:41:46 +0300 )edit