GNOME Bugzilla – Bug 468402
crash in Computer: I just clicked on my upd...
Last modified: 2007-08-21 20:42:40 UTC
Version: 2.16.2 What were you doing when the application crashed? I just clicked on my updates directory icon within a Nautilus directory window showing the contents of my home directory 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: 617455616 vsize: 617455616 resident: 63295488 share: 44572672 rss: 63295488 rss_rlim: 0 CPU usage: start_time: 1187411651 rtime: 3233 utime: 2509 stime: 724 cutime:5 cstime: 30 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 12679)] 0x00000030a820d9ff in __libc_waitpid (pid=22037, stat_loc=0x7fff56ca05fc, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 156494
Thread 1 (Thread 46912496437184 (LWP 12679))
0x00000030a820d9ff 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); ----------- .xsession-errors (69705 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 349551 ***