Bug 377670 – crash in CD/DVD Creator: Reloaded a (non-blank) C...

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 377670 - crash in CD/DVD Creator: Reloaded a (non-blank) C...


Summary:	crash in CD/DVD Creator: Reloaded a (non-blank) C...


Status:	RESOLVED INCOMPLETE

Product:	gtk+
Classification:	Platform
Component:	Backend: X11
Version:	2.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	gtk-bugs

URL:
Whiteboard:

Duplicates:	378797 447667 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-21 07:12 UTC by siddharth.patwardhan
Modified:	2007-06-20 12:46 UTC

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

Description siddharth.patwardhan 2006-11-21 07:12:34 UTC

What were you doing when the application crashed?
Reloaded a (non-blank) CD.


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

Memory status: size: 86523904 vsize: 0 resident: 86523904 share: 0 rss: 28983296 rss_rlim: 0
CPU usage: start_time: 1164076080 rtime: 0 utime: 4830 stime: 0 cutime:4552 cstime: 0 timeout: 278 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 -1226705232 (LWP 5435)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88168

Thread 1 (Thread -1226705232 (LWP 5435))

#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 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#5 gdk_region_rectangle
from /usr/lib/libgdk-x11-2.0.so.0
#6 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_widget_queue_resize
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_label_set_justify
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_label_set_text
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_statusbar_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 _gtk_marshal_VOID__UINT_STRING
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 gtk_statusbar_push
from /usr/lib/libgtk-x11-2.0.so.0
#18 POA_Nautilus_MetafileMonitor__init
#19 nautilus_undo_transaction_unregister_object
#20 fm_directory_view_bump_zoom_level
#21 fm_directory_view_bump_zoom_level
#22 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 POA_Nautilus_MetafileMonitor__init
#28 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#29 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-11-24 22:08:39 UTC

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

Comment 2 Christian Kirbach 2006-11-24 22:10:39 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!

please isntall the glib and gtk+ packages

Comment 3 Bruno Boaventura 2006-12-27 20:20:52 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 4 André Klapper 2007-06-20 12:46:57 UTC

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