GNOME Bugzilla – Bug 419191
crash in Gimmie: Removing gimmie from too...
Last modified: 2007-03-17 05:48:35 UTC
What were you doing when the application crashed? Removing gimmie from tool bar. Had huge panels that persisted under and behind the gimmiw panel. New since latest update Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 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 --------------------- *** Scaling image of height 32 to 48: win-group://Spider (Medium) - 1939945250 - Patience *** Reloading TopicRunningList: Running Applications *** Scaling image of height 32 to 48: win-group://kfbishop@kfbishop: ~/.mozilla/eclipse *** Scaling image of height 32 to 48: win-group://Spider (Medium) - 1939945250 - Patience *** Reloading TopicRunningList: Running Applications *** Scaling image of height 32 to 48: win-group://kfbishop@kfbishop: ~/.mozilla/eclipse *** Scaling image of height 32 to 48: win-group://Spider (Medium) - 1939945250 - Patience *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Active Conversations *** Reloading TopicRunningList: Active Conversations *** Reloading TopicRunningList: Active Conversations *** Reloading TopicRunningList: Active Conversations *** Reloading TopicRunningList: Computer Runni -------------------------------------------------- Traceback (most recent call last):
+ Trace 119294
if self.prefs.get(pref_key, default=True) == True:
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 419134 ***