nautilus crashed with SIGSEGV in g_list_remove()

Bug #362342 reported by Rick Spencer
422
This bug affects 85 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Unfortunately I did not witness this crash, so I am unable to repro it.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.26.2-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_list_remove () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_datalist_id_set_data_full ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_list_remove()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__g_list_remove (list=0x2585c80, data=0x25d60a0)
module_object_weak_notify (
weak_refs_notify (data=<value optimized out>)
IA__g_datalist_id_set_data_full (
IA__g_object_unref (_object=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, so it just crashed while not using nautilus and happened once? The stacktrace might still be useful but it seems a referencing bug which means it probably needs informations and debugging from somebody having the issue easily to work on it in an efficient way

visibility: private → public
Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
Pedro Villavicencio (pedro) wrote :

I've sent this upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=590272 ; the backtrace is good and complete so they might have an idea on what happened, thanks.

Changed in nautilus (Ubuntu):
status: New → Triaged
Changed in nautilus:
status: Unknown → New
Revision history for this message
Francisco Sánchez-Aedo Gálvez (sanchezaedo) wrote :

hi,

i had the same bug once while having the computer unattended so i have nothing else to add :(

Revision history for this message
Rolando Garza (rolandog) wrote :

Me too, though I have i386 architecture instead of amd64 bit.

Revision history for this message
stop (whoopwhoop) wrote :

Happens here as well on 64bit karmic

Revision history for this message
Laryllan (laryllan) wrote :

Happens here too.
Don't know how to reproduce it either, cause it happend (seemingly) without reason.

tags: added: bugpattern-written
Revision history for this message
Monkey (monkey-libre) wrote :

This bug also affect to Ubuntu Lucid Alpha 2

Revision history for this message
Bernd Laser (bernd-laser) wrote :

Hit me in 10.04 beta 1(++) too

Changed in nautilus:
importance: Unknown → Critical
Changed in nautilus:
status: New → Incomplete
Changed in nautilus:
status: Incomplete → Expired
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some year and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
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.