Version: 0.56 (using KDE KDE 3.5.6) Installed from: Unspecified Linux OS: Linux when opening a file ,kpdf puts a big X over the screen what even crosses its own window boundary, also when you push PageDown or scroll fast, its very annoying. and even disturbs other windows :( with a big "X" i mean a gray line from the left upper corner to the right lower corner and from the right upper corner to the left lower corner...I hope this will be corrected soon :) success If you need screenshots,please let me know by email Greetings from Thailand Gudy http://picasaweb.google.com/jazzcommunication
this happends in Kubuntu from version 6.06 until 7.04, installed from life cd,and upgrades
What is your video driver?
Video Driver: Vendor : Via Technology Renderer: Mesa DRI Unichrome(KM400) 20060710 x86/MMX +3DNow!+/SSE OpenGL version: 1.3 Mesa 6.5.2 Kernel Module: via is this enough? or need more details? :)
IT should be enough to say that look like a duplicate of bug 138076, as it should be the same video driver (via). *** This bug has been marked as a duplicate of 138076 ***
On 30 Apr 2007 17:44:26 -0000, Pino Toscano <toscano.pino@tiscali.it> wrote: [bugs.kde.org quoted mail] okay, :) do you think its in the video driver???.... its typical only in kpdf and it happends when data is being read from the harddisk and kpdf is waiting for the data..... this is how far my first diagnostic can go.. hopefully it gives you a hint in what kind of direction we must search. Of course I'm willing to help out solving this problem. If you like me to test for you, no problem at all :) <br><br><div><span class="gmail_quote">On 30 Apr 2007 17:44:26 -0000, <b class="gmail_sendername">Pino Toscano</b> <<a href="mailto:toscano.pino@tiscali.it">toscano.pino@tiscali.it</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex"> ------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=144883">http://bugs.kde.org/show_bug.cgi?id=144883</a><br>toscano.pino tiscali it changed:<br><br> What |Removed |Added<br>----------------------------------------------------------------------------<br> Status|UNCONFIRMED |RESOLVED <br> Resolution| |DUPLICATE<br><br><br><br>------- Additional Comments From toscano.pino tiscali it 2007-04-30 19:44 -------<br>IT should be enough to say that look like a duplicate of bug 138076, as it should be the same video driver (via). <br><br>*** This bug has been marked as a duplicate of 138076 ***<br></blockquote></div>okay, :) do you think its in the video driver???.... its typical only in kpdf and it happends when data is being read from the harddisk and kpdf is waiting for the data..... <br>this is how far my first diagnostic can go.. hopefully it gives you a hint in what kind of direction we must search. Of course I'm willing to help out solving this problem.<br>If you like me to test for you, no problem at all :) <br><br>
Yep, I think it's the video driver, and no idea why it should be a problem in KPDF only, even if we just draw lines on the page. Anyway, please avoid sending HTML mails, as they makes your comment almost unreadable (open the bug page directly to see yourself).
okay , I see...I was replying via gmail ...:( sorry..I'm only brain storming now, to generate more options where so search, because I have seen many bug reports about that kpdf is crashing and I "think,guess, there can be a possibility(I say it carefully because I'm also not sure,so i hope you also see it that way)" maybe its because of this effect when the "X" goes even outside the shared video memory, not real unthinkable... an idea is maybe let blanc pages blanc don't put any cross on it or something like that and see if the number of bug reports becomes less... :) thank you already for your time and effort
Mr Pino Toscano, can you please explain to me what you mean with this citate in bug 130076 "and using the cvs version of the driver itself fixed the issue.", tell me please what I must do....what is the CVS version and where to get it?... :)