After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335114 - Nautilus Crash [nautilus_file_get_string_attribute]
Nautilus Crash [nautilus_file_get_string_attribute]
Status: RESOLVED DUPLICATE of bug 343488
Product: nautilus
Classification: Core
Component: Navigation
2.14.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 335725 337159 339771 341162 341458 342460 342909 343781 345792 345847 347580 347787 348069 348899 349441 349618 352158 353047 354548 354576 355875 355923 357013 357487 358053 358240 360968 366892 369312 382119 386404 399732 409995 411395 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-19 13:24 UTC by my.ekoes
Modified: 2007-02-23 23:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
5 backtraces (4.27 KB, application/x-bzip)
2006-06-26 09:18 UTC, Richard Edmands 		Details
Trace of the crash (8.16 KB, text/plain)
2006-10-07 19:27 UTC, dbet1 		Details
The prevously mentioned backtraces (4.33 KB, application/x-bzip)
2006-11-17 16:19 UTC, dbet1 		Details
Another crash (8.72 KB, application/octet-stream)
2006-12-09 18:43 UTC, dbet1 		Details

Description my.ekoes 2006-03-19 13:24:36 UTC 
Distribution: Ubuntu 6.04 (dapper)
Package: nautilus
Severity: Normal
Version: GNOME2.14.0 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Nautilus Crash
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.0)
Description:
Description of the crash:
Nautilus crashes when I tryto open a mounted folder (ext3 fs)

Steps to reproduce the crash:
1. mount $devices_with_ext3_fs $your_home/$dir
2. Open $your_home in Nautilus
3. Click on $dir

Expected Results:


How often does this happen?
This happen often, but no always.

Additional Information:



Debugging Information:

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)
[Thread debugging using libthread_db enabled]
[New Thread -1225263424 (LWP 18700)]
[New Thread -1227428944 (LWP 18707)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 67049

Thread 1 (Thread -1225263424 (LWP 18700))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #6 nautilus_file_get_string_attribute
  • #7 nautilus_file_get_string_attribute
  • #8 nautilus_directory_unref
  • #9 nautilus_directory_unref
  • #10 egg_recent_item_unref
  • #11 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-03-19 13:24 -------
Comment 1 Sergej Kotliar 2006-03-23 20:49:41 UTC 
*** Bug 335725 has been marked as a duplicate of this bug. ***
Comment 2 Fabio Bonelli 2006-04-04 14:38:51 UTC 
*** Bug 337159 has been marked as a duplicate of this bug. ***
Comment 3 Fabio Bonelli 2006-04-26 08:11:54 UTC 
*** Bug 339771 has been marked as a duplicate of this bug. ***
Comment 4 Martin Wehner 2006-05-06 01:10:16 UTC 
Dups, confirming.
Comment 5 Teppo Turtiainen 2006-05-09 20:10:35 UTC 
*** Bug 341162 has been marked as a duplicate of this bug. ***
Comment 6 Fabio Bonelli 2006-05-14 09:41:59 UTC 
*** Bug 341458 has been marked as a duplicate of this bug. ***
Comment 7 Fabio Bonelli 2006-05-21 08:21:04 UTC 
*** Bug 342460 has been marked as a duplicate of this bug. ***
Comment 8 Emmanuel Touzery 2006-05-21 12:09:19 UTC 
I think I got the same crash too, here is my stack:
(ubuntu dapper up to date as of may 21)

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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225595200 (LWP 4952)]
[New Thread -1227048016 (LWP 4982)]
(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)
(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)
(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)
(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)
0xffffe410 in __kernel_vsyscall ()

+ Trace 68349

Thread 1 (Thread -1225595200 (LWP 4952))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #6 nautilus_file_get_string_attribute
  • #7 nautilus_file_get_string_attribute
  • #8 nautilus_directory_unref
  • #9 nautilus_directory_unref
  • #10 egg_recent_item_unref
  • #11 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 __kernel_vsyscall 






Comment 9


Fabio Bonelli





          2006-05-25 13:25:18 UTC
        



*** Bug 342909 has been marked as a duplicate of this bug. ***






Comment 10


Fabio Bonelli





          2006-05-25 13:26:52 UTC
        



Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 11


Martin Wehner





          2006-05-26 16:12:15 UTC
        



All dupes seem to be from Ubuntu Dapper, so this is probably caused by one of their patches.







Comment 12


Sebastien Bacher





          2006-05-26 22:33:29 UTC
        



most of the patches from the Ubuntu package are backport from the stable cvs, could anybody get a backtrace with nautilus-dbg installed?






Comment 13


mathesis





          2006-05-28 13:20:12 UTC
        



I've tried it, but the file was empty :-/






Comment 14


Elijah Newren





          2006-06-03 19:51:39 UTC
        



*** Bug 343781 has been marked as a duplicate of this bug. ***






Comment 15


Tom G





          2006-06-13 18:53:14 UTC
        



Nautilus Version 2.14.1






Comment 16


Fabio Bonelli





          2006-06-22 12:00:34 UTC
        



Dapper's nautilus 2.14.1 here and I can't reproduce it.






Comment 17


mathesis





          2006-06-22 12:32:27 UTC
        



Ubuntu Dapper up to date : Gnome 2.14.2
I still have this problem, I think it happens less often, but it still happens.






Comment 18


mathesis





          2006-06-22 21:02:00 UTC
        



Here is the backtrace I get with 2.14.2 :

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225886016 (LWP 12366)]
[New Thread -1227592784 (LWP 12389)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    69008






Thread 1
          (Thread -1225886016 (LWP 12366))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_module_info_get

    
                from
                /usr/lib/libgnomeui-2.so.0

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
g_str_hash

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#5
g_hash_table_lookup

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#6
get_link_files

    
                at nautilus-file.c
                  line
                  1355

    

    • 

  • 
#7
nautilus_file_emit_changed

    
                at nautilus-file.c
                  line
                  5396

    

    • 

  • 
#8
nautilus_directory_emit_change_signals

    
                at nautilus-directory.c
                  line
                  762

    

    • 

  • 
#9
emit_change_signals_for_all_files

    
                at nautilus-directory.c
                  line
                  265

    

    • 

  • 
#10
corba_metafile_ready

    
                at nautilus-directory-metafile-monitor.c
                  line
                  110

    

    • 

  • 
#11
ORBit_c_stub_invoke

    
                from
                /usr/lib/libORBit-2.so.0

    

    • 

  • 
#12
Nautilus_MetafileMonitor_metafile_ready

    
                at nautilus-shell-interface-stubs.c
                  line
                  17

    

    • 

  • 
#13
metafile_read_mark_done

    
                at nautilus-metafile.c
                  line
                  822

    

    • 

  • 
#14
metafile_read_done

    
                at nautilus-metafile.c
                  line
                  1836

    

    • 

  • 
#15
eel_read_entire_file

    
                from
                /usr/lib/libeel-2.so.2

    

    • 

  • 
#16
gnome_vfs_job_get_count

    
                from
                /usr/lib/libgnomevfs-2.so.0

    

    • 

  • 
#17
g_child_watch_add

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#18
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#19
g_main_context_check

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#20
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#21
gtk_main

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#22
main

    
                at nautilus-main.c
                  line
                  406

    

    • 

  • 
#23
__libc_start_main

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#24
_start

    
                at ../sysdeps/i386/elf/start.S
                  line
                  119

    

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 19


Fabio Bonelli





          2006-06-25 22:04:58 UTC
        



*** Bug 345847 has been marked as a duplicate of this bug. ***






Comment 20


Richard Edmands





          2006-06-26 09:18:59 UTC
        



Created attachment 68022 [details]
5 backtraces

here are the 5 backtraces of this i have gathered over the past week. i am also running ubuntu dapper 6.06. (up to date as of 20 minutes ago)






Comment 21


Fabio Bonelli





          2006-06-28 08:12:59 UTC
        



*** Bug 345792 has been marked as a duplicate of this bug. ***






Comment 22


Sergej Kotliar





          2006-07-15 10:52:54 UTC
        



*** Bug 347580 has been marked as a duplicate of this bug. ***






Comment 23


Karsten Bräckelmann





          2006-07-17 16:45:31 UTC
        



*** Bug 347787 has been marked as a duplicate of this bug. ***






Comment 24


Teppo Turtiainen





          2006-07-20 08:24:18 UTC
        



*** Bug 348069 has been marked as a duplicate of this bug. ***






Comment 25


Fabio Bonelli





          2006-07-27 10:05:24 UTC
        



*** Bug 348899 has been marked as a duplicate of this bug. ***






Comment 26


Karsten Bräckelmann





          2006-07-31 16:35:41 UTC
        



*** Bug 349441 has been marked as a duplicate of this bug. ***






Comment 27


Karsten Bräckelmann





          2006-08-02 14:54:15 UTC
        



*** Bug 349618 has been marked as a duplicate of this bug. ***






Comment 28


Christian Kirbach





          2006-08-08 20:54:45 UTC
        



*** Bug 350452 has been marked as a duplicate of this bug. ***






Comment 29


Christian Kirbach





          2006-08-08 21:00:38 UTC
        



arg that was wrong. 

mathesis in comment #18 posted a different trace caused by a different problem (the one in Bug 350452 )






Comment 30


Sergej Kotliar





          2006-08-20 20:38:32 UTC
        



*** Bug 352158 has been marked as a duplicate of this bug. ***






Comment 31


Sergej Kotliar





          2006-08-27 12:54:25 UTC
        



*** Bug 353047 has been marked as a duplicate of this bug. ***






Comment 32


Karsten Bräckelmann





          2006-09-06 08:07:39 UTC
        



*** Bug 354548 has been marked as a duplicate of this bug. ***






Comment 33


Karsten Bräckelmann





          2006-09-06 08:28:56 UTC
        



*** Bug 354576 has been marked as a duplicate of this bug. ***






Comment 34


Karsten Bräckelmann





          2006-09-13 23:18:52 UTC
        



*** Bug 355875 has been marked as a duplicate of this bug. ***






Comment 35


Karsten Bräckelmann





          2006-09-14 10:35:10 UTC
        



*** Bug 355923 has been marked as a duplicate of this bug. ***






Comment 36


Sergej Kotliar





          2006-09-21 05:36:30 UTC
        



*** Bug 357013 has been marked as a duplicate of this bug. ***






Comment 37


towsonu2003





          2006-09-21 06:50:22 UTC
        



a number of people sent backtraces, why is this still "needs info"?

PS. just asking.






Comment 38


Emmanuel Touzery





          2006-09-21 06:58:08 UTC
        



(In reply to comment #37)
> a number of people sent backtraces, why is this still "needs info"?

developers want a backtrace with debug symbols (with a nautilus compiled in "debug" mode). those backtraces contain more information and are more reliable.

the problem is that the users don't seem to be able to reliably reproduce the bug (certainly it's my case, it happened to me once and i can't reproduce it), so we just have a bunch of non-debug backtraces.

if someone knows a 100% way of reproducing the bug, it would help.






Comment 39


Fabio Bonelli





          2006-09-24 17:58:18 UTC
        



*** Bug 357487 has been marked as a duplicate of this bug. ***






Comment 40


Sebastien Bacher





          2006-09-27 09:13:57 UTC
        



could ubuntu users install libglib2.0-0-dbg and nautilus-dbg and get a backtrace with those installed?






Comment 41


Emmanuel Touzery





          2006-09-27 09:31:08 UTC
        



(In reply to comment #40)
> could ubuntu users install libglib2.0-0-dbg and nautilus-dbg and get a
> backtrace with those installed?

I'll put it another way. does anybody have any way to reproduce this bug whenever they want? if anybody has a way to reproduce this bug, i'll get debug packages, and post a debug backtrace.

the problem here IMHO is that nobody can reproduce this bug "on demand" and that nobody is running permanently debug packages. So I think we'll wait a long time for a debug backtrace, no matter how much users want to help.








Comment 42


towsonu2003





          2006-09-27 18:33:25 UTC
        



(In reply to comment #41)
> (In reply to comment #40)
> > could ubuntu users install libglib2.0-0-dbg and nautilus-dbg and get a
> > backtrace with those installed?
> 
> does anybody have any way to reproduce this bug
> whenever they want?

I just noticed I already had nautilus-dbg installed when I had that crash. I'm installing the other one, but I have no way to reproduce. my bug # 357013 . hopefully the automatic report it generates includes debug symbols [does it?]






Comment 43


Karsten Bräckelmann





          2006-09-27 23:41:13 UTC
        



*** Bug 358053 has been marked as a duplicate of this bug. ***






Comment 44


Karsten Bräckelmann





          2006-09-27 23:42:55 UTC
        



Qouting bug 358053:

> Additional Information:
> This is a previously reported bug (e.g. 335114, 355875).  However, as 
> I've had Nautilus minimized, there's
> an interesting new wrinkle - Gnome habitually places the icons for the
> plugged in USB drive's partitions in exactly the same place on the
> desktop screen (in my case the two appear at the top, and 1/3 of the way
> from the bottom, respectively, of empty second 'column' from left of the
> screen, the first 'column' being filled with icons of internal hard
> drive partitions).  If it places them in the normal place, Nautilus does
> NOT crash when USB plugged in.  On occasions when Nautilus DOES crash,
> it has placed the icon(s) somewhere else (different places on different
> occasions).






Comment 45


towsonu2003





          2006-09-28 00:29:28 UTC
        



I don't have USB drive's partitions on my desktop screen (feature disabled thru gconf, mounted partitions don't appear on my desktop automatically) but I still got the crash (once). just in case this is relevant info. 






Comment 46


Fabio Bonelli





          2006-09-29 09:35:14 UTC
        



*** Bug 358240 has been marked as a duplicate of this bug. ***






Comment 47


dbet1





          2006-10-03 08:58:29 UTC
        



I have changed nautilus from browser mode to spartial mode and does not had any crash.
I will try to produce a backtrace with debug symbols as soon as possible.
One crash I can reproduce any time, but perhaps this is an other bug. If I have an FTP server icon on the desktop and after the mouse klick instead I connect, I cancel the dialog which asks me for the password. Then nautilus also crashes.






Comment 48


dbet1





          2006-10-06 10:52:35 UTC
        



I have uploaded a new bug (360120). It is reproducible and I have the debug packages installed. I hope it helps you.






Comment 49


Christian Kirbach





          2006-10-06 13:37:47 UTC
        



dbet1 the new bug is not the same as the one discussed here. can you please disable/uninstall the libeiciel extension and try again. please post your trace as an attachment to this report and I'll analyse it.

Richard from comment #20: that is a different trace caused by a different problem
(the one in Bug 350452 )






Comment 50


dbet1





          2006-10-07 18:31:54 UTC
        



I have seen the comment in 360120 to eiciel later.

After uninstalling eiciel there is no crash anymore using the properties dialog disconnected. Therefore I can not upload a trace. Thank you for your attention.






Comment 51


dbet1





          2006-10-07 19:27:56 UTC
        



Created attachment 74241 [details]
Trace of the crash

This is one of the random crashes of nautilus. This time it crashes after clicking properties of a newly connected USB device just after login in.






Comment 52


dbet1





          2006-10-08 15:38:39 UTC
        



No, it is not random. I can reproduce it each time I right click on the symbol on the desktop for this USB device. After deinstalling eiciel this does not occur again. Therefore this is not a nautilus bug. Sorry.






Comment 53


Christian Kirbach





          2006-10-09 17:29:40 UTC
        



thanks the trace from comment #51 is definitely a crash in the eiciel extension and not related to this report.






Comment 54


Elijah Newren





          2006-10-09 18:56:55 UTC
        



*** Bug 360968 has been marked as a duplicate of this bug. ***






Comment 55


Alexander Larsson





          2006-10-16 13:48:17 UTC
        



This really looks like a dup of 343488, but that bug has full debug info, so marking this as duplicate.


*** This bug has been marked as a duplicate of 343488 ***






Comment 56


André Klapper





          2006-10-29 15:37:02 UTC
        



*** Bug 366892 has been marked as a duplicate of this bug. ***






Comment 57


André Klapper





          2006-11-02 10:55:08 UTC
        



*** Bug 369312 has been marked as a duplicate of this bug. ***






Comment 58


dbet1





          2006-11-17 16:18:38 UTC
        



Since I have removed the package eiciel I had several crashes with nautilus. Each time I don't know what could be the reason. If you find any hints in my backtrace I would try it out.
I have attached three backtraces and hope, there are useful.






Comment 59


dbet1





          2006-11-17 16:19:53 UTC
        



Created attachment 76771 [details]
The prevously mentioned backtraces






Comment 60


Susana





          2006-12-04 19:17:54 UTC
        



*** Bug 382119 has been marked as a duplicate of this bug. ***






Comment 61


dbet1





          2006-12-09 18:43:14 UTC
        



Created attachment 78042 [details]
Another crash

Nautilus crashed again if I click on the new desktop symbol on the desktop after I put in a USB stick. At this time I had several nautilus windows opened.
I hope this stack trace is helpful.






Comment 62


Christian Kirbach





          2006-12-10 22:36:29 UTC
        



thank you dbet1, but this report is a duplicate.
your traces are excellent, but the problem has already been analysed and fixed - see bug 343488

the problem should be gone with the next nautilus update of your distribution.






Comment 63


Susana





          2006-12-16 10:54:59 UTC
        



*** Bug 386404 has been marked as a duplicate of this bug. ***






Comment 64


Bruno Boaventura





          2007-01-24 00:26:10 UTC
        



*** Bug 399732 has been marked as a duplicate of this bug. ***






Comment 65


Pedro Villavicencio





          2007-02-20 14:31:05 UTC
        



*** Bug 409995 has been marked as a duplicate of this bug. ***






Comment 66


Pedro Villavicencio





          2007-02-23 23:41:43 UTC
        



*** Bug 411395 has been marked as a duplicate of this bug. ***