Version: 2.7.4 (using KDE 4.7.4) OS: Linux Double clicking in the konsole window doesn't select any text at all. Double click in every other application functions as expected. Reproducible: Always Steps to Reproduce: Double click on any text in the konsole window Actual Results: No text or characters are selected Expected Results: Highlight the selected text OS: Linux (x86_64) release 3.0.0-15-generic Compiler: gcc
Apparently only affects konsole sessions that were saved from a previous session
Thanks for reporting. (In reply to comment #1) > Apparently only affects konsole sessions that were saved from a previous > session However, I have never had or noticed such problem. I just checked it again using konsole-2.7.4 and konsole-2.8.999. Both worked fine. Could you please provide more information? Or, could you please check it using a new user account?
Apparently the universe is conspiring against me. I am unable to reproduce despite having reproduced it multiple times this morning.
Thanks for your quick feedback. I will leave this report open for a few days before closing it as 'WORKSFORME'. If the problem happens again and you find some pattern for reproducing, please add your findings here.
I see this bug in 4.9.1 out of nowhere. What the heck? Also, it is true that it happens only with konsole opened from saved session. A new konsole window does not have this behavior.
(In reply to comment #5) > I see this bug in 4.9.1 out of nowhere. What the heck? Also, it is true that > it happens only with konsole opened from saved session. A new konsole window > does not have this behavior. Since you are using KDE SC 4.9.1, I wonder whether you are experiencing a different bug. Is that double click just fails to select text, or konsole freezes after double click? See bug 306338.
No freezes. If I open a new konsole window (which mean a new konsole process), it works fine there. I am using Gentoo btw.
logout and its gone!
This bug is really annoying. I upgraded to 4.9.2 and the problem is back. And this time, no amount of logging out and logging back in has helped me to get the text selection working again. This is a show-stopper folks.
(In reply to comment #9) > This bug is really annoying. I upgraded to 4.9.2 and the problem is back. > And this time, no amount of logging out and logging back in has helped me to > get the text selection working again. This is a show-stopper folks. There is little change in konsole between 4.9.1 and 4.9.2 . So I really don't know how "the problem is back in 4.9.2 ". No matter how annoying it is, so far only two users have encountered it and the original reporter can't reproduce it anymore. Such rare and random problem can hardly be seen as "show stopper". I really need more information on how to reproduce it in the highest possibility. On maybe I should come up with a patch which adds debugging information to see where the thing goes wrong, if you would like try it and I also have the time. BTW, I'm using Gentoo, too.
(In reply to comment #10) > (In reply to comment #9) > > This bug is really annoying. I upgraded to 4.9.2 and the problem is back. > > And this time, no amount of logging out and logging back in has helped me to > > get the text selection working again. This is a show-stopper folks. > > There is little change in konsole between 4.9.1 and 4.9.2 . So I really > don't know how "the problem is back in 4.9.2 ". > > No matter how annoying it is, so far only two users have encountered it and > the original reporter can't reproduce it anymore. Such rare and random > problem can hardly be seen as "show stopper". > > I really need more information on how to reproduce it in the highest > possibility. On maybe I should come up with a patch which adds debugging > information to see where the thing goes wrong, if you would like try it and > I also have the time. > > BTW, I'm using Gentoo, too. It is a sort of show stopper for a person for whom it happens because it renders one of the fundamental features useless. Selection with double click is very fundamental for me. What I meant by "back in 4.9.2" is that I first encountered it when I upgraded to 4.9.0 or 4.9.1, logged out and logged back in. Then, I logged out and logged back in, and it was gone. Never saw it again. Now, in 4.9.2, same thing happened. Upgrade, logout, log back in. No double click. Log out, log in. Still no double click selecting text. Repeat. No success. There is another bug where the konsole freezes when double clicking but for me konsole keeps working fine. Its just that I can't select text with double click. konsole has been going downhill for whatever reasons with upgrades. Before the last logout (running version 4.9.1), I noticed it was eating 1.1G of RSS (resident memory) and it was constantly eating 8-10% of one core. I had many windows (12) and many tabs (8 per window) but I have had the same tabs since 4.1 days. I have no idea what has happened to konsole development. It used to be a good application.
(In reply to comment #11) > It is a sort of show stopper for a person for whom it happens because it > renders one of the fundamental features useless. Selection with double click > is very fundamental for me. I have said, *no matter* how annoying it is, a problem only happening to two(or one) users can hardly be called as "show stopper". It does not work to use strong words for your most-hated bug to increase the chance of it being fixed. The proper way is try to provide more information so that others can reproduce it. > konsole has been going downhill for whatever reasons with upgrades. Before > the last logout (running version 4.9.1), I noticed it was eating 1.1G of RSS > (resident memory) and it was constantly eating 8-10% of one core. I had many > windows (12) and many tabs (8 per window) but I have had the same tabs since > 4.1 days. I have no idea what has happened to konsole development. It used > to be a good application. OK, when that huge memory consumption happens again, take a screenshot of the detailed memory usage shown in ksysguard and open a new bug report. In that way you have a convincing proof. I don't want to argue with you. Here are some links that can give you better *overview* of the konsole development. https://bugs.kde.org/buglist.cgi?f1=cf_versionfixedin&list_id=243352&o1=equals&query_format=advanced&bug_status=RESOLVED&v1=4.8&product=konsole https://bugs.kde.org/buglist.cgi?f1=cf_versionfixedin&list_id=243352&o1=equals&query_format=advanced&bug_status=RESOLVED&v1=4.9.0&product=konsole https://bugs.kde.org/reports.cgi?product=konsole&output=show_chart&datasets=NEW&datasets=ASSIGNED&datasets=REOPENED&datasets=UNCONFIRMED&banner=1 https://bugs.kde.org/weekly-bug-summary.cgi?tops=70&days=450 ( check the line for konsole ) But sure you have succeeded in de-motivating me. I don't think I'm willing to write a debug patch in the short time. PS: I'm removing myself from the CC list, but don't interpret it as "I don't care about this report anymore". I have subscribed to the konsole-devel ML as I should, so I still receive all the messages. I'm just tired of receiving two (actually, three) mails for each message.
I must say that it was not my intention to hurt or demotivate you. May be I was just venting because I love KDE too much and it hurts me to see regressions like this. I have come to expect high standards. I have never had issues with konsole, even during early releases of KDE 4. This is a hard bug for sure. But we will need to diagnose and fix it. Let me know how I can help.
Also, can we please reopen the bug?
Holy cow! I just discovered that its not specific to konsole. I can't double click and select text in knotes/kwrite either. I don't know how to proceed now.
(In reply to comment #13) > This is a hard bug for sure. But we will need to diagnose and fix it. Let me > know how I can help. I currently have no clear idea. I still suspect it is a slight different variant of the problem reflected in bug 306338. And by the way, that bug is actually not an issue of konsole itself. It is just that the implementation of web shortcuts support in konsole make it very easy to notice/reveal the unlying problem of some kded module. I can come up with a patch which adds more debugging message to reveal where the thing goes wrong, if this issue is still reliably reproducible for you after rebooting. (In reply to comment #14) > Also, can we please reopen the bug? (In reply to comment #15) > Holy cow! I just discovered that its not specific to konsole. I can't double > click and select text in knotes/kwrite either. I don't know how to proceed > now. I don't mind reopening this report, but comment #15 really makes me hesitating. Something goes wrong with you X server? I don't know how to proceed, either.
I can confirm that this is an issue with KDE applications in general. gnome-terminal and all other applications (libreoffice, firefox, gvim etc.) are working fine. Something in QT or kdelibs is busted in my setup. My X server is a VNC server.
(In reply to comment #17) > I can confirm that this is an issue with KDE applications in general. > gnome-terminal and all other applications (libreoffice, firefox, gvim etc.) > are working fine. Something in QT or kdelibs is busted in my setup. My X > server is a VNC server. hmm, then it is becoming mystery to me. I almost never use VNC. Considering that you use a special setup (VNC) and the problem happens to many KDE applications, I really suspect you are encountering a problem quite different from the one from the original reporter. Please try to do more diagnostic yourself, then open a new report against the appropriate product (kde or kdelibs, but clearly it does fit into this konsole product), if you are confident the problem lies in KDE.
I wanted to come in here and give an update on what the reason for this behavior was. Apparently, gnome-settings-daemon has some collision with KDE. If gnome-settings-daemon is running, KDE will have tough time selecting text with double click. Once I removed gnome-settings-daemon from the picture, the issue is reolved.