GNOME Bugzilla – Bug 519153
crash in Deskbar: iniciando o soistema ope...
Last modified: 2008-02-28 11:55:06 UTC
What were you doing when the application crashed? iniciando o soistema operacional Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: HighContrastInverse 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 (25 sec old) --------------------- evolution-alarm-notify-Message: Setting timeout for 9260 1204156800 1204147540 evolution-alarm-notify-Message: Wed Feb 27 21:00:00 2008 evolution-alarm-notify-Message: Wed Feb 27 18:25:40 2008 (evolution-alarm-notify:5553): libecal-WARNING **: e-cal.c:1033: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2) Não foi possível abrir o arquivo desktop /home/firenoitans/Área de Trabalho/gnome-terminal.desktop para o lançador do painel: Arquivo ou diretório inexistente (evolution-alarm-notify:5553): libecal-WARNING **: e-cal.c:1033: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2) (evolution-alarm-notify:5553): libecal-WARNING **: e-cal.c:1033: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2) PID TTY TIME CMD (evolution-alarm-notify:5553): libecal-WARNING **: e-cal.c:1033: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2) -------------------------------------------------- Traceback (most recent call last):
+ Trace 190669
from deskbar.ui.DeskbarApplet import DeskbarApplet
from deskbar.ui.CuemiacWindowController import CuemiacWindowController
from deskbar.ui.preferences.DeskbarPreferences import DeskbarPreferences
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 478337 ***