GNOME Bugzilla – Bug 485295
crash in Gimmie: trying to add a program ...
Last modified: 2007-10-10 14:13:29 UTC
What were you doing when the application crashed? trying to add a program to favorites Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Oct 9 09:51:52 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: LegacyHuman Icon Theme: Nuovo 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 --------------------- *** Reloading TopicRunningList: Running Applications *** Scaling image of height 32 to 48: win-group://nekostar-feisty - conky *** Scaling image of height 32 to 48: win-group://xmms *** Scaling image of height 32 to 48: win-group://Pidgin *** Scaling image of height 32 to 48: win-group://xchat *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Active Conversations *** Reloading TopicRunningList: Computer Running Source *** Setting source: <MenuSource Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 2 arguments (1 given) /usr/share/themes/LegacyHuman/gtk-2.0/gtkrc:55: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored. /usr/share/themes/LegacyHuman/gtk-2.0/gtkrc:56: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/LegacyHuman/gtk-2.0/gtkrc:57: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 2 arguments (1 given)
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 ***