GNOME Bugzilla – Bug 434070
crash in Gimmie:
Last modified: 2007-05-03 03:37:20 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (28 sec old) --------------------- libdvdread: Attempting to use device /dev/scd0 mounted on /media/cdrom0 for CSS authentication libdvdread: Couldn't find device name. libdvdnav: Using dvdnav version 1.1.4 from http://xine.sf.net libdvdnav: Can't read name block. Probably not a DVD-ROM device. libdvdnav: Unable to find map file '/home/sbrinkmann/.dvdnav/.map' libdvdnav: DVD disk reports itself with Region mask 0x00000000. Regions: 1 2 3 4 5 6 7 8 (totem:6440): Gtk-WARNING **: Attempting to add `dvd:/' to the list of recently used resources, but not MIME type was defined libdvdread: Using libdvdcss version 1.2.9 for DVD access libdvdread: Attempting to use device /dev/scd0 mounted on /media/cdrom0 for CSS authentication libdvdread: Couldn't find device name. libdvdnav: Using dvdnav version 1.1.4 from http://xine.sf.net libdvdnav: Can't read name block. Probably not a DVD-ROM device. libdvdnav: Unable to find map file '/home/sbrinkmann/.dvdnav/.map' libdvdnav: DVD disk reports itself with Region mask 0x00000000. Regions: 1 2 3 4 5 6 7 8 -------------------------------------------------- Traceback (most recent call last):
+ Trace 131056
cmp(item1.get_name().lower(), item2.get_name().lower())
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 419093 ***