*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY<html>Cannot obtain lock:<br/><br/>E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. </html> STEPS TO REPRODUCE 1. attempt to manually run in Konsole but not found 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
If you got "command not found" when you entered "dpkg --configure -a" in Konsole, does entering "/usr/bin/dpkg --configure -a" work?
Created attachment 175818 [details] attachment-73626-0.html Sorry to be so long but been waiting for the update to happen again. it has and I put in what you suggested but it came up with "bash: /usr/bin/dpkg--configure-a: No such file or directory" I am totally lost on all this as I have no knowledge of Lynux command coding so the simpler the better for me. Should I have proceeded the instructions with "sudo" or my password or something? On Wed, 6 Nov 2024 at 19:22, Paul Worrall <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=495883 > > Paul Worrall <p.r.worrall@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |p.r.worrall@gmail.com > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Paul Worrall <p.r.worrall@gmail.com> --- > If you got "command not found" when you entered "dpkg --configure -a" in > Konsole, does entering "/usr/bin/dpkg --configure -a" work? > > -- > You are receiving this mail because: > You reported the bug.
A three things: 1. The spaces in the command line are important, i.e. before " --config" and before " -a", your comment seems to indicate you didn't have them 2. Yes, you will need to put "sudo" at the beginning (sorry, I should have mentioned that) 3. You don't have to wait for the next update, you can do it now. So the full command, including the required spaces, is: sudo /usr/bin/dpkg --configure -a You'll be prompted for your password.
Created attachment 175826 [details] attachment-111498-0.html Thanks - that seemed to work at the start but after putting my password in went into a repetition phil@phil-n13n140zu:~$ sudo /usr/bin/dpkg --configure -a [sudo] password for phil: Setting up linux-firmware (20220329.git681281e4-0ubuntu3.29) ... update-initramfs: Generating /boot/initrd.img-6.5.0-21-generic I: The initramfs will attempt to resume from /dev/nvme0n1p3 I: (UUID=f27b1db8-625d-4b92-bcf4-557d03cc4122) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-6.5.0-18-generic I: The initramfs will attempt to resume from /dev/nvme0n1p3 I: (UUID=f27b1db8-625d-4b92-bcf4-557d03cc4122) I: Set the RESUME variable to override this. So I have quit as I assume this is not going anywhere. What next? On Thu, 14 Nov 2024 at 17:22, Paul Worrall <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=495883 > > --- Comment #3 from Paul Worrall <p.r.worrall@gmail.com> --- > A three things: > 1. The spaces in the command line are important, i.e. before " --config" > and > before " -a", your comment seems to indicate you didn't have them > 2. Yes, you will need to put "sudo" at the beginning (sorry, I should have > mentioned that) > 3. You don't have to wait for the next update, you can do it now. > > So the full command, including the required spaces, is: > sudo /usr/bin/dpkg --configure -a > > You'll be prompted for your password. > > -- > You are receiving this mail because: > You reported the bug.
I do not see anything wrong in the above. Suggest you try again if you can, and let it run to completion.
Created attachment 175837 [details] attachment-236291-0.html Thanks again, I neglected to notice the image numbers changing. I have now run this to completion and looking at my system configuration I get the following :- Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Notebook Product Name: N13_N140ZU Does that look correct? On Thu, 14 Nov 2024 at 23:26, Paul Worrall <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=495883 > > --- Comment #5 from Paul Worrall <p.r.worrall@gmail.com> --- > I do not see anything wrong in the above. Suggest you try again if you > can, > and let it run to completion. > > -- > You are receiving this mail because: > You reported the bug.
Nothing wrong there. I expect you'll get updates to Plasma 6.2
Created attachment 175852 [details] attachment-320790-0.html Paul I have now received and upgraded both KDE Neon and Plasma to 6.2 without the need for any further intervention, presumably as the prior, manual running, of "dpkg configure a" has cleared the initial problems. The matter is now resolved. Thank you for your help and advice. Phil On Fri, 15 Nov 2024 at 15:25, Paul Worrall <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=495883 > > Paul Worrall <p.r.worrall@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |WORKSFORME > Status|NEEDSINFO |RESOLVED > > --- Comment #7 from Paul Worrall <p.r.worrall@gmail.com> --- > Nothing wrong there. I expect you'll get updates to Plasma 6.2 > > -- > You are receiving this mail because: > You reported the bug.