Bug 472277 - Specific configs makes KDE plasma mostly unusable
Summary: Specific configs makes KDE plasma mostly unusable
Status: RESOLVED DUPLICATE of bug 469445
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.6
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-15 11:48 UTC by labmasterX55
Modified: 2023-09-11 22:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description labmasterX55 2023-07-15 11:48:17 UTC
As mentioned in
https://discuss.kde.org/t/where-is-the-kde-plasma-desktops-config-file/2939

Here is a detailed bug report;
after updating Nobara 38's softwares (Fedora based OS)  and changing some random plasma settings, the desktop's files became invisible and unclickable, and all programs weren't able to start (simply started loading for a few seconds and then stopping), sometimes saying that there was insufficient memory

This issue is specific to the KDE plasma because it didn't affect Gnome and other desktop environments and it affect both Plasma X11 and Plasma Wayland

The issue persisted after reinstall of the KDE desktop environment, even full deletion of the desktop environment (which I severely regretted doing) and installing it cleanly again

After moving away the plasma-org.kde.plasma.desktop-appletsrc file, and rebooting, everything worked flawlessly again with no issues

Here is the plasma-org.kde.plasma.desktop-appletsrc in question, I put it in github because it was 11mb in size

https://github.com/SomeUser9/Unusable-KDE-plasma-Config/blob/main/plasma-org.kde.plasma.desktop-appletsrc

Thank you for making an indispensable desktop environment, it is by far my most preferred desktop environment of all, no matter the few bugs that may appear every now and then
Best regards

Some User
Comment 1 Nate Graham 2023-09-11 22:20:23 UTC

*** This bug has been marked as a duplicate of bug 469445 ***