Hi all,

My first time posting in the KDE forums, excuse me if I have posted in the wrong section because I cannot see a "support section" in the forum except for searching with firefox and the word support was highlighted in this section.

In a nutshell I use kali KDE, plasma v5. I have been using KDE since kali was backtrack so I am pretty familiar with it.
My previous install on another laptop gave me a similar issue as stated in the title bar.

Just to clarify on this before anyone starts with the good old "have you done this or this" or even worse "have you googled it" this is my checklist:
I have wiped my .cache
I have wiped my .config
I have rebuilt the plasma-org.kde.plasma.desktop-appletsrc
I have wiped kactivitymanagerd/resources/database
I have wiped my kdeglobals
I have wiped /var/tmp/kdecache
I have run the command kbuildsycoca4 --noincremental
I have done a apt- install --reinstall desktop-base kali-defaults kde-plasma-desktop kde-standard plasma-workspace plasma-desktop
I have done a apt purge kde-plasma-desktop kde-standard plasma-workspace plasma-desktop and redone the apt install kde-plasma-desktop kde-standard plasma-workspace plasma-desktop
I even tried gdb which yielded no results anyway (except a few qt errors which I fixed anyway)
I have tried to create a new user after all of this too...

and yet I still have these issues:
bottom panel might not even load (unless I do killall plasmashell and then plasmashell)
systray is ALWAYS missing
"add to panel" does nothing
can't right click on panels or desktop anymore
krunner doesn't pick up applications properly (and I have rebuilt baloo plenty times to test)

So my question is...seriously wtf is going on here? I have wasted 4 days trying fixes and rebuilding kde installs but it's still not working (even after a purge and wiping cache files)
On a side note, I have done 3 system updates since my fresh install, then all of a sudden after a update like 4/5 days ago this **** show happened.

here is what konsole spits if I try run plasmashell (after all of the attempts above):

Code: Select all

org.kde.plasmaquick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:61:28: Unable to assign [undefined] to int
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:52:27: Unable to assign [undefined] to int
trying to show an empty dialog
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
trying to show an empty dialog
Plasma Shell startup completed
org.kde.plasmaquick: New Applet  "Application Launcher" with a weight of 89
org.kde.plasmaquick: New Applet  "Digital Clock" with a weight of 34
trying to show an empty dialog
org.kde.plasmaquick: Delayed preload of  "Application Launcher" after 0.917 seconds
Empty filename passed to function
KAStatsFavoritesModel::setFavorites is ignored
KActivities: Database connection:  "kactivities_db_resources_139679991263488_readonly"
    query_only:          QVariant(qlonglong, 1)
    journal_mode:        QVariant(QString, "wal")
    wal_autocheckpoint:  QVariant(qlonglong, 100)
    synchronous:         QVariant(qlonglong, 0)
Entry is not valid "kontact.desktop" 0x55778c8f12c0
Entry is not valid "ktp-contactlist.desktop" 0x55778c8f12c0
Entry is not valid "kontact.desktop" 0x55778c8f12c0
Entry is not valid "ktp-contactlist.desktop" 0x55778c8f12c0
Closing SQL connection:  "kactivities_db_resources_139679991263488_readonly"
trying to show an empty dialog
org.kde.plasmaquick: Applet "Application Launcher" loaded after 94 msec
org.kde.plasmaquick: Delayed preload of  "Digital Clock" after 5.977 seconds
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
org.kde.plasmaquick: Applet "Digital Clock" loaded after 59 msec

The forum is (generally) all about support, so use the section that best fits the software you have the issue with. This section is about development with the KDE frameworks.

Generally, if you find an issue, you could try with a LiveCD with a different distribution to decide if the issue is specific to the distribution you are using.

kde-cfeck wrote:The forum is (generally) all about support, so use the section that best fits the software you have the issue with. This section is about development with the KDE frameworks.

Ok, thanks.

I guess the mods can move it to the relevant section if need be, although it could be considered part of development as this is a multi distro issue.

kde-cfeck wrote:Generally, if you find an issue, you could try with a LiveCD with a different distribution to decide if the issue is specific to the distribution you are using.

According to my research this has occurred in kubuntu, open suse and manjaro with more specific issues in red hat (related to steam, dropbox and pidgin). I obviously scoured the net to fix this myself without needing to post in a forum because that is usually quicker that trying to figure it out step by step through a forum to begin with, especially if you are competent with linux already.

The development section is for developers that need help while developing with KDE frameworks or libraries.

This is a bug in the latest update and hopefully, they will fix it soon.

From Luigi Toscano:

The issue seems to come from the missing update of Frameworks packages in testing.
Only few packages from Frameworks 5.49 migrated to testing, and the vast majority of them are still version 5.47, but the newer version of Plasma was built against Frameworks 5.49. Just update all Frameworks 5.47 packages to the unstable version (5.49) and Plasma should work again.

The bug should solve itself when all the packages migrate. Packagers should ensure that the migration of Frameworks happens all at the same time, and it blocks the dependent packages.

avashNekros wrote:This is a bug in the latest update and hopefully, they will fix it soon.

From Luigi Toscano:

The issue seems to come from the missing update of Frameworks packages in testing.
Only few packages from Frameworks 5.49 migrated to testing, and the vast majority of them are still version 5.47, but the newer version of Plasma was built against Frameworks 5.49. Just update all Frameworks 5.47 packages to the unstable version (5.49) and Plasma should work again.

The bug should solve itself when all the packages migrate. Packagers should ensure that the migration of Frameworks happens all at the same time, and it blocks the dependent packages.

Thanks for the info, I will be sure to look further into these framework packages as mentioned.