updated to plasma 5.5 yesterday and mostly it is a slight improvement over its predecessor.
One glaring problem I am having though is that I cannot access sddm settings in configure desktop > startup and shut down > login screen
as you can see in this screenshot, after clicking on login/sddm it remains stuck on the autostart screen
indeed, whatever screen I am on before clicking on the login screen it remains stuck.
anybody else seeing this?
A question
http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42.1/
is the repo hosting plasma 5.5 right?
Not the same problem here. sddm menu item stuck only sometimes…not ever. 
yep
another issue I am seeing is that the screenlocker in plasma 5.5 doesn’t work.
When it goes into screenlock mode it takes me to a blank screen showing nothing but my desktop wallpaper - there is no way to log back into an active desktop other than to hit ctrl+alt+backspace x2 and re-login
Yes…same lockscreen problem here…i wrote about it here
https://forums.opensuse.org/showthread.php/511704-systray-problemS-and-lockscreen-problem-on-plasma-5-5
can you tell me something about the others bug in that post! Thanks!
EDIT: other bug: baloo stop finding files and folder. Just tried to reindex all…but i can’t see files or folder if i write in kde menu search box or from the plasmoid “search” 
I can confirm the problem with the SDDM settings.
Apparently just the window is not updated though. A workaround is to press any button (“All Settings” i.e. back, “Defaults”, or “Help”), and the settings should appear.
You don’t have to actually push the button, just click on it and hold the mouse button (this should fix the problem already), then move the mouse away to not trigger the action.
The lock screen works fine here. Did you do a full switch to the repo? You might have an incompatible mixture of packages installed otherwise.
I am on 13.2 and are additionally using the KDE:Qt5 repo, though.
Haven’t tries Baloo, I have it disabled because I have no use for that indexed search and don’t want to waste my free hard disk space (which is too low most of the time anyway…) for the index.
Thanks Wolfi. I have two question for you:
-how can i be sure to allign all packages to kde 5.5?
Thanks
Choose “View”->“Repositories” in YaST->Software Management, select the KDE:Frameworks5 repo in the list on the left, and click on “Switch all system packages to the versions from this repository” above the package list on the right.
Or run “sudo zypper dup --from name_or_number_of_your_KF5_repo”.
See also: SDB:Vendor change update - openSUSE Wiki
how can i “downgrade” to kde 5.4.3
Remove the repo and run “zypper dup”. But that can be dangerous if you have a lot of other repos.
and use the patched xembed-sni-Proxy?
Download the package and install it.
Or add my test repo, and xembed-sni-proxy to that version as explained above. You could also just switch that one package by selecting it and clicking on “Versions” below the package list in YaST. The repo doesn’t actually contain anything else anyway, though.
As I mentioned in the bug report, you should also be able to install my patched xembed-sni-proxy package with Plasma 5.5, by ignoring all conflicts.
This will overwrite the files of the standard packages, and might get lost when you update those though.
I will try to come up with a patched plasma5-workspace package in the next days… 
i really need icons in systray because is the laptop with i do the big part of my work!
Well, there only should be a problem with old-style XEmbed icons. Depending on the applications you use, you can make them use the new-style SNI protocol which should just work and would actually be the preferred “solution”…
xembed-sni-proxy is more or less a hack, implemented to make old-style icons show up at all.
thanks
yes, I did a full repo switch when the frameworks 5 repo was still on 5.4.3 and then updated via yast when 5.5 became available.
I’ve disabled the screenlocker in the meantime.
as for the xembed systray icons - these seem fixed for me in 5.5
seems this works at completing the update of the window - but once loaded it cannot be navigated (scrolled or switch to the advance tab) without a large delay.
I don’t want to highjack this thread but I can’t seam to find sddm settings in Configure Desktop, I have kcm_sddm installed.
I have Leap and just upgraded to plasma 5.5, any idea’s on what package I might be missing?
a possible bug I found in plasma 5.5
the gtk configure kcm modules seam to be missing, and gtk apps look “stranger” then with plasma 5.4 (for example fonts and menu’s in Firefox)
http://imgur.com/XWAcHHC
The obvious question:
Are you sure you are indeed running systemsettings5?
If kcm_sddm is installed, it should show up there.
It should be in “Startup and Shutdown”…
Your screenshot does look like KDE4’s systemsettings, otherwise the items would be arranged differently.
If you have kde-gtk-config5 installed it should show up in systemsettings5 as well.
This one should be in “Application Appearance”.
So, please run systemsettings5, and you should find both things.
Should be unrelated to the update to 5.5 though, unless the application menu’s behaviour changed in regards to which one of the two similar items (systemsettings or systemsettings5) is shown/hidden, but I don’t think so…
kde system settings in my menu is from kde4 there is kde5 version but that one is not in my menu?
I did a live upgrade from 13.2 to Leap and although I had plasma 5 on 13.2 it seams I still have a few kde4 apps running around any idea how to get rid of them and use plasma 5 apps
edit the menu you probably want to keep the systemsettings from 4 also since ther is still some mixing of versions but name thm differently
tanks guys did that and now the launcher starts systemsettings5 and I can see the gtk decorations, the reason they seamed strange was that plasma 5.5 defaulted to adwaita instead of breeze.
I did a test and created another user, in the new user’s menu the launcher was still systemsettings from kde4, there is a plasma5 systemsettings desktop file but plasma seams to default to the older one in
/usr/share/applications/kde4/
is there a way to force plasma to use the launchers from /usr/share/applications/ instead?
Well, the problem is that both systemsettings and systemsettings5 are called “Configure Desktop” in Leap.
The application menu then hides one of the duplicate entries.
We always had/have a patch in openSUSE to rename KDE4’s systemsettings to “Configure Desktop”, and we have the same for systemsettings5.
Since the switch to Plasma5 as default, KDE4’s systemsettings is being renamed to “Configure KDE4 Applications”.
But, this patch is only being applied for openSUSE 13.2 and higher.
And when Leap was introduced (long after the switch to Plasma5 was made), it was announced as 13.15 actually (in OBS at least) as it is based on SLE12.
In this case this was overlooked, so the wrong patch is applied in Leap and KDE4’s systemsettings is still called “Configure Desktop” as well.
I submitted a fix to the devel repo already, so this should be ok in the next Plasma update for Leap.
Unfortunately, there’s still one problem left then:
openSUSE’s translation team (which I am not part of) neglected to translate this at all since years.
So for other languages, both still will be called “System Settings” (in the upstream translation), as is the case in Tumbleweed.
I hope we can get this fixed as well though.
For now, a workaround would be to create a menu entry for systemsettings5 yourself, or uninstall kdebase4-workspace-addons (which contains the KDE4 systemsettings) if you don’t want/need it.
I did a live upgrade from 13.2 to Leap and although I had plasma 5 on 13.2 it seams I still have a few kde4 apps running around any idea how to get rid of them and use plasma 5 apps
Other than systemsettings/systemsettings5, there shouldn’t be a problem.
Not all applications are ported to KF5 yet, so this is even to be expected.
You can perfectly run KDE4 applications in Plasma5 (KDE even takes care that they are integrated), as you can run them in any other desktop environment, or even MacOS X and Windows.
tanks wolfi323 I’ll patch the desktop file manually.
The mentioned screenlocker problem seems to have been a packaging bug:
http://lists.opensuse.org/opensuse-kde/2015-12/msg00019.html
Should be fixed soon or even now already.
I think it’s related to which theme you actually use then, that might be the reason why I couldn’t reproduce it… 