FS#50413 - [evolution] creates segmentation fault
Attached to Project:
Arch Linux
Opened by Michael Dressel (mdrslmr) - Tuesday, 16 August 2016, 11:09 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 26 October 2016, 08:45 GMT
Opened by Michael Dressel (mdrslmr) - Tuesday, 16 August 2016, 11:09 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 26 October 2016, 08:45 GMT
|
Details
Description:
evolution creates segmentation fault $ evolution openjdk version "1.8.0_102" OpenJDK Runtime Environment (build 1.8.0_102-b14) OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode) Segmentation fault (core dumped) Additional info: I made at most two upgrades after evolution worked properly. I tried to find the packages listed with ldd /usr/binevolution and upgraded within the last week: glibc (2.23-5 -> 2.24-1) libcups (2.1.4-1 -> 2.1.4-2) libcdio (0.93-3 -> 0.93-4) libcap-ng (0.7.7-1 -> 0.7.8-1) lib32-glibc (2.23-5 -> 2.24-1) glibc (2.24-1 -> 2.24-2) lib32-glibc (2.24-1 -> 2.24-2) The log file shows: evolution[4889]: segfault at 760 ip 0000000000000760 sp 00007ffed1c5da48 error 14 in evolution[400000+7000] Steps to reproduce: Unfortunately I cannot downgrade since I cleaned my package cache. |
This task depends upon
evolution-data-server 3.20.5-1
evolution 3.20.5-1
The difference between packages in the backup and the current version
can be found in the attached file pack-diff.
I tried using evolution, glibc (and dependent packages) form the
backup version in the current version but I still get the segmentation fault.
I also attached a stack trace from running evolution inside gdb: evo-bt.txt
I tried both kernels lts and ARCH with the same result.
I also tried removing .config/evolution and .local/share/evolution,
still segmentation fault.
evo-bt.txt (4 KiB)
So I dd the backup to the normal installation and start from there over again.
Since no one else seams to have the problem, this task may be closed.
Your backtrace indicates a module is opened from webkitgtk3, segfault occurs at unknown location when init is called.
The home directories are on different partitions and I tried a user with his home directory under afs as well as a locale user.
I think the plugin or something similar could be the source of the problem only that it must be something that does not get
re-installed. Because I did a re-installation of almost all packages.