GNOME Bugzilla – Bug 695030
Crashes with running Nautilus
Last modified: 2013-09-02 22:29:47 UTC
GNOME Shell course many times when I open the Nautilus. It should be noted that the possibility 'Have file manager handle the desktop' is enabled.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. See also https://live.gnome.org/GnomeShell/Debugging for information specific on running the shell under gdb. Thanks in advance!
This seems to mostly happen, when launching nautilus while there are no other windows open. Logs show (gnome-shell:5814): St-ERROR **: st_widget_get_theme_node called on the widget [0x647b0b0 StWidget.window-picker:first-child] which is not in the stage. Attaching two stacktraces, first is at the SIGTRAP triggered from the above error. Second is ignoring the SIGTRAP (but now gnome-shell just hangs rather than crashes)
Created attachment 240671 [details] trace at SIGTRAP
Created attachment 240672 [details] trace at hang after SIGTRAP shell doesnt want to crash while gdb is attached ;(
Saw this same crash (gnome-shell crashed with signal5 in st_widget_get_theme_node()) when using Ubuntu 13.04 & gnome3 ppa which is using nautilus-3.7.2 Went away entirely & isn't an issue at all once I built & installed nautilus 3.8 release (tried both 3.8 release & current git master as of tonight, both are fine Also debianized the 3.8.0 release using the ppa's patches, ect., again this issue is gone.
Well I can reproduce this using jhbuild gnome-shell + nautilus (still using 3.8 moduleset). 1. close all windows 2. Launch nautilus from the overview 3. this will crash gnome-shell on atleast 2 out of 3 attempts.
crash happens here https://git.gnome.org/browse/gnome-shell/tree/js/ui/workspace.js#n1530 It seems to be caused by incorrect firing of 'window-added' and window-entered-monitor' signals, causing a new clone to be created when it shouldnt be. normally in the non-crash case, neither of these signals are fired when launching the first window/app.
I also have this issue running ArchLinux x64 updated to the latest gnome 3.8.1 packages. I will do anything that I can to help this issue along. Also, I agree with darkxst above in his assessment of the bug activating when there are no windows open.
*** Bug 699097 has been marked as a duplicate of this bug. ***
Yeah this issue definitely is not gone... I saw this in both full up to date arch linux 64-bit and opensuse 12.3 with gnome 3.8 from gnome:stable. This is a very severe bug because sometimes it totally crashes gnome and forces you to log out losing any work.
I agree with bwat47. This is an extremely serious issue that is causing many people to quit using nautilus or even gnome purely out of necessity.
I confirm this bug. It is important to open no other application *before* opening Nautilus! Steps to reproduce (works always): 1. Login to GNOME 2. Alt+F1 3. enter "nautilus" 4. hit enter 5. nautilus appears and shell crashes after ~ 2 seconds, restart of shell follows I will attach output of journalctl.
Created attachment 245289 [details] journalctl output journalctl -b --no-pager --full
So, I tried what you suggested here, with my jhbuild (master) installation, and with regular Fedora packages (3.8.2), but I had no success reproducing the bugs. In all cases, nautilus runs just fine, and the shell does not crash. I tried with and without desktop icons enabled. Sorry guys.
I have two identical gnome-shell installations, one running with the nouveau driver (gallium 0.4 on nv86) and one with the ati dri driver (gallium 0.4 on amd rv740). The former never crashes (notwithstanding some graphical corruptions from time to time, not related to nautilus), the latter always crashes when lunching nautilus on a empty desktop as described above. So, maybe it is somehow related to the graphic driver.
For me, I must launch nautilus from the activities menu for it to crash, and there must not be any other gtk windows open. Also, this crash happens for me on my laptop running the latest ati drivers on archx64, and on my laptop running the latest fglrx driver on archx64, and I was able to confirm it on a friends laptop running UbuntuGnomex64 and archx64 on the latest Nvidia drivers. I have read that this bug only pertains to 64bit installations.
And I see it with intel hd4000. crash happens for me when opening it from activities with no other windows open. Doesn't always happen on first try.
I think that the crash only occurs when two conditions are met : 1) no other windows are present in the current desktop 2) launching nautilus triggers the transition form the activities view to the normal view. If I launch nautilus with CTRL click from the dash, such that the shell does not exit the acitivities view, I don't get any crash.
Additional note : when you lunch with CTRL click nautilus from the activities view on the last empty desktop, most of the times a new desktop is created below (which is normal), but most times the newly created desktop is destroyed and you are left with no extra desktop below the last one.
Try the following steps : With no windows open lunch on the first (and only) desktop some application different from nautilus. Go to the activities view, have nautilus on the preferred applications on the dash Switch to the second (and last) empty desktop and run nautilus by CTRL click on the dash from the activities view. Nautilus appears and a new desktop is created below. If nothing else happens (normal situation) kill nautilus by clicking on the cross without leaving the activity. Try running again nautilus with CTRL click from the activities and repeat until the newly created desktop gets destroyed (anomalous situation). Kill a last time nautilus still without leaving the activities. Now the active desktop switches back to the previous (first) desktop. Click from the activities on the empty desktop where you had killed nautilus. The shell crashes.
Took like 15 seconds for me to reproduce this on a fedora 19 liveusb, I find it hard to believe that a developer can't. I just opened nautilus from activities a few times with no other windows open (it was pinned to the favorites and thats where I clicked it). and bam, crash.
I can easily reproduce this as well....(In reply to comment #2) > This seems to mostly happen, when launching nautilus while there are no other > windows open. > > Logs show > (gnome-shell:5814): St-ERROR **: st_widget_get_theme_node called on the widget > [0x647b0b0 StWidget.window-picker:first-child] which is not in the stage. > I can reproduce this as well; same error in my journal.
Hi! Archlinux added a patch to it's gnome-shell package from upstream GNOME. Which is workaround for this issue: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gnome-shell&id=376f1cd750c2852a4b714c75e587ccb82e94b799 Source: https://bugzilla.gnome.org/show_bug.cgi?id=610279#c24 Please note, that this is not a fix for Nautilus. Whatever Nautilus does (or not) is probably still wrong and shouldn't happen.
(In reply to comment #24) > Hi! Archlinux added a patch to it's gnome-shell package from upstream GNOME. > Which is workaround for this issue: > https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gnome-shell&id=376f1cd750c2852a4b714c75e587ccb82e94b799 > > Source: > https://bugzilla.gnome.org/show_bug.cgi?id=610279#c24 > > Please note, that this is not a fix for Nautilus. Whatever Nautilus does (or > not) is probably still wrong and shouldn't happen. Even with the patch, you can still crash the shell following the steps in my comment #21.
For me, on ArchLinux with GNOME 3.9.x (from git), no crashes. Nothing, not even a single collapse. The system is very stable, although she Development version (unstable).
I can no longer reproduced this at all on arch linux with their patched gnome 3.8.3 package. I tried archiesix's steps several times, and I could easily reproduce the situation where the virtual desktop gets incorrectly destroyed, but the last step of opening nautilus on the first desktop after that happens is no longer crashing the shell for me. Also, before the patched package not only did I regular run into this during regular usage, but I could easily reproduce it this way: reboot and login to a fresh gnome session. Position your mouse close to where nautilus is pinned on your overlay dock. Very quickly open overlay with super key and click nautilus as quick as you can. Doing this 1-2 times in a row would almost always trigger the crash for me, but now I cannot reproduce that either, the nautilus related crashes seem fixed here(shell randomly crashes occasionally still when I'm installing/removing software with pacman, but thats a different issue :p).
comment 24 indicates that the patch for bug 610279 fixes this. *** This bug has been marked as a duplicate of bug 610279 ***
I wouldn't use this wording. See: https://bugzilla.gnome.org/show_bug.cgi?id=610279#c21
It "fixes" it by not making it crash. Any instance of the "st_widget_get_theme_node" error is still a bug that we should fix.
The bug is fixed. GNOME Shell already not crashed with running Nautilus.