nautilus crashed with SIGSEGV in gtk_widget_destroy()

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

Bug Description

No idea why this happened whilst no-one was using the PC.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic i686
ApportVersion: 2.6.1-0ubuntu9
Architecture: i386
CrashCounter: 1
Date: Fri Dec 28 21:51:30 2012
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2010-10-08 (813 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
MarkForUpload: True
ProcCmdline: nautilus /media/other
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb74c5ce3 <gtk_widget_destroy+35>: mov (%esi),%edx
 PC (0xb74c5ce3) ok
 source "(%esi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_widget_destroy () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in gtk_widget_destroy()
UpgradeStatus: Upgraded to quantal on 2012-05-26 (217 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin mythtv plugdev sambashare wireshark

Revision history for this message
Jonathan Sambrook (jonathan-hmmn) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1095873, 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.

information type: 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.