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 462750 - crash in Gimmie: i'm running evolution
crash in Gimmie: i'm running evolution
Status: RESOLVED DUPLICATE of bug 416060
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-02 10:56 UTC by Jorge Luis Endres
Modified: 2007-09-06 09:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jorge Luis Endres 2007-08-02 10:56:55 UTC
What were you doing when the application crashed?
i'm running evolution


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: UbuntuStudio
Icon Theme: UbuntuStudio

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 (216 sec old) ---------------------
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
(evolution-2.10:5863): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Ha ocurrido un error al ejecutar el proceso hijo «/usr/bin/bogofilter» (No existe el fichero ó d
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 474 in do_button_press_event
    self._show()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 479 in _show
    self.topic_win = self.topic.get_topic_window()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 351 in get_topic_window_mod
    self.topic_window = TopicMenu(self)
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 181 in __init__
    TopicView.__init__(self, topic)
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 909 in __init__
    self.sidebar = Sidebar(topic)
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 837 in __init__
    gtk.VBox.__init__(self, False, 4)
TypeError: could not convert parameter 'spacing' of type 'gint'

Comment 1 Benedikt Henrichs 2007-09-06 09:25:19 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 416060 ***