nautilus crashed with SIGSEGV in g_slice_alloc() when ejecting drive

Bug #788382 reported by steubens
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: nautilus

i've gotten various crashes ejecting and deleting files, i don't expect this one to be any more enlightening, but maybe ... who knows

it does not happen regularly, it happens semi regularly and so far i haven't been able to prompt a crash; it just happens during regular use

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.39-3.9-generic 2.6.39
Uname: Linux 2.6.39-3-generic x86_64
Architecture: amd64
Date: Wed May 25 16:01:16 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8c064732b6 <g_slice_alloc+294>: mov (%rbx),%rdx
 PC (0x7f8c064732b6) ok
 source "(%rbx)" (0x2020202020202020) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_checksum_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gnome_desktop_thumbnail_factory_save_thumbnail () from /usr/lib/libgnome-desktop-2.so.17
 ?? ()
Title: nautilus crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to natty on 2011-03-17 (69 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
steubens (steubens) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
steubens (steubens) wrote :

it may take quite some time to catch it, but i'll try, stymied a bit at the sheer number of related crashes

Revision history for this message
steubens (steubens) wrote :

i couldn't figure out how to get nautilus to keep from spawning, i copied the autostart .desktop to .local/share/applications and changed it to not autostart but apparently that didn't override the main one; i also tried nautilus -q, and searching for whatever gconf keys are restarting it, to no avail; pedro, if you know or know where i can ask someone (i already asked on #nautilus on gimpnet, not many people around) i'd appreciate it

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.

Other bug subscribers

Remote bug watches

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