Bug 402065 - Fails to properly quit on close
Summary: Fails to properly quit on close
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: fwupd Backend (show other bugs)
Version: 5.14.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Abhijeet Sharma
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-12 17:33 UTC by Terry
Modified: 2019-01-06 12:08 UTC (History)
1 user (show)

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 Terry 2018-12-12 17:33:49 UTC
SUMMARY

Plasma-discover-updater frequently fails to shutdown on system power off or logging out in KDE Neon.  Upon system boot and log in Discover application opens up with NO updates available and without any input from the operator.

STEPS TO REPRODUCE
1. Update system when updates are available.
2. Properly close Discover.
3. Shut system down/log out of desktop ((X11 (Wayland session not attempted))

OBSERVED RESULT

Upon booting system back up and logging into an X11 session Discover application opens up as if it was never properly shut down.

EXPECTED RESULT

I expect to log into a desktop without any applications "popping up" at all without my actual input.

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: KDE Neon Developers Stable Edition
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.54
Qt Version: 5.11.2

ADDITIONAL INFORMATION
Comment 1 Terry 2018-12-12 17:35:16 UTC
This does NOT happen all the time, but it happens frequently enough to warrant reporting.
Comment 2 Aleix Pol 2018-12-13 02:42:30 UTC
Guessing it's the fwupd backend issue.

Thank you very much for reporting.
Comment 3 Nate Graham 2018-12-27 04:13:26 UTC
Can confirm. You can see this pretty frequently when launching from the command-line and quitting. The process doesn't actually exit, and you need to ctrl+C it.
Comment 4 Nate Graham 2019-01-05 05:30:35 UTC
I haven't seen this recently on git master after all your welcome fixes to the fwupd backend BTW. I do still experience it with 5.14.4.