nautilus crashed with SIGSEGV in g_timeout_dispatch()

Bug #1034735 reported by Evan Huus
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was modifying the quick-search filter on a folder with many files. It seems semi-reproducible if you just keep changing the search filter.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
Date: Thu Aug 9 00:09:41 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'828x628+49+24'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'160'
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x492390: movzbl 0x30(%rsi),%eax
 PC (0x00492390) ok
 source "0x30(%rsi)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_timeout_dispatch (source=source@entry=0x2b0a160, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.33.6/./glib/gmain.c:4002
Title: nautilus crashed with SIGSEGV in g_timeout_dispatch()
UpgradeStatus: Upgraded to quantal on 2012-06-10 (60 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark

Revision history for this message
Evan Huus (eapache) 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 #1034548, 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.

visibility: 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.