Bug 164635 - In Konsole, sometimes need to hit enter twice to see result of command
Summary: In Konsole, sometimes need to hit enter twice to see result of command
Status: RESOLVED LATER
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-22 02:22 UTC by Julian King
Modified: 2011-03-03 21:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julian King 2008-06-22 02:22:51 UTC
Version:            (using KDE 4.0.5)
Installed from:    SuSE RPMs
OS:                Linux

I am running openSuse 11.0, with the nvidia drivers, and compiz fusion enabled (with usecompositewrapper=true, although the problem appears regardless).

If I open up a konsole window, the first few commands process fine. After
perhaps a few screens worth of text, the bug appears, which then happens every
time.

Suppose I type "ls" in the prompt (it doesn't matter if the directory has 1 or
50 files), then hit enter.
I get a new prompt on the next line, with no ls output. The "ls" command is
carried onto the new prompt. If I then hit "enter" again, I get the output of
ls.

Similarly, if I type "whoami" in the prompt, then hit enter, I get a new prompt
with "whoami" out the front. If I hit enter again, I get the the output of
whoami.

Sometimes, instead of getting a prompt with the command repeated, I just get a
blank newline. If I hit enter then I get the results of the command.

This is very weird.

I have tried updating to the latest version of the KDE programs (including
konsole) from the KDE YAST repository, but the effect is the same.

This bug has been posted at https://bugzilla.novell.com/show_bug.cgi?id=402439, with a request for me to cite that bug report.

Thanks guys.
Comment 1 Robert Knight 2008-06-22 23:27:47 UTC
This may be an NVidia-specific issue related to Bug #163176
Comment 2 Robert Knight 2008-06-28 01:07:49 UTC
Do you get strange scrolling effects in other applications, such as Okular?
Comment 3 Robert Russell 2008-12-18 03:27:44 UTC
I have the same problem. Just installed Kubuntu today with KDE 4.1. I then switched to the Gnome desktop, set up Compiz and now I'm seeing the same issue. I found a workaround for this problem: I went to Settings -> Edit Current Profile then on the Scrolling tab I disabled scrollback. Seems to eliminate the double-enter problem. Hope this helps.
Comment 4 Robert Russell 2008-12-18 06:20:19 UTC
Turning off the scrollback doesn't completely fix it. I also see the problem if I use shift with the left or right arrow keys to change Konsole tabs. It seem like it's just not repainting. Setting Visual Effects to None in Gnome (which I believe turns off Compiz) fixes it. I do think this is related to <a href="http://bugs.kde.org/show_bug.cgi?id=163176>Bug 163176</a> but the comments there seem to indicate it's not just NVidia.
Comment 5 M. Thomas Frederiksen 2009-01-30 05:07:39 UTC
I have the same problem.  It does seem to relate to repainting, as I have problems in just about every Qt app that scrolls.  I've seen trouble in Dolphin, Kid3, KeePassX, and others.  It even seems to effect firefox, which scrolls fine, but the widgets such as check-boxes and drop downs are often only half drawn.
Comment 6 Joakim Rosqvist 2009-08-31 10:52:36 UTC
I can confirm this or a very similar problem.
Konsole version 2.2.2   
KDE 4.2.2
Ubuntu 9.04.  
NVIDIA GLX Module  180.44
Running in Gnome
Desktop effects enabled  (no problem otherwise)
Steps to reproduce:
1) Start konsole
2) run /bin/ls /usr/bin
3) Repeat step 2
4) After about 3 runs of ls, the output freezes halfway thru
5) I then click the titlebar of the konsole window and try to drag it
6) As soon as the window starts moving, the missing lines are output

It seems to me the graphics commands have been sent, but got stuck in a buffer, waiting to get flushed.
Comment 7 Kurt Hindenburg 2011-03-03 21:47:40 UTC
From the comments this appears to be a graphics driver issue.