Ubuntu
nautilus package

Nautilus crashes continuoulsy in dual screen setup (nautilus crashed with signal 5 in gdk_x_error())

Bug #518092 reported by Flávio Etrusco on 2010-02-06

This bug report is a duplicate of: Bug #508890: Nautilus crashes when there are multiple XScreens. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: nautilus

I'm trying to use a dual screen setup (two screen sections, two device sections for the same card in xorg). Both desktops show fine, but a nautilus process is continuously started and crashed (occupying 100% of a cpu core).

Obs. Two screen setup in general is not very stable (had to disable radeon kernel module, remove mergefb in xorg.conf, etc), but I don't think it's related, as otherwise everything seems to run fine except that trying to terminate gnome-session freeze the screen (I'm unable to switch terminals, but alt+sysrq works). The setup was previously dual monitor with single screen.

ProblemType: Crash
Architecture: i386
Date: Sat Feb 6 12:37:22 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.29.2-0ubuntu4
ProcCmdline: nautilus
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
Signal: 5
SourcePackage: nautilus
StacktraceTop:
gdk_x_error (display=0x8ad99a8, error=0xbf7ff67c)
_XError () from /usr/lib/libX11.so.6
?? () from /usr/lib/libX11.so.6
_XReply () from /usr/lib/libX11.so.6
XInternAtom () from /usr/lib/libX11.so.6
Title: nautilus crashed with signal 5 in gdk_x_error()
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
XsessionErrors:
(gnome-settings-daemon:1179): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:1179): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(polkit-gnome-authentication-agent-1:1205): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Tags:

Revision history for this message

Flávio Etrusco (etrusco) wrote on 2010-02-06:

Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (803 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (47.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (781 bytes, text/plain; charset="utf-8")
Registers.txt Edit (462 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (30.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (32.5 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (411 bytes, text/plain; charset="utf-8")

Revision history for this message

Flávio Etrusco (etrusco) wrote on 2010-02-06:

Maybe it's not a nautilus bug after all. See my other report:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/518103

Revision history for this message

Sense Egbert Hofstede (sense) wrote on 2010-02-06:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #508890, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.