Bug 21796 - Update request: Evolution
Summary: Update request: Evolution
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-01 08:27 CEST by aguador
Modified: 2017-10-04 20:10 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description aguador 2017-10-01 08:27:16 CEST
Evolution-data-server was updated to 3.26 a week ago, but Evolution cannot be run as it has not been updated from 3.22.
Marja Van Waes 2017-10-01 14:21:49 CEST

CC: (none) => marja11
Assignee: bugsquad => gnome

Comment 1 aguador 2017-10-01 23:37:16 CEST
Just downloaded the last updates on evolution (thank you) and evolution-data-server, but evo will still not start. I have notifications waiting that give an error on boot up and attempts to start evo fail with a simple "unable to start application".

I did restart after the update to make sure.

If it matters, I am running evo in E21, but have never had problems with it in E.
Comment 2 Robert Fox 2017-10-02 17:52:16 CEST
[rfox@foxmain ~]$ evolution
evolution: error while loading shared libraries: libevolution-shell.so: cannot open shared object file: No such file or directory

[rfox@foxmain ~]$ rpm -qa | grep evolution
evolution-data-server-tests-3.26.1-1.mga7
evolution-data-server-3.26.1-1.mga7
lib64evolution-data-server-gir1.2-3.26.1-1.mga7
evolution-3.26.1-1.mga7
evolution-debuginfo-3.22.1-1.mga6

I can confirm this issue since recent Cauldron updates

CC: (none) => rfox

Comment 3 aguador 2017-10-02 20:37:41 CEST
Latest update seems to have done the trick. Evo starts and all components seem to function without problem, although I have not tested e-mail very much as yet. Thanks for getting us back up and running with Evo. There are some nice new touches.
Comment 4 Jani Välimaa 2017-10-04 20:10:52 CEST
Closing as FIXED.

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


Note You need to log in before you can comment on or make changes to this bug.