GNOME Bugzilla – Bug 418832
crash in Gimmie: Crash when clicking on a...
Last modified: 2007-03-17 06:06:55 UTC
What were you doing when the application crashed? Crash when clicking on a topic, either Linux or Programs. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Human 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 (947 sec old) --------------------- for dbus_interface in interface_keys:
+ Trace 119018
signal_name):
for dbus_interface in interface_keys:
if match.maybe_handle_message(message):
self._handler(*args, **kwargs)
elif state == self.avahi.CLIENT_FAILURE:
** Message: <information> You are now connected to the wireless network 'amygda7a'. checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 516, in do_button_press_event self._show() File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 521, in _show self.topic_win = self.topic.get_topic_window() File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 393, in get_topic_window_mod self.topic_window = TopicMenu(self) File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 181, in __init__ TopicView.__init__(self, topic) File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 917, in __init__ self.sidebar = Sidebar(topic) File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 845, in __init__ gtk.VBox.__init__(self, gtk.FALSE, 4) TypeError: could not convert parameter 'spacing' of type 'gint'
Not sure why this is happening. Can you remove the ", 4" from that line and see if fixes things?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 416060 ***