Version: (using KDE 3.5.9) OS: Linux Installed from: SuSE RPMs for some pdf files I get in the xterm the following window: **** Warning: format of the startxref line in this file is invalid. **** This file had errors that were repaired or ignored. **** The file was produced by: **** >>>> FujiXerox Co.,Ltd. RST3.0 <<<< **** Please notify the author of the software that produced this **** file that it does not conform to Adobe's published PDF **** specification. In order to have success contacting the vendor it would be good to see in the message on what the value for this startxref is in my document and why you think this is wrong. Just with this text the vendor will claim that your software does a wrong check.
Which application give you this output?
This is not kpdf, this is kghostview
I get this if I open some pdfs as preview in konquerer
Could you please check whether or not you get this with Okular?
No answer for years.
yeap, no answer for years... I replied 2009 and you 3 years later. Do you think after 3 years I still have these pdfs? I honor all the work you guys do and give you a big thank you for that. But if you don't have the time to follow up on bug reports on a timely manner then close bugzilla and don't pretent that someone is taking care of bugs. Reporting bugs for KDE and do testing is a waste of time.
(In reply to p from comment #6) > yeap, no answer for years... I replied 2009 and you 3 years later. Do you > think after 3 years I still have these pdfs? Maybe we should change the bug template and ask people to *always* attach all the files needed to reproduce an issue. But this bug has a different history (see below). (note: this is mostly for people coming up here in the future) > But if you don't have the time to > follow up on bug reports on a timely manner then close bugzilla and don't > pretent that someone is taking care of bugs. Reporting bugs for KDE and do > testing is a waste of time. Please check the history of the bug: https://bugs.kde.org/show_bug.cgi?id=175485 It was originally reported against konqueror, then moved to kpdf, and the (then) maintainer promptly moved it to kghostview, as the output you reported in the bug description refers to that program. IIRC at that point, kghostview was mostly unmaintained already. Fast forward to 2012, when the remaining kghostview bugs have been assigned back to Okular, as the official "successor" of kghostview and other programs (even if Okular does not share kghostview code, but took kghostview role), and the bug triager asked for some feedback again. So it's a quite specific case, but I wouldn't say that there have been no reaction on the bug from the maintainers of Okular (and generally from maintained programs).