Evince produces segmentation fault
up vote
2
down vote
favorite
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?
I entered
~/.local/share/gnome-shell
to check what is in the extensions folder - it happens, there is no such folder (no folders at all), 'ls' in /gnome-shell produces:
application_state
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.
Running 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.
https://i.imgur.com/Q8zHcV0.jpg
Running 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:
Older: https://i.imgur.com/ri3oAmP.jpg
Newer: https://i.imgur.com/tsQ3dSY.jpg
evince segmentation-fault
asked Oct 16 at 18:04
Smoksul
134
|
show 10 more comments
up vote
2
down vote
favorite
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?
I entered
~/.local/share/gnome-shell
to check what is in the extensions folder - it happens, there is no such folder (no folders at all), 'ls' in /gnome-shell produces:
application_state
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.
Running 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.
https://i.imgur.com/Q8zHcV0.jpg
Running 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:
Older: https://i.imgur.com/ri3oAmP.jpg
Newer: https://i.imgur.com/tsQ3dSY.jpg
evince segmentation-fault
asked Oct 16 at 18:04
Smoksul
134
Welcome! It would be very difficult to diagnose without some additional details, such as: the Ubuntu version, evince package version, the complete output prior to the crash, and any other possibly useful details.
– valiano
Oct 16 at 18:21
Sadly, the only output I get is just the "Segmentation fault (core dumped)" no other information is provided. I'm using Ubuntu 18.04.1 LTS, evince package is the one got from the Software Center (I believe the one I am getting also through apt-get is the same) - version 3.30.0. Can't really give any more details just as they are not present.
– Smoksul
Oct 16 at 18:34
Evince 3.30.0 doesn't appear to be the default version used in 18.04.1... oh, it's a snap package. Have you installed any fonts? Themes? Interminal, typeevinceand edit your question to include the error messages.
– heynnema
Oct 16 at 19:24
As I said, the only error message (through terminal, running evince in GUI produces nothing at all) is the Segmentation Fault. Regarding the fonts I doubt I have installed some of them manually. I installed TeXMaker as well as MikTex, these could bring in some more fonts; also I have edited a certain xkb file to change the layout of my keyboard slightly.
– Smoksul
Oct 16 at 19:32
Older laptop? How much RAM? Where/how did you install the extra fonts? Have you tried removing them to see if it impacts Evince? Have you installed any GNOME extensions? Report back to @heynnema
– heynnema
Oct 16 at 19:34
|
show 10 more comments
up vote
2
down vote
favorite
up vote
2
down vote
favorite
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?
I entered
~/.local/share/gnome-shell
to check what is in the extensions folder - it happens, there is no such folder (no folders at all), 'ls' in /gnome-shell produces:
application_state
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.
Running 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.
https://i.imgur.com/Q8zHcV0.jpg
Running 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:
Older: https://i.imgur.com/ri3oAmP.jpg
Newer: https://i.imgur.com/tsQ3dSY.jpg
evince segmentation-fault
asked Oct 16 at 18:04
Smoksul
134
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?
I entered
~/.local/share/gnome-shell
to check what is in the extensions folder - it happens, there is no such folder (no folders at all), 'ls' in /gnome-shell produces:
application_state
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.
Running 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.
https://i.imgur.com/Q8zHcV0.jpg
Running 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:
Older: https://i.imgur.com/ri3oAmP.jpg
Newer: https://i.imgur.com/tsQ3dSY.jpg
evince segmentation-fault
evince segmentation-fault
asked Oct 16 at 18:04
Smoksul
134
asked Oct 16 at 18:04
Smoksul
134
edited Oct 20 at 7:08
asked Oct 16 at 18:04
Smoksul
134
asked Oct 16 at 18:04
Smoksul
134
asked Oct 16 at 18:04
Smoksul
134
134
Welcome! It would be very difficult to diagnose without some additional details, such as: the Ubuntu version, evince package version, the complete output prior to the crash, and any other possibly useful details.
– valiano
Oct 16 at 18:21
Sadly, the only output I get is just the "Segmentation fault (core dumped)" no other information is provided. I'm using Ubuntu 18.04.1 LTS, evince package is the one got from the Software Center (I believe the one I am getting also through apt-get is the same) - version 3.30.0. Can't really give any more details just as they are not present.
– Smoksul
Oct 16 at 18:34
Evince 3.30.0 doesn't appear to be the default version used in 18.04.1... oh, it's a snap package. Have you installed any fonts? Themes? Interminal, typeevinceand edit your question to include the error messages.
– heynnema
Oct 16 at 19:24
As I said, the only error message (through terminal, running evince in GUI produces nothing at all) is the Segmentation Fault. Regarding the fonts I doubt I have installed some of them manually. I installed TeXMaker as well as MikTex, these could bring in some more fonts; also I have edited a certain xkb file to change the layout of my keyboard slightly.
– Smoksul
Oct 16 at 19:32
Older laptop? How much RAM? Where/how did you install the extra fonts? Have you tried removing them to see if it impacts Evince? Have you installed any GNOME extensions? Report back to @heynnema
– heynnema
Oct 16 at 19:34
|
show 10 more comments
Welcome! It would be very difficult to diagnose without some additional details, such as: the Ubuntu version, evince package version, the complete output prior to the crash, and any other possibly useful details.
– valiano
Oct 16 at 18:21
Sadly, the only output I get is just the "Segmentation fault (core dumped)" no other information is provided. I'm using Ubuntu 18.04.1 LTS, evince package is the one got from the Software Center (I believe the one I am getting also through apt-get is the same) - version 3.30.0. Can't really give any more details just as they are not present.
– Smoksul
Oct 16 at 18:34
Evince 3.30.0 doesn't appear to be the default version used in 18.04.1... oh, it's a snap package. Have you installed any fonts? Themes? Interminal, typeevinceand edit your question to include the error messages.
– heynnema
Oct 16 at 19:24
As I said, the only error message (through terminal, running evince in GUI produces nothing at all) is the Segmentation Fault. Regarding the fonts I doubt I have installed some of them manually. I installed TeXMaker as well as MikTex, these could bring in some more fonts; also I have edited a certain xkb file to change the layout of my keyboard slightly.
– Smoksul
Oct 16 at 19:32
Older laptop? How much RAM? Where/how did you install the extra fonts? Have you tried removing them to see if it impacts Evince? Have you installed any GNOME extensions? Report back to @heynnema
– heynnema
Oct 16 at 19:34
Welcome! It would be very difficult to diagnose without some additional details, such as: the Ubuntu version, evince package version, the complete output prior to the crash, and any other possibly useful details.
– valiano
Oct 16 at 18:21
Welcome! It would be very difficult to diagnose without some additional details, such as: the Ubuntu version, evince package version, the complete output prior to the crash, and any other possibly useful details.
– valiano
Oct 16 at 18:21
Sadly, the only output I get is just the "Segmentation fault (core dumped)" no other information is provided. I'm using Ubuntu 18.04.1 LTS, evince package is the one got from the Software Center (I believe the one I am getting also through apt-get is the same) - version 3.30.0. Can't really give any more details just as they are not present.
– Smoksul
Oct 16 at 18:34
Sadly, the only output I get is just the "Segmentation fault (core dumped)" no other information is provided. I'm using Ubuntu 18.04.1 LTS, evince package is the one got from the Software Center (I believe the one I am getting also through apt-get is the same) - version 3.30.0. Can't really give any more details just as they are not present.
– Smoksul
Oct 16 at 18:34
Evince 3.30.0 doesn't appear to be the default version used in 18.04.1... oh, it's a snap package. Have you installed any fonts? Themes? In
terminal, type evince and edit your question to include the error messages.– heynnema
Oct 16 at 19:24
Evince 3.30.0 doesn't appear to be the default version used in 18.04.1... oh, it's a snap package. Have you installed any fonts? Themes? In
terminal, type evince and edit your question to include the error messages.– heynnema
Oct 16 at 19:24
As I said, the only error message (through terminal, running evince in GUI produces nothing at all) is the Segmentation Fault. Regarding the fonts I doubt I have installed some of them manually. I installed TeXMaker as well as MikTex, these could bring in some more fonts; also I have edited a certain xkb file to change the layout of my keyboard slightly.
– Smoksul
Oct 16 at 19:32
As I said, the only error message (through terminal, running evince in GUI produces nothing at all) is the Segmentation Fault. Regarding the fonts I doubt I have installed some of them manually. I installed TeXMaker as well as MikTex, these could bring in some more fonts; also I have edited a certain xkb file to change the layout of my keyboard slightly.
– Smoksul
Oct 16 at 19:32
Older laptop? How much RAM? Where/how did you install the extra fonts? Have you tried removing them to see if it impacts Evince? Have you installed any GNOME extensions? Report back to @heynnema
– heynnema
Oct 16 at 19:34
Older laptop? How much RAM? Where/how did you install the extra fonts? Have you tried removing them to see if it impacts Evince? Have you installed any GNOME extensions? Report back to @heynnema
– heynnema
Oct 16 at 19:34
|
show 10 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
From the comments...
We've got a malloc error with Evince.
Step #1:
To check the file system on your Ubuntu partition for errors...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Step #2:
Boot to the Ubuntu Live DVD/USB and run memtest for one complete pass.
Update #1:
Memtest showed a memory failure, as I suspected. Remove or replace some RAM sticks.
answered Oct 17 at 7:06
heynnema
17.8k22053
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
1
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. Seesudo lshw -c memoryfor a clue. Report back to @heynnema
– heynnema
Oct 20 at 14:16
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1084347%2fevince-produces-segmentation-fault%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
From the comments...
We've got a malloc error with Evince.
Step #1:
To check the file system on your Ubuntu partition for errors...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Step #2:
Boot to the Ubuntu Live DVD/USB and run memtest for one complete pass.
Update #1:
Memtest showed a memory failure, as I suspected. Remove or replace some RAM sticks.
answered Oct 17 at 7:06
heynnema
17.8k22053
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
1
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. Seesudo lshw -c memoryfor a clue. Report back to @heynnema
– heynnema
Oct 20 at 14:16
add a comment |
up vote
0
down vote
accepted
From the comments...
We've got a malloc error with Evince.
Step #1:
To check the file system on your Ubuntu partition for errors...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Step #2:
Boot to the Ubuntu Live DVD/USB and run memtest for one complete pass.
Update #1:
Memtest showed a memory failure, as I suspected. Remove or replace some RAM sticks.
answered Oct 17 at 7:06
heynnema
17.8k22053
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
1
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. Seesudo lshw -c memoryfor a clue. Report back to @heynnema
– heynnema
Oct 20 at 14:16
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
From the comments...
We've got a malloc error with Evince.
Step #1:
To check the file system on your Ubuntu partition for errors...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Step #2:
Boot to the Ubuntu Live DVD/USB and run memtest for one complete pass.
Update #1:
Memtest showed a memory failure, as I suspected. Remove or replace some RAM sticks.
answered Oct 17 at 7:06
heynnema
17.8k22053
From the comments...
We've got a malloc error with Evince.
Step #1:
To check the file system on your Ubuntu partition for errors...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Step #2:
Boot to the Ubuntu Live DVD/USB and run memtest for one complete pass.
Update #1:
Memtest showed a memory failure, as I suspected. Remove or replace some RAM sticks.
answered Oct 17 at 7:06
heynnema
17.8k22053
edited Oct 20 at 13:19
answered Oct 17 at 7:06
heynnema
17.8k22053
answered Oct 17 at 7:06
heynnema
17.8k22053
answered Oct 17 at 7:06
heynnema
17.8k22053
17.8k22053
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
1
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. Seesudo lshw -c memoryfor a clue. Report back to @heynnema
– heynnema
Oct 20 at 14:16
add a comment |
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
1
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. Seesudo lshw -c memoryfor a clue. Report back to @heynnema
– heynnema
Oct 20 at 14:16
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
Sorry for replying so late, I was very busy last days, the post got updated accordingly to your suggestions
– Smoksul
Oct 20 at 7:09
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
@Smoksul as I had suspected, bad RAM. Remove or replace a RAM stick.
– heynnema
Oct 20 at 13:19
1
1
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
that's quite surprising. I am running all kind of software without any issues on Windows, on Fedora, never had a bluescreen nor anything of that sort. I will try to maybe remove some of the RAM sticks and look for the bad one (provided it's not a malfunction of them being combined) in the future. Could it lead to more damage if I did not remove/replace the RAM stick soon (if it is actually malfucntioning)?
– Smoksul
Oct 20 at 14:11
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. See
sudo lshw -c memory for a clue. Report back to @heynnema– heynnema
Oct 20 at 14:16
If you've mixed and matched different RAM sticks, that could certainly lead to a memtest error. If you have 4 RAM sticks, you can remove 2 paired sticks, rerun memtest, and when you get a pass, retry evince. Memory normally needs to get RAM added/removed in pairs, for memory interleaving performance reasons. Hence the suggestion to remove 2 RAM sticks... but you have to look closely to make sure to remove the proper pairs. Don't wait to repair this. See
sudo lshw -c memory for a clue. Report back to @heynnema– heynnema
Oct 20 at 14:16
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1084347%2fevince-produces-segmentation-fault%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome! It would be very difficult to diagnose without some additional details, such as: the Ubuntu version, evince package version, the complete output prior to the crash, and any other possibly useful details.
– valiano
Oct 16 at 18:21
Sadly, the only output I get is just the "Segmentation fault (core dumped)" no other information is provided. I'm using Ubuntu 18.04.1 LTS, evince package is the one got from the Software Center (I believe the one I am getting also through apt-get is the same) - version 3.30.0. Can't really give any more details just as they are not present.
– Smoksul
Oct 16 at 18:34
Evince 3.30.0 doesn't appear to be the default version used in 18.04.1... oh, it's a snap package. Have you installed any fonts? Themes? In
terminal, typeevinceand edit your question to include the error messages.– heynnema
Oct 16 at 19:24
As I said, the only error message (through terminal, running evince in GUI produces nothing at all) is the Segmentation Fault. Regarding the fonts I doubt I have installed some of them manually. I installed TeXMaker as well as MikTex, these could bring in some more fonts; also I have edited a certain xkb file to change the layout of my keyboard slightly.
– Smoksul
Oct 16 at 19:32
Older laptop? How much RAM? Where/how did you install the extra fonts? Have you tried removing them to see if it impacts Evince? Have you installed any GNOME extensions? Report back to @heynnema
– heynnema
Oct 16 at 19:34