SUMMARY After a print job has finished, the Printers widget still thinks that printing is happening. STEPS TO REPRODUCE 1. Make sure that Printers widget is set to "Shown when relevant" 2. Print something 3. Note the Printers widget appears 4. Wait for the printing to finish OBSERVED RESULT The Printers widget is still present. Hovering over it shows "Printing (job name) with (queue name)". Clicking on the widget, the printer shows "Idle" underneath the name. Clicking on the printer, underneath Configure Printer and View Print Queue, it shows the job name with a Cancel button alongside. EXPECTED RESULT The Printers widget to disappear into the overflow area. Hovering over it in the overflow area to show "Print queue is empty". Expanding the printer in the widget to not show any jobs underneath Configure Printer and View Print Queue. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20251119 KDE Plasma Version: 6.5.2 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 Kernel Version: 6.17.8-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Note that if I view the full print queue, no print jobs are showing, so the problem seems to be just a display issue in the widget. This used to behave as in the EXPECTED RESULT section. I don't print very often so I can't be certain when the problem first started, but it was quite recently, so maybe with 6.5.
I can confirm this behavior. After printing, the icon remains in the system tray. When you open it, the printer is shown as "idling," and the print queue displays it as "completed." However, the last job is still displayed with the "Cancel" button, even though it's already finished. The "Cancel" button doesn't do anything because there's nothing to cancel. Only after logging out and back in to the desktop does the icon disappear. Operating System: Arch Linux KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.17.9-arch1-1 (64-bit) Graphics Platform: X11
It appears we're not getting notification that the job queue is cleared, but I can't reproduce this in 6.5 or master. Any chance you could try this out with Plasma 6.6?
Also, what version of CUPS are you running?
I can't test Plasma 6.6 right now, but I am running CUPS 2.4.14.
Alright, I have found a scenario this can happen and it appears to be related to a CUPS dbus-notifier lock that is not released or is "stuck". Plasma version doesn't matter, but if for some reason, a dbus-notifier get stuck (hangs), we stop getting notified of CUPS events, like for example, a print job finishing. Even restarting the plasma shell has no effect. Short of a complete logout, the following seems to put CUPS back into a working state: Logout of plasma Switch to a TTY login systemctl stop cups rm /etc/cups/subscriptions.* rm -rf /var/cache/cups systemctl restart cups logout Switch back to SDDM, start the plasma session As to why this happens, I'm not really sure. It's possible a crashing process that holds a notification subscription would prevent a clean "unlock" of the notifier, but I see no evidence that is happening. Plasma will generally have two processes running that "listen" for CUPS events, one is the marker level checker (kded process) and the other is the plasmoid, (plasmashell process). Both seem to operate normally and react properly to signals that are received and they log no errors or warnings in this scenario.
I should follow that up with this: If you see plasmashell crash or a kded crash, then that could possibly cause this behavior because both will attempt to restart and continue on.
I can also confirm this on openSUSE Tumbleweed 20260128 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.7-1-default (64-bit) Graphics Platform: X11 cups: 2.4.16 I've been test printing quite a lot recently, and I haven't come across any crashes. A small correction of the initial bug description, the printer queue window does still show the job after printing, but it reports "printer idle" in its header again. However, you can make the stuck job disappear by switching the filter from "active jobs" to "completed jobs" and back. The printer and queue state reported by "lpstat -t" is always correct during the printing process which supports the analysis that it's merely a dbus issue.
I still can't repro this on master or 6.6. However, there is a MR that cleans up the job model a bit, may help: https://invent.kde.org/plasma/print-manager/-/merge_requests/280
Git commit a74d40f233229ab01cf9e5ea6b492bd8b17f7cc2 by Mike Noe. Committed on 19/02/2026 at 11:12. Pushed by noee into branch 'master'. Add new print queue manager app Related: bug 499546 FIXED-IN: 6.7 M +1 -0 .kde-ci.yml M +6 -0 CMakeLists.txt M +14 -13 README.md M +1 -0 src/CMakeLists.txt M +1 -1 src/libkcups/ProcessRunner.cpp A +42 -0 src/print-queue/CMakeLists.txt A +8 -0 src/print-queue/Messages.sh A +132 -0 src/print-queue/PrintQueue.cpp [License: GPL(v2.0+)] A +36 -0 src/print-queue/PrintQueue.h [License: GPL(v2.0+)] A +80 -0 src/print-queue/main.cpp [License: LGPL(v2.0+)] A +11 -0 src/print-queue/org.kde.plasma.printqueue.desktop A +358 -0 src/print-queue/qml/JobView.qml [License: LGPL(v2.0+)] A +356 -0 src/print-queue/qml/Main.qml [License: LGPL(v2.0+)] A +81 -0 src/print-queue/qml/NotAvailablePage.qml [License: LGPL(v2.0+)] https://invent.kde.org/plasma/print-manager/-/commit/a74d40f233229ab01cf9e5ea6b492bd8b17f7cc2
*** This bug has been marked as a duplicate of bug 518706 ***
You marked the duplicates the wrong way round!
*** Bug 518706 has been marked as a duplicate of this bug. ***
*** Bug 518944 has been marked as a duplicate of this bug. ***
*** Bug 521634 has been marked as a duplicate of this bug. ***
The bug still occurs in Plasma 6.7
I understand there will be a final release of the 6.6 series planned as 6.6.6 for July. Can the fix be backported and released there too?
(In reply to Sergio from comment #16) > I understand there will be a final release of the 6.6 series planned as > 6.6.6 for July. Can the fix be backported and released there too? If I can get approval, yes it can be backported to 6
(In reply to Sergio from comment #16) > I understand there will be a final release of the 6.6 series planned as > 6.6.6 for July. Can the fix be backported and released there too? There is no fix… the problem still exist in KDE-Plasma 6.7.1; the only thing that has changed is that I now also see an additional number of open print jobs ➀, even though they are all completed.
Technically, the "fix" above is a work-around for what I'm pretty sure is a CUPS issue that has been around since flush toilets.
Weird. The problem with CUPS is from your word very old, but this bug is not, nor the duplicates appear to be. Personally, I have started experiencing the issue with the printer applet when I installed plasma 6.5 and all the bug reports in the duplicates list appear to be for 6.5, 6.6 and 6.7. Even if the ultimate problem is with CUPS, there must be something with plasma that has started "triggering" the problem (possibly starting with the 6.5 series).
Is there a CUPS issue to follow?
(In reply to Sergio from comment #20) > Weird. The problem with CUPS is from your word very old, but this bug is > not, nor the duplicates appear to be. Personally, I have started > experiencing the issue with the printer applet when I installed plasma 6.5 > and all the bug reports in the duplicates list appear to be for 6.5, 6.6 and > 6.7. Even if the ultimate problem is with CUPS, there must be something with > plasma that has started "triggering" the problem (possibly starting with the > 6.5 series). Seems like that but we also have many more people now using plasma since 6, the applet now has a badge showing the job count whereas before, it was just an icon, so much more noticeable now. As far as what we're doing differently, there is literally nothing AFAICT. We simply ask CUPS for dbus notifications for certain events (job and printer events) and then we react to the event signal. In the case we see with these issues, I have confirmed that we are simply not receiving the signal from CUPS through our basic connection. Our CUPS connection has not materially changed since Plasma5 and I can also confirm that the issue was happening then as well. I've reported the issue but have been unable to create consistent repro steps and until I (or someone) can give a definitive, always reproducible case, there is not much actionable.
Yes, I agree with Mike. The issue has been in Plasma for a very long time. I did notice the icon not hiding as it should but never reported that. Now with the newer queue view and the icon with the number is more noticeable. Martin Schnitkemper: The workaround has not been merged yet (https://invent.kde.org/plasma/print-manager/-/merge_requests/334) so it is not fixed in 6.7.1 or 6.7.2.
I'm using a network printer and it happens all the time, there are no special steps to reproduce the issue. In fact, my "network printer" is a USB printer on a Raspberry Pi running CUPS. The local CUPS connects to the remote CUPS by DNSSD. What I don't understand is that the job display is always correct when I open the queue by clicking on the print icon. So the detailed print queue display must retrieve the job information by another more reliable path. Can the icon not just use the same mechanism?
Is this relevant? https://github.com/OpenPrinting/cups/issues/1513#issuecomment-4158152176
(In reply to Gerhard from comment #24) > I'm using a network printer and it happens all the time, there are no > special steps to reproduce the issue. In fact, my "network printer" is a USB > printer on a Raspberry Pi running CUPS. The local CUPS connects to the > remote CUPS by DNSSD. > What I don't understand is that the job display is always correct when I > open the queue by clicking on the print icon. > So the detailed print queue display must retrieve the job information by > another more reliable path. Can the icon not just use the same mechanism? They use the same model, each a separate process, with it's own connection. Basically, the same code.
(In reply to valdikss from comment #25) > Is this relevant? > https://github.com/OpenPrinting/cups/issues/1513#issuecomment-4158152176 yeah, that's one of my original reports and Michael's recommendation for our connection, which made no difference in this issue, however.
*** Bug 522541 has been marked as a duplicate of this bug. ***
Git commit d705315c95ea36fdf467b5a4179a169aedea5927 by Mike Noe. Committed on 14/07/2026 at 12:27. Pushed by noee into branch 'master'. libkcups/plasmoid: Add a timer to reload the job queue when not empty FIXED-IN: 6.7.4 M +2 -1 src/libkcups/JobModel.h M +11 -0 src/plasmoid/main.qml https://invent.kde.org/plasma/print-manager/-/commit/d705315c95ea36fdf467b5a4179a169aedea5927
Git commit 85075675af4982fdff6daaaffacbd2dc7cf6b3b3 by Mike Noe. Committed on 15/07/2026 at 21:10. Pushed by noee into branch 'Plasma/6.7'. libkcups/plasmoid: Add a timer to reload the job queue when not empty FIXED-IN: 6.7.4 (cherry picked from commit d705315c95ea36fdf467b5a4179a169aedea5927) Co-authored-by: Mike Noe <noeerover@gmail.com> M +2 -1 src/libkcups/JobModel.h M +11 -0 src/plasmoid/main.qml https://invent.kde.org/plasma/print-manager/-/commit/85075675af4982fdff6daaaffacbd2dc7cf6b3b3
*** Bug 522896 has been marked as a duplicate of this bug. ***