After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 668388 - Gnome 3.0 and 3.2 crashing when disabling wireless
Gnome 3.0 and 3.2 crashing when disabling wireless
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.2.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-01-21 07:53 UTC by Uranio23
Modified: 2012-12-20 06:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
xsession-error file (73.65 KB, text/plain)
2012-01-21 09:37 UTC, Uranio23
  Details
Panel: don't allow failures loading the network menu (1.67 KB, patch)
2012-02-06 17:33 UTC, Giovanni Campagna
rejected Details | Review

Description Uranio23 2012-01-21 07:53:04 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.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-01-21 07:57:59 UTC
Is there anything interesting in ~/.xsession-errors or dmesg?
Comment 2 Uranio23 2012-01-21 09:35:48 UTC
(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 ...
Comment 3 Uranio23 2012-01-21 09:37:01 UTC
Created attachment 205755 [details]
xsession-error file
Comment 4 André Klapper 2012-01-21 12:05:56 UTC
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?
Comment 5 Uranio23 2012-01-21 17:49:26 UTC
(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
Comment 6 Giovanni Campagna 2012-02-06 17:33:26 UTC
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.
Comment 7 Owen Taylor 2012-02-15 21:05:52 UTC
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.
Comment 8 Giovanni Campagna 2012-02-15 21:11:27 UTC
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...
Comment 9 Owen Taylor 2012-02-15 21:23:08 UTC
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
Comment 10 Giovanni Campagna 2012-03-09 14:59:02 UTC
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 11 Dan Winship 2012-03-19 13:01:13 UTC
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...
Comment 12 André Klapper 2012-06-10 01:37:49 UTC
Uranio23: Any chance to provide the patch in comment 6?
Comment 13 André Klapper 2012-08-20 13:26:09 UTC
Uranio: Is this still an issue in 3.4?
Comment 14 Tobias Mueller 2012-12-20 06:53:00 UTC
Let's assume this to not be the case. If it is, please reopen. Thanks.