nautilus crashed with signal 5 in _XError()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
Description: Ubuntu lucid (development branch)
Release: 10.04
nvidia-settings:
Installed: 190.53-0ubuntu1
Candidate: 190.53-0ubuntu1
Version table:
*** 190.53-0ubuntu1 0
500 http://
100 /var/lib/
Just defined a second TV-Out for s-video to an external TV monitor.
The crash ensues with a crash icon in the system tray, but the second monitors does indeed appear (on the TV) as a result of logout and restart of XServer.
In addition to the crash, the Mouse pointer flashes between pointer and hour-glass and the 2nd display TV monitor's bottom panel shows a flashing "Starting the File Manager" which does not respond to any click event.
That's it. Pleased to see the great progress on 10.04 and that Nvidia-settings does indeed detect the second display (it didn't work in 9.10)
Best Regards,
Dietrich T. Schmitz
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 21 12:51:26 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelMo
Package: nautilus 1:2.29.90-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
Signal: 5
SourcePackage: nautilus
StacktraceTop:
?? () from /usr/lib/
_XError () from /usr/lib/
?? () from /usr/lib/
_XReply () from /usr/lib/
XInternAtom () from /usr/lib/
Title: nautilus crashed with signal 5 in _XError()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #508890, so 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. Please continue to report any other bugs you may find.