https://bugs.kde.org/show_bug.cgi?id=375804
Bug ID: 375804
Summary: Discover doesn't open again after it's closed and
httpd.so it's being kept using too much CPU in the
background
Product: Discover
Version: 5.8.5
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: NOR
Component: discover
Assignee: aleix...@kde.org
Reporter: jpf...@gmail.com
Target Milestone: ---
Problem:
Discover close after install but it doesnt open after I launch it again
What was excpected:
Open Discover, use it, close it, open it again without issues
Steps to reproduce:
1. Open Discover from menu icon or plasma-discover in command line
2. Install any package and wait until it's installed
3. Close Discover
4. Try to open it again, doesn't work
In the background we can see that at least two process are still up from the
original run:
Example:
18714 ? Sl 0:01 http.so [kdeinit5] https
local:/run/user/1000/klauncherTJ1770.1.slave-socket
local:/run/user/1000/discoverT18696.2.slave-socket
18724 ? Rl 4:57 http.so [kdeinit5] http
local:/run/user/1000/klauncherTJ1770.1.slave-socket
local:/run/user/1000/discoverM18696.5.slave-socket
With time those two processes end up consuming 100% of the CPU until I SigKill
them, after that plasma discover can open and work again.
--
You are receiving this mail because:
You are watching all bug changes.
