If I am in the middle/beginning of a message, I can keep pressing space to go to the end of the message and the next space key displays the next message. This is a very convenient feature. However, if I use mouse to scroll all the way down to the end of the message and press space key, nothing happens. It does not advance to the next message. Space should simply advance to the next message even in this case. I am using a mixture of Debian stable + testing (Squeeze + Lenny), knode version 4.4.11, KDE 4.8.4, $uname -a Linux kusumanchi.mae.cornell.edu 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux Reproducible: Always Steps to Reproduce: 1. open a message in knode. The message should be long enough so that a vertical scroll bar appears on the right side of the reading panel. 2. In the reading panel, scroll to the bottom of the message using mouse's scroll wheel. 3. Press space key. Actual Results: Nothing happens Expected Results: Pressing space key when already at the end of the message, should advance to the next unread message. Initially I reported the problem at http://lists.debian.org/debian-user/2012/08/msg00763.html .
In the original bug report, I wrote "I am using a mixture of Debian stable + testing (Squeeze + Lenny), knode version 4.4.11, KDE 4.8.4, " It should have been "I am using a mixture of Debian stable + testing (Squeeze + Wheezy), knode version 4.4.11, KDE 4.8.4, " The version numbers are correct, but I got confused with the current release name of Debian testing.
Well, it is not a very good idea to use KDE applications that do not have the same version. You should upgrade your Knode to 4.8.4 as well.
Well, those are the versions of kde, knode available in Debian Wheezy currently. Do you see the problem disappearing in later versions of knode? What versions did you test it on? I would appreciate if you can share success/failure reproducibility of this bug with other versions.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.