GNOME Bugzilla – Bug 465910
crash in Gimmie: editing preferences
Last modified: 2007-08-28 13:49:10 UTC
What were you doing when the application crashed? editing preferences Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: nuoveXT-1.6 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 (15 sec old) --------------------- *** Reloading TopicRunningList: Running Applications *** Scaling image of height 32 to 48: win-group://gdebi-gtk *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Active Conversations *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Reloading TopicRunningList: Computer Running Source *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Reloading TopicRunningList: Running Applications *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Active Conversations *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Reloading TopicRunningList: Computer Running Source *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Reloading TopicRunningList: Running Applications *** Scaling image of height 32 to 48: win-group://File Roller *** Reloading TopicRunnin -------------------------------------------------- Traceback (most recent call last):
+ Trace 154613
Preferences(self.prefs).show()
self.set_title(_("Gimmie Preferences"))
return dgettext(_current_domain, message)
codeset=_localecodesets.get(domain))
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 417988 ***