GNOME Bugzilla – Bug 468751
crash in Computer: Trying to copy an '. Cl...
Last modified: 2007-10-05 15:03:44 UTC
Version: 2.16.2 What were you doing when the application crashed? Trying to copy an '. Clicking on 'Audio Disc' to see the contents... 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.22.2-42.fc6 #1 SMP Wed Aug 15 11:52:47 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 606748672 vsize: 606748672 resident: 60325888 share: 44748800 rss: 60325888 rss_rlim: 0 CPU usage: start_time: 1187590422 rtime: 1136 utime: 858 stime: 278 cutime:1 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496437184 (LWP 22075)] 0x00000035aca0d9ff in __libc_waitpid (pid=28955, stat_loc=0x7fffa3479cec, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 156753
Thread 1 (Thread 46912496437184 (LWP 22075))
0x00000035aca0d9ff 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); ----------- .xsession-errors (156772 sec old) --------------------- *** libdvdread: CHECK_VALUE failed in ../input/libdvdnav/nav_read.c:356 *** *** for dsi->dsi_gi.zero1 == 0 *** *** libdvdread: CHECK_VALUE failed in nav_read.c:356 *** *** for dsi->dsi_gi.zero1 == 0 *** *** libdvdread: CHECK_VALUE failed in ../input/libdvdnav/nav_read.c:356 *** *** for dsi->dsi_gi.zero1 == 0 *** Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 320020 ***