Bug 456345 - Task Manager and Desktop Don't Load on Login / Launch
Summary: Task Manager and Desktop Don't Load on Login / Launch
Status: CLOSED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.25.2
Platform: Arch Linux Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://git.harting.dev/ALHP/ALHP.GO/...
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-05 07:28 UTC by nekonexus
Modified: 2022-07-06 16:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
nekonexus: Wayland?
nekonexus: X11+
nekonexus: Usability+


Attachments
Global Env Files and journald Log (21.65 KB, application/zip)
2022-07-05 07:28 UTC, nekonexus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nekonexus 2022-07-05 07:28:13 UTC
Created attachment 150403 [details]
Global Env Files and journald Log

SUMMARY
Describing this issue is a bit strange, since it's just severe enough to be a pain but not severe enough that it isn't usable?
I have "control" of my desktop but only thanks to Yakuake auto-starting, but what happens here is this:
the (icons-only) task manager and the "desktop" (where you'd see wallpapers and application icons) are completely missing. (It doesn't even load my wallpaper; there's nothing to interact with at all if you don't have a terminal that auto-launches on login.)
The only semblance of whatever is going on here is some vague failures in journald that I don't understand at all.

This only started the other day.... I want to say roughly around June 30th(? Can't quite remember) after an update.
I've no clue what's going on nor how to fix it - rebooting doesn't help and my filesystem checked out as clean/non-corrupt. :/


STEPS TO REPRODUCE
1. Login to Plasma via SDDM

OBSERVED RESULT
The Plasma shell doesn't load correctly

EXPECTED RESULT
The Plasma shell should load as normal

SOFTWARE/OS VERSIONS
Linux : Arch Linux
Kernel: Linux 5.17.9-258-tkg-pds-llvm ( https://github.com/frogging-family/linux-tkg )
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
GPU: Nvidia RTX 2080 Ti
GPU Driver Version:  515.48.07 (Proprietary)

ADDITIONAL INFORMATION
Moving my entire user config folder to a temporary location does not seem to fix the issue, so something deeper is going on, somehow. :/

I'm including the mentioned journald log and files that set environment variables, though nothing I've done seems to make any difference in solving (or cause) the issue. :/

I did additionally (originally) use an x86-64-v3 repo for this, but I did downgrade from that repo to the official Arch repos and this made no difference - the issue persisted. :/

And to clarify, I only have one display connected.
Comment 1 Antonio Rojas 2022-07-05 08:30:40 UTC
"Error loading QML file.\n12: plugin cannot be loaded for module \"org.kde.plasma.activityswitcher\": Cannot load library /usr/lib/qt/qml/org/kde/plasma/activityswitcher/libactivityswitcherextensionplugin.so: (/usr/lib/libtaskmanager.so.6: undefined symbol: _ZNK8KWayland6Client12PlasmaWindow12resourceNameEv)\n"

You're still mixing packages from different sources. This is a local/installation problem.
Comment 2 nekonexus 2022-07-05 19:32:10 UTC
@Antonio This wasn't an issue literally overnight, so were components seperated from pre-existing packages to new ones?
Comment 3 nekonexus 2022-07-05 20:36:08 UTC
Additionally, I searched for the library that claims to be missing and my package manager says I have it installed; please don't dismiss this issue so readily without conversation.
Comment 4 nekonexus 2022-07-05 20:39:24 UTC
Additionally, everything is from that other repo (originally); regardless, I did downgrade *everything without exception* to the *official repos* and the issue *still persists.* (pacman -Syuu)

I guarantee you, at that point, there is nothing being mixed.
Comment 5 Nate Graham 2022-07-06 16:57:38 UTC
I'm afraid Antonio is right, or at least in the ballpark. The error you're seeing is caused by mixing incompatible library versions that were not all compiled against one another, and there is no chance that it's a KDE problem. It's either a distro packaging problem, or a user configuration problem.