nautilus crashed with SIGSEGV

Bug #186530 reported by mattismyname
This bug report is a duplicate of:  Bug #185360: nautilus crashed with SIGSEGV 8.04. Edit Remove
6
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: nautilus

I had just saved a .png to the desktop (incidentally a screenshot for a different nautilus problem report). The icon was still showing a clock as the preview had not yet been generated. I right-clicked the icon and at that point nautilus crashed.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Jan 27 22:18:21 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.21.6-0ubuntu2
PackageArchitecture: i386
ProcCmdline: nautilus --sm-client-id 117f000101000120148926500000056100001 --screen 0
ProcCwd: /home/matt
ProcEnviron:
 PATH=/home/matt/sw/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libgdk_pixbuf-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux Aluminumy 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse klog lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner syslog video

Tags: apport-crash
Revision history for this message
mattismyname (mattismyname) wrote :

I got the crash to go away by adding myself to the group "disk". Nautilus was somehow crashing when trying to access a device I did not have access to (/dev/sdb2)

Revision history for this message
mattismyname (mattismyname) wrote :

Ok, I take that back. It still happens immediately after I try to save another screenshot.png file to the desktop.

If I fire up nautilus from the terminal, I get:

matt@Aluminumy:~$ nautilus

** (nautilus:11163): WARNING **: Unable to add monitor: Not supported
Segmentation fault (core dumped)

If I load up the coredump, I get:

Core was generated by `nautilus'.
Program terminated with signal 11, Segmentation fault.
#0 0xb729d72b in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0 0xb729d72b in ?? () from /lib/tls/i686/cmov/libc.so.6
#1 0xb78188db in ?? () from /usr/lib/libgdk_pixbuf-2.0.so.0
#2 0xbf914b08 in ?? ()
#3 0xb768d248 in ?? () from /usr/lib/libglib-2.0.so.0
#4 0x00000802 in ?? ()
#5 0xb73c4520 in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#6 0x085e9620 in ?? ()
#7 0xb76ce680 in ?? () from /usr/lib/libgobject-2.0.so.0
#8 0x086eba80 in ?? ()
#9 0x086eba80 in ?? ()
#10 0xbf914b28 in ?? ()
#11 0xb769e552 in g_object_get_qdata () from /usr/lib/libgobject-2.0.so.0
#12 0xb729d490 in strtol () from /lib/tls/i686/cmov/libc.so.6
#13 0x080e7cf8 in ?? ()
#14 0x00000000 in ?? ()

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

StacktraceTop:____strtol_l_internal () from /lib/tls/i686/cmov/libc.so.6
strtol () from /lib/tls/i686/cmov/libc.so.6
thumbnail_read_callback (source_object=0x86067d0, res=0x8670cc0, user_data=0x86cc7c0)
IA__g_simple_async_result_complete (simple=0x8670cc0)
load_contents_close_callback (obj=0x868b090, close_res=0x8670c00, user_data=0x86e2360)

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in nautilus:
importance: Undecided → Medium
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.