https://bugs.kde.org/show_bug.cgi?id=364650
Bug ID: 364650
Summary: Crash when searching for '_' with non-native keyboard
layout
Product: kate
Version: unspecified
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Vi Input Mode
Assignee: kwrite-bugs-n...@kde.org
Reporter: bplusp...@hotmail.com
I tried out the KDevelop AppImage from here
http://files.svenbrauch.de/kdevelop-linux/, specifically the build from
2016-06-21. The about dialog says this is v. 4.90.92, using KDE Frameworks
5.24.0 and Qt 5.6.1.
On this build, I can consistently crash the entire application (not just the
Kate part--I hope I'm correct thinking KDevelop uses that?) very easily in vi
mode. All I have to do is set my keyboard layout to us (my physical keyboard is
Swedish, I use us for development), hit '/' to enter search mode and type '_'.
Instant crash.
This does not happen if I use my native keyboard layout. Nor does it happen in
ctrl+f search in normal mode, regardless of layout.
Running from command-line, the only related output I get is
/tmp/.mount_3SmjWq/AppRun: line 28: 11529 Segmentation fault (core dumped)
kdevelop $@
Running in gdb, the only additional output is
[Inferior 1 (process 11512) exited with code 0213]
Telling gdb to print a backtrace just says "No stack."
Reproducible: Always
Steps to Reproduce:
1. Set keyboard layout to 'us' (native layout is 'se')
2. Activate vi mode
3. Type '/' to enter forward search
4. Type '_'
Actual Results:
Application crashes
Expected Results:
Cursor jumps to and highlights the next occurrence of the '_' character in the
open buffer
--
You are receiving this mail because:
You are watching all bug changes.
