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 373697 - crash in CD/DVD Creator: Browsing my home directo...
crash in CD/DVD Creator: Browsing my home directo...
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: Urgent critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 374026 374197 374200 374223 374266 374422 374452 374481 374487 374526 374625 374644 374694 374889 374899 376063 376537 376682 377520 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-11 05:34 UTC by syazdani
Modified: 2007-12-12 13:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
bugbuddy report (41.41 KB, text/plain)
2006-11-13 00:45 UTC, syazdani 		Details

Description syazdani 2006-11-11 05:34:13 UTC 
What were you doing when the application crashed?
Browsing my home directory.


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.1 2006-11-09 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 202883072 vsize: 202883072 resident: 21229568 share: 14880768 rss: 21229568 rss_rlim: -1
CPU usage: start_time: 1163223235 rtime: 67 utime: 64 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47706498335616 (LWP 12876)]
0x00002b638795cacf in waitpid () from /lib/libpthread.so.0

+ Trace 85290

Thread 1 (Thread 47706498335616 (LWP 12876))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #4 nautilus_directory_async_state_changed
  • #5 nautilus_directory_async_state_changed
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 POA_Nautilus_MetafileMonitor__init
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #29 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 POA_Nautilus_MetafileMonitor__init
  • #34 __libc_start_main
    from /lib/libc.so.6
  • #35 ??
  • #36 ??
  • #37 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Karsten Bräckelmann





          2006-11-12 13:46:31 UTC
        



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






Comment 2


Karsten Bräckelmann





          2006-11-12 13:46:44 UTC
        



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






Comment 3


Karsten Bräckelmann





          2006-11-12 13:46:51 UTC
        



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






Comment 4


Karsten Bräckelmann





          2006-11-12 13:47:00 UTC
        



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






Comment 5


syazdani





          2006-11-12 19:46:33 UTC
        



Hi,

I've been able to consistently reproduce this bug on my computer now. When I open a folder in nautilus, clicking on the changing folder icon at the bottom left hand corner of the window (the one that gives all the parent directories) causes nautilus to crash. Also, I did uninstall nautilus-cdburner, since I thought that was the problem, however nothing changed. Also, when I do the same thing for a 
folder corresponding to a ssh window, everything works out fine.


I am using safe flags for compiling everything "-O2 -pipe -march=k8", and have
rebuild my system since I came across this problem.






Comment 6


Karsten Bräckelmann





          2006-11-12 20:27:35 UTC
        



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






Comment 7


Karsten Bräckelmann





          2006-11-12 20:31:57 UTC
        



syazdani, since you can reproduce this crash at will -- would be great if you can provide a stacktrace with debugging symbols, either just pasted here as a comment or attached to this bug.  Thanks!

Confirming as per duplicates.







Comment 8


syazdani





          2006-11-12 20:59:22 UTC
        



Sure thing. How can I do that?
I added "debug" to my use flags, and recompiled nautilus, but that didn't provide much information. Which other libraries do I need to recompile?







Comment 9


Karsten Bräckelmann





          2006-11-12 22:34:37 UTC
        



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






Comment 10


Karsten Bräckelmann





          2006-11-12 23:03:56 UTC
        



By a quick look at the stacktrace, enabling debugging (hence building with debugging symbols, not stripped) should be sufficient for nautilus and glib. Doing the same for gnome-vfs and gtk+ won't hurt either.

Once these packages have been rebuilt with debugging symbols, please make sure they are properly reloaded. Especially gnome-vfs might need logging out for that.


Finally -- just reproduce the crash. :)

Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here.  Thanks!


[ Also, please be sure that the crash you can reproduce really is this very bug, maybe by comparing the result (see bug-buddy details) with your original stacktrace. The stacktrace after rebuilding with debugging symbols is likely to look different. ]

If you need more info, you should find all you need here, including lots of advanced Details linked:
  http://live.gnome.org/GettingTraces







Comment 11


Karsten Bräckelmann





          2006-11-12 23:47:13 UTC
        



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






Comment 12


Karsten Bräckelmann





          2006-11-12 23:49:31 UTC
        



Note:  All reports apparently on 64 bit architectures.







Comment 13


Karsten Bräckelmann





          2006-11-12 23:52:37 UTC
        



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






Comment 14


Karsten Bräckelmann





          2006-11-13 00:05:04 UTC
        



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






Comment 15


syazdani





          2006-11-13 00:35:41 UTC
        



I think I got what you wanted.. If not, I will try again. (I recompiled glibc.
I think that might have been unnecessary.)

Here is the details from bug-buddy:

Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.1 2006-11-12 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 226279424 vsize: 226279424 resident: 40448000 share: 15306752 rss: 40448000 rss_rlim: -1
CPU usage: start_time: 1163376247 rtime: 188 utime: 178 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47333895187024 (LWP 17237)]
0x00002b0cc6b4eacf in __libc_waitpid (pid=18038, stat_loc=0x7fffffde3dbc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c




+
Trace
    85945






Thread 1
          (Thread 47333895187024 (LWP 17237))


    

  • 
#0
__libc_waitpid

    
                at ../sysdeps/unix/sysv/linux/waitpid.c
                  line
                  41

    

    • 

  • 
#1
gnome_gtk_module_info_get

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

    

    • 

  • 
#2
<signal handler called>

    • 

  • 
#3
call_ready_callbacks_at_idle

    
                at nautilus-directory-async.c
                  line
                  1864

    

    • 

  • 
#4
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#5
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#6
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#7
location_button_clicked_callback

    
                at nautilus-spatial-window.c
                  line
                  677

    

    • 

  • 
#8
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#9
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2440

    

    • 

  • 
#10
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2199

    

    • 

  • 
#11
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#12
gtk_box_class_intern_init

    
                at gtkbox.c
                  line
                  141

    

    • 

  • 
#13
??

    • 

  • 
#14
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#15
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2370

    

    • 

  • 
#16
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2199

    

    • 

  • 
#17
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#18
IA__gtk_binding_entry_add_signal

    
                at gtkbindings.c
                  line
                  784

    

    • 

  • 
#19
??

    • 

  • 
#20
??

    • 

  • 
#21
??

    • 

  • 
#22
??

    • 







0x00002b0cc6b4eacf	41	in ../sysdeps/unix/sysv/linux/waitpid.c







Comment 16


syazdani





          2006-11-13 00:45:42 UTC
        



Created attachment 76452 [details]
bugbuddy report

Oops, I forgot to logout and log back in.
Here is the bugbuddy report after restart






Comment 17


Karsten Bräckelmann





          2006-11-13 01:15:11 UTC
        



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






Comment 18


Karsten Bräckelmann





          2006-11-13 01:27:02 UTC
        



Thanks, syazdani, nice trace! :)

syazdani, please stay tuned for the developers to have a look at this. Pleasure working with you, you have been highly responsive. Should be all that's needed, but let's see what the devs say...

All dupes so far in about one single day. Priority urgent.







Comment 19


naimo





          2006-11-13 04:12:04 UTC
        



...I would NOT get the bug if I first (imemdiately after booting) opened the file system via clicking the "computer" icon, and navigated the filesystem down from root and then up with the "lower left button". If after this I used the "home" icon to navigate attempt to go "up" I would not get the bug.

However, if after rebooting I opened my "home' folder on the desktop, and tried to use the "lower left button' then it crashed.

-N






Comment 20


syazdani





          2006-11-13 16:36:11 UTC
        



If I do as naimo suggested, I would not get the bug either.








Comment 21


Karsten Bräckelmann





          2006-11-14 09:22:47 UTC
        



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






Comment 22


Karsten Bräckelmann





          2006-11-14 09:22:49 UTC
        



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






Comment 23


Karsten Bräckelmann





          2006-11-14 09:22:52 UTC
        



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






Comment 24


Karsten Bräckelmann





          2006-11-14 09:22:58 UTC
        



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






Comment 25


Karsten Bräckelmann





          2006-11-14 09:22:59 UTC
        



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






Comment 26


Germán Poo-Caamaño





          2006-11-30 13:50:44 UTC
        



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






Comment 27


Germán Poo-Caamaño





          2006-12-02 02:22:12 UTC
        



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






Comment 28


Germán Poo-Caamaño





          2006-12-02 02:23:29 UTC
        



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






Comment 29


Germán Poo-Caamaño





          2006-12-02 02:24:05 UTC
        



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






Comment 30


André Klapper





          2007-12-12 13:32:47 UTC
        



no duplicates in the last 12 months.
assuming that this bug has been fixed in the meantime and closing as obsolete.

anybody running into this problem on gnome 2.18 or 2.20, please reopen this report! thanks.