I've been having a couple problems with kpdf. Both have been going on for some time now; I don't remember exactly when they started, but it could've been when I switched from 13.2 to R14 several months ago. This is on Debian 7.
1. Occasionally it will refuse to render a single page of a multipage PDF (or maybe a couple pages of a very long document), when other viewers render all pages just fine. It's the same pages every time, and there's nothing different about them that I can see -- just a random page in the middle of a document. If I burst the PDF into individual files for each page, it still refuses to render that same page.
2. It "forgets" a page as soon as it's no longer displayed, and has to re-render it to display it again. It's as though Memory Usage is set to Low instead of Normal or Aggressive, but the setting makes no difference. This is very inconvenient in cases where it takes more than a fraction of a second to render a page, which is the case with most of the PDFs I use.
3. One more that's not a new problem, just the way kpdf has always been: It's extremely slow -- something like 3x slower than Adobe Reader, and at least 50% slower than Evince. I'd have switched to one of those long ago, but there are several features of kpdf that I really like.
Is there any chance of getting these things fixed? Thanks.
On Tuesday 23 December 2014 9:11:28 am you wrote:
I've been having a couple problems with kpdf. Both have been going on for some time now; I don't remember exactly when they started, but it could've been when I switched from 13.2 to R14 several months ago. This is on Debian 7.
- Occasionally it will refuse to render a single page of a multipage PDF
(or maybe a couple pages of a very long document), when other viewers render all pages just fine. It's the same pages every time, and there's nothing different about them that I can see -- just a random page in the middle of a document. If I burst the PDF into individual files for each page, it still refuses to render that same page.
- It "forgets" a page as soon as it's no longer displayed, and has to
re-render it to display it again. It's as though Memory Usage is set to Low instead of Normal or Aggressive, but the setting makes no difference. This is very inconvenient in cases where it takes more than a fraction of a second to render a page, which is the case with most of the PDFs I use.
- One more that's not a new problem, just the way kpdf has always been:
It's extremely slow -- something like 3x slower than Adobe Reader, and at least 50% slower than Evince. I'd have switched to one of those long ago, but there are several features of kpdf that I really like.
Is there any chance of getting these things fixed? Thanks.
+1, no solution though other than use what works.
I think kpdf could use some attemtion. Refer to bug #1, I added comments to that bug concerning an issue with kpdf.
kpdf is good for quick views while browsing the web, for working with pdf's at work I view with 'mupdf', and evince to working around bug #1 for my printing pdf needs. Okular is nice but way more depends thasn evince..I could go on and on about pretty DE's taking precedence over applications :-)
On 24 December 2014 at 09:18, Greg Madden gomadtroll@gci.net wrote:
On Tuesday 23 December 2014 9:11:28 am you wrote:
I've been having a couple problems with kpdf.
<snip>
So far kpdf has given me almost no problems. In krusader I hit F3 on a 69M file and it renders within two seconds. Perhaps because my machine is fairly fast, 4x Intel Core i7-4600U CPU @ 2.10GHz with 7861MB RAM.
Robert
Is there any hope of getting these issues addressed? #2 is particularly inconvenient and would be very helpful to have fixed.
On 12/23/2014 10:11 AM, Dan Youngquist wrote:
I've been having a couple problems with kpdf. Both have been going on for some time now; I don't remember exactly when they started, but it could've been when I switched from 13.2 to R14 several months ago. This is on Debian 7.
- Occasionally it will refuse to render a single page of a multipage PDF
(or maybe a couple pages of a very long document), when other viewers render all pages just fine. It's the same pages every time, and there's nothing different about them that I can see -- just a random page in the middle of a document. If I burst the PDF into individual files for each page, it still refuses to render that same page.
- It "forgets" a page as soon as it's no longer displayed, and has to
re-render it to display it again. It's as though Memory Usage is set to Low instead of Normal or Aggressive, but the setting makes no difference. This is very inconvenient in cases where it takes more than a fraction of a second to render a page, which is the case with most of the PDFs I use.
- One more that's not a new problem, just the way kpdf has always been:
It's extremely slow -- something like 3x slower than Adobe Reader, and at least 50% slower than Evince. I'd have switched to one of those long ago, but there are several features of kpdf that I really like.
Is there any chance of getting these things fixed? Thanks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Is there any hope of getting these issues addressed? #2 is particularly inconvenient and would be very helpful to have fixed.
Yes, we'll take a look at them. Have you filed a bug report? If so I'd like to get it added to the next release punch list.
Thanks!
Tim
On 01/17/2015 02:29 PM, Timothy Pearson wrote:
Yes, we'll take a look at them. Have you filed a bug report? If so I'd like to get it added to the next release punch list.
Thanks, Tim. Just filed on the (suspected) Memory Usage issue. I'll file the other one a little later, after I find a PDF to use as an example.
On Saturday 17 January 2015 4:38:41 pm you wrote:
On 01/17/2015 02:29 PM, Timothy Pearson wrote:
Yes, we'll take a look at them. Have you filed a bug report? If so I'd like to get it added to the next release punch list.
Thanks, Tim. Just filed on the (suspected) Memory Usage issue. I'll file the other one a little later, after I find a PDF to use as an example.
I have some pdfs you can test with. Mine are of construciton drawings, multi-page. I can only email them, no cloud stuff here.
FYI, I view large amounts of drawings, for the pdf's I use 'mupdf', it is a very fast , keyboard controlled, viewer. Viewer only though, no printing or saving to file
On Saturday 17 January 2015, Dan Youngquist wrote:
...
- It "forgets" a page as soon as it's no longer displayed, and has to
re-render it to display it again. It's as though Memory Usage is set to Low instead of Normal or Aggressive, but the setting makes no difference. This is very inconvenient in cases where it takes more than a fraction of a second to render a page, which is the case with most of the PDFs I use.
I can verify that the default behavior is to redraw pages on scroll, but not some of the other details for R14.0 on Wheezy. Changing to "Aggressive" memory usage speeds up page display and thumbnails are remembered. It's still possible to see a X page flash if you scroll very quickly but the overall speed in the default and aggressive setting is good. It's about as fast or faster than Okular. This is with a 2008 Thinkpad x61s.
For fun, I fired up an Etch VM. A small pdf rendered instantly, but a larger one had the Xs, but was still speedy. That's basically what I remembered.
On Saturday 17 January 2015, Dan Youngquist wrote:
- It "forgets" a page as soon as it's no longer displayed, and has to
re-render it to display it again. It's as though Memory Usage is set to Low instead of Normal or Aggressive, but the setting makes no difference. This is very inconvenient in cases where it takes more than a fraction of a second to render a page, which is the case with most of the PDFs I use.
I tested this on TDE 13.2 and saw that the default behavior is to start the new page with a scaled thumbnail and then to render. You have to scroll quickly to see this.
-
Dan Youngquist -
Greg Madden -
Robert Peters -
Timothy Pearson -
Will Hill