Ubuntu
nautilus package

Nautilus crashes when opening a folder

Bug #14877 reported by Matthew Franz
64
This bug affects 12 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
High
Sebastien Bacher

Bug Description

mfranz@mfranz-t40u:~$ dpkg -s nautilus
Package: nautilus
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 2588
Maintainer: Takuo KITAME <email address hidden>
Architecture: i386
Version: 2.10.0-0ubuntu8

Symptom: click on any folder and app quits unexpectedly...

Tried purging and re-installing (and reboots, of course) to no effect...

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.

[snip]

[Thread debugging using libthread_db enabled]
[New Thread -1224067840 (LWP 10426)]
[New Thread -1236866128 (LWP 10458)]
[New Thread -1236599888 (LWP 10457)]
[New Thread -1236333648 (LWP 10456)]
[New Thread -1236067408 (LWP 10455)]
[New Thread -1235801168 (LWP 10454)]
[New Thread -1235534928 (LWP 10453)]
[New Thread -1234863184 (LWP 10452)]
[New Thread -1226044496 (LWP 10435)]
(no debugging symbols found)

[snip]

0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7bfb48b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7dd7d97 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xffffe410 in __kernel_vsyscall ()
#5 0xb7369175 in raise () from /lib/tls/i686/cmov/libc.so.6
#6 0xb736a7d8 in abort () from /lib/tls/i686/cmov/libc.so.6
[snip]

#40 0x00000000 in ?? ()
#41 0x083563a8 in ?? ()
#42 0x0814a0bc in ?? ()
#43 0xbfffd1b8 in ?? ()
#44 0xb75b0c2d in g_free () from /usr/lib/libglib-2.0.so.0

http://lists.ubuntu.com/archives/ubuntu-users/2005-April/028410.html: http://lists.ubuntu.com/archives/ubuntu-users/2005-April/028410.html

See original description
Revision history for this message
Matthew Franz (mdfranz) wrote :

Getting rid of spatial browsing sort of fixes this but still rather unstable

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

does it happen an all the directories ? Could you get a backtrace with
libglib2.0-0-dbg libgtk2.0-0-dbg libgnomevfs2-0-dbg and nautilus-dbg installed ?

Revision history for this message
Matthew Franz (mdfranz) wrote :

Yes, happens in all the dirs --

Trace looks very similar to 8556

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1224084224 (LWP 13087)]
[New Thread -1237197904 (LWP 13119)]
[New Thread -1236931664 (LWP 13118)]
[New Thread -1236665424 (LWP 13117)]
[New Thread -1236399184 (LWP 13116)]
[New Thread -1236132944 (LWP 13115)]
[New Thread -1235866704 (LWP 13114)]
[New Thread -1235600464 (LWP 13113)]
[New Thread -1234928720 (LWP 13112)]
[New Thread -1226093648 (LWP 13092)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7bf748b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7dd3d97 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xffffe410 in __kernel_vsyscall ()
#5 0xb7365175 in raise () from /lib/tls/i686/cmov/libc.so.6
#6 0xb73667d8 in abort () from /lib/tls/i686/cmov/libc.so.6
#7 0xbfffd0f0 in ?? ()
#8 0x00000000 in ?? ()
#9 0x00000020 in ?? ()
#10 0x00000000 in ?? ()
#11 0x00000000 in ?? ()
#12 0x00000000 in ?? ()
#13 0x00000000 in ?? ()
#14 0x00000000 in ?? ()
#15 0x00000000 in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x00000000 in ?? ()
#19 0x00000000 in ?? ()
#20 0x00000000 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000000 in ?? ()
#23 0x00000000 in ?? ()
#24 0x00000000 in ?? ()
#25 0x00000000 in ?? ()
#26 0x00000000 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x0840c1a8 in ?? ()
#42 0x0814a0c8 in ?? ()
#43 0xbfffd188 in ?? ()
#44 0xb75acc2d in IA__g_free (mem=0x0) at gmem.c:187

Revision history for this message
Matthew Franz (mdfranz) wrote :

with gnome-ui-dbg
Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1224084224 (LWP 13191)]
[New Thread -1236264016 (LWP 13315)]
[New Thread -1234928720 (LWP 13193)]
[New Thread -1226093648 (LWP 13192)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7bf748b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7dd3d97 in libgnomeui_segv_handle (signum=6) at gnome-ui-init.c:741
#3 <signal handler called>
#4 0xffffe410 in __kernel_vsyscall ()
#5 0xb7365175 in raise () from /lib/tls/i686/cmov/libc.so.6
#6 0xb73667d8 in abort () from /lib/tls/i686/cmov/libc.so.6
#7 0xbfffd100 in ?? ()
#8 0x00000000 in ?? ()
#9 0x00000020 in ?? ()
#10 0x00000000 in ?? ()
#11 0x00000000 in ?? ()
#12 0x00000000 in ?? ()
#13 0x00000000 in ?? ()
#14 0x00000000 in ?? ()
#15 0x00000000 in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x00000000 in ?? ()
#19 0x00000000 in ?? ()
#20 0x00000000 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000000 in ?? ()
#23 0x00000000 in ?? ()
#24 0x00000000 in ?? ()
#25 0x00000000 in ?? ()
#26 0x00000000 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x0840c850 in ?? ()
#42 0x0814a0a0 in ?? ()
#43 0xbfffd198 in ?? ()
#44 0xb75acc2d in IA__g_free (mem=0x0) at gmem.c:187

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

I don't know why but your backtrace are useless. Can you try to get one in this way:
- gnome-session-remove nautilus
- gdb nautilus
(gdb) r
.. crash ...
(gdb) thread apply all bt

Revision history for this message
Matthew Franz (mdfranz) wrote :

(nautilus:20396): Pango-CRITICAL **: _pango_engine_shape_covers: assertion
`PANGO_IS_FONT (font)' failed

(nautilus:20396): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT
(object)' failed

(nautilus:20396): Pango-CRITICAL **: _pango_engine_shape_shape: assertion
`PANGO_IS_FONT (font)' failed

Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed:
(glyphs->num_glyphs > 0)
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1224084224 (LWP 20396)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 3 (Thread -1234928720 (LWP 20400)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7bf400e in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb77394fd in gnome_vfs_thread_pool_wait_for_work (state=0x81fe520)
    at gnome-vfs-thread-pool.c:163
#3 0xb773953e in thread_entry (cast_to_state=0x81fe520)
    at gnome-vfs-thread-pool.c:176
#4 0xb75c0362 in g_thread_create_proxy (data=0x81fd348) at gthread.c:561
#5 0xb7bf1ae0 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#6 0xb740fc9a in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1226093648 (LWP 20399)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7407549 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb75a88de in g_main_context_poll (context=0x8167530, timeout=-1,
    priority=2147483647, fds=0xfffffffc, n_fds=9) at gmain.c:2880
#3 0xb75a7f57 in g_main_context_iterate (context=0x8167530, block=1,
    dispatch=1, self=0x8170988) at gmain.c:2573
#4 0xb75a851e in IA__g_main_loop_run (loop=0x816fd78) at gmain.c:2782
#5 0xb7644f28 in link_thread_io_context () from /usr/lib/libORBit-2.so.0
#6 0xb75ff398 in __JCR_LIST__ () from /usr/lib/libglib-2.0.so.0
#7 0xb6eb4ad8 in ?? ()
#8 0xb75c0362 in g_thread_create_proxy (data=0x8170988) at gthread.c:561
Previous frame inner to this frame (corrupt stack?)
#0 0xffffe410 in __kernel_vsyscall ()

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

do you still have this issue?

Revision history for this message
Stefano Costa (steko) wrote :
Download full text (4.2 KiB)

i don't know if it can be useful, but following your advice as in #5 I get the
following (long and annoying.. but I can't understand what is actually useful)

This GDB was configured as "i386-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) r
Starting program: /usr/bin/nautilus
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224067392 (LWP 11110)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1226114128 (LWP 11115)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging sy...

Read more...

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

(In reply to comment #8)
> i don't know if it can be useful, but following your advice as in #5 I get the
> following (long and annoying.. but I can't understand what is actually useful)
> ...
> Program received signal SIG33, Real-time event 33.
> [Switching to Thread -1226114128 (LWP 11115)]
> 0xffffe410 in __kernel_vsyscall ()
> (gdb) thread apply all bt

Thanks but this not a crash. Can you use "handle SIG33 pass nostop noprint"
before "r" so gdb ignores these signal and you can get the actual crash?

Revision history for this message
Daniel Holbach (dholbach) wrote :

Matthew, any news? Does this still happen for you?

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

no reply, bug closed. Feel free to reopen with the asked informations if that's
still an issue for you

Revision history for this message
Jesse Haubrich (jhaubrich) wrote :

I have experienced the above problem exactly as described. I was playing with some nautilus plugins (naultilus-gksu nautilus-open-terminal nautilus-image-resize). I installed them, tested gksu, then open-terminal, then opened a folder to test image-resize and nautilus crashed. I can open any folder, but when I try to open a folder from within nautilus.. boom. I'm able to use nautilus in the spatial browsing mode (shudder).

I completely removed all nautilus related packages and config files in my home, no better after reinstalling. I installed nautilus-dbg and attached its log.

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

The new comment is bug #127826 which is new and has already been fixed in gutsy

Revision history for this message
Bill Pearce (pearceg) wrote :

I was looking at a network folder when using Copyto. I then reverted to copy and pastre which worked OK.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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