After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 455606 - crash in Gimmie: loading the applet
crash in Gimmie: loading the applet
Status: RESOLVED DUPLICATE of bug 455468
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-10 16:44 UTC by semakwetu
Modified: 2007-07-11 12:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description semakwetu 2007-07-10 16:44:37 UTC
What were you doing when the application crashed?
loading the applet


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.4 2007-06-29 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gummy
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 (11 sec old) ---------------------
** (update-notifier:5118): WARNING **: no cdrom: disk
--- Hash table keys for warning below:
--> file:///home/semakwetu
(nautilus:7864): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(gnome-panel:5022): Bonobo-WARNING **: Cannot get value: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
(gnome-panel:5022): Bonobo-WARNING **: Cannot get value: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: function takes exactly 0 arguments (1 given)
Comment 1 palfrey 2007-07-11 12:32:07 UTC
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 455468 ***