GNOME Bugzilla – Bug 486071
crash in Deskbar: Je ne faisais que me rel...
Last modified: 2007-10-13 16:17:40 UTC
What were you doing when the application crashed? Je ne faisais que me reloguer.... ?? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Wed Oct 10 06:00:47 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux 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 --------------------- evolution-alarm-notify-Message: Setting timeout for 25987 1192233600 1192207613 evolution-alarm-notify-Message: Sat Oct 13 02:00:00 2007 evolution-alarm-notify-Message: Fri Oct 12 18:46:53 2007 Connexion au daemon [ ###] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon (evolution-alarm-notify:8574): evolution-alarm-notify-WARNING **: Impossible de créer la fabrique de services de notification d'alarme, peut-être qu'elle fonctionne déjà... alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New alarm-notify.c:304 (alarm_channel_setup) - Channel Setup alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify alarm-queue.c:1870 (alarm_queue_init) alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Sat Oct 13 02:00:00 2007 Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [ ### ] Connexion au daemon [### ] Connexion au daemon [ ### ] Connexion au daemon -------------------------------------------------- Traceback (most recent call last):
+ Trace 169768
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
Thank you for reporting this bug. It looks like this bug is the same as bug 474179.
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 474179 ***