Bug 429024

I've just tried to reproduce this issue but I cannot on Konsole 21.03.70 (from git master).

I see all numbers from 1 to 20 printed.

I'm no longer able to reproduce this issue at this time.

I don't see anything that could be related to this in my update logs since I posted the bug, but for completeness sake, here's what has been updated/installed since yesterday according to dpkg.log: openjdk, mime-support, hicolor-icon-theme, desktop-file-utils, install-info.

Like I said in my first post, I suspect it is some race condition. If I can figure out how to trigger it again I'll post an update.

I suspect a local configuration or font issue. Let us know if it happens again.

(In reply to Justin Zobel from comment #1)
> I've just tried to reproduce this issue but I cannot on Konsole 21.03.70
> (from git master).
> 
> I see all numbers from 1 to 20 printed.

It started occurring again, but the bashrc needs to print more lines for me now (greater than 27 lines).

Can you try again but increase the number of lines to the max your terminal can show at the size it is at startup? Make sure that the for loop is the first thing executed when bash starts, i.e., that there are no other bash profiles or rc's.

Again, it seems to be a race condition because if I put a sleep before the for loop, the bug isn't triggered.

Something I noticed now is that my scroll bar isn't taking the full right side even though there is enough room to display all the lines.(In reply to Nate Graham from comment #3)
> I suspect a local configuration or font issue. Let us know if it happens
> again.

It is still happening intermittently unfortunately.

(In reply to rockybulwinkle from comment #4)
> (In reply to Justin Zobel from comment #1)
> > I've just tried to reproduce this issue but I cannot on Konsole 21.03.70
> > (from git master).
> > 
> > I see all numbers from 1 to 20 printed.
> 
> It started occurring again, but the bashrc needs to print more lines for me
> now (greater than 27 lines).
> 
> Can you try again but increase the number of lines to the max your terminal
> can show at the size it is at startup? Make sure that the for loop is the
> first thing executed when bash starts, i.e., that there are no other bash
> profiles or rc's.
> 
> Again, it seems to be a race condition because if I put a sleep before the
> for loop, the bug isn't triggered.
> 
> Something I noticed now is that my scroll bar isn't taking the full right
> side even though there is enough room to display all the lines.(In reply to
> Nate Graham from comment #3)
> > I suspect a local configuration or font issue. Let us know if it happens
> > again.
> 
> It is still happening intermittently unfortunately.

Sounding really odd. Can you please try with a freshly created user?

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!

(In reply to Justin Zobel from comment #5)
> Sounding really odd. Can you please try with a freshly created user?

I'd rather avoid that if I can, since it is an intermittent issue. I'd likely need to be working as this other user for a while to know if the issue went away. Could I reset my KDE settings instead? What folders does KDE store its settings in?

(In reply to rockybulwinkle from comment #7)
> (In reply to Justin Zobel from comment #5)
> > Sounding really odd. Can you please try with a freshly created user?
> 
> I'd rather avoid that if I can, since it is an intermittent issue. I'd
> likely need to be working as this other user for a while to know if the
> issue went away. Could I reset my KDE settings instead? What folders does
> KDE store its settings in?

I believe they are all stored in ~/.config/. Konsole specifically is the file konsolerc.

Let us know how your testing goes.

So far it's been fine. I'll let you know if I see the issue again. I should have mentioned this in the initial post, but this system was upgraded from 18.04 to 20.04 earlier this year. I don't recall if that is when this started. I only really started noticing it when I started using larger ascii art for the MOTD.

Thanks for the update; changing status.

Unfortunately I just caught it happening again. Maybe I should share my configuration?

[Desktop Entry]
DefaultProfile=New Profile.profile

[Favorite Profiles]
Favorites=New Profile.profile

[KonsoleWindow]
ShowMenuBarByDefault=false

[MainWindow]
Height 1152=1094
MenuBar=Disabled
State=AAAA/wAAAAD9AAAAAAAABAAAAARGAAAABAAAAAQAAAAIAAAACPwAAAAA
ToolBarsMovable=Disabled
Width 2048=1024

[Profile Shortcuts]
Ctrl+D, Ctrl+D=

(In reply to rockybulwinkle from comment #11)
> Unfortunately I just caught it happening again. Maybe I should share my
> configuration?
> 
> [Desktop Entry]
> DefaultProfile=New Profile.profile
> 
> [Favorite Profiles]
> Favorites=New Profile.profile
> 
> [KonsoleWindow]
> ShowMenuBarByDefault=false
> 
> [MainWindow]
> Height 1152=1094
> MenuBar=Disabled
> State=AAAA/wAAAAD9AAAAAAAABAAAAARGAAAABAAAAAQAAAAIAAAACPwAAAAA
> ToolBarsMovable=Disabled
> Width 2048=1024
> 
> [Profile Shortcuts]
> Ctrl+D, Ctrl+D=

Are you able to make a backup of your config and try it without it?

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

(In reply to Justin Zobel from comment #12)
> (In reply to rockybulwinkle from comment #11)
> > Unfortunately I just caught it happening again. Maybe I should share my
> > configuration?
> > 
> > [Desktop Entry]
> > DefaultProfile=New Profile.profile
> > 
> > [Favorite Profiles]
> > Favorites=New Profile.profile
> > 
> > [KonsoleWindow]
> > ShowMenuBarByDefault=false
> > 
> > [MainWindow]
> > Height 1152=1094
> > MenuBar=Disabled
> > State=AAAA/wAAAAD9AAAAAAAABAAAAARGAAAABAAAAAQAAAAIAAAACPwAAAAA
> > ToolBarsMovable=Disabled
> > Width 2048=1024
> > 
> > [Profile Shortcuts]
> > Ctrl+D, Ctrl+D=
> 
> Are you able to make a backup of your config and try it without it?
> 
> I've set the bug status to "needsinfo" pending your response, please change
> back to "reported" or "resolved" when you respond, thanks.

That was the config it generated (with some quality of life changes like font size) after I moved the konsolerc. I have since installed arch linux (so I should be on the latest or nearly the latest versions) alongside kubuntu. They share the home directory, but just now I booted into arch, moved the entire .config to oldconfig (to avoid any corrupt or incompatible configs between kubuntu and arch versions) rebooted back into arch. I seem to be able to trigger the bug a little more reliably on arch. I haven't tried the below method on kubuntu yet.

Here's how I am triggering the bug on arch:
1. delete/move konsolerc (It is unclear if this is necessary)
2. Start konsole.
3. Set the initial terminal size in your default profile to be too short to fit your MOTD and the bash prompt.
4. Start a new konsole window. It will be cutting off the MOTD because it is too short.
5. Resize that new konsole window so it is tall enough to display the MOTD and the prompt.
6. Scroll up so you see your MOTD and the prompt.
7. Type something.

Expected result: It does not scroll and continues to show both MOTD and the bash prompt

Actual result: It scrolls back up cutting off the MOTD in the same spot as before the resize in step 5.

On kubuntu, I don't think I needed to go through all those steps to do step 3 to get it to trigger, but I think it may still be the same bug.

Created attachment 133877 [details]
attachment-14910-0.html

We are working on something that might fix this, I'll update here when we
land.


On Fri, Dec 4, 2020 at 5:16 PM <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=429024
>
> rockybulwinkle@gmail.com changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|WAITINGFORINFO              |---
>      Ever confirmed|1                           |0
>              Status|NEEDSINFO                   |REPORTED
>
> --- Comment #13 from rockybulwinkle@gmail.com ---
> (In reply to Justin Zobel from comment #12)
> > (In reply to rockybulwinkle from comment #11)
> > > Unfortunately I just caught it happening again. Maybe I should share my
> > > configuration?
> > >
> > > [Desktop Entry]
> > > DefaultProfile=New Profile.profile
> > >
> > > [Favorite Profiles]
> > > Favorites=New Profile.profile
> > >
> > > [KonsoleWindow]
> > > ShowMenuBarByDefault=false
> > >
> > > [MainWindow]
> > > Height 1152=1094
> > > MenuBar=Disabled
> > > State=AAAA/wAAAAD9AAAAAAAABAAAAARGAAAABAAAAAQAAAAIAAAACPwAAAAA
> > > ToolBarsMovable=Disabled
> > > Width 2048=1024
> > >
> > > [Profile Shortcuts]
> > > Ctrl+D, Ctrl+D=
> >
> > Are you able to make a backup of your config and try it without it?
> >
> > I've set the bug status to "needsinfo" pending your response, please
> change
> > back to "reported" or "resolved" when you respond, thanks.
>
> That was the config it generated (with some quality of life changes like
> font
> size) after I moved the konsolerc. I have since installed arch linux (so I
> should be on the latest or nearly the latest versions) alongside kubuntu.
> They
> share the home directory, but just now I booted into arch, moved the entire
> .config to oldconfig (to avoid any corrupt or incompatible configs between
> kubuntu and arch versions) rebooted back into arch. I seem to be able to
> trigger the bug a little more reliably on arch. I haven't tried the below
> method on kubuntu yet.
>
> Here's how I am triggering the bug on arch:
> 1. delete/move konsolerc (It is unclear if this is necessary)
> 2. Start konsole.
> 3. Set the initial terminal size in your default profile to be too short
> to fit
> your MOTD and the bash prompt.
> 4. Start a new konsole window. It will be cutting off the MOTD because it
> is
> too short.
> 5. Resize that new konsole window so it is tall enough to display the MOTD
> and
> the prompt.
> 6. Scroll up so you see your MOTD and the prompt.
> 7. Type something.
>
> Expected result: It does not scroll and continues to show both MOTD and the
> bash prompt
>
> Actual result: It scrolls back up cutting off the MOTD in the same spot as
> before the resize in step 5.
>
> On kubuntu, I don't think I needed to go through all those steps to do
> step 3
> to get it to trigger, but I think it may still be the same bug.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

Is the fix you're working on checked in to any dev or feature branch I could try? Still seeing the bug on latest Arch Linux builds.