GNOME Bugzilla – Bug 459454
crash in Gimmie:
Last modified: 2007-08-30 23:51:19 UTC
What were you doing when the application crashed? 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: 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 (29 sec old) ---------------------
+ Trace 149900
self._resume ()
self._continuation.next ()
yield self.loader.get_url (str (url), plexer.send ())
gnomevfs.async.open (url, self.open_cb, data=("", callback, args))
gnome-mount 0.5 Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x4d non valide indiquée pour 0x145bf90 (). DOUBLE-CLICK: 400 --> -1 THRESHOLD: 4 --> -1 sox: Unknown input file format for '-': File type 'spx' is not known sh: ogg123: not found Impossible d'ouvrir le fichier de bureau /usr/share/applications/apkg-amsn.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type Impossible d'ouvrir le fichier de bureau /usr/share/applications/apkg-amsn.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type -------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 579, in _compare_item_name cmp(item1.get_name().lower(), item2.get_name().lower()) UnicodeDecodeError: 'utf8' codec can't decode bytes in position 24-26: invalid data
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 419093 ***