nautilus crashed with SIGSEGV in g_list_foreach()

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

Bug Description

Not sure what caused this to happen.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Fri Feb 1 09:39:53 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1008x718+0+335'"
InstallationDate: Installed on 2010-10-11 (843 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f7ab11daaa0 <g_list_foreach+16>: mov 0x8(%rdi),%rbx
 PC (0x7f7ab11daaa0) ok
 source "0x8(%rdi)" (0x4144490f02000090) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_list_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in g_list_foreach()
UpgradeStatus: Upgraded to quantal on 2012-10-27 (96 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin netdev plugdev sambashare whoopsie

Revision history for this message
Colan Schwartz (colan) 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 #1053862, 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-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.