GNOME Bugzilla – Bug 370163
crash in CD/DVD Creator: copy a second directory ...
Last modified: 2006-11-03 19:41:20 UTC
What were you doing when the application crashed? copy a second directory from a samba window to the desktop 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:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (<unknown>:21821): WARNING **: Add decoder wavpack (86044) please ** (<unknown>:21821): WARNING **: Add decoder targa (96) please ** (<unknown>:21821): WARNING **: Add decoder dsicinvideo (97) please ** (<unknown>:21821): WARNING **: Add decoder dsicinaudio (86045) please ** (<unknown>:21821): WARNING **: Add decoder tiertexseqvideo (98) please ** (<unknown>:21821): WARNING **: Add decoder tiff (99) please 2821: assertion failed "message->refcount.value == 0" file "dbus-message.c" line 672 function dbus_message_cache_or_finalize ** (bug-buddy:23784): WARNING **: Couldn't load icon for Open Folder Unable to connect to yum-updatesd... -------------------------------------------------- Memory status: size: 129507328 vsize: 0 resident: 129507328 share: 0 rss: 26193920 rss_rlim: 0 CPU usage: start_time: 1162578079 rtime: 0 utime: 185932 stime: 0 cutime:177558 cstime: 0 timeout: 8374 it_real_value: 0 frequency: 3730 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 -1208907008 (LWP 2821)] [New Thread -1317983344 (LWP 23776)] [New Thread -1231991920 (LWP 30372)] (no debugging symbols found) 0x00bf5394 in g_ptr_array_add () from /lib/libglib-2.0.so.0
+ Trace 82473
Thread 2 (Thread -1317983344 (LWP 23776))
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 ***