GNOME Bugzilla – Bug 430098
crash in Gimmie: I loaded it then clicked...
Last modified: 2007-04-26 07:28:30 UTC
What were you doing when the application crashed? I loaded it then clicked on the "Library" button 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: Enforcing 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 --------------------- DCOP: unregister 'amarokcollectionscanner' ** (agave:6372): WARNING **: Can't open palette directory: /home/cldoyle/.local/share/agave/palettes DCOP: register 'amarokcollectionscanner' -> number of clients is now 2 DCOP: unregister 'amarokcollectionscanner' X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4800029 DCOP: register 'amarokcollectionscanner' -> number of clients is now 2 DCOP: unregister 'amarokcollectionscanner' DCOP: register 'amarokcollectionscanner' -> number of clients is now 2 DCOP: unregister 'amarokcollectionscanner' DCOP: register 'amarokcollectionscanner' -> number of clients is now 2 DCOP: unregister 'amarokcollectionscanner' -------------------------------------------------- Traceback (most recent call last):
+ Trace 128060
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicWindow(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 ***