nautilus crashed with signal 5 in _XReply()

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

Bug Description

Nautilus crashed right after boot, no desktop icons were shown. When I started Nautilus manually afterwards, everything went back to normal, i.e. the desktop items reappeared and I had no problems since.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu16
Uname: Linux 3.11.1-zen+ x86_64
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 1 10:38:26 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'823x550+41+110'"
InstallationDate: Installed on 2012-06-05 (482 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 SHELL=/usr/bin/fish
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:en
 XDG_RUNTIME_DIR=<set>
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 gdk_flush () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to raring on 2013-05-04 (149 days ago)
UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark

Revision history for this message
Jens Kehne (jkehne) wrote :
information type: Private → Public
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 this software better. This particular crash has already been reported and is a duplicate of bug #1071155, 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.

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.