Bug #1272613 “evince-thumbnailer crashed with SIGSEGV” : Bugs : evince package : Ubuntu

Revision history for this message

Chris Johnston (cjohnston) wrote on 2014-01-25:

#1

Dependencies.txt Edit (7.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (670 bytes, text/plain; charset="utf-8")
KernLog.txt Edit (11.7 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (35.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (843 bytes, text/plain; charset="utf-8")
Registers.txt Edit (765 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (161 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-01-25: Stacktrace.txt

#3

Stacktrace.txt Edit (53.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-01-25: StacktraceSource.txt

#4

StacktraceSource.txt Edit (6.4 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-01-25: StacktraceTop.txt

#5

StacktraceTop.txt Edit (1.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-01-25: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (57.0 KiB, text/plain)

Changed in evince (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2014-02-12:

#7

Thank you for your bug report, is that reproducible on that directory? Can you find what file is creating the issue?

information type:

Private → Public

Revision history for this message

Chris Johnston (cjohnston) wrote on 2014-02-12:

#8

It is reproducible for the directory.. I will work on figuring out the file.

Bug Watch Updater (bug-watch-updater) on 2014-03-09

Changed in evince:
importance:	Unknown → Critical
status:	Unknown → New

Pedro Villavicencio (pedro) on 2014-08-22

Changed in evince (Ubuntu):
status:	New → Triaged

Revision history for this message

Germán Poo-Caamaño (gpoo) wrote on 2014-10-02:

#9

From the bug report in GNOME:

Could you upload the file? According to the trace should be
file:///home/chris/Dropbox/Chris_Documents/stucert-vcc-ipy-0710-ChristopherJohnston.pdf

Revision history for this message

Petar Velkovski (pvelkovski) wrote on 2014-11-25:

#10

Download full text (5.6 KiB)

Any news on fixing this bug?

Can someone guide me with step by step instructions to generating crash report files for this bug as I'm hit by it in the most dreadful way. Browsing my directories containing pdf files (actually pdf books) crashes my computer, resulting in a blank screen, a blinking led light indicationg hard disk activity after which all I can do is press the reset button and restart the computer.

I've been hit by this bug for the first time almost a year ago when I was still using Ubuntu 12.04. At that time the crashes were so bad that i couldn;t even start the computer unless I unplugged the electrical cord since the computer simply refused to boot up again after pressing the power button to turn it off and then pressing the power button to turn it on again.

At that time I was convinced that it might have something to do with:
a) a failing harddrive
b) a failing power supply
c) a failing motherboard

I assumed option a) because I have multiple HD-s installed into my computer. I use one of them specifically for storing ebooks (most of them in pdf format). But then i realised that this crashes appear even during a generation of pdf thumbnails on my main HD - the one that has the operating system and my home directory on that at the time I started having this problem was only a month old. Also I was getting kernel messages about disk i/o errors labeled with date/time that coincided with the crashes. Since I have 4 HD-s in my system and the crashes happened during pdf thumbnail generation for files on each of them, I ruled out this assumption about a failing HD.

Then I moved on to analyzing assumption b). I presume that having installed 4HD's in a system with an older power supply that was already built in the computer case that I bought at the time I bought the parts for my computer(which equals to a very cheap
and mediocre power supply) could be the reason for the crashes. Since the crashes came soon after I installed yet another HD (a fourth one) it sounded reasonable that maybe the weak power supply is the culprit for the crashes. After making multiple tweaks with the HD cables (changind the PATA ports) etc and temporarily disconnection some of the disk I finally decided to purchase a better power supply since I was a bit desperate and since it would have been a cheaper purchase than buying a new motherboard. This didn't work either.

Then while looking for a new motherboard to buy - this is a core2duo system and motherboards compatible with my processor and My DDR2 memory are no longer easy to find I suddenly remembered that I added some pdf related PPA to my system at the time that i started experiencing the crashes. This was almost 3-4 months after I started having the crashes. I uninstalled the PPA and suddenly the system crashes disappeared. Although I still find it unbelievable that a user space program can bring the system to its knees, it seams that this was the exact case!!! After this I decided to be more careful with adding untrusted PPAs. I even got the impression that the PPA package was even tampered with due to the believe in the "mighty uncrushable linux".

All worked fine on my Ubuntu 12.04.5 system un...

Any news on fixing this bug?

Can someone guide me with step by step instructions to generating crash report files for this bug as I'm hit by it in the most dreadful way. Browsing my directories containing pdf files (actually pdf books) crashes my computer, resulting in a blank screen, a blinking led light indicationg hard disk activity after which all I can do is press the reset button and restart the computer.

I've been hit by this bug for the first time almost a year ago when I was still using Ubuntu 12.04. At that time the crashes were so bad that i couldn;t even start the computer unless I unplugged the electrical cord since the computer simply refused to boot up again after pressing the power button to turn it off and then pressing the power button to turn it on again.

At that time I was convinced that it might have something to do with:
a) a failing harddrive
b) a failing  power supply
c) a failing motherboard

I assumed option a) because I have multiple HD-s installed into my computer. I use one of them specifically for storing ebooks (most of them in pdf format). But then i realised that this crashes appear even during a generation of pdf thumbnails on my main HD - the one that has the operating system and my home directory on that at the time I started having this problem was only a month old. Also I was getting kernel messages about disk i/o errors labeled with date/time that coincided with the crashes. Since I have 4 HD-s in my system and the crashes happened during pdf thumbnail generation for files on each of them, I ruled out this assumption about a failing HD.

Then I moved on to analyzing assumption b). I presume that having installed 4HD's in a system with an older power supply that was already built in the computer case that I bought at the time I bought the parts for my computer(which equals to a very cheap 
and mediocre power supply) could be the reason for the crashes. Since the crashes came soon after I installed yet another HD (a fourth one) it sounded reasonable that maybe the weak power supply is the culprit for the crashes. After making multiple tweaks with the HD cables (changind the PATA ports) etc and temporarily disconnection some of the disk I finally decided to purchase a better power supply since I was a bit desperate and since it would have been a cheaper purchase than buying a new motherboard. This didn't work either.

Then while looking for a new motherboard to buy - this is a core2duo system and motherboards compatible with my processor and My DDR2 memory are no longer easy to find I suddenly remembered that I added some pdf related PPA to my system at the time that i started experiencing the crashes. This was almost  3-4 months after I started having the crashes. I uninstalled the PPA and suddenly the system crashes disappeared. Although I still find it unbelievable that a user space program can bring the system to its knees, it seams that this was the exact case!!! After this I decided to be more careful with adding untrusted PPAs. I even got the impression that the PPA package was even tampered with due to the believe in the "mighty uncrushable linux".

All worked fine on my Ubuntu 12.04.5 system until few days ago I finally decided it is time to do the upgrade to 14.04. Yesterday few days after the upgrade, I needed to look for some of the pdf books stored on my other drive. Since I wiped the thumbnail directory from my home drive after the clean installation of Ubuntu 14.04.1 (I have separate / and home partitions) nautilus has to recreate the pdf thumbnails. As I said most of my pdf files are stored on a separate HD. Most of them are e-books stored in multiple directories named by a subject. Some of the directories contain 4 pdf files, some 20, some 100+. Opening some of the directories containing pdf files work. All of the pdf thumbnails are being normally generated. But certain directories are "dangerous" to be opened. The thumbnailer manages to generate a few thumbnails and then my whole system crashes.

Sometimes opening the same directory after the crash works. The thumbnailer manages to generate the rest of the thumbnails. Just before I sat down to write this comment i thought of new type of "test" - copying the "problematic directories" to an external NTFS formated hard drive. The first time I did this, it actually worked. I copied one of the crashy directories to my hd, opened nautilus so that it would generate the thumbnails for the pdf files contasined on the external HD and it workeded. Then I erased that same directory from the internal HD and then copied it back from the external HD. After this operation, nautilus managed to recreate the thumbnails on the internal drive without crashing. But I realized that this will not solve my problem because after my seciond attempt to do it with other directories, MY COMPUTER CRASHED while generating the thumbnails for the pdf files copied and stored on my external hard drive.

Thanks god I finally managed to figure out that the bug is  related to the evince-thumbnailer program from the evince package and not to the libthumbnailer package that i previously thought was used during the generation of the thumbnails and for which google didn't show any bug reports.

Sorry for this long post that lacks any useful debugging information, but please help me help you by instructing me how to generate useful debug files, taking into account that after the crash my computer is not in a usable state. It's not that I can normally use my computer with such a critical bug since I tend to download and read pdf files on my computer all the time and if the problem persists, I guess I'll have to downgrade to ubuntu 12.04 as soon as possible.

Apport retracing service (apport) on 2015-03-27

tags:

added: vivid

Bug Watch Updater (bug-watch-updater) on 2015-10-16

Changed in evince:
status:	New → Invalid

Revision history for this message

Sebastien Bacher (seb128) wrote on 2015-10-27:

#11

that's no an evince issue but a cairo one and there is already bug #1404715 about it so closing the evince side

Changed in evince (Ubuntu):
status:	Triaged → Invalid

Affects		Status	Importance	Assigned to	Milestone
	Evince	Invalid	Critical	gnome-bugs #725984
	evince (Ubuntu)	Invalid	Medium	Unassigned

Ubuntu
evince package

evince-thumbnailer crashed with SIGSEGV

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuevince package

evince-thumbnailer crashed with SIGSEGV

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
evince package