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 686621 - Nautilus 3.6.1 from GNOME 3 ppa crashes
Nautilus 3.6.1 from GNOME 3 ppa crashes
Status: RESOLVED DUPLICATE of bug 686585
Product: nautilus
Classification: Core
Component: Crashers
3.6.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-10-22 10:41 UTC by ajovanov93
Modified: 2012-10-22 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ajovanov93 2012-10-22 10:41:47 UTC 
Here is the output when ran from terminal :

(nautilus:3769): Gdk-CRITICAL **: gdk_x11_display_get_xdisplay: assertion `GDK_IS_DISPLAY (display)' failed
Segmentation fault (core dumped)

Nautilus 3.6.0 works well.
Comment 1 ajovanov93 2012-10-22 10:46:38 UTC 
This happens when run from terminal and from its launcher.
It does not happen when a folder is opened from desktop.
Comment 2 ajovanov93 2012-10-22 10:51:22 UTC 
I unchecked `have file manager handle the desktop` it Tweak Tool and nautilus started fine from both terminal and its launcher. 

So it looks like the problem is that nautilus crashes when trying to open a new window from nautilus launcher or terminal and nautilus handles the desktop.
Comment 3 Cosimo Cecchi 2012-10-22 14:02:40 UTC 
I can't reproduce here...could you please provide a stacktrace for the crash?

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!
Comment 4 Cosimo Cecchi 2012-10-22 14:17:07 UTC 
Apparently this was caused by a downstream patch - closing as a duplicate of 686585.

*** This bug has been marked as a duplicate of bug 686585 ***