Bug 406723 – crash in CD/DVD Creator:

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 406723 - crash in CD/DVD Creator:


Summary:	crash in CD/DVD Creator:


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Duplicates:	406725 423625 428417 438067 438069 439961 (view as bug list)
Depends on:
Blocks:

Reported:	2007-02-11 15:28 UTC by ryskul
Modified:	2007-07-30 03:06 UTC

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

Description ryskul 2007-02-11 15:28:21 UTC

What were you doing when the application crashed?



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

Memory status: size: 53018624 vsize: 0 resident: 53018624 share: 0 rss: 16936960 rss_rlim: 0
CPU usage: start_time: 1171207662 rtime: 0 utime: 105 stime: 0 cutime:96 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

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 -1227209040 (LWP 4718)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109800

Thread 1 (Thread -1227209040 (LWP 4718))

#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 gnome_vfs_file_info_list_unref
from /usr/lib/libgnomevfs-2.so.0
#5 nautilus_directory_ref
#6 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#7 nautilus_directory_unref
#8 nautilus_file_ref
#9 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#10 nautilus_file_unref
#11 nautilus_directory_async_state_changed
#12 nautilus_directory_async_state_changed
#13 nautilus_directory_async_state_changed
#14 nautilus_directory_async_state_changed
#15 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
from /usr/lib/libglib-2.0.so.0
#22 ??
#23 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#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 POA_Nautilus_MetafileMonitor__init
#30 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#31 ??
#0 __kernel_vsyscall

Comment 1 Susana 2007-02-11 18:42:25 UTC

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

Comment 2 André Klapper 2007-02-14 15:59:04 UTC

Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

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 in advance!

[1] Please install the following debug packages provided by Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, libgnome2-0-dbgsym, and libgnomeui-0-dbg.

More details can be found here: http://live.gnome.org/GettingTraces

Also, this bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Comment 3 André Klapper 2007-03-31 13:36:12 UTC

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

Comment 4 André Klapper 2007-04-11 16:35:54 UTC

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

Comment 5 palfrey 2007-05-13 15:44:28 UTC

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

Comment 6 palfrey 2007-05-13 15:44:31 UTC

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

Comment 7 palfrey 2007-05-20 18:41:14 UTC

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

Comment 8 Pedro Villavicencio 2007-07-30 03:06:03 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!