27.02.2016 21:01, Carlos E. R. пишет:
On 2016-02-27 18:11, Andrei Borzenkov wrote:
27.02.2016 20:04, Carlos E. R. пишет:
On 2016-02-27 17:39, Lars Müller wrote:
But the OP did not use zypper. He used the desktop update applet. The issue would be avoiding the desktop to crash, but perhaps postpone the actual update till an automatic graphic system restart. A new update paradigm. :-)
The actual update happens in background, performed by packagekit daemon. At least I just had experienced the same and although I was kicked out of GUI session, the installation seems to continue. I could not find how can I query packagekit backend for current operations, at least before disk activity stopped :)
So it appears to provide the same level of protection as zypper in screen. Except when packagekit itself is restarted :p
Yes, in that sense, yes. But the user experiences a crash of his session. My suggestion is to get everything ready, tell the user to accept a session restart, close the session, update critical things, start the session again. Automatically. Windows does it this way, yes.
Windows does not close session - it reboots and installs updates during reboot. That is how packagekit offline updates work and I believe offline updates are the only ones supported by native GNOME client (I may be mistaken, but I got this impression when I looked last time).
Just saying an idea, I like how it is currently :-)