https://bugs.kde.org/show_bug.cgi?id=478091
Bug ID: 478091
Summary: Does not remove previous KCM header when switching to
KDE Connect KCM
Classification: Applications
Product: systemsettings
Version: 5.90.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: j.acco...@petsovits.com
Target Milestone: ---
SUMMARY
Weird visual bug that ends up in two KCM headers showing at the same time. The
KDE Connect KCM already has a non-standard header bar, with header title
misaligned and no separator below it. I was tempted to report it in that
component. However, removing the previous header bar when switching to a
different (however non-standard) KCM is the job of the System Settings app. So
here goes.
STEPS TO REPRODUCE
1. Open the "Device Actions" KCM in System Settings. It doesn't matter if you
navigate there via "Disks & Cameras" or open it directly via KRunner.
2. Press back in the sidebar and click on "KDE Connect" to navigate there.
OBSERVED RESULT
The header bar from "Device Actions" is still present. Below it you can find
the entirety of the "KDE Connect" KCM, including its own "KDE Connect" header.
EXPECTED RESULT
The "Device Actions" header disappears and the main view only shows the "KDE
Connect" KCM by itself.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
ADDITIONAL INFORMATION
This can also be reproduced with "Keyboard" or "Wi-Fi & Networking" instead of
"Device Actions". Which strongly suggests that this is an interaction between
1. QtWidget KCM as the origin to navigate away from, 2. whatever weird stuff
the (presumably also QtWidget-based) KDE Connect KCM is doing to avoid using
the native System Settings header.
No screenshot because I still haven't figured out how to make privileged D-Bus
services work in my Plasma 6 dev environment.
--
You are receiving this mail because:
You are watching all bug changes.
