[SOLVED] On printing to Boomaga, "Error on 318", then segfault
l0ddej0kk0 opened this issue · comments
Hi,
on LinuxMint 19.1 Mate, Boomaga 1.0.0-1, printing a PDF to Boomaga pops up its GUI with a message "Error on 318 [ OK ]". Clicking OK closes that and Boomaga as well.
Meanwhile, the CUPS error_log only shows
W [27/Jun/2019:19:46:32 +0200] [Job 52] [Boomaga] QIODevice::read (QFile, \"/proc/2670/environ\"): device not open
All other lines pertaining to Boomaga are no Errors or Warnings.
The libpoppler packages are v.0.62.0-2ubuntu2.8.
If called from the Shell, boomaga complains during printing like this:
$ boomaga qt5ct: using qt5ct plugin qt5ct: D-Bus global menu: no Failed to create for shader cache (No such file or directory)---disabling. poppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablepoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref table"Error on 318" Segmentation fault (core dumped)
Interestingly, if i print just 1 page, it's
"Error on 319"
all other details the same as above.
best regards,
-- l0ddej0kk0
Hi,
just found the new 3.0 version and the error seems to be gone.
My mistake for looking in the wrong places.
Many thanks and keep up the good work on this great Software!
best regards,
-- l0ddej0kk0