Description of problem: Network applet forgets previously added 3G connections on Gnome-Shell, after unplugging the 3G dongle. Version-Release number of selected component (if applicable): Fedora-16-Beta-i686-Live-Desktop.iso's version How reproducible: Always. Steps to Reproduce: 1. plug 3G dongle 2. add a new connection ( using nm-connection-editor ) 3. connect to it 4. disconnect 5. unplug 3G dongle 6. plug it again Actual results: The previously created connection doesn't appear on the network applet's list Expected results: The previously created connection should appear on the network applet's list Additional info: 1. If you disable the network applet ( mv /usr/share/gnome-shell/js/ui/status/network.js /usr/share/gnome-shell/js/ui/status/network.disabled, ALT+F2, 'r' ), everything works. 2. using nm-connection-editor to change something on the conenction (e.g., checking/unchecking "system connection" checkbox) and it will appear again on the list Possible related bugs: https://bugzilla.redhat.com/show_bug.cgi?id=738099 [ Mobile Broadband connection disappears from NM applet connection list after waking ]
Created attachment 549379 [details] dmesg of plugging the device I forgot to add that doing *just* ALT+F2, 'r' and reloading gnome-shell also works: the previously configured connections will then appear. So the problem just happens if I plug the pen *after* gnome-shell is fully loaded. The pen goes through 3 phases: 1- fake CD-ROM 2- network device, usb0 created, not yet probed by modem-manager 3- probed by modem-manager and ready to work Maybe there should be a signal at the end of phase 3 which isn't being properly handled by network.js ? I'll attach this pen's plugging dmesg.
Created attachment 558844 [details] screenshot: usb 3G dongle plugged in after gnome-shell loaded -- phase 1
Created attachment 558846 [details] screenshot: usb 3G dongle plugged in after gnome-shell loaded -- phase 2
Created attachment 558847 [details] screenshot: gnome-shell *reloaded* after usb 3G dongle plugged in
- Is this still happening with 3.4.0? - Does anything appear in ~/.xsession-errors when you plug the device in? (In particular, Javascript backtraces would be interesting)
Yes, with Gnome 3.4 happens. Verified with Fedora-17-Nightly-20120409.08-i686-Live-desktop.iso . Nothing appears in ~/.xsession-errors of relevance. Do you want any of the following files? Nothing of relevance seems to be there: -== Logs collected ==- gs-3g-dongle-dbus-session-1preshell-restart.txt gs-3g-dongle-dbus-session-2during_and_after-gnome-shell-restart.txt <-- gs-3g-dongle-dbus-session-3using-nm-connection-editor-to-force-refresh.txt* <-- gs-3g-dongle-dbus-system-1preshell-restart.txt gs-3g-dongle-dbus-system-2during_and_after-gnome-shell-restart.txt <-- gs-3g-dongle-dbus-system-3using-nm-connection-editor-to-force-refresh.txt* <-- gs-3g-dongle-modem-manager-debug-output-including-gnome-shell-restart.txt <-- gs-3g-dongle-xsession-errors-1preshell-restart.txt gs-3g-dongle-xsession-errors-2during_and_after-gnome-shell-restart.txt <-- -== Caption ==- <-- => connection appears on gnome-shell network manager * => preceded by unplugging and replugging the pen before starting logging. -== Hypothesis ==- IMHO, the network.js code loads all connection info when usb0 is created. Since the connection is of type "modem" and usb0 is, at that time, of time "Ethernet", it discards all the connections; later, usb0 is reclassified as "modem" but the connection list is not reloaded thus, presenting an empty list. However, if by the time network.js is loaded the usb0 device is already of type "modem", it doesn't discard the connections. I'll try again to write a patch but do note my previous attempt failed. If I succeed, I'll post it here today.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.