Evolution fails to start
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
Please confirm there isn't an existing open bug report
- I have searched open bugs for this issue
Summary
Evolution fails to start and presents a timeout to dataServer error:
Mai 06 17:09:39 t495 systemd[1346]: Starting evolution-source-registry.service - Evolution source registry...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has begun execution.
░░
░░ The job identifier is 671.
Mai 06 17:09:39 t495 evolution-sourc[4355]: cannot register existing type 'CamelM365Settings'
Mai 06 17:09:39 t495 evolution-sourc[4355]: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
Mai 06 17:09:39 t495 evolution-sourc[4355]: cannot add private field to invalid (non-instantiatable) type '<invalid>'
Mai 06 17:09:39 t495 evolution-sourc[4355]: g_once_init_leave: assertion 'result != 0' failed
Mai 06 17:10:09 t495 systemd[1346]: evolution-source-registry.service: start operation timed out. Terminating.
Mai 06 17:10:20 t495 systemd[1346]: evolution-source-registry.service: State 'stop-sigterm' timed out. Killing.
Mai 06 17:10:20 t495 systemd[1346]: evolution-source-registry.service: Killing process 4355 (evolution-sourc) with signal SIGKILL.
Mai 06 17:10:20 t495 systemd[1346]: evolution-source-registry.service: Main process exited, code=killed, status=9/KILL
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit UNIT has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 9.
Mai 06 17:10:20 t495 systemd[1346]: evolution-source-registry.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT has entered the 'failed' state with result 'timeout'.
Mai 06 17:10:20 t495 systemd[1346]: Failed to start evolution-source-registry.service - Evolution source registry.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 671 and the job result is failed.
Steps to reproduce
- Boot into solus gnome 46 with kernel 6.8.8-288.current
- Start evolution
- The error comes up
Expected result
Evolution should start
Actual result
The error comes up
Environment
- Is system up to date?
Repo
Shannon (stable)
Desktop Environment
GNOME
System details
System:
Host: t495 Kernel: 6.8.8-288.current arch: x86_64 bits: 64
Desktop: GNOME v: 46.1 Distro: Solus 4.5 resilience
Machine:
Type: Laptop System: LENOVO product: 20NJCTO1WW v: ThinkPad T495
serial: <superuser required>
Mobo: LENOVO model: 20NJCTO1WW serial: <superuser required> UEFI: LENOVO
v: R12ET43W(1.13 ) date: 08/15/2019
Battery:
ID-1: BAT0 charge: 43.5 Wh (100.0%) condition: 43.5/50.5 Wh (86.2%)
CPU:
Info: quad core AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx [MT MCP]
speed (MHz): avg: 1677 min/max: 1400/2300
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-2: Chicony ThinkPad T490 Webcam driver: uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
gpu: amdgpu resolution: 1: 3440x1440 2: 1920x1080~60Hz
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6 renderer: AMD
Radeon Vega 10 Graphics (radeonsi raven LLVM 16.0.6 DRM 3.57
6.8.8-288.current)
Network:
Device-1: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Device-3: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Drives:
Local Storage: total: 476.94 GiB used: 432.26 GiB (90.6%)
Info:
Memory: total: 24 GiB note: est. available: 21.4 GiB used: 3.16 GiB (14.8%)
Processes: 298 Uptime: 16m Shell: fish inxi: 3.3.34
Other comments
It happened after sync week 17, and sync week 18 didn't fix the issue unfortunately.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on Solus GNOME and inspect evolution-source-registry.service logs, especially the CamelM365Settings registration errors. Compare package changes around sync weeks 17 and 18 to identify what introduced the failure. Done means Evolution starts without the dataServer timeout.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100