GNOME Bugzilla – Bug 418667
crash in Gimmie:
Last modified: 2007-10-25 23:21:03 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 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 SystemError: NULL object passed to Py_BuildValue
Desmonté una unidad de memoria USB (pendrive) desde el mismo gimmie, y al moverme por el menu, me dio el error. I umounted a unit of memory USB (pendrive) from gimmie, and when moving me by the menu, it gave the error me. (In reply to comment #0) > What were you doing when the application crashed? > > > > Distribution: Ubuntu 6.10 (edgy) > Gnome Release: 2.16.1 2006-10-02 (Ubuntu) > BugBuddy Version: 2.16.0 > > 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 > > SystemError: NULL object passed to Py_BuildValue >
I have no idea on this one. Sorry. :-(
This happens for me to. I'll try to find out what happens.
gnomevfs.Drive.eject is causing this error, maybe the fault is in the GnomeVFS python bindings
(In reply to comment #4) > gnomevfs.Drive.eject is causing this error, maybe the fault is in the GnomeVFS > python bindings > Yes, definately a bindings bug. In the meantime, I've committed a workaround in SVN change #361. Thanks for tracking this down Markus. Please consider filing a python-gnome bug about this for the version of python-gnome you have installed.
*** Bug 482455 has been marked as a duplicate of this bug. ***
*** Bug 463220 has been marked as a duplicate of this bug. ***
*** Bug 485884 has been marked as a duplicate of this bug. ***
*** Bug 488121 has been marked as a duplicate of this bug. ***
*** Bug 487778 has been marked as a duplicate of this bug. ***
*** Bug 487761 has been marked as a duplicate of this bug. ***
*** Bug 490263 has been marked as a duplicate of this bug. ***