Version: 4.6.5 (using KDE 4.6.5) OS: Linux Dear maintainers, this is more a question than a bugreport. Since some time I get the following behavior: 1. I click on a link (to a pdf, avi, wmf or similar). The link is called, but it is not opened (for example a pdf-file). But when I call this link again, which is shown in the URL-bar, then the pdf (avi, wmv, whatever) is opened and will be shown. Is this a security feature and wanted, or is this a bug? Reproducible: Always Steps to Reproduce: see above Expected Results: The pdf file should be opened at once, when it is cliecked on the link (pdf is standing for any file)
4.6.5 is rather old. The current version of KDE is 4.8.0 so any testing the maintainers do will be based on that and will probably not match whatever you experience. I personally cannot duplicate this issue. Were you clicking on a PDF file from a web page or while browsing your own file system ? If you were clicking on links from a web page, then the linke should be opened with the appropriate application without a need for a second click. BTW, what happens if you wait a little while for after clicking on the link first ? Also which browsing engine are you using ? You can find out by doing Settings->Configure Konqueror->General and looking at the "Default web browser engine" selection.
Hi Dawit, yes, thieversion is rather old, it is just Debian. However, this issue is showing now for several versions. I cannot remember, when it appeared first, but at least since 3 versions it is shown. I am clicking on a pdf link on a webfile/website. Waiting does not help. The problem appeared not only on PDF files, this was just an example. Other files show the same behaviour, but not all. Maybe it is plugin related. So I first thought, it might be a security option, that people, when they click a link, just do not start the link and have to check it twice. The rendering engine I am using is webkit. I switched fron khtml to webkit, but it has nothing to do with it, as it happens on both. Besides, this behaviour is not hardware specific, because on my netbook, which is 32-bit/debian-testing and on my notebook, which is 64-bit/debian-testing this problem appears on both. Dawit, the problem is not such important for me, but I wanted to mention it, and wanted to know, if this might be a feature not a bug. If someone will look at it, I will be happy, but maybe this is already fixed in newer versions. As I said, I can live with it, but I found it worth to mention it. Thank you very much for your response. Please fell free to ask, if I can help somehow. Have a nice weekend! Hans
(In reply to comment #2) > Hi Dawit, > > yes, thieversion is rather old, it is just Debian. However, this issue is > showing now for several versions. I cannot remember, when it appeared first, > but at least since 3 versions it is shown. > > I am clicking on a pdf link on a webfile/website. Waiting does not help. The > problem appeared not only on PDF files, this was just an example. Other > files show the same behaviour, but not all. Maybe it is plugin related. > > So I first thought, it might be a security option, that people, when they > click a link, just do not start the link and have to check it twice. > > The rendering engine I am using is webkit. I switched fron khtml to webkit, > but it has nothing to do with it, as it happens on both. > > Besides, this behaviour is not hardware specific, because on my netbook, > which is 32-bit/debian-testing and on my notebook, which is > 64-bit/debian-testing this problem appears on both. > > Dawit, the problem is not such important for me, but I wanted to mention it, > and wanted to know, if this might be a feature not a bug. Well all I can say for sure is that it is not a feature. At least it is not something we put in there on purpose. And since you tried two separate machines as well as both browser engines, I am at a loss as to what could be the issue. You might want ot check your .xsession-errors file to see if there are an error messages that might be the cause of this. I most certainly am not able to reproduce it or else it would have been addressed already.
have you been able to update to a more recent version of KDE ? I am curious if you still see this issue with more recent versions of KDE, v4.8.0 or higher for example.
This is probably a case of the Bug 325942 I just reported. (I reported it separately to make the apparent cause more clear.)
More precisely a case of Bug 325942 in conjunction with Bug 325940.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!