Bug 186094 - konsole keyboard input fails when second tab is opened
Summary: konsole keyboard input fails when second tab is opened
Status: RESOLVED DUPLICATE of bug 183649
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-03-04 02:30 UTC by Joe Conway
Modified: 2018-09-19 14:33 UTC (History)
0 users

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 Joe Conway 2009-03-04 02:30:25 UTC
Version:           2.2 (using 4.2.00 (KDE 4.2.0), 4.2.0-15.fc10 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.19-170.2.35.fc10.x86_64

Immediately after "yum update" today (fedora 10, 2009-03-03), konsole stopped working correctly. Whenever I open a second tab, all keyboard input is frozen within the konsole. The mouse still works, and menu items work. Opening or closing additional tabs does not help, nor does switching between tabs. No workarounds found. All other applications open at the time continue to function fine.
Comment 1 Kurt Hindenburg 2009-03-08 15:56:39 UTC
Since you just upgraded, I would suggest asking on the Fedora site.  Or at least open a bug report there and see what they say.

Feel free to reopen this w/ more info.
Comment 2 Joe Conway 2009-03-08 17:31:51 UTC
I did *not* upgrade, I updated a few seemingly unrelated packages. In any case this appears the same as 183649 (SuSe) and 166143 (Kubuntu) which I did not find when I first entered my bug. Given that it shows up on three distinct distributions I don't think it ought to be pushed downstream.

*** This bug has been marked as a duplicate of bug 183649 ***
Comment 3 Andrew Crouthamel 2018-09-19 04:33:43 UTC
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!
Comment 4 Andrew Crouthamel 2018-09-19 14:33:34 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.