Bug 102952 - Internal Error (0): Call to Object where the object was type 5, not the expected type 8
Summary: Internal Error (0): Call to Object where the object was type 5, not the expec...
Status: RESOLVED NOTOURBUG
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-23 11:45 UTC by max.schlemmer
Modified: 2017-09-27 18:02 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
PDF file which fails to compile in pdflatex (11.35 KB, application/pdf)
2017-09-23 11:45 UTC, max.schlemmer
Details

Description max.schlemmer 2017-09-23 11:45:49 UTC
Created attachment 134447 [details]
PDF file which fails to compile in pdflatex

I am using poppler/pdflatex on Arch Linux, after the upgrade from poppler 0.57.0 to version 0.59.0 I am getting the following error:

[11 <./chain.pdf
Internal Error (0): Call to Object where the object was type 5, not the expected type 8(edited)

Removing all the pdf files from the tex file compiles the document normally, also when downgrading back to poppler 0.57.0. I attached one included pdf file, which raises an error. The pdf file was created by gnuplot version 4.6 patchlevel 6.
Comment 1 Albert Astals Cid 2017-09-23 14:15:04 UTC
I don't understand, is this a pdflatex error? If so open a bug in their bugtracker and not in poppler

Also i see a pdf file you have attached, how would a pdf file "fail to compile", isn't the pdf the result of the compilation?
Comment 2 max.schlemmer 2017-09-23 14:46:14 UTC
I thought this might be a poppler issue, since poppler is called from texlive and only poppler has received an update. But I now see, that arch has modified version of texlive, in this new release: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/texlive-bin&id=9d93b64063f7d98568d4f029453c7edf5597a7b4 (I only read the commit message before)

I will first write a bug report in the arch bugzilla. 

The issue is, that the compilation of the pdf document fails, when the attached pdf file is included, that is why I thought it might be a poppler issue.
Comment 3 jmscaramal 2017-09-23 14:53:31 UTC
I can confirm such bug. Same here... Arch Linux and after poppler being updated pdflatex crashes... downgrading poppler to 57.0.1 solves the issue...
Comment 4 Albert Astals Cid 2017-09-23 15:22:22 UTC
Well if you think it's a bug in Poppler you should at least give us a way to reproduce the bug, no? Otherwise how are we supposed to investigate?
Comment 5 Vagner Clementino 2017-09-23 21:21:37 UTC
Same error here. It was solved downgrading poppler to 58.0.1 and downgrading texlive-bin to texlive-bin-2017.44590-2. The problem can be reproduce with a latex file with a includepdf command.
Comment 6 surreal pie 2017-09-23 21:34:27 UTC
Same. Downgrading poppler, poppler-glib, and texlive-bin fixed it
Comment 7 Jason Crain 2017-09-23 22:37:51 UTC
This still isn't an actionable bug report since no one has given any information beyond "pdflatex doesn't work on Arch".

I'm betting it's related to the recent Object API changes though, since texlive uses poppler's private API. In which case, the correct place to handle this is in the Arch bug tracker, so they can fix their library dependencies, and in texlive bugtracker, so they either switch to using a supported API or update their use of the private API.
Comment 8 Lizao Li 2017-09-25 04:49:23 UTC
I can confirm this problem on ArchLinux. I was able to fix this by keeping the new poppler package but install texlive directly from the official website rather than the Arch repo. So it is highly likely that this is an ArchLinux problem.
Comment 9 max.schlemmer 2017-09-27 18:02:57 UTC
The problem has been resolved, it seems, that it was an error in the texlive-bin package. Sorry for the inconvenience.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.