Bug 404198 – crash in CD/DVD Creator: Was not using the CD cre...

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 404198 - crash in CD/DVD Creator: Was not using the CD cre...


Summary:	crash in CD/DVD Creator: Was not using the CD cre...


Status:	RESOLVED DUPLICATE of bug 361777

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:

Depends on:
Blocks:

Reported:	2007-02-04 08:57 UTC by f.murillo7459
Modified:	2007-02-04 13:59 UTC

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

Description f.murillo7459 2007-02-04 08:57:57 UTC

What were you doing when the application crashed?
Was not using the CD create application as the bug report tool suggested. Maybe just need a reboot. thanks


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

Memory status: size: 86908928 vsize: 0 resident: 86908928 share: 0 rss: 31592448 rss_rlim: 0
CPU usage: start_time: 1170543751 rtime: 0 utime: 4896 stime: 0 cutime:3828 cstime: 0 timeout: 1068 it_real_value: 0 frequency: 154

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

+ Trace 107862

Thread 1 (Thread -1227221328 (LWP 4645))

#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 gdk_window_foreign_new_for_display
from /usr/lib/libgdk-x11-2.0.so.0
#5 _gtk_selection_request
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 POA_Nautilus_MetafileMonitor__init
#20 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#21 ??
#0 __kernel_vsyscall

Comment 1 Marc-Andre Lureau 2007-02-04 13:59:05 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 361777 ***