Kf5 removeable progress in 2025?

[Daniel-I]

I did find an older 2024 post @ Can I remove kde5 things now?, which more or less suggested two approaches:

1. waiting for packages to become orphans; then remove
2. allowing sudo pacman -Rns kf5 to remove what it can

I’ve more or less been following these strategies; however, today I noticed that there really are only 5 packages that fail dependency checks when executiing

sudo pacman -Rns kf5

sudo pacman -Rns kf5
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing frameworkintegration5 breaks dependency 'frameworkintegration5' required by breeze5
:: removing kconfig5 breaks dependency 'kconfig5' required by breeze5
:: removing kconfigwidgets5 breaks dependency 'kconfigwidgets5' required by breeze5
:: removing kguiaddons5 breaks dependency 'kguiaddons5' required by breeze5
:: removing kiconthemes5 breaks dependency 'kiconthemes5' required by breeze5
:: removing kirigami2 breaks dependency 'kirigami2' required by breeze5
:: removing kwindowsystem5 breaks dependency 'kwindowsystem5' required by breeze5
:: removing kwayland5 breaks dependency 'kwayland5' required by kwayland-integration
:: removing kwindowsystem5 breaks dependency 'kwindowsystem5' required by kwayland-integration
:: removing kauth5 breaks dependency 'kauth5' required by manjaro-settings-manager
:: removing kcoreaddons5 breaks dependency 'kcoreaddons5' required by manjaro-settings-manager
:: removing kitemmodels5 breaks dependency 'kitemmodels5' required by manjaro-settings-manager
:: removing knotifications5 breaks dependency 'knotifications5' required by manjaro-settings-manager-knotifier
:: removing frameworkintegration5 breaks dependency 'frameworkintegration5' required by oxygen5
:: removing kcompletion5 breaks dependency 'kcompletion5' required by oxygen5
:: removing kconfig5 breaks dependency 'kconfig5' required by oxygen5
:: removing kconfigwidgets5 breaks dependency 'kconfigwidgets5' required by oxygen5
:: removing kguiaddons5 breaks dependency 'kguiaddons5' required by oxygen5
:: removing ki18n5 breaks dependency 'ki18n5' required by oxygen5
:: removing kwidgetsaddons5 breaks dependency 'kwidgetsaddons5' required by oxygen5
:: removing kwindowsystem5 breaks dependency 'kwindowsystem5' required by oxygen5
:: removing kcompletion5 breaks dependency 'kcompletion5' required by plasma5-integration
:: removing kconfig5 breaks dependency 'kconfig5' required by plasma5-integration
:: removing kconfigwidgets5 breaks dependency 'kconfigwidgets5' required by plasma5-integration
:: removing kcoreaddons5 breaks dependency 'kcoreaddons5' required by plasma5-integration
:: removing ki18n5 breaks dependency 'ki18n5' required by plasma5-integration
:: removing kiconthemes5 breaks dependency 'kiconthemes5' required by plasma5-integration
:: removing kio5 breaks dependency 'kio5' required by plasma5-integration
:: removing kjobwidgets5 breaks dependency 'kjobwidgets5' required by plasma5-integration
:: removing knotifications5 breaks dependency 'knotifications5' required by plasma5-integration
:: removing kservice5 breaks dependency 'kservice5' required by plasma5-integration
:: removing kwayland5 breaks dependency 'kwayland5' required by plasma5-integration
:: removing kwidgetsaddons5 breaks dependency 'kwidgetsaddons5' required by plasma5-integration
:: removing kwindowsystem5 breaks dependency 'kwindowsystem5' required by plasma5-integration
:: removing kxmlgui5 breaks dependency 'kxmlgui5' required by plasma5-integration

1. breeze5
2. oxygen5
3. plasma5-integration
4. manjaro-settings-manager
5. kwayland-integration

As far as I can figure out, manjaro-settings-manager and kwayland-integration for sure will keep elements of kf5 around for a bit until they transition.

But when I check what removing breeze5, oxygen5, and plasma5-integration would impact, the only dependencies mentioned are OPTIONAL, so not required?

sudo pacman -Rns breeze5 (2 optional dependencies)

checking dependencies...
:: breeze optionally requires breeze5: Breeze widget style for Qt5 applications
:: qt5-quickcontrols2 optionally requires qt5-graphicaleffects: for the Material style

Packages (4) kirigami2-5.116.0-1  qt5-graphicaleffects-5.15.17-1  qt5-quickcontrols-5.15.17-1  breeze5-6.3.6-1

Total Removed Size:  7.83 MiB

sudo pacman -Rns oxygen5

checking dependencies...

Packages (2) oxygen-6.3.6-1  oxygen5-6.3.6-1

Total Removed Size:  19.29 MiB

sudo pacman -Rns plasma5-integration (1 optional dependency)

checking dependencies...
:: plasma-workspace optionally requires plasma5-integration: use Plasma settings in Qt5 applications

Packages (16) kbookmarks5-5.116.0-1  kcrash5-5.116.0-1  kdbusaddons5-5.116.0-1  kded5-5.116.0-1  kglobalaccel5-5.116.0-1  kio5-5.116.0-2  kitemviews5-5.116.0-1
              kjobwidgets5-5.116.0-1  kservice5-5.116.0-1  ktextwidgets5-5.116.0-1  kwallet5-5.116.0-3  kxmlgui5-5.116.0-1  qca-qt5-2.3.10-3  solid5-5.116.0-1  sonnet5-5.116.0-1
              plasma5-integration-6.3.6-1

Total Removed Size:  50.39 MiB

Not sure why the oxygen5 removal strategy didn’t include one optional dependency… likely the cause of why it was wanting to remove the plasma6 version of the oxygen theme as well… so I’ll need to adjust my command until only the one oxygen5 package is removed… if/when I prceed.

Does anyone know whether removing breeze5, oxygen5, and/or plasma5-integration would have negative consequences under plasma6? I’m assuming not as only “optional dependency” checks are noted, but I figured it’s better to ask than assume.

I imagine once any of these packages were removed that sudo pacman -Rns kf5 will purge more as well.

[Aragorn]

@Daniel-I

Not sure why the oxygen5 removal strategy didn’t include one optional dependency…

Optional dependencies are not real dependencies. It means that the package to be removed can be used by the other package if present, but is not required for said other package to work.

@Daniel-I

Does anyone know whether removing breeze5, oxygen5, and/or plasma5-integration would have negative consequences under plasma6?

No, but not every Plasma application has been ported to qt6 yet, and thus there may be packages that still require some of those things.

@Daniel-I

I imagine once any of these packages were removed that sudo pacman -Rns kf5 will purge more as well.

It will unfortunately still take quite a while before every Plasma application gets ported to qt6, and thus I’m afraid that most of us will still have to tolerate the presence of qt5 en kf5 on our systems for quite a while.

[Teo]

Just for reference from the other big framework, GTK. Upstream will now deprecate and remove GTK 2, which was released … In 2002.

I bet it will be several years until all dvelopers convert their apps.

[Metam0rph0sis]

I only know of two applications from the KDE project, which still require qt5/kf5 is Krita (porting process going on and you can even download a working version as appimage) and okteta.

But there are also a lot of third-party applications that still require QT5, like KeepassXC. So yes, it will probably take another year or two

[Daniel-I]

Thank you everyone for the replies!

I guess what I have to keep in mind in that plasma5 got up to what… 5,27.x? a lot of sub/versions… so we’re still fairly “early days” with plasma6 at only 6.3.6 in stable.

For lack of knowing a better way, I took a peek at what all might be requiring qt5-base and found packages like smplayer and vlc-gui-qt via pacman -Qi qt5-base

Since I use breeze I guess I could safely dump oxygen5… but that would feel kinda hollow as far as making real progress. I’ll keep things status quo for now.

Thank you for the sanity check.