Last night I shutdown my workstation properly.
This morning when I booted the system, evolution 2.4.0 (SuSE 10.0 x64) would display and then crash immediately. Logged out of my X session and re-logged in - same behaviour. Same behaviour manifested for a newly created userid as well, eliminating the possibility of some corrupt setting in my regular login.
Refreshed the evolution related RPMs (rpm -h -U --replacepkgs ...) still no go.
Finally, rebooted the system and logged in usign my regular userid and voila evolution works!
To capture some debugging info, I started evolution from the CLI. I see the same initial warning messages in both cases.
Any idea/suggestion what could have gone wrong with the first boot causing the problem is welcome so that I can look for it when it happens next. Went thru /var/log/messages and found a kernel message shown below.
<evolution crashes> $ evolution
(evolution:8840): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:8840): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed </evolution crashes>
<from /var/log/messages> Mar 2 15:08:09 genesis kernel: evolution[7936] trap invalid operand rip:2aaaaca50ee2 rsp:7fffff8c68 f8 error:0 </from /var/log/messages>
<evolution starts up> $ evolution adding hook target 'source'
(evolution:6200): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:6200): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed
(evolution:6200): camel-WARNING **: Could not find key entry for word 'ea651436a4239010vgnvcm10000024f64189': Success
(evolution:6200): camel-WARNING **: Could not find key entry for word '224803d3bca19010vgnvcm10000024f64189': Success
</evolution starts up>
Thanks,
Arun K. Khan wrote:
This morning when I booted the system, evolution 2.4.0 (SuSE 10.0 x64) would display and then crash immediately. Logged out of my X session and re-logged in - same behaviour. Same behaviour manifested for a
...
Last night I shutdown my workstation properly.Any idea/suggestion what could have gone wrong with the first boot
evolution does not exit. when you close the application. Its runs an alarm daemon in the background. That will explain why it worked when you "rebooted"
(sounds funny to talk about rebooting a linux system don't it? :)
to confirm this, .. if this happens again, ps -ax and kill -15 the process.
as to why it happend at all? hmmm, ..........
" much more difficult, that answer is..."
-Erle
On Tue, 2006-03-07 at 14:58 +1100, Erle Pereira wrote:
evolution does not exit. when you close the application. Its runs an alarm daemon in the background. That will explain why it worked when you "rebooted"
(sounds funny to talk about rebooting a linux system don't it? :)
to confirm this, .. if this happens again, ps -ax and kill -15 the process.
As the saying goes ... "You learn something new everyday." Yup, when my X session up, there are 3 evolution daemons a) alarm-notify, b) data-server, and c) exchange-storage.
However, when I terminate my X session these daemons terminate leaving no trace of any evolution related stack in the OS. Therefore I don't think the daemons were the problem because when I created a new user and logged in with that ID, evolution was still crashing.
It has not crashed subsequently. Thx,
-
Arun K. Khan -
Erle Pereira