nautilus 3.6 crashes when a second instance is launched

Bug #1069485 reported by gerstrong
38
This bug affects 9 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

When I updated the system last time and some newly created user uses this at returns:

(nautilus:5534): Gdk-CRITICAL **: gdk_x11_display_get_xdisplay: assertion `GDK_IS_DISPLAY (display)' failed
Speicherzugriffsfehler (Speicherabzug geschrieben)

This is critical because it doesn't allow to browse files.

Revision history for this message
gerstrong (gerstrong) wrote :

I found out that it only crashes when a second instance is launched.

Here is the output using gdb:

gerstrong@gerstrong-desktop:~$ gdb /usr/bin/nautilus
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/nautilus...Reading symbols from /usr/lib/debug/usr/bin/nautilus...done.
done.
(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec8f4700 (LWP 10587)]

(nautilus:10584): Gdk-CRITICAL **: gdk_x11_display_get_xdisplay: assertion `GDK_IS_DISPLAY (display)' failed

Program received signal SIGSEGV, Segmentation fault.
nautilus_application_add_platform_data (application=<optimized out>,
    builder=0x7ce810) at nautilus-application.c:711
711 nautilus-application.c: Datei oder Verzeichnis nicht gefunden.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Takehaniyasubiko (takehaniyasubiko) wrote :

I have the same problem. This and a lot of other issues really make me regret switching to 3.6...

Revision history for this message
gerstrong (gerstrong) wrote :

I like that version, it got more useful but it's a bit buggy understandably. Nevertheless Quantal got in release status in this bug is really critical for that matter of fact.

summary: - nautilus 3.6 crashes since last update
+ nautilus 3.6 crashes when a second instance is launched
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report but Ubuntu doesn't use nautilus 3.6 (for a reason), you should report the issue to whoever provided you the version you are using (e.g the ppa owner if you use a ppa version)

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: Confirmed → Invalid
Revision history for this message
gerstrong (gerstrong) wrote :

Okay, will do that in future. It is fixed anyway...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.