Feisty's Evolution unstabil?
Sven
sven.lug-dorsten at gmx.de
Die Aug 14 20:14:13 BST 2007
Hi Leute!
ich wollte mal nachfragen obs noch mehr gibt wie mich, Evolution
schmiert seit Feisty regelmässig ab. Die .xsession-errors sieht so aus:
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
seahorse nautilus module initialized
evolution-alarm-notify-Message: Setting timeout for 17898 1187136000
1187118102
evolution-alarm-notify-Message: Wed Aug 15 02:00:00 2007
evolution-alarm-notify-Message: Tue Aug 14 21:01:42 2007
Fenstermanager-Warnung: Thema »« konnte nicht geladen werden: Es konnte
keine gültige Datei für das Thema »« gefunden werden
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:1875 (alarm_queue_init)
alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Wed Aug 15
02:00:00 2007
alarm-notify.c:220 (load_calendars) - Loading Calendar
file:///home/sven-tek/.evolution/calendar/local/system
alarm-notify.c:456 (alarm_notify_add_calendar)
file:///home/sven-tek/.evolution/calendar/local/system - Calendar Open
Async... 0x80bf240
alarm-notify.c:220 (load_calendars) - Loading Calendar
webcal://ruhr.pm.org/feeds/ical/ankuendigungen.ics
alarm-notify.c:456 (alarm_notify_add_calendar)
webcal://ruhr.pm.org/feeds/ical/ankuendigungen.ics - Calendar Open
Async... 0x80d0f10
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:///
alarm-notify.c:456 (alarm_notify_add_calendar) contacts:/// - Calendar
Open Async... 0x80cf280
alarm-notify.c:220 (load_calendars) - Loading Calendar
file:///home/sven-tek/.evolution/tasks/local/system
alarm-notify.c:456 (alarm_notify_add_calendar)
file:///home/sven-tek/.evolution/tasks/local/system - Calendar Open
Async... 0x80d6d20
alarm-notify.c:220 (load_calendars) - Loading Calendar
file:///home/sven-tek/.evolution/memos/local/system
alarm-notify.c:456 (alarm_notify_add_calendar)
file:///home/sven-tek/.evolution/memos/local/system - Calendar Open
Async... 0x80d8060
alarm-notify.c:393 (cal_opened_cb)
webcal://ruhr.pm.org/feeds/ical/ankuendigungen.ics - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:393 (cal_opened_cb)
file:///home/sven-tek/.evolution/calendar/local/system - Calendar Status
0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:393 (cal_opened_cb)
file:///home/sven-tek/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80f8308: Received at thread
b4d51b90
alarm-queue.c:2008 (alarm
(gnome-panel:5867): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
to allocate widget with width -39 and height 21
_queue_add_async) - 0x80d0f10
alarm-queue.c:560 (load_alarms_for_today) - From Tue Aug 14 02:00:00
2007
to Tue Aug 14 02:00:00 2007
alarm-queue.c:497 (load_alarms)
alarm-notify.c:393 (cal_opened_cb)
file:///home/sven-tek/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80d4f78: Received at thread
b4d51b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80bf240
alarm-notify.c:337 (alarm_msgport_replied) - 0x80f8308: Replied to GUI
thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Aug 14 02:00:00
2007
to Tue Aug 14 02:00:00 2007
alarm-queue.c:497 (load_alarms)
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80d4020: Received at thread
b4d51b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d6d20
alarm-notify.c:337 (alarm_msgport_replied) - 0x80d4f78: Replied to GUI
thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Aug 14 02:00:00
2007
to Tue Aug 14 02:00:00 2007
alarm-queue.c:497 (load_alarms)
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80daab0: Received at thread
b4d51b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d8060
alarm-notify.c:337 (alarm_msgport_replied) - 0x80d4020: Replied to GUI
thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Aug 14 02:00:00
2007
to Tue Aug 14 02:00:00 2007
alarm-queue.c:497 (load_alarms)
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80d8488: Received at thread
b4d51b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80cf280
alarm-notify.c:337 (alarm_msgport_replied) - 0x80daab0: Replied to GUI
thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Aug 14 02:00:00
2007
to Tue Aug 14 02:00:00
200Desktop-Datei /usr/local/share/applications/rhythmbox.desktop konnte
nicht für Panel-Starter : geöffnet werdenNo such file or directory
CalDAV Eplugin starting up ...
(evolution-2.10:6098): evolution-mail-WARNING **: ignored this junk
plugin: not enabled or we have already loaded one
(evolution-2.10:6098): e-utils-WARNING **: Plugin 'Bogofilter
Ausschuss-Erweiterung' failed to load hook
'org.gnome.evolution.mail.junk:1.0'
(evolution-2.10:6098): camel-WARNING **: camel_exception_get_id called
with NULL parameter.
(evolution-2.10:6098): camel-WARNING **: camel_exception_get_id called
with NULL parameter.
(evolution-2.10:6098): e-data-server-WARNING **: Could not open
converter for 'unknown-8bit' to 'UTF-8' charset
camel-Message: --
camel-Message: --
CalDAV Eplugin starting up ...
(evolution-2.10:6183): evolution-mail-WARNING **: ignored this junk
plugin: not enabled or we have already loaded one
(evolution-2.10:6183): e-utils-WARNING **: Plugin 'Bogofilter
Ausschuss-Erweiterung' failed to load hook
'org.gnome.evolution.mail.junk:1.0'
(evolution-2.10:6183): camel-WARNING **: camel_exception_get_id called
with NULL parameter.
(evolution-2.10:6183): camel-WARNING **: camel_exception_get_id called
with NULL parameter.
camel-Message: --
checking for valid crashreport now
Es erscheint kein Crashreport-Dialog. Der Fehler scheint nicht
absichtlich repoduzierbar zu sein.
Grüsse, Sven