Created attachment 130838 [details] Example of a more thorough printer test page Saw this output today during an otherwise routine `apt upgrade', during the dpkg processing of the breeze package from the neon unstable repository, currently version 4:5.19.4+p20.04+git20200812.0306-0: dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x Leaving 'diversion of /usr/share/cups/data/default-testpage.pdf to /usr/share/cups/data/default-testpage.pdf.distrib by breeze' This is obviously related to the preinst[1] and prerm[2] scripts which intend to replace the generic CUPS printer test page with a KDE branded one. This brings me to the second issue regarding the package, which is that I think the included printer test page is long overdue for a quick once-over from the Visual Design Group for its aesthetics, and should also be reevaluated regarding its core competency, namely testing print output. I've attached an example of what I think would be a good target for those functional improvements. I also thought it might be useful to have an open bug report about it now, before dpkg 1.20 gets imported into the Ubuntu repositories, as will likely happen before the Groovy freeze. To be clear though, this does not currently result in any unanticipated results when installing the package using the version of dpkg distributed with Focal; it will likely start to do so in October. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04.1 LTS "Focal Fossa" with Neon/untable package archives added KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 [1]: https://packaging.neon.kde.org/kde/breeze.git/tree/debian/breeze.preinst?h=Neon/unstable [2]: https://packaging.neon.kde.org/kde/breeze.git/tree/debian/breeze.prerm?h=Neon/unstable
Thank you for your bug report! However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since before 01/01/2025. Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's. Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report. Thanks for understanding!