GNOME Bugzilla – Bug 371098
crash in CD/DVD Creator:
Last modified: 2006-11-05 16:47:18 UTC
What were you doing when the application crashed? 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.2 #7 PREEMPT Sat Nov 4 13:21:37 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors (4148 sec old) --------------------- localuser:gnome2 being added to access control list /etc/profile.d/sendfile.sh: line 2: /usr/bin/check_sendfile: No such file or directory SESSION_MANAGER=local/m5:/tmp/.ICE-unix/23356 (openbox:23783): ObRender-WARNING **: Failed to load the theme 'TheBear' Falling back to the default: 'bear2' Gnome-Message: gnome_execute_async_with_env_fds: returning -1 I/O warning : failed to load external entity "/home/gnome2/.config/openbox/menu.xml" (gnome-panel:23788): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80f98c0 (gnome-panel:23788): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f98c0 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 Xlib: unexpected async reply (sequence 0xa)! gnome-screensaver-Message: Found best visual for GL: 0x21 -------------------------------------------------- Memory status: size: 60080128 vsize: 0 resident: 60080128 share: 0 rss: 10842112 rss_rlim: 0 CPU usage: start_time: 1162700383 rtime: 0 utime: 128 stime: 0 cutime:108 cstime: 0 timeout: 20 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 -1208752432 (LWP 23849)] (no debugging symbols found) 0xb7f63410 in __kernel_vsyscall ()
+ Trace 83253
Thread 1 (Thread -1208752432 (LWP 23849))
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 ***