The libkf5completion5 package doesn't install the '/usr/lib/x86_64-linux-gnu/qt5/plugins/designer/kcompletion5widgets.so' plugin as it installed via the 'libkf5completion-dev' package. Normally this is not an issue as mostly it's not needed at runtime, but if an application uses the plugin via scripting (like the Kolab account wizard from the kdepim-runtime package does), then certain ui widgets (like KLineEdit) will be broken. STEPS TO REPRODUCE 1. Install kmail without any development packages being installed (like on a fresh install) 2. Try to create a Kolab account by going through the account wizard OBSERVED RESULT On the dialog with the e-mail/password fields the KLineEdit and KPasswordLineEdit widgets are not shown, only the label next to them EXPECTED RESULT All of the widgets should be properly shown. If you install the 'libkf5completion-dev' package (and its dependencies), then the widgets will be properly shown. Obviously an application shouldn't depend on a development package, therefore the libkf5completion5 package should install the '/usr/lib/x86_64-linux-gnu/qt5/plugins/designer/kcompletion5widgets.so' file. It's possible that this is happening with other (which ship designer plugins) packages as well. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.4.0-52-generic OS Type: 64-bit ADDITIONAL INFORMATION I was looking for the place where the packaging itself is maintained at places like https://invent.kde.org/neon/neon-packaging, but couldn't find it for libkf5completion. Is the package taken from Ubuntu (and in turn from Debian?). Anyhow, I'm more than happy to also send patch if I'm pinpointed to the right placel
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!