GNOME Bugzilla – Bug 427791
crash in Gimmie: clicked on the Linux but...
Last modified: 2007-04-12 22:43:11 UTC
What were you doing when the application crashed? clicked on the Linux button Distribution: Ubuntu 6.04 (dapper) Gnome Release: 2.18.0 2007-03-17 (Debian) BugBuddy Version: 2.18.0 System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299903 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: dlg-neu 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 (113052 sec old) --------------------- This codecs.conf is too old and incompatible with this MPlayer release! at line 6 Can't open joystick device /dev/input/js0: No such file or directory Can't init input joystick mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing http://www.enormous.tv/movies/dj.mov. Resolving www.enormous.tv for AF_INET6... Couldn't resolve name for AF_INET6: www.enormous.tv Resolving www.enormous.tv for AF_INET... Connecting to server www.enormous.tv[207.106.172.144]: 80... Cache size set to 320 KBytes Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache f ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 126218
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicWindow(self)
self.find_first_button()
filtered = self._filter_items_num_days_ago(items, zoom)
return [x for x in items if self._filter_compare(x, days_ago)]
for i in self.get_items_uncached():
for item in source.get_items_uncached():
yield DriveItem(drive)
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
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 421620 ***