Bug 11700

Summary:	Evolution won't start, no messages on the command line
Product:	Mageia	Reporter:	Norm Proffitt <normproffitt>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal
Version:	2
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Norm Proffitt 2013-11-18 20:12:31 CET

Description of problem:
  On two different fully up to date (as of Nov 18, 2013) Mageia 2 systems (I know support goes away in a few days) evolution refuses to start.  When started from the command line no window is created and no messages are displayed.  The command just hangs until I press Ctrl-C.  I've waited as long as 10 minutes or more before pressing Ctrl-C and still nothing happens.  Also, the system is very idle (CPU, I/O, and network) during the wait.

The only hint I can find are messages in the .xsession-errors file saying:

(evolution-alarm-notify:2909): libecal-WARNING **: e_cal_client_new: Failed to run calendar factory: Error calling StartServiceByName for org.gnome.evolution.dataserver.Calendar1: Timeout was reached.


Version-Release number of selected component (if applicable):  
  Evolution 3.4.1-1
  Evolution Data Server 3.4.4-1.1


How reproducible:
  Fails on both systems each time I try to start it.


Steps to Reproduce:
1. Open a command prompt
2. Type the command evolution
3. Press enter


Reproducible: 

Steps to Reproduce:

Comment 1 Manuel Hiebel 2013-11-23 16:18:49 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 2 Norm Proffitt 2013-11-23 21:11:32 CET

While I understand why this bug is being closed down I don't have good feelings about how it was done.  I opened this problem on Nov 18 while Mageia 2 was still under support.  It was not looked at until the release reached EOL.  I realize that everyone is busy but I feel as if this problem was consciously ignored knowing that the release would reach EOL and the bug could be "swept under the rug".

Unfortunately due to timing upgrading to Mageia 3 is not an option right now so I guess I'm going to have to live with out my preferred email client for a while.

Comment 3 Manuel Hiebel 2013-11-24 00:44:03 CET

Yes sorry, there was two new bugs after the first reminder, in this one is part of them.

Could be something like this https://bugs.mageia.org/show_bug.cgi?id=11654

Comment 4 Norm Proffitt 2013-11-25 20:26:39 CET

Thanks for the pointer.  The problem is something with the timezone package update process.  The solution in https://bugs.mageia.org/show_bug.cgi?id=11559 is to downgrade timezone package and then re-update it.