nautilus crashed with signal 5 in _XError()

Bug #525404 reported by dietrich
10
This bug affects 1 person
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://us.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

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)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.90-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _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 _XError()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2451): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
dietrich (dtschmitz) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-amd64-retrace
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.