Bug 385912 – crash in CD/DVD Creator: This application is alwa...

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 385912 - crash in CD/DVD Creator: This application is alwa...


Summary:	crash in CD/DVD Creator: This application is alwa...


Status:	RESOLVED DUPLICATE of bug 320020

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:	nautilus[debugsymbols]

Duplicates:	385890 385891 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-14 16:49 UTC by andre.brioso
Modified:	2007-01-12 02:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description andre.brioso 2006-12-14 16:49:56 UTC

What were you doing when the application crashed?
This application is always crashing, crashes when gnome inits and every second after.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 45170688 vsize: 0 resident: 45170688 share: 0 rss: 12472320 rss_rlim: 0
CPU usage: start_time: 1166114782 rtime: 0 utime: 37 stime: 0 cutime:34 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

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 -1227422032 (LWP 5710)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 94161

Thread 1 (Thread -1227422032 (LWP 5710))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 nautilus_directory_async_state_changed
at nautilus-directory-async.c line 1917
#5 nautilus_directory_monitor_add_internal
at nautilus-directory-async.c line 669
#6 vfs_file_monitor_add
at nautilus-vfs-directory.c line 105
#7 nautilus_directory_file_monitor_add
at nautilus-directory.c line 1619
#8 add_directory_to_directory_list
at fm-directory-view.c line 1706
#9 add_directory_to_scripts_directory_list
at fm-directory-view.c line 1741
#10 fm_directory_view_init
at fm-directory-view.c line 1929
#11 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set
from /usr/lib/libgobject-2.0.so.0
#13 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 fm_desktop_icon_view_create
at fm-desktop-icon-view.c line 777
#17 nautilus_view_factory_create
at nautilus-view-factory.c line 69
#18 create_content_view
at nautilus-window-manage-views.c line 1019
#19 got_file_info_for_view_selection_callback
at nautilus-window-manage-views.c line 912
#20 desktop_callback_check_done
at nautilus-desktop-directory-file.c line 221
#21 ready_callback_call
at nautilus-directory-async.c line 1237
#22 nautilus_directory_async_state_changed
at nautilus-directory-async.c line 1849
#23 execute_queued_functions
at nautilus-idle-queue.c line 66
#24 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
at nautilus-main.c line 372
#30 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#31 _start
#0 __kernel_vsyscall

Comment 1 andre.brioso 2006-12-14 16:54:00 UTC

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

Comment 2 andre.brioso 2006-12-14 16:54:33 UTC

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

Comment 3 André Klapper 2007-01-12 02:47:03 UTC

this is the same stacktrace as http://bugzilla.gnome.org/show_bug.cgi?id=320020#c19 , therefore marking as a duplicate.

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