Bug 381036 – 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 381036 - crash in CD/DVD Creator:


Summary:	crash in CD/DVD Creator:


Status:	RESOLVED DUPLICATE of bug 374002

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:	425782 444985 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-30 20:37 UTC by elliotn
Modified:	2007-06-22 22:09 UTC

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

Description elliotn 2006-11-30 20:37:30 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: 253652992 vsize: 0 resident: 253652992 share: 0 rss: 196538368 rss_rlim: 0
CPU usage: start_time: 1164916271 rtime: 0 utime: 3881 stime: 0 cutime:3697 cstime: 0 timeout: 184 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 -1226606928 (LWP 4626)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90643

Thread 1 (Thread -1226606928 (LWP 4626))

#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 gtk_ui_manager_remove_ui
from /usr/lib/libgtk-x11-2.0.so.0
#5 nautilus_marshal_BOOLEAN__POINTER
#6 fm_directory_view_bump_zoom_level
#7 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_hide
from /usr/lib/libgtk-x11-2.0.so.0
#15 fm_directory_view_bump_zoom_level
#16 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#17 fm_directory_view_bump_zoom_level
#18 gtk_clipboard_get_owner
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gtk_marshal_VOID__BOXED_UINT
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#24 gtk_target_list_unref
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gtk_selection_notify
from /usr/lib/libgtk-x11-2.0.so.0
#26 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#32 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 POA_Nautilus_MetafileMonitor__init
#40 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#41 ??
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-11-30 21:37:05 UTC

Thanks for taking the time to report this bug.
Unfortunately, that 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. 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. Thanks in advance!

Comment 2 Jens Granseuer 2006-12-25 12:22:08 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!

Comment 3 palfrey 2007-04-07 14:18:15 UTC

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

Comment 4 André Klapper 2007-06-22 17:56:12 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, and libgnomeui-0-dbg.

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

Comment 5 André Klapper 2007-06-22 17:56:41 UTC

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

Comment 6 André Klapper 2007-06-22 22:09:04 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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