https://bugs.kde.org/show_bug.cgi?id=520687
Bug ID: 520687
Summary: Displaying U+009D stops the output for the running
process
Classification: Applications
Product: konsole
Version First unspecified
Reported In:
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 192627
--> https://bugs.kde.org/attachment.cgi?id=192627&action=edit
archive containing a file that stops text output
DESCRIPTION
The problem is that printing U+009D stops the output for the running process.
This happens to me when I do some file processing, as I happen to have a file
with such a name (and I have no idea how it got this way). Of course I could
rename it, but that is not the point. I don't have this issue in the text
console or xterm, for one thing.
STEPS TO REPRODUCE
1. Unpack attached archive and go into the dir.
2. Run `ls | grep G`. The point of the grep call is that a plain `ls` would
convert the character to something printable
OBSERVED RESULT
Just "GGG" is printed
EXPECTED RESULT
"GGG?PPP" should be printed. Or, at any rate, all 3 P should be printed
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20260520
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.0
Kernel Version: 7.0.9-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i9-9900K CPU @ 3.60GHz
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: Intel® UHD Graphics 630
ADDITIONAL INFORMATION
I don't know when this first happened, but it's been like this for years.
For a more dramatic effect, add files whose names start with letters after G
and run something like `ls | grep -v q1w2e3`, which should let all of them
pass, and see the output stop after GGG
--
You are receiving this mail because:
You are watching all bug changes.
