Recently I have installed Ubuntu 18.04.1 on my laptop (Dell Precision M4700, 16GB RAM), it's quite pure at the moment. The problem is that Evince 3.30.0 produces segmentation fault (core dumped) on launch. It is happening since the system was installed and purging and reinstalling (through Synaptic as well) did not help. Any ideas how to make it work?
to check what is in the extensions folder - it happens, there is no such folder (no folders at all), 'ls' in /gnome-shell produces:
Swapping to another (freshly made) user and running Evince there produces the same result.
Running sudo debsums -s provided output:
debsums: changed file /usr/share/X11/xkb/symbols/pl (from xkb-data package)
which is a file I have edited manually. Having it replaced by the original file (and deleting that new user I made) I got some more output from running evince in terminal:
Attempting to read the recently used resources file at '/home/january/.local/share/recently-used.xbel', but the parser failed: Failed to open file “/home/january/.local/share/recently-used.xbel”: Permission denied. Segmentation fault (core dumped)
This file had permission to read and write for my user, but had no permissions for my group. I edited these permission to provide my group with read an write and now it's just
Segmentation fault like before when I run Evince.
I purged Evince again also with Synaptic to install version
3.28.2-1 (through Synaptic). First of all I encountered an error when I used GUI
Apply button when trying to install Evince again:
E: Unable to correct problems, you have held broken packages. E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies E: Unable to lock the download directory.
The error did not appear though when I selected
Edit->Apply Marked Changes. Reinstallation still produces Seg.fault when running Evince.
sudo evince I get:
No protocol specified Unable to init server: Could not connect: Connection refused Cannot parse arguments: Cannot open display:
As things happen out of random sometimes I managed to get an error from evince in GUI (splash would you call it?), sorry for it being quite big I wanted to include all possible data.
fsck in recovery root command line yielded no errors.
I did memtest a couple of days ago and then I did one after doing the
fsck, receiving this result: