FS#18154 - [apvlv] segfaults upon opening some documents

Attached to Project: Community Packages
Opened by Jay Tanzman (jt512) - Thursday, 04 February 2010, 00:02 GMT
Last edited by Stefan Husmann (stefanhusmann) - Saturday, 06 February 2010, 17:37 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Stefan Husmann (stefanhusmann)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Apvlv segfaults when opening some, but not all, documents. Sometimes the following error is reported:

(apvlv:11326): Gtk-CRITICAL **: gtk_image_set_from_pixbuf: assertion `GTK_IS_IMAGE (image)' failed

The problem seems to occur only in documents containing graphics (but, again, not all such documents), so I wonder if the problem might be related the recent upgrade to libpng 1.4.0-2 and libjpeg 8-1. Downgrading apvlv to version 0.0.8.1-1 solves.

Additional info:
* package version(s)
apvlv 0.0.9.2-1
apvlv 0.0.9-1

Steps to reproduce:
1. Open the attached file in apvlv
   statin-letter-lancet.pdf (69 KiB)
This task depends upon

Closed by  Stefan Husmann (stefanhusmann)
Saturday, 06 February 2010, 17:37 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Cannot be reproduced.
Comment by Stefan Husmann (stefanhusmann) - Thursday, 04 February 2010, 02:03 GMT
Cannot confirm, the document you gave opens fine here. But there are no graphics in it, maybe you wanted to upload another file?

What DE or WM do you use?
Comment by Jay Tanzman (jt512) - Thursday, 04 February 2010, 02:06 GMT
No. That one segfaults for me. Try other documents. I get segfaults on about half of documents that include anything other than text. But documents that do segfault, do so 100% of the time.

Is your system up to date on libjpeg and libpng?
Comment by Stefan Husmann (stefanhusmann) - Thursday, 04 February 2010, 02:38 GMT
Sorry I edited the massage above. And sure, I am up to date.
Comment by Stefan Husmann (stefanhusmann) - Thursday, 04 February 2010, 02:39 GMT
Another question: how do you generate your documents and your graphics? Do they work with other pdf viewers?
Comment by Jay Tanzman (jt512) - Thursday, 04 February 2010, 02:55 GMT
That document was just downloaded from the web. I do have a document that I generated with pdflatex that includes a jpg, which apvlv can open.
Comment by Jay Tanzman (jt512) - Thursday, 04 February 2010, 03:09 GMT
I take back what I said about it segfaulting consistently on some documents. In fact, I can't predict when it will segfault and when it won't.

I just got these messages trying to open a document.

(apvlv:23482): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkImage'

(apvlv:23482): Gtk-CRITICAL **: gtk_image_set_from_pixbuf: assertion `GTK_IS_IMAGE (image)' failed
Segmentation fault

That's the first time I've seen that warning.
Comment by Jay Tanzman (jt512) - Thursday, 04 February 2010, 03:11 GMT
Here's something else I just noticed. Once it segfaults on a document, it becomes much more likely to segfault on subsequent documents. And, conversely, once it opens a document successfully, it is much more likely to open subsequent documents successfully.
Comment by Thomas Dziedzic (tomd123) - Thursday, 04 February 2010, 17:22 GMT
apvlv-0.0.9.3 just came out. I marked the package out of date.
I took a look at the changes and I couldn't find anything related to this.
I think reporting this upstream would be more appropriate.
Don't forget to include backtraces and the pdf that causes the crashes when you report upstream.

Link to apvlv's bug tracker:
http://code.google.com/p/apvlv/issues/list
Comment by Stefan Husmann (stefanhusmann) - Friday, 05 February 2010, 00:16 GMT
Sorry, I will not report something I cannot confirm. Why don't you do that?
Comment by Thomas Dziedzic (tomd123) - Saturday, 06 February 2010, 05:01 GMT
@stefan
Why would I tell you to file a bug upstream you didn't file here?

@jt512
See previous comment if you want to get this fixed since it doesn't seem to be reproducible.
Comment by Ionut Biru (wonder) - Saturday, 06 February 2010, 17:32 GMT
cannot confirm x86_64

Loading...