GNOME Bugzilla – Bug 482902
crash in Gimmie: I deleted "Recently used...
Last modified: 2007-10-05 20:48:39 UTC
What were you doing when the application crashed? I deleted "Recently used" Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (34 sec old) --------------------- Could not set idle IO priority...attempting best effort 7 priority Throttle level is 0 /usr/bin/compiz.real /usr/bin/ccsm /usr/bin/compiz /usr/bin/gtk-window-decorator /usr/bin/metacity /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format Impossible d'ouvrir le fichier de bureau /usr/share/applications/mozilla-thunderbird.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type PID TTY TIME CMD compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (gnome-panel:14284): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height 36 Impossible d'ouvrir le fichier de bureau /usr/share/applications/mozilla-thunderbird.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/mozilla-thunderbird.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 167367
cmp((item1.get_name() or "").lower(), (item2.get_name() or "").lower())
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 ***