enabling flight mode shows airplane + [2g|3g] icon

[Sergio Schvezov]

known duplicate with different end result: bug #1386109

====

NM fails to send a proper networking status updated signal.

[Alexander Sack (asac)]

tvoss asked to have this also tracked on network-manager...

[Alexander Sack (asac)]

used ota-1 tag assuming that its just UI problem. If thats not case, please drop that tag again.

[Mathieu Trudel-Lapierre (cyphermox)]

tvoss; how does this relate to NetworkManager? Does this have to do with PrimaryConnectionType?

[Jussi Pakkanen (jpakkane)]

Attached is a dbus dump trace of when this happens. The only difference is that it displays a 3G icon rather than a 2G one.

[Jussi Pakkanen (jpakkane)]

Combing through the log we find these kinds of things:

method call sender=:1.132 -> dest=org.freedesktop.NetworkManager serial=121 path=/; interface=org.freedesktop.DBus.Properties; member=Get
   string "org.freedesktop.NetworkManager.Connection.Active"
   string "Devices"
method call sender=:1.133 -> dest=org.freedesktop.NetworkManager serial=121 path=/; interface=org.freedesktop.DBus.Properties; member=Get
   string "org.freedesktop.NetworkManager.Connection.Active"
   string "Devices"
error sender=:1.6 -> dest=:1.132 error_name=org.freedesktop.DBus.Error.UnknownMethod reply_serial=121
   string "Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
"
error sender=:1.6 -> dest=:1.133 error_name=org.freedesktop.DBus.Error.UnknownMethod reply_serial=121
   string "Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

NetworkManager does not have an object at path "/", at least according to d-feet on my desktop machine. A default value leaking from somewhere?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Cris Dywan (kalikiana)]

Possibly related to bug 1388473? The symptoms seem similar at least.

[Antti Kaijanmäki (kaijanmaki)]

@kalikiana: yes. it's the same bug. marking as duplicate. Rest assured, it's only UI.

[Jussi Pakkanen (jpakkane)]

The reason this is happening is that NetworkManager is not sending the proper signal. In the log we should find a signal sent with value 20. This is not there. If you do 'nmcli nm' when your phone is in this state, it will get fixed (nm reinitializes its state and sends the signal it should have sent earlier). This makes this bug a duplicate of #1386109.

However please do NOT mark this bug as a duplicate of that bug. The reason being that if you do, it will vanish from bug searches and people will keep refiling this one again and again.

[Antti Kaijanmäki (kaijanmaki)]

yes, so indeed this is a duplicate of bug #1386109, but let's keep this open for making it easier for people to find it and having less duplicates filed.

[Olli Ries (ories)]

removed rtm tag in reference to comment #12, issue being tracked in #1386109

[Tony Espy (awe)]

I just made both NM tasks Incomplete as:

 * there's no device information, nor reference to branch or image number. In fact, it's hard to tell that this is a "touch" bug.

 * there are no "steps to reproduce"

 * comment #11 says NM is failing to send a proper signal, yet the signal name is not mentioned...

 * multiple comments say that this bug is a duplicate of bug #1386109, which is now FixReleased. Can this bug also now be closed?

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu Vivid) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu Utopic) because there has been no activity for 60 days.]