nautilus crashed with SIGSEGV in g_timeout_dispatch()

Bug #832705 reported by Martin Pool
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 24 10:01:48 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x4c0cbe: mov 0x390(%rax),%rdi
 PC (0x004c0cbe) ok
 source "0x390(%rax)" (0xaaaaaaaaaaaaae3a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_timeout_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:3904
 g_main_dispatch (context=0x10b17f0) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:2439
 g_main_context_dispatch (context=0x10b17f0) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:3008
 g_main_context_iterate (context=0x10b17f0, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:3086
Title: nautilus crashed with SIGSEGV in g_timeout_dispatch()
UpgradeStatus: Upgraded to oneiric on 2011-08-23 (0 days ago)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare

Revision history for this message
Martin Pool (mbp) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #804724, 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.