nautilus crashed with signal 5 in _XError()

Bug #603098 reported by aviramof
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

Happen when i try to change things in xorg monitors or fglrx catalyst about displays and resolutions.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.30.1-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
CrashCounter: 1
Date: Thu Jul 8 14:10:35 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100613)
ProcCmdline: nautilus
ProcEnviron:
 LANG=he_IL.utf8
 SHELL=/bin/bash
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()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1416): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-display-properties:2149): Gtk-WARNING **: Ignoring the separator setting
 (gnome-display-properties:2149): Gtk-WARNING **: No object called:

Revision history for this message
aviramof (aviramof) 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-i386-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.