Bug 448307 - Plasmashell settings (?) (eg. "Desktop Folder Settings - Plasma") not correctly starting
Summary: Plasmashell settings (?) (eg. "Desktop Folder Settings - Plasma") not correct...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (show other bugs)
Version: 5.22.90
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-12 11:09 UTC by jonumand
Modified: 2022-01-13 03:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Terminal under empty Application Launcher Settings (93.95 KB, image/png)
2022-01-12 11:09 UTC, jonumand
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jonumand 2022-01-12 11:09:42 UTC
Created attachment 145358 [details]
Terminal under empty Application Launcher Settings

SUMMARY

I just updated my Kubuntu packages (and restarted), and wanted to change my wallpaper using the UI, but nothing ever came "up" after right clicking and selecting "Configure Desktop ..." besides the titlebar:  "Desktop Folder Settings - Plasma" over the current window. 
I then tried other plasmashell settings (eg. Application Launcher Settings), same result.
I'm uncertain whether I'm filing this bug under the right component 

STEPS TO REPRODUCE
1. Open any Plasmashell Settings
2. Observe

OBSERVED RESULT
An empty window

EXPECTED RESULT
An window with the Desktop Folder Settings UI

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  5.22.90
(available in About System)
KDE Plasma Version:  5.22.90
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Kubuntu 21.10 "beta" ppa
Kernel:5.15.13-xanmod1
Theme: Breeze Dark
Comment 1 jonumand 2022-01-12 13:00:29 UTC
After a quick restart, everything worked again.

I don't know what happend in between rebooting for the 1st time and now, but it might be something to look into?

I'm sorry if this is a known bug, but I couldn't find a similar bug in the search-box.
Comment 2 Nate Graham 2022-01-13 03:17:39 UTC
If you didn't restart after your system upgrade, that would cause it. You should always restart after updating, especially after a giant system upgrade. Not doing so causes weird issues like this. :)