GNOME Bugzilla – Bug 495442
crash in Gimmie: Starting it up
Last modified: 2007-11-11 14:17:39 UTC
What were you doing when the application crashed? Starting it up Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc) BugBuddy Version: 2.20.1 System: Linux 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora 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 (73 sec old) --------------------- SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/13493,unix/unix:/tmp/.ICE-unix/13493 11 ** (gsynaptics-init:13519): WARNING **: Using synclient Unknown parameter CoastingSpeedThreashold (gnome-panel:13510): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x8fabf58 (gnome-panel:13510): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x8fabf58 Unable to open desktop file /usr/share/applications/gaim.desktop for panel launcher: No such file or directory (gnome-panel:13510): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x8fabf58 (gnome-panel:13510): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x8fabf58 Unable to open desktop file /usr/share/applications/gaim.desktop for panel launcher: No such file or directory -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 1 argument (2 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 ***