nautilus crashed with signal 5 in _XEventsQueued()

Bug #1228365 reported by Anton Islitzer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Sep 20 23:34:48 2013
ExecutablePath: /usr/bin/nautilus
MarkForUpload: True
ProcCmdline: /usr/bin/nautilus --no-default-window
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
 XPending () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 1:
Title: nautilus crashed with signal 5 in _XEventsQueued()
UpgradeStatus: Upgraded to saucy on 2013-03-21 (183 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors:
 (process:3660): dconf-CRITICAL **: unable to create directory '/run/user/1000/dconf': Keine Berechtigung. dconf will not work properly.
 (process:3660): dconf-CRITICAL **: unable to create directory '/run/user/1000/dconf': Keine Berechtigung. dconf will not work properly.
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-03-23T14:32:29.972460

Revision history for this message
Anton Islitzer (a-islitzer2365) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XPending (dpy=dpy@entry=0x9046120) at ../../src/Pending.c:55
 _gdk_x11_display_queue_events (display=0x9053808) at /build/buildd/gtk+3.0-3.8.4/./gdk/x11/gdkeventsource.c:324
 gdk_display_get_event (display=display@entry=0x9053808) at /build/buildd/gtk+3.0-3.8.4/./gdk/gdkdisplay.c:313
 gdk_event_source_dispatch (source=source@entry=0x9064380, callback=0x0, user_data=0x0) at /build/buildd/gtk+3.0-3.8.4/./gdk/x11/gdkeventsource.c:360
 g_main_dispatch (context=0x903eb28) at /build/buildd/glib2.0-2.37.93/./glib/gmain.c:3065

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Ads20000 (ads20000) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1228365

and any other logs that are relevant for this particular issue.

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
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.