Bug 440126 - Always requests system restart, often unnecessarily
Summary: Always requests system restart, often unnecessarily
Status: RESOLVED DUPLICATE of bug 435574
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.21.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-21 20:49 UTC by Mark Stanton
Modified: 2021-08-05 08:20 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Stanton 2021-07-21 20:49:00 UTC 
SUMMARY

Discover *always* wants a system restart to apply changes, no matter how irrelevant to system operation they are.

Today I have been notified of a single update, Google Chrome, and Discover still wants to restart the system after applying it.

It is quite possible to detect what actions specific to the updates applied are required, either system or daemon (eg) restart (eg Cockpit), without simply applying a blanket action.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 5.12.15-300.fc34.x86_64
(available in About System)
KDE Plasma Version: 5.22.3
KDE Frameworks Version:  5.83.0
Qt Version: 5.15.2
Comment 1 Nate Graham 2021-08-04 23:25:59 UTC 
Can you outline how to do that from the data that we have from PackageKit?

*** This bug has been marked as a duplicate of bug 435574 ***
Comment 2 Mark Stanton 2021-08-05 08:20:58 UTC 
I have no idea. However, as mentioned previously, the server management program Cockpit *does* do this in the same environment. 

It's open source so perhaps you can just see how they do it.

https://cockpit-project.org/