Version: (using KDE 4.0.98)
Installed from: Ubuntu Packages
If I use Page Up or Page Down to move while composing a new message, only the top (or bottom) line is refreshed during scrolling; the rest of the message remains static until the cursor reaches its new position. This is not the case when scrubbing with the scrollbar or moving with the arrow keys; in both of those cases, scrolling is smooth.
I can confirm that with kmail 1.1.0 from KDE4.1RC1 Kubuntu packages.
Yeah, can confirm it too, no idea what causes this.
*** Bug 175436 has been marked as a duplicate of this bug. ***
I'm having this problem on nvidia, maybe this is related?
*** Bug 180614 has been marked as a duplicate of this bug. ***
I can confirm this too, here on KDE-4.2.0's KMail running on top of KDE-3.5.10 on Mandriva Linux Cooker. I have a Radeon HD 2600 card and am using the radeonhd open-source drivers of my distribution. My KMail composer font is Bitstream Vera Sans Mono 12.
I can confirm this too. My description of this is:
- create a new email a couple of pages long.
- if you hit page-down you
1) see the caret move line by line down the window until it reaches the bottom (the email text is static). Takes about 0.5 seconds.
2) the text on the bottom line then starts change rapidly for a second; presumably displaying one of the below lines at a time (the rest of the email text is still static). Takes about 2 seconds.
3) the email then suddenly jumps up one full page.
Similar behaviour happens for page-up. This behaviour makes composing long messages very cumbersome as the whole page scroll event takes about 3 seconds instead of being instant.
I have smooth scrolling turned off in kontact.
Forgot to say, scrolling with arrow up/down has the same weird behaviour of the
top/bottom line updating as you scroll while the rest of the message is static;
when you stop holding an arrow-key, the text instantly scrolls to where you'd
Using the mouse wheel or click/dragging the scroll bar does not have this
*** Bug 186008 has been marked as a duplicate of this bug. ***
This seems to be fixed now, I can't reproduce it any longer.
So it could have been everything from Qt to graphic driver.
I can confirm this being fixed after upgrading to Qt 4.5.