GNOME Bugzilla – Bug 434590
crash in Gimmie: I click in Library, noth...
Last modified: 2007-05-03 03:12:36 UTC
What were you doing when the application crashed? I click in Library, nothing more 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: Human 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 (224 sec old) --------------------- /usr/bin/compiz.real: Couldn't bind redirected window 0xe1539f to texture /usr/bin/compiz.real: pixmap 0x2c00590 can't be bound to texture /usr/bin/compiz.real: Couldn't bind redirected window 0xe15422 to texture /usr/bin/compiz.real: pixmap 0x2c00588 can't be bound to texture /usr/bin/compiz.real: Couldn't bind redirected window 0xe1539f to texture /usr/bin/compiz.real: pixmap 0x2c00590 can't be bound to texture /usr/bin/compiz.real: Couldn't bind redirected window 0xe15422 to texture /usr/bin/compiz.real: pixmap 0x2c00588 can't be bound to texture /usr/bin/compiz.real: Couldn't bind redirected window 0xe1539f to texture Cutting log (size: 101791, max: 100000) ** (yelp:9892): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (yelp:9892): WARNING **: IOR not set. ** (yelp:9892): WARNING **: Could not locate registry -------------------------------------------------- Traceback (most recent call last):
+ Trace 131446
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
self._add_toolbar_items()
for i in self.topic.get_toolbar_items(self.tooltips):
btn = PlacesMenuButton(tooltips)
self.set_menu(PlacesMenu())
for item in device_source.get_items():
for i in self.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 ***