GNOME Bugzilla – Bug 686585
Nautilus crashes with SIGSEV in nautilus_application_add_platform_data function
Last modified: 2012-10-22 19:23:56 UTC
Nautilus version: 3.6.1 System architecture: amd64 I'm running Ubuntu 12.10 and have been successfully using gnome-shell 3.6 from the official gnome ppa. Today (10/12/12) I received an update that makes nautilus crash every time it is opened. When run from the terminal this is the output I get: (nautilus:6958): Gdk-CRITICAL **: gdk_x11_display_get_xdisplay: assertion `GDK_IS_DISPLAY (display)' failed Segmentation fault (core dumped)
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. Thanks in advance!
Created attachment 226941 [details] I believe this is the stack trace. Not sure Is this what you're looking for? This is my first attempt to get a stack trace :)
Additional info: I've noticed that nautilus is still drawing the icons on the desktop, and I can still access nautilus via double click on one of them. When I try to launch nautilus from the dock, run dialog, or terminal, I get the crash.
Reverting http://git.gnome.org/browse/nautilus/commit/?id=629c9bc27a fixes this problem (which is, I believe, the same as bug 686600 and bug 686589).
Ah, I think you can close this problem as NOTGNOME — the nautilus_application_add_platform_data function in which this crash happens is Ubuntu-specific function, added by our 21_correct_timestamp_use_fix_focus_issue.patch.
*** Bug 686600 has been marked as a duplicate of this bug. ***
*** Bug 686589 has been marked as a duplicate of this bug. ***
*** Bug 686621 has been marked as a duplicate of this bug. ***
This should now be fixed in Nautilus 1:3.6.1-0ubuntu1~ubuntu12.10.2 in the GNOME3 PPA.
(In reply to comment #9) > This should now be fixed in Nautilus 1:3.6.1-0ubuntu1~ubuntu12.10.2 in the > GNOME3 PPA. I can confirm that after today's (10/22/12) update, the problem no longer exists.