GNOME Bugzilla – Bug 370079
crash in CD/DVD Creator: nothing, totally nothing
Last modified: 2006-11-03 19:43:38 UTC
What were you doing when the application crashed? nothing, totally nothing Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- ** (gnome-terminal:2909): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2909): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2909): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2909): WARNING **: No handler for control sequence `device-control-string' defined. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! 2796: assertion failed "message->refcount.value == 0" file "dbus-message.c" line 672 function dbus_message_cache_or_finalize ** (bug-buddy:6638): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 113979392 vsize: 0 resident: 113979392 share: 0 rss: 28205056 rss_rlim: 0 CPU usage: start_time: 1162567438 rtime: 0 utime: 9592 stime: 0 cutime:9305 cstime: 0 timeout: 287 it_real_value: 0 frequency: 0 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 -1208526080 (LWP 2796)] [New Thread -1221121136 (LWP 6629)] (no debugging symbols found) 0x00a7b402 in __kernel_vsyscall ()
+ Trace 82406
Thread 2 (Thread -1221121136 (LWP 6629))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 351713 ***
Nope...
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 364864 ***