Bug 408161 - UP ARROW doesn't work in konsole 19.04.1
Summary: UP ARROW doesn't work in konsole 19.04.1
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: history (show other bugs)
Version: 19.04.1
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-31 21:12 UTC by Yuriy Vidineev
Modified: 2019-06-02 04:30 UTC (History)
1 user (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 Yuriy Vidineev 2019-05-31 21:12:40 UTC
SUMMARY
In konsole 18.12 UP ARROW used to show previous command. It does nothing after update to konsole 19.04.1 on KDE Neon User with all updates

STEPS TO REPRODUCE
1. Open konsole (19.04.1 version)
2. Push UP ARROW

OBSERVED RESULT
Nothing happened

EXPECTED RESULT
Previous command from .bash_history is displayed

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE Neon 5.15
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.0
Comment 1 Yuriy Vidineev 2019-05-31 21:13:50 UTC
Forgot to mention: up arrow still works fine in xterm. And CTRL+P works in konsole (but not the UP ARROW)
Comment 2 Yuriy Vidineev 2019-05-31 21:51:02 UTC
Looks like I'm not the only one
https://forum.kde.org/viewtopic.php?f=227&t=160348&sid=3135337f2e80224f72fb17126e687475
Comment 3 Kurt Hindenburg 2019-06-01 17:57:01 UTC
I'm running basically the same system as you and it works here in zsh/bash.
Comment 4 Yuriy Vidineev 2019-06-02 02:20:37 UTC
Thanks, Kurt. It's weird. I'll check in liveusb
Comment 5 Nate Graham 2019-06-02 03:04:08 UTC
Yeah works for me too.
Comment 6 Yuriy Vidineev 2019-06-02 04:27:59 UTC
On liveusb it works for me.
If I remove all konsole settings - it works as well
mv ~/.local/share/konsole/ ~/.local/share/konsole_bkp

Looks like I see what's wrong - for some reason ARROW UP was set as a key to switch profiles in konsole. I'll try to dig deeper why it happened.
Thanks for checking, guys! And sorry for false (most possible) alarm
Comment 7 Nate Graham 2019-06-02 04:30:00 UTC
Thanks, glad you got it figured out and working again. :)