nautilus crashed with SIGSEGV in strcpy(), error 6 in libglib-2.0.so.0.3102.0

Bug #903845 reported by Colin Law
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This is happening reliably for me about 50% of the time when I start nautilus in Precise 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

Revision history for this message
Colin Law (colin-law) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 strcpy (__src=0x1d9 <Address 0x1d9 out of bounds>, __dest=0x5f <Address 0x5f out of bounds>) at /usr/include/i386-linux-gnu/bits/string3.h:105
 zone_for_constant_offset (name=0x1d9 <Address 0x1d9 out of bounds>) at /build/buildd/glib2.0-2.31.4.is.2.31.2/./glib/gtimezone.c:297
 g_time_zone_new (identifier=0x9455c88 "") at /build/buildd/glib2.0-2.31.4.is.2.31.2/./glib/gtimezone.c:364
 ?? () from /tmp/tmp79VKjU/lib/i386-linux-gnu/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
summary: - nautilus crashed with SIGSEGV in g_timer_stop(), error 6 in
+ nautilus crashed with SIGSEGV in strcpy(), error 6 in
libglib-2.0.so.0.3102.0
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, is that still an issue? It seems a bit similar to a gtk issue which got fixed recently in the precise gtk updates

Changed in nautilus (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Colin Law (colin-law) wrote :

I don't know, sadly I trashed my virtual machine and am not able to re-generate it at the moment. Looking at my description I note that I said it was an issue with Oneric whereas I meant Precise of course (as is noted in the system report. I will change the description. Perhaps the other person who has added themselves can comment?

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.