Bug 435761 – crash in CD/DVD Creator: Adding folders to burn t...

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 435761 - crash in CD/DVD Creator: Adding folders to burn t...


Summary:	crash in CD/DVD Creator: Adding folders to burn t...


Status:	RESOLVED DUPLICATE of bug 431773

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-05-04 09:31 UTC by treydaddy
Modified:	2007-05-04 11:23 UTC

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

Description treydaddy 2007-05-04 09:31:36 UTC

What were you doing when the application crashed?
Adding folders to burn to disk


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 93499392 vsize: 0 resident: 93499392 share: 0 rss: 28598272 rss_rlim: 0
CPU usage: start_time: 1178078116 rtime: 0 utime: 5417 stime: 0 cutime:4331 cstime: 0 timeout: 1086 it_real_value: 0 frequency: 106

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208342832 (LWP 3186)]
(no debugging symbols found)
0x00fda402 in __kernel_vsyscall ()

+ Trace 132298

Thread 1 (Thread -1208342832 (LWP 3186))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 nautilus_directory_async_state_changed
#11 fm_directory_view_bump_zoom_level
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 fm_directory_view_bump_zoom_level
#19 fm_directory_view_bump_zoom_level
#20 nautilus_clipboard_monitor_emit_changed
#21 nautilus_directory_async_state_changed
#22 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 g_main_context_check
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /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/libc.so.6
#29 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall



----------- .xsession-errors (105430 sec old) ---------------------
** (eggcups:3197): WARNING **: IPP request failed with status 1030
** (eggcups:3197): WARNING **: IPP request failed with status 1030
** (eggcups:3197): WARNING **: IPP request failed with status 1030
** (eggcups:3197): WARNING **: IPP request failed with status 1030
** (eggcups:3197): WARNING **: IPP request failed with status 1030
** (eggcups:3197): WARNING **: IPP request failed with status 1030
** (eggcups:3197): WARNING **: IPP request failed with status 1030
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-05-04 11:23: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 431773 ***