nautilus crashed with SIGSEGV in g_slice_alloc()"

Bug #128142 reported by StoatWblr
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

no idea what caused this.

ProblemType: Crash
Architecture: i386
Date: Wed Jul 25 03:42:08 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: cdrom
Package: nautilus 1:2.19.5-0ubuntu1
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcCwd: /home/alan
ProcEnviron:
 LANGUAGE=en_NZ.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0xb757da6e in g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 #1 0xb755f176 in g_list_prepend () from /usr/lib/libglib-2.0.so.0
 #2 0xb755a928 in ?? () from /usr/lib/libglib-2.0.so.0
 #3 0x00000000 in ?? ()
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_list_prepend () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGSEGV in g_slice_alloc()
Uname: Linux msslqd 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
StoatWblr (stoatwblr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:��Z () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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 backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)?

Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in nautilus:
status: Incomplete → Invalid
Revision history for this message
Andrew M Tapp (andrew-tapp) wrote :

I don't know about the other guys, but the bug happened to me while copying files from one location to another. I've since reattempted the copy while waiting for the bug data to upload and it went smoothly. So I don't know if I can reproduce the bug for a valgrind log. Is there a way to set up a running log or something so the next time if it happens, the log will already be generated without having to reproduce it?

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.