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 435426 - crash in Gimmie: Menü geöffnet
crash in Gimmie: Menü geöffnet
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-05-03 07:12 UTC by Joerggrosshans
Modified: 2007-05-13 23:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Joerggrosshans 2007-05-03 07:12:22 UTC 
What were you doing when the application crashed?
Menü geöffnet		


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

System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
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 (113 sec old) ---------------------
SESSION_MANAGER=local/bellemerlord:/tmp/.ICE-unix/5168
Fenstermanager-Warnung: In der Konfigurationsdatenbank gefundenes »« ist kein zulässiger Wert für die Tastenkombination »toggle_shaded«
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Fenstermanager-Warnung: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160001b (tilda)
Fenstermanager-Warnung: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Initializing gnome-mount extension
(gnome-panel:5230): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 25
** (gnome-app-install:5417): WARNING **: return value of custom widget handler was not a GtkWidget
/usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1532: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed
  item.applications.set_default_sort_func(None)
Fenstermanager-Warnung: Fenster 0x2c06a8f () zeigt durch einen MWM-Wink an, dass die Größe nicht veränderbar ist, setzt jedoch die minimale Größe auf 597 x 290 und die maximale Größe auf 214748
Fenstermanager-Warnung: Fenster 0x2c06a8f () zeigt durch einen MWM-Wink an, dass die Größe nicht veränderbar ist, setzt jedoch die minimale Größe auf 597 x 290 und die maximale Größe auf 214748
--------------------------------------------------
Traceback (most recent call last):

+ Trace 132054

  • 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


Tony Tsui





          2007-05-13 23:08:32 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 ***