FS#57981 - [evolution] doesn't start

Attached to Project: Arch Linux
Opened by Ralf Mardorf (Ralf) - Monday, 26 March 2018, 21:29 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 27 March 2018, 11:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

[evolution] doesn't start

After installing all available updates, including evolution, it doesn't start anymore.

[rocketmouse@archlinux ~]$ grep 2018-03-26 /var/log/pacman.log | grep evo
[2018-03-26 22:52] [ALPM] upgraded evolution-data-server (3.26.5-1 -> 3.28.0+6+g501f51b1c-1)
[2018-03-26 22:52] [ALPM] upgraded evolution (3.26.5-1 -> 3.28.0+8+gf3e2c90d24-1)
[2018-03-26 22:52] [ALPM] upgraded evolution-bogofilter (3.26.5-1 -> 3.28.0+8+gf3e2c90d24-1)
[2018-03-26 22:52] [ALPM] upgraded evolution-spamassassin (3.26.5-1 -> 3.28.0+8+gf3e2c90d24-1)
[rocketmouse@archlinux ~]$ pkill -9 evo
[rocketmouse@archlinux ~]$ evolution
Gtk-Message: 23:18:15.614: GtkDialog mapped without a transient parent. This is discouraged.
[rocketmouse@archlinux ~]$

Only a dialog Window opens: "Cannot start Evolution. Another Evolution instance may be unresponsive. System error: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources5: Timeout was reached"
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Tuesday, 27 March 2018, 11:24 GMT
Reason for closing:  Not a bug
Comment by Tim Ruffing (realorrandom) - Tuesday, 27 March 2018, 09:37 GMT
I had the same issue. The problem is actually with evolution-data-server.

> journalctl -fp err
[...]
systemd[22111]: evolution-source-registry.service: Failed to execute command: No such file or directory
systemd[22111]: evolution-source-registry.service: Failed at step EXEC spawning /usr/lib/evolution-data-server/evolution-source-registry: No such file or directory
systemd[1345]: Failed to start Evolution source registry.

The problem is the path: The file is installed in /usr/lib/evolution-source-registry instead of /usr/lib/evolution-data-server/evolution-source-registry but when I checked the path is actually correct in the new (?) unit file.

> systemctl --user daemon-reload
> systemctl --user restart evolution-source-registry.service

solved the problem job for me. (I guess a reboot should work as well.)
Comment by Ralf Mardorf (Ralf) - Tuesday, 27 March 2018, 10:31 GMT
Just this minute, already before I got notified about your comment, I wanted to report that logging out and starting a new user session didn't, but a shutdown and restarting the computer did solve the issue for me.
Comment by Tim Ruffing (realorrandom) - Tuesday, 27 March 2018, 10:45 GMT
Yes, starting a new session didn't work for me either.
(I don't know why. I assumed that logging out and in restarts the user systemd instance but apparently something is wrong with this assumption...)

Comment by Jan Alexander Steffens (heftig) - Tuesday, 27 March 2018, 11:24 GMT
Yes, the files were moved during the upgrade and this was caused by your user systemds not getting reloaded.

Loading...