https://bugs.kde.org/show_bug.cgi?id=484463
Bug ID: 484463
Summary: balooctl prints output over shell, and doesn't accept
control codes from user.
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 5.115.0
Platform: openSUSE
URL: https://discuss.kde.org/t/balooctl-purge-fails-to-stop
-baloo/12945/33?u=rokejulianlockhart
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: balooctl
Assignee: baloo-bugs-n...@kde.org
Reporter: 4wy78...@rokejulianlockhart.addy.io
Target Milestone: ---
Flags: performance-
SUMMARY
`balooctl` doesn't retain shell context (like `zypper`, `dnf`, or even
`systemsettings`' CLI output does), instead merely printing over the shell
prompt its output until another command is invoked.
STEPS TO REPRODUCE
1. Install cpe:/o:opensuse:tumbleweed:20240321.
2. Install
https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/kf6-baloo-file-6.0.0-1.1.x86_64.rpm.
3. Invoke `balooctl enable` when it is disabled (via `balooctl disable`, for
instance).
OBSERVED RESULT
It ends as expected, and the shell prompt is displayed. However, logs continue
to be outputted to the shell (like the shell itself it has become it stdout, if
that makes sense).
EXPECTED RESULT
It should retain the shell context so that its output isn't interrupted by the
shell prompt, and so that it can be killed or *manually* `bg`'d by the user.
SOFTWARE/OS VERSIONS
Operating System: cpe:/o:opensuse:tumbleweed:20240321
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 5700
Manufacturer: ASRock
Product Name: X670E Taichi
ADDITIONAL INFORMATION
https://discuss.kde.org/t/balooctl-purge-fails-to-stop-baloo/12945/33?u=rokejulianlockhart
--
You are receiving this mail because:
You are watching all bug changes.
