GNOME Bugzilla – Bug 486282
crash in Gimmie: Je vennais juste d'insta...
Last modified: 2007-10-14 13:46:40 UTC
What were you doing when the application crashed? Je vennais juste d'installer et de lancer Gimmie... 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 Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (590 sec old) --------------------- ./Shell/__init__.py:153: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead gtk.threads_init() /usr/lib/gdesklets/utils/ErrorFormatter.py:118: RuntimeWarning: Python C API version mismatch for module gtop: This Python has API version 1013, module gtop has version 1012. module = _old_imp(name, globs, locls, fromlist) sh: disown: not found sh: disown: not found sh: disown: not found sh: disown: not found sh: disown: not found warnings.warn("apt API not stable yet", FutureWarning) ** Message: cant load file '/home/havany/.kiba-dock/config': L'ouverture du fichier « /home/havany/.kiba-dock/config » a échoué : Aucun fichier ou répertoire de ce type (rhythmbox:5992): RhythmDB-WARNING **: trying to sync properties of non-editable file Lecture en cours WAVE '/home/havany/.amsn/skins/Cannabis aMSN v1.2/sounds/online.wav' : Signed 16 bit Little Endian, Taux 44100 Hz, Stéréo (synaptic:21970): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 169928
for mi in self.topic.get_context_menu_items():
self._add_templates(menu)
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 413620 ***