[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 --- Comment #9 from Nate Graham --- *** This bug has been marked as a duplicate of bug 436928 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 --- Comment #8 from Harald Sitter --- It's something that'd need taking to the respective upstream projects really. Neither systemd nor packagekit actively support this use case, which is why the hack to bring dbus.service into the requirement tree is necessary. We are bound by the rules set forth elsewhere. If the options are reboot and power-off and power-off means reboot-then-power-off then that is what we, discover/plasma, have to work with for now. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 --- Comment #7 from Tobias G. --- (In reply to Harald Sitter from comment #6) > Huge caveat: this is entirely not fit for production. > > Technically one could do a poweroff update without any reboot. If > packagekit-offline-update.service grew an additional rule > Requires=dbus.service (in addition to dbus.target, which will on its own not > prevent ordering problems) one can simply isolate into the update target > instead of doing a poweroff. > > - pkcon update -d > - sudo qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit > org.freedesktop.PackageKit.Offline.Trigger power-off > - sudo systemctl daemon-reload > - sudo systemctl isolate system-update.target > > at this point the system should shut down all units that aren't part of the > dependency tree of system-update.target and fire up > packagekit-offline-update.service (which is part of that target) and > packagekit-offline-update.service will then issue the final system power-off > once its done. > This is however also a fair amount less reliable because isolation doesn't > necessarily ensure that everything else has been killed by the time the > update starts. Working under the assumption that the update cannot make > systemd or dbus fall over that shouldn't really matter though. > > Anyway, mostly posting this for academic purposes. Oh wow, even though it's mostly academic, I like the approach here. But since this bug has been marked as a duplicate of a newer report of today, this should maybe be written under the other one,so the discussion is all in one place, though, most/all of the discussion happened here already -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org --- Comment #6 from Harald Sitter --- Huge caveat: this is entirely not fit for production. Technically one could do a poweroff update without any reboot. If packagekit-offline-update.service grew an additional rule Requires=dbus.service (in addition to dbus.target, which will on its own not prevent ordering problems) one can simply isolate into the update target instead of doing a poweroff. - pkcon update -d - sudo qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit org.freedesktop.PackageKit.Offline.Trigger power-off - sudo systemctl daemon-reload - sudo systemctl isolate system-update.target at this point the system should shut down all units that aren't part of the dependency tree of system-update.target and fire up packagekit-offline-update.service (which is part of that target) and packagekit-offline-update.service will then issue the final system power-off once its done. This is however also a fair amount less reliable because isolation doesn't necessarily ensure that everything else has been killed by the time the update starts. Working under the assumption that the update cannot make systemd or dbus fall over that shouldn't really matter though. Anyway, mostly posting this for academic purposes. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED See Also|https://bugs.kde.org/show_b | |ug.cgi?id=436924| Resolution|--- |DUPLICATE --- Comment #5 from Nate Graham --- *** This bug has been marked as a duplicate of bug 436924 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=436924 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 --- Comment #4 from Tobias G. --- (In reply to francisco_t from comment #1) > In Neon with the new deafault "offline updates" Plasma/Discover does not > allow you to install updates when shutting down the system. > > For example: Fedora/gnome you can install "offline updates" in two different > ways: > 1-. restart -> install -> restart -> boot finally. (like discover now) > 2.- Go turn off -> restart -> install -> shutdown finally. > > I add an screenshot with the option to install updates before confirm the > turn off on Fedora. > > > EXPECTED RESULT > I want install offline updates while turn off my computer becasue It has > less impact in my work. I need a fast start, but I don't care an slow > shutdown. Yeah OK, that would be better, but won't solve the main issue I have with the current implementation, as I'd then have to enter the password when it reboots, as my system is encrypted (at least when it's a normal reboot to "install updates mode" :D) It then would be the same update behavior as Windows (which is also encrypted) and annoying because of the same reason. I want to shutdown my system, but instead it waits infinitely for me to enter the password to install the updates. Wouldn't it be possible to install the updates without the need of a reboot or the ability to cache the system password somehow? (even though I wouldn't know how that might be implemented securely). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Priority|NOR |HI Keywords||usability Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Yeah, this would be more user-friendly for sure. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 --- Comment #2 from francisco_t --- Created attachment 138008 --> https://bugs.kde.org/attachment.cgi?id=138008&action=edit Fedora/gnome turn off dialog with option to install "offline updates" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #1 from francisco_t --- In Neon with the new deafault "offline updates" Plasma/Discover does not allow you to install updates when shutting down the system. For example: Fedora/gnome you can install "offline updates" in two different ways: 1-. restart -> install -> restart -> boot finally. (like discover now) 2.- Go turn off -> restart -> install -> shutdown finally. I add an screenshot with the option to install updates before confirm the turn off on Fedora. EXPECTED RESULT I want install offline updates while turn off my computer becasue It has less impact in my work. I need a fast start, but I don't care an slow shutdown. -- You are receiving this mail because: You are watching all bug changes.
