Bug 372471 – crash in CD/DVD Creator: Clicking on a USB pendri...

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 372471 - crash in CD/DVD Creator: Clicking on a USB pendri...


Summary:	crash in CD/DVD Creator: Clicking on a USB pendri...


Status:	RESOLVED FIXED

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	Immediate blocker
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	373293 373294 373473 373545 373630 373678 373679 373730 373734 373743 373842 373859 373875 373876 373882 373921 373933 373962 374008 374017 374045 374115 374127 374336 374363 379546 456905 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-08 14:20 UTC by vonbrand
Modified:	2007-07-26 12:55 UTC

See Also:
GNOME target:	2.16.x
GNOME version:	2.15/2.16

Description vonbrand 2006-11-08 14:20:47 UTC

What were you doing when the application crashed?
Clicking on a USB pendrive...


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.16.1 2006-10-21 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-rc4 #1 SMP PREEMPT Tue Nov 7 18:58:18 CLST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (2837 sec old) ---------------------
evolution-shell-Message: Killing old version of evolution-data-server...
evolution-shell-Message: Killing old version of evolution-data-server...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:7232): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:7232): DEBUG: mailto URL program: evolution
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Max failures exceeded, exiting now
--------------------------------------------------

Memory status: size: 94126080 vsize: 0 resident: 94126080 share: 0 rss: 17764352 rss_rlim: 0
CPU usage: start_time: 1162995521 rtime: 0 utime: 127 stime: 0 cutime:104 cstime: 0 timeout: 23 it_real_value: 0 frequency: 311

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 -1208984832 (LWP 12658)]
(no debugging symbols found)
0xb7f2d410 in __kernel_vsyscall ()

+ Trace 84352

Thread 1 (Thread -1208984832 (LWP 12658))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_cast
from /lib/libgobject-2.0.so.0
#5 nautilus_directory_ref
#6 nautilus_directory_async_state_changed
#7 nautilus_directory_async_state_changed
#8 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#10 g_main_context_check
from /lib/libglib-2.0.so.0
#11 g_main_loop_run
from /lib/libglib-2.0.so.0
#12 POA_Nautilus_MetafileMonitor__init
#13 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#21 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /lib/libgobject-2.0.so.0
#23 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#25 g_signal_emit
from /lib/libgobject-2.0.so.0
#26 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /lib/libgobject-2.0.so.0
#34 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#38 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#39 g_main_context_check
from /lib/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/libglib-2.0.so.0
#41 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#42 POA_Nautilus_MetafileMonitor__init
#43 __libc_start_main
from /lib/libc.so.6
#44 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-11-10 11:33:52 UTC

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

Comment 2 Karsten Bräckelmann 2006-11-11 02:06:46 UTC

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

Comment 3 Karsten Bräckelmann 2006-11-11 02:06:53 UTC

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

Comment 4 Karsten Bräckelmann 2006-11-11 02:07:00 UTC

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

Comment 5 André Klapper 2006-11-12 02:06:18 UTC

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

Comment 6 André Klapper 2006-11-12 02:06:18 UTC

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

Comment 7 André Klapper 2006-11-12 02:06:54 UTC

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

Comment 8 André Klapper 2006-11-12 02:06:57 UTC

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

Comment 9 André Klapper 2006-11-12 02:07:34 UTC

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

Comment 10 André Klapper 2006-11-12 02:07:47 UTC

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

Comment 11 André Klapper 2006-11-12 02:08:05 UTC

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

Comment 12 André Klapper 2006-11-12 02:10:49 UTC

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

Comment 13 André Klapper 2006-11-12 02:10:55 UTC

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

Comment 14 André Klapper 2006-11-12 02:11:01 UTC

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

Comment 15 André Klapper 2006-11-12 02:11:09 UTC

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

Comment 16 André Klapper 2006-11-12 02:14:23 UTC

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

Comment 17 André Klapper 2006-11-12 02:14:33 UTC

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

Comment 18 André Klapper 2006-11-12 02:14:36 UTC

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

Comment 19 André Klapper 2006-11-12 02:14:43 UTC

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

Comment 20 André Klapper 2006-11-12 02:14:49 UTC

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

Comment 21 André Klapper 2006-11-12 02:14:57 UTC

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

Comment 22 André Klapper 2006-11-12 02:33:13 UTC

bug 373730 is most probably a duplicate.

Comment 23 Karsten Bräckelmann 2006-11-12 02:36:22 UTC

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

Comment 24 Karsten Bräckelmann 2006-11-12 02:46:45 UTC

Bug 373730 actually are 20 reports including its duplicates. All of them within 24 hours. Plus these identical dupes above. This is huge.

Note:  Developers, please note that we immediately added this bug report to
       the auto-stacktrace-reject list!  If you need more info, contact the
       Bugsquad on IRC.


Also see bug 373730 comment 21.

Comment 25 Nickolay V. Shmyrev 2006-11-12 13:45:01 UTC

Hm, there were a lot of changes in directory-async during last time, for example this one:

2006-11-07  Alexander Larsson  <alexl@redhat.com>                               
                                                                                
        * NEWS:                                                                 
        Update for release                                                      
                                                                                
        * libnautilus-private/nautilus-directory-async.c:                       
        * libnautilus-private/nautilus-directory.c:                             
        Unschedule call_ready callbacks on directory finalize, not              
        on file finalize.                                                       
        Keep monitors around until we call the call_when_ready callback         
        at idle time.                                                           
        Call async_state_changed and update_metadata_monitors after             
        call_when_ready callbacks have been called at idle.                     
                                                                                
        (fixes make check)                                                      
                               
One of them caused crash. Is this problem reproducable, probably we can just bisect CVS to find wrong code.

Comment 26 Karsten Bräckelmann 2006-11-12 19:50:42 UTC

Bug 373904 comment 1, a duplicate of bug 373730, which is the same issue as this bug got a stacktrace with (some) debugging symbols. According to the comment it is the same crash, reproducible.

However, please note that this particular stacktrace actually looks like the crash in bug 373294.

See my previous comment 373294 comment 18, possibly related. This could be the missing link.


Also note that bug 373294 comment 19 got a stacktrace with (Nautilus) debugging symbols, which is supposed to be that issue, reproduced.


Bug 374336 got another stacktrace just like the first one I mentioned here, actually looking like the other bug. Not duping that one for now but leaving a note, since I can't decide if bug 373904 comment 1 really is the same crash.

This is hell of confusing.

Comment 27 André Klapper 2006-11-13 01:19:56 UTC

42 duplicates in 5 days => gnome 2.16.x blocker.

Comment 28 Alexander Larsson 2006-11-13 11:51:29 UTC

Fixed in CVS:

2006-11-13  Alexander Larsson  <alexl@redhat.com>

	* libnautilus-private/nautilus-directory-async.c:
	Ref the NautilusDirectory during call_ready_callbacks_at_idle.
	Fixes #372471

Comment 29 Alexander Larsson 2006-11-13 11:54:47 UTC

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

Comment 30 Alexander Larsson 2006-11-13 11:56:02 UTC

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

Comment 31 Diego Escalante Urrelo (not reading bugmail) 2006-11-14 04:31:31 UTC

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

Comment 32 Diego Escalante Urrelo (not reading bugmail) 2006-11-14 04:44:01 UTC

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

Comment 33 Diego Escalante Urrelo (not reading bugmail) 2006-11-14 05:03:54 UTC

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

Comment 34 Diego Escalante Urrelo (not reading bugmail) 2006-11-14 05:04:36 UTC

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

Comment 35 Alexander Larsson 2006-11-14 12:37:14 UTC

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

Comment 36 Germán Poo-Caamaño 2006-11-27 21:33:32 UTC

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

Comment 37 André Klapper 2006-12-03 14:34:01 UTC

possible duplicates of http://bugzilla.gnome.org/show_bug.cgi?id=373294#stacktrace :
http://bugzilla.gnome.org/show_bug.cgi?id=364335#stacktrace
http://bugzilla.gnome.org/show_bug.cgi?id=379286#stacktrace
http://bugzilla.gnome.org/show_bug.cgi?id=369188#stacktrace
http://bugzilla.gnome.org/show_bug.cgi?id=368135#stacktrace
http://bugzilla.gnome.org/show_bug.cgi?id=379951#stacktrace

would be nice if a dev could take a look at them.

Comment 38 André Klapper 2007-04-02 02:39:29 UTC

only 2 rejected traces between 2007-01-23 and 2007-04-02 => removing from the auto-reject list.

Comment 39 André Klapper 2007-07-26 12:55:43 UTC

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