Created attachment 147391 [details] Terminal input and output, when trying to update using pkcon tool After trying to upgrade from Plasma 5.24.2 to 5.24.3, the system rebooted without installing the update and the error message “Offline Update Failed” was shown. Three subsequent attempts also failed, with exactly the same result. STEPS TO REPRODUCE I am actually not quite sure how this issue can be reproduced on other platforms and configurations. However. I believe I can reproduce it on my own PC and gather additional information if someone gives me instructions on how to do that. OBSERVED RESULT Other than repeated update failure error on subsequent attempts, I also ran into another issue afterwards. When trying to resume after my PC had been suspended, the lock screen was not accessible. Instead, an error message appeared on the screen, saying that lock screen is broken and to unlock, the command “loginctl unlock session 4” should be used in a virtual (If I remember correctly) terminal. Since this PC is my daily driver, I have restored it to a prior system snapshot using Timeshift. But I assume I can reproduce this issue if it helps generate more information. EXPECTED RESULT I do not have enough information to speculate on that. These are the information of my PC: KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30 (64 Bit) Distribution: KDE Neon User Edition (Based on Ubuntu 20.04 LTS) ADDITIONAL INFORMATION Since I'm fairly new to Linux and have no development experience whatsoever, the best thing I thought I could do and did was trying to update packages from terminal to gather more information for reporting. I used the command “sudo pkcon update -vv” which generated a response with name of the packages that would be modified, etc. Proceeding with changes resulted in an error message which was shown within the prior message, making it harder to read. I try to copy it as much as possible here, but I saved the entire terminal input and output to a text file, which I have added as an attachment as well. The Error As Show in the Terminal After Running the Command “sudo pkcon update -vv” : [=========================] all Discover software manager suite (common data files) Updating packages [=========================] :31:50S.M.A.R.PackageKit using frontend gnomein Plasma Loading cache [=========================] badbccdd.socketnfiguration module for firewalls Running [=========================] 06:31:54tworkmPackageKit socket hung upr: Use of uninitialized value $ENV{"PATH"} in split at /usr/share/perl/5.30/TFinished [=========================] :32:11d frontePackageKit sending SIGQUIT 2857ebconf/FrontEnd/Dialog.pm line 76.) Fatal error: Error while installing package: 0.00007f1254003ca0init server: Could not connect: Connection refusedonf/passwords.dat morteza@Morteza-Laptop:~$ child has error: Use of uninitialized value $ENV{"PATH"} in split at /usr/share/perl/5.30/Term/Cap.pm line 251. 06:31:53(db): maPackageKit child has error: debconf (db passwords): loading databaser Plasma 5 (debconf-communicate:2869): Gtk-WARNING **: 06:31:53.398: cannot open display: :0eme for Plymouth debconf (db): making DbDriver of type Stackas error: debconf (db): making DbDriver of type Stack 06:31:53vil-dataPackageKit child has error: debconf: unable to initialize frontend: Gnomes data files. debconf: (DISPLAY problem?) child has error: debconf (user): trying frontend Gnome Filend monitoring tools python3-distupgrade-1:20.04.37+p20.04+trelease+git20220301.1108.all manage release upgrades 06:31:53ule-org-PackageKit child has error: debconf: falling back to frontend: Dialoge is /var/cache/debconf/templates.dat This is my first time reporting a bug, so I hope I have given enough information to help someone troubleshoot.
Today, I tried again to install the same system update, which again failed in the same manner. I also tried four subsequent reboots to see if updates will be installed successfully, but unfortunately they did not (twice, the machine was shut down completely and then powered back on, but that made no difference either). Everything seemed to work normally afterwards (no broken screen lock as happened the last time), except any attempts to install system updates. This time, I also tried to get as much information as I knew how to get. So I saved all system logs following the reboot after the failure in installing the system updates and then, the attempted process to repair the system by clicking “Repair System” on Discover notification pop-up. I tried to install the packages by choosing “Full Upgrade” in Muon package manager as well, and saved the system log generated by that process to another text file. I had to perform a restore again using Timeshift, and if there is no workaround or any way to fix this problem, I suppose I have to perform a clean installation using the 5.24.3 image of KDE Neon to continue getting future updates. This is kind of frustrating since my time using KDE Neon had been excellent thus far. So if anyone knows any method that could prevent all the hassle of a full system reinstall, I'll be looking forward to hearing it.
Created attachment 147440 [details] System log after rebooting following the update failure
Created attachment 147441 [details] Muon logs when trying to install package updates
The error message I got after running “sudo pkcon update”; “Fatal error: Error while installing package: 0.0000”, had been reported before. Unfortunately, I had not found it earlier. Link to the bug report: https://bugs.kde.org/show_bug.cgi?id=451047 Seems like this is what caused the failure in system updates. Apparently there is a workaround too. I posted this here in case anyone else runs into a failed update error and can't solve the issue themselves.