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 487778 - crash in Gimmie: - ejected a device
crash in Gimmie: - ejected a device
Status: RESOLVED DUPLICATE of bug 418667
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-18 05:46 UTC by unmerkbar
Modified: 2007-10-22 22:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description unmerkbar 2007-10-18 05:46:31 UTC
What were you doing when the application crashed?
 - ejected a device


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 Sun Oct 14 23:05:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaCappuccino
Icon Theme: Gion

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 (11623 sec old) ---------------------
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
monitor callback
...Too much output, ignoring rest...
--------------------------------------------------
Gimmie Version: 0.2.7

SystemError: NULL object passed to Py_BuildValue
Comment 1 H. 2007-10-22 22:31:42 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 418667 ***