I hit this before already from time to time on various CiteSeerX pages, and I think it doesn't always occur - when I tried to reload the page, the problem also disappeared. Just now, it does not disappear on pressing F5 or hitting Enter in the location bar again, so maybe there's a chance you can reproduce it too. Steps to (maybe) reproduce: 1. Go to http://citeseerx.ist.psu.edu/viewdoc/summary;jsessionid=B2E72BD7BE16ED2D9041C628354D1EC3?doi=10.1.1.16.700 2. On the rather top right-hand side, note the "DOWNLOAD: PDF" text, where "PDF" is a link. Although being displayed correctly, the link does not transform the mouse arrow into the "hand" cursor, and does not show the standard link options (including "Save link as...", which is unfortunate as I have to open the HTML source in that case). On other CiteSeerX pages, the same "PDF" link worked flawlessly, maybe it will also work on the mentioned page when you try to reproduce it. Browsing through countless papers makes it show up sometimes, though. I would guess that their CSS is sloppy too (the same site also had problems with showing the search field before - that works again now), but maybe the issue is not solely in their responsibility. Please try and see if you can reproduce that bug. Thanks!
Er. a) of course, you can take that ";jsessionid=(...)" out b) and of course, directly after doing that and trying again (with or without session id), it worked again. Hrm.
*** Bug 177094 has been marked as a duplicate of this bug. ***
*** Bug 175256 has been marked as a duplicate of this bug. ***
I'm not able to reproduce this bug (using current trunk) on the sites listed on this bug and on the two report I've just marked as dup (comment #2 and comment #3). Someone is able to reproduce using KDE 4.3 or trunk?
*** Bug 177304 has been marked as a duplicate of this bug. ***
Using 4.3, I can't reproduce at the moment. Then again, I couldn't reliably reproduce even when I opened the but. If https://bugs.kde.org/show_bug.cgi?id=175256 is indeed the same bug and its instructions managed to bring up the bug reliably, maybe one should try out those instead of the link above.
Closing based on comment #4 and #6