GNOME Bugzilla – Bug 428107
crash in Gimmie: Попытался воспользоватьс...
Last modified: 2007-04-12 22:43:29 UTC
What were you doing when the application crashed? Попытался воспользоваться аплетом Gimmie. Добавился корректно, вылетел при попытке досутпа к меню Library. 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.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled 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 (31729 sec old) --------------------- beryl: pixmap 0x3000136 can't be bound to texture beryl: Couldn't bind redirected window 0x1200388 to texture beryl: pixmap 0x3000133 can't be bound to texture beryl: Couldn't bind redirected window 0x120035c to texture beryl: pixmap 0x3000136 can't be bound to texture beryl: Couldn't bind redirected window 0x1200388 to texture beryl: pixmap 0x3000133 can't be bound to texture beryl: Couldn't bind redirected window 0x120035c to texture beryl: pixmap 0x3000136 can't be bound to texture beryl: Couldn't bind redirected window 0x1200388 to texture beryl: pixmap 0x3000133 can't be bound to texture beryl: Couldn't bind redirected window 0x120035c to texture beryl: pixmap 0x3000136 can't be bound to texture ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 126454
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 ***