SUMMARY The unattended updates feature hangs in the "apply unattended updates" phase infinitely, I waited a few hours, but never seems to finish. This happens on two systems independently. After the update to 5.21, the feature already worked, but stopped working. Can this be confirmed? If there's a way to take logs, I'd like to do so. STEPS TO REPRODUCE 1. Enable unattended updates 2. Wait for updates to be available 3. See the cloud logo indicating the installation of unattended updates OBSERVED RESULT The cloud logo remains, but updates are not installed at next reboot EXPECTED RESULT The process finishes and updates are installable at reboot SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.21.1 and 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
I created a video of it not working, a version in normal speed (2h long) https://www.youtube.com/watch?v=4OQPYS7je-0 and one at 500% speed https://www.youtube.com/watch?v=AG0cZnNqRWg In the status bar at the top, the updater status can be seen. I didn't use my PC in that time (except for listening to music, but I controlled the program with my Smartphone, so no keyboard or mouse interactions). Installing the updates manually works without issues via Discover. As already stated, the feature worked with Plasma 5.21.0, but stopped working with 5.21.1. I hope this screen recording is a proof that I don't imagine it not working properly. :P
The issue still exists, it just worked once when I started my PC and did nothing with it, so the system could install the updates without interruptions. But when I use the system,e.g. By watching a video, it starts the updates, but may be interrupted when I close the browser afterwards. Could there lay the issue, that it isn't and to finish after an interruption? I'd like to provide logs, but don't know which unfortunately.
You say that 5.21.1 broke it, and I see one suspicious related commit that was introduced in 5.21.1: https://invent.kde.org/plasma/discover/commit/c730100fd5bb69f7ef38ef5658ce3948725d7c66 Aleix, could you take a look?
@Nate: I doubt it. This is mostly a cosmetic change for properly displaying progress. @Tobias: Can you try running plasma-discover-update on a terminal and see if you get any kind of error? plasma-discover-update is what we launch to perform the unattended updates.
Sorry, forgot to mention. The command is "plasma-discover-update --offline".
(In reply to Aleix Pol from comment #5) > Sorry, forgot to mention. The command is "plasma-discover-update --offline". Thank you, I did that, after two hours this is the output, it still didn't finish. plasma-discover-update --offline invalid kns backend! "/usr/share/knsrcfiles/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct adding empty sources model QStandardItemModel(0x557c9be1eec0) ready 0 steady 0 QObject::connect(Transaction, DiscoverUpdate): invalid nullptr parameter go! QObject(0x0) ready 203 steady 0 go! UpdateTransaction(0x7f8bf001d610) status! Transaction::CommittingStatus 203 PackageKit stopped running! PackageKit stopped running! took really long to fetch PackageKitBackend(0x557c9be2ffa0) PackageKit stopped running! PackageKit stopped running! took really long to fetch PackageKitBackend(0x557c9be2ffa0) PackageKit stopped running!
That's the output I get on my second system, installing updates manually via Discover worked, but also showed the message that qogir-dark could not be installed. I tried to find it in the system settings to see if I can update it using the get-new-stuff-dialog, but it didn't even show me an update: plasma-discover-update --offline invalid kns backend! "/usr/share/knsrcfiles/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct adding empty sources model QStandardItemModel(0x55ca8bc84d90) ready 1 steady 0 go! UpdateTransaction(0x55ca8c7085d0) status! Transaction::CommittingStatus 1146 already installed. already installed. already installed. installing... kf.newstuff.core: could not install "Qogir icon theme" to "/home/tobias/.local/share/icons/" kns error: KNSCore::InstallationError "„Qogir icon theme“ kann nicht installiert werden: Datei nicht gefunden." QVariant(Invalid) kf.newstuff.core: The file could not be parsed. KNS error in "Globale Designs" : KNSCore::InstallationError "Installation von /tmp/sxkMhP-01-com.github.vinceliuice.Qogir-dark.tar.xz fehlgeschlagen: Die Abhängigkeit kann nicht installiert werden: kns://icons.knsrc/api.kde-look.org/1296407" QVariant(Invalid) kns error "/usr/share/knsrcfiles/lookandfeel.knsrc" "Installation von /tmp/sxkMhP-01-com.github.vinceliuice.Qogir-dark.tar.xz fehlgeschlagen: Die Abhängigkeit kann nicht installiert werden: kns://icons.knsrc/api.kde-look.org/1296407" status! Transaction::DoneStatus 1146
Git commit a24561835628773ddb72df38c6d2fa8cfabbb946 by Aleix Pol. Committed on 12/04/2021 at 15:41. Pushed by apol into branch 'master'. update: close the application if we are not running a transaction Otherwise the process would linger forever unnecessarily. M +6 -0 update/DiscoverUpdate.cpp https://invent.kde.org/plasma/discover/commit/a24561835628773ddb72df38c6d2fa8cfabbb946
So the log in #6 is showing the issue, but only because there were no updates at this moment in time. The fix is in, but since presumably this was happening when there actually are updates, I'll leave the bug open. Can you try to repeat the steps in #6 when there are updates to apply? Thank you very much!
.
(In reply to Aleix Pol from comment #9) > So the log in #6 is showing the issue, but only because there were no > updates at this moment in time. > > The fix is in, but since presumably this was happening when there actually > are updates, I'll leave the bug open. > > Can you try to repeat the steps in #6 when there are updates to apply? > > Thank you very much! I re-ran it on the system of comment 6, this is the output. I had to run it 2 times as it just stopped the first time. I waited for half an hour, I'll check later if there's anything new. familie@Medienzentrale:~> plasma-discover-update --offline invalid kns backend! "/usr/share/knsrcfiles/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct adding empty sources model QStandardItemModel(0x55e7fa31b1f0) took really long to fetch FlatpakBackend(0x55e7fa2dcdb0) took really long to fetch PackageKitBackend(0x55e7fa116e60) ready 2 steady 0 go! UpdateTransaction(0x55e7fa861790) status! Transaction::CommittingStatus 208 status! Transaction::DoneStatus 206 familie@Medienzentrale:~> plasma-discover-update --offline invalid kns backend! "/usr/share/knsrcfiles/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct adding empty sources model QStandardItemModel(0x561895436ac0) ready 0 steady 0 QObject::connect(Transaction, DiscoverUpdate): invalid nullptr parameter go! QObject(0x0) ready 206 steady 0 go! UpdateTransaction(0x7fd9a401ec80) status! Transaction::CommittingStatus 206 PackageKit stopped running! PackageKit stopped running! PackageKit stopped running!
Well you are still running without my patch. What happened here in #11 is that the first time it triggered the updates, the second it didn't had any so you fell on the issue that #8 solves. I'd say let's wait until you get a fixed version from your distro and then we can see if there is anything else still broken.
(In reply to Aleix Pol from comment #12) > Well you are still running without my patch. What happened here in #11 is > that the first time it triggered the updates, the second it didn't had any > so you fell on the issue that #8 solves. > > I'd say let's wait until you get a fixed version from your distro and then > we can see if there is anything else still broken. Oh yeah, I'm sorry. I can pretty easily install a precompiled master that's updated regularly, so I'll switch to that and check if it still happens
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!