https://bugs.kde.org/show_bug.cgi?id=515206
--- Comment #13 from [email protected] --- (In reply to John from comment #12) > (In reply to thiagocanutof84 from comment #11) > > > 2. it's not intended to manage the entire version leap. > > Bummer!!! Fedora or KDE Linux it is, then... (as.windows alternative, > naturally!) > Thanks for clarifying! > > Considering this bug: > There's also that weird behavior, in unattended updates, of Discover having > to open and close the GUI to start the updates... apparently there's on > workaround for this, but I imagine this as a source of problems... can it > have anything to do with this issue? Hi John, That's a very good observation. Yes, I believe they are directly related. If the backend (PackageKit) is failing to trigger the updates autonomously and only "wakes up" when the GUI is opened, that would explain why the "Automatic" mode isn't truly automatic. In my case, even with Discover open, it still waits for that final "Update All" click, but your point about the GUI interaction being a trigger for the backend suggests a deeper flaw in how the autonomous mode is handled by the system's timers and background services. It definitely belongs in the same discussion. -- You are receiving this mail because: You are watching all bug changes.
