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 422755 - crash in Gimmie: I was updating my system
crash in Gimmie: I was updating my system
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-03-25 19:59 UTC by Jaime Rave
Modified: 2007-05-26 01:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jaime Rave 2007-03-25 19:59:12 UTC
What were you doing when the application crashed?
I was updating my system


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.0 2007-03-13 (Ubuntu)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: IndustrialTango
Icon Theme: Tango

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 (436 sec old) ---------------------
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
fixme:winsock:NtStatusToWSAError Status code c0000024 converted to DOS error code 6
...Too much output, ignoring rest...
--------------------------------------------------
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 Stuart Read 2007-03-27 01:27:35 UTC
I also had this bug. I was updating a large number of packages, but I don't think that it was a specific one, because it created a "'Gimmie' has quit unexpectedly" pop-up box, but as long as I pressed "reload applet" it would reload Gimmie, and crash again. Note that this did not start bug-buddy for me. Once update-manager was finished and exited, the "reload" button restarted Gimmie and it no longer crashed. 

I am using Ubuntu 7.04 (continually updated from 6.10) and Gimmie 0.2.5
Comment 2 Tony Tsui 2007-05-26 01:12:46 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 ***