Comment 0 for bug 903845

Revision history for this message
Colin Law (colin-law) wrote : nautilus crashed with SIGSEGV in g_timer_stop(), error 6 in libglib-2.0.so.0.3102.0

This is happening reliably for me about 50% of the time when I start nautilus in Oneiric running in VirtualBox on 11.10 host.
The launcher icon pulsates as normal for a few seconds then nautilus crashes. In dmesg I see
nautilus[31311]: segfault at aaaaaaba ip 00be929e sp bfb75fa0 error 6 in libglib-2.0.so.0.3102.0[b7f000+f3000]

This may be a duplicate of bug#804891 but as I am able to make it fail fairly reliably it may be different so I am reporting it as such so that the stack trace and so on will be captured.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Dec 13 17:32:16 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5e829e <g_timer_stop+30>: andb $0xfe,0x10(%esi)
 PC (0x005e829e) ok
 source "$0xfe" ok
 destination "0x10(%esi)" (0xaaaaaaba) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_timer_stop () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_timer_stop()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo