https://bugs.kde.org/show_bug.cgi?id=423493
--- Comment #19 from Nate Graham <n...@kde.org> --- Even though for some reason I cannot reproduce the issue, the bug in the code is obvious: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/kcms/feedback/feedback.cpp#L56 It will run `plasma-discover --feedback` to get the feedback information from Discover. If Discover isn't already running, it gets launched (and then quit) and briefly appears in the Task Manager. If Discover is already running, it gets activated and switched to the main view. There is no chance that the previously-mentioned commit would have solved the issue, so now I'm not sure why I can't reproduce it again. :/ But the code is clearly wrong here. Ideally we shouldn't be invoking Discover's executable to get the feedback stats. We should get it from DBus or an API or something. If this is somehow technically problematic or impossible, we need to make sure to launch the app in such a manner that it doesn't appear in the Task Manager, and we need to always start a new instance if it's already running, so that we don't interfere with any already-running instances. -- You are receiving this mail because: You are watching all bug changes.
