Bug 375804 - Discover doesn't open again after it's closed and httpd.so it's being kept using too much CPU in the background
Summary: Discover doesn't open again after it's closed and httpd.so it's being kept us...
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.8.5
Platform: Neon Linux
: NOR critical
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-01-31 16:12 UTC by Juan Pablo Firrincieli
Modified: 2018-10-28 03:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Pablo Firrincieli 2017-01-31 16:12:50 UTC
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.
Comment 1 Juan Pablo Firrincieli 2017-01-31 16:14:56 UTC
As an additional info I'm running behind a proxy http
Comment 2 Aleix Pol 2017-02-06 16:25:19 UTC
Would you be able to run discover within gdb and get a backtrace?

If you've never done that tell me and I'll help you do so.
Comment 3 Andrew Crouthamel 2018-09-28 02:40:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-28 03:32:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!