Version: unspecified (using KDE 4.4.5) OS: Linux This only concerns inverse search with personnal command. If I use the predefined Kile for example, everything is working well. Notes. 1. the same if I use konqueror and then open DVI in tabs. 2. I am using the same home directory with two computers. The first on Ubuntu Lucid Lynx and the second on Ubtuntu Maverick. Thus if something changed between the two versions, my bug could not be relevant ! Reproducible: Didn't try Steps to Reproduce: 1. Launch konqueror using a button in KDE or a compiz personnal shortcut. ("konqueror" as command in Compiz's shortcut system) 2. Open a DVI with okular or in a new tab 3. Set the inverse search command to a personnal script (in my case, it is a pytjon script which launches gvim) 4. Try SHIFT-left button to initiate the inverse search. Actual Results: Nothing happens. Note : in order to isolate the bug, I made my script launch a video, beep and write in a file before to launch gvim. Thus I'm sure if my script was actually launched or not. However, if Okular or konqueror were first launched in a konsole (open a konsole and type "konqueror"), the actual result is that my script is launched correctly. In any case, if I set the inverse search's command to the predefined Kile, it works. Expected Results: The inverse search in Okular should works even with a personnal command, even if Okular was not launched in a konsole. I tried to put "konsole -e konqueror" as command for my Compiz's shortcut. In this case, the inverse search still don't work. When I open the konsole using the compiz shortcut and then type "konqueror" in the konsole, the inverse search works. So it seems that I have to write by hand "konqueror" in a konsole in order to have my inverse search working with personnal commands.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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!
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!