Bug 390132

Summary: mc stopped working
Product: [Applications] konsole Reporter: Vadym Krevs <vkrevs>
Component: keyboardAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: akontsevich
Priority: NOR    
Version: 17.12.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Vadym Krevs 2018-02-09 08:35:05 UTC
After the latest openSUSE Tumbleweed update, mc (Midnight commander) stopped working in konsole. mc starts but not of the navigation keys  - up/down/left/right - work. mc in xterm works just fine.

The current profile->Keyboard is set to Default (XFree 4)

mc-4.8.20-1.1.x86_64
konsole-17.12.1-2.1.x86_64

$ rpm  -qa  | grep plasma  | sort
patterns-kde-kde_plasma-20170319-13.1.noarch
plasma5-addons-5.12.0-1.1.x86_64
plasma5-addons-lang-5.12.0-1.1.noarch
plasma5-defaults-openSUSE-15.0~git20180116T134836~c3ce1b2-3.1.noarch
plasma5-desktop-5.12.0-1.1.x86_64
plasma5-desktop-lang-5.12.0-1.1.noarch
plasma5-integration-plugin-5.12.0-1.1.x86_64
plasma5-integration-plugin-lang-5.12.0-1.1.noarch
plasma5-pa-5.12.0-1.1.x86_64
plasma5-pa-lang-5.12.0-1.1.noarch
plasma5-pk-updates-0.3.1-3.1.x86_64
plasma5-pk-updates-lang-0.3.1-3.1.noarch
plasma5-session-5.12.0-1.1.noarch
plasma5-theme-openSUSE-15.0~git20180116T134836~c3ce1b2-3.1.noarch
plasma5-workspace-5.12.0-1.1.x86_64
plasma5-workspace-branding-openSUSE-15.0~git20180116T134836~c3ce1b2-3.1.noarch
plasma5-workspace-lang-5.12.0-1.1.noarch
plasma5-workspace-libs-5.12.0-1.1.x86_64
plasma-framework-5.42.0-1.1.x86_64
plasma-framework-components-5.42.0-1.1.x86_64
plasma-framework-lang-5.42.0-1.1.noarch
plasma-framework-private-5.42.0-1.1.x86_64
plasma-nm5-5.12.0-1.1.x86_64
plasma-nm5-lang-5.12.0-1.1.noarch
plasma-nm5-openvpn-5.12.0-1.1.x86_64
plasma-nm5-pptp-5.12.0-1.1.x86_64
plasma-nm5-vpnc-5.12.0-1.1.x86_64
Comment 1 Vadym Krevs 2018-02-09 09:27:15 UTC
Please close. https://bugzilla.opensuse.org/show_bug.cgi?id=1079543
Comment 2 Christoph Feck 2018-02-09 21:47:47 UTC
*** Bug 390145 has been marked as a duplicate of this bug. ***