GNOME Bugzilla – Bug 668388
Gnome 3.0 and 3.2 crashing when disabling wireless
Last modified: 2012-12-20 06:53:00 UTC
So here is my problem, haven't found anything similar yet. I have a DELL Inspiron 1526 with integrated ATI X1200, my wireless card is a Broadcom BCM4312 and I also have to use a USB WiFi adapter Realtek RTL8187. I'm using Fedora 16 and when I first installed it, I had my USB WiFi (RTL8187) plugged and everything works "fine" almost all the time, the problems come whenever I unplug the USB WiFi adapter from the laptop, gnome-shell freezes and there is no way to get it back but to reboot from a tty, remove gnome-shell, plug the USB WiFi adapter again and reinstall gnome-shell ... I have tested Fedora 16 (gnome-shell 3.2) and Ubuntu 11.10 (gnome-shell 3.0) both x64 and both have the same issue. Don't know what else I can add ... fell free to ask anything else.
Is there anything interesting in ~/.xsession-errors or dmesg?
(In reply to comment #1) > Is there anything interesting in ~/.xsession-errors or dmesg? Hi, I'm not sure ... I can't see anything that could be related ... I just made some tests. I disabled the NetworkManager service and as expected, gnome-shell suddenly froze ... I guess it has something to be with a really bad bug in NetworkManager and wifi ... haven't tested this with a wired connection ...
Created attachment 205755 [details] xsession-error file
From your log: > JS LOG: NMApplet is not supported. It is possible that your NetworkManager version is too old > (nm-connection-editor:1838): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:58:14: Themeing engine 'unico' not found Which versions of NetworkManager-gnome and NetworkManager do you have installed?
(In reply to comment #4) > From your log: > > > JS LOG: NMApplet is not supported. It is possible that your NetworkManager version is too old > > (nm-connection-editor:1838): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:58:14: Themeing engine 'unico' not found > > > Which versions of NetworkManager-gnome and NetworkManager do you have > installed? I have version 0.9.2-1.fc16 I keep my system updated with the official fedora repository
Created attachment 206919 [details] [review] Panel: don't allow failures loading the network menu NetworkManager 0.9.0 was released during the GNOME 3.0 cycle, and at this time all distributions that ship 3.4 include it. Therefore it is no longer useful to let the network indicator fail to load, and instead it becomes harmful, as it hides potential JS errors. ------ @original poster: It appears that you have an error loading the network indicator, which makes you fallback to nm-applet. Please try this patch - you should instantly see more output in .xsession-errors, which could help diagnose the problem.
Review of attachment 206919 [details] [review]: NetworkManager (surprisingly) isn't actually officially part of GNOME, or an approved external dependency. If we needed to make our dependency hard to fix some problem that there wasn't an easy way to fix some other way, then that would be fine with me. But as a debugging aid, doesn't seem like worth the exception from normal GNOME procedures. Would be nice to get it proposed as a piece of GNOME for 3.5, but don't know if that will happen.
jhbuild info says otherwise: Name: NetworkManager Module Set: gnome-suites-core-3.4 Required by: meta-gnome-extended-devel-platform, network-manager-applet, meta-gnome-core-os-services Maybe we should go back to full module lists in live.gnome.org...
I certainly agree that NetworkManager is defacto part of GNOME, but not officially. See https://mail.gnome.org/archives/desktop-devel-list/2011-June/msg00083.html for most recent discussion
Ok, this was marked as a blocker, so an update is due. Unfortunately, the patch was only meant as a debug aid and without further information no fix is possible, as the provided .xsession-errors only shows that gnome-shell's network indicator was bypassed entirely and the nm-applet used.
Comment on attachment 206919 [details] [review] Panel: don't allow failures loading the network menu >-try { >- STANDARD_STATUS_AREA_SHELL_IMPLEMENTATION['network'] = imports.ui.status.network.NMApplet; >-} catch(e) { >- log('NMApplet is not supported. It is possible that your NetworkManager version is too old'); you could do logError(e, 'NMApplet is not supported...') instead...
Uranio23: Any chance to provide the patch in comment 6?
Uranio: Is this still an issue in 3.4?
Let's assume this to not be the case. If it is, please reopen. Thanks.