nautilus crashed with signal 5 in _XReply()

Bug #1296009 reported by Dmitry Shachnev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Nautilus crashed while I was doing nothing with it.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Sat Mar 22 14:05:11 2014
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2010-03-20 (1463 days ago)
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: nautilus -n
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
 XSync () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to trusty on 2013-09-29 (173 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video

Revision history for this message
Dmitry Shachnev (mitya57) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb693a40a in ?? ()
 No symbol table info available.
 #1 0xb714d276 in ?? () from /tmp/apport_sandbox_HF2Py_/usr/lib/i386-linux-gnu/libgdk-3.so.0
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceSource:
 #0 0xb693a40a in ?? ()
 #1 0xb714d276 in ?? () from /tmp/apport_sandbox_HF2Py_/usr/lib/i386-linux-gnu/libgdk-3.so.0
StacktraceTop:
 ?? ()
 ?? () from /tmp/apport_sandbox_HF2Py_/usr/lib/i386-linux-gnu/libgdk-3.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.

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