I hope someone can help.
I was tinkering last week. I think I'd just updated using slackpkg. 11th feb changes. On reboot had "blackl" screen but as there were updates to xorg I reinstalled the Nvidia driver ( usually works).Anyway still black screen although by right clicking I could get the desktop settings window ( without any content). I switched to xfce which was Ok.
In trying to get Plasma working again I've buggered something up. xinitrc.plasma still shows only black screen but xinitrc.xfce loads xfce then carries on to load plasma over the top Most things work as you would expect them to in plasma although the only way out is alt,control and backspace. This drops back to xfce and then to a console prompt.Talk about weird.

I've tried renaming .config, .cache, ksmserverrc and ~/.kde and rebooting but now I'm stumped.

I'm running alienbob's current and kernel 4.3.

Any ideas anyone?

Mike

Sounds like the windowmanager (kwin) and/or plasmashell are not running. Try finding out with "ldd" on the binaries of the "plasma-workspace" and "kwin" packages to see if you are missing any library.

Mike,

I too have recently encountered trouble arising after upgrading via slackpkg. I found that slackpkg does not always overwrite executable shell scripts such as /usr/bin/startkde in my particular case, even when instructed to upgrade a given package, kde-workspace-4.11.22-x86_64 in this instance. I finally resolved the resulting fatal error arising from a startkde script from KDE4 calling on a KDE4 kstartupconfig4 only by completely removing kde-workspace-4.11.22, then running upgradepkg --reinstall plasma-workspace-5.5.4, then the same for Eric's kde-workspace-4.11.22-x86_64-alien, to be DEAD CERTAIN that ONLY Eric's proper binaries and scripts got installed, and remained on the system. This properly restored Plasma to functionality, sans problems.

DON'T RELY ON SLACKPKG to upgrade a big, complex desktop environment like KDE for you! I'm going back to Eric's tried and true ways, detailed in his READMEs and will certainly use the vital --reinstall switch to insure that any package which may have somehow been compromised by other installations gets restored to fresh, functional status. "For want of a nail, the kingdom fell." For want of a script, my env turned to shit. Dig?

Thanks for the responses guys. I've checked for missing libraries and they seem to be OK.

I'm not sure how to proceed with the other suggestion. I don't know where all of these things get kicked off. I'm also a bit bemused by the fact that XFCE starts and then Plasma starts on top.;So visible on my dektop I hjave a plasma type task bar with an XFCE style panel at the same time.I've tried removing kde-workspace and reinstalling plasma workspace and have also done an upgradepkg --reinstall with Erics latest issue. No better.

A question. Would I expect to see Kwin running as a process? ie visible in ksysguard. Plasmashell is running.
Maybe I'll just have to wait for SlackWare 14.2 and do afresh install. Hope not.

Mike

PS if I right click on tghe desktop and select "leave" i get dropped back to XFCE.

Well if your running alien Bobs Current and you did a upgrade and rysnc his current you will have issues because as of Feb 1st it was not in sync with slackware. and mesa was one of them. if you want to run current you may want to just massconvert32.sh your own and keep an up to date mirror.
you will see 23 rd of February was the last update for the compat32 stuff
I see Pat has another one. running current is a work of art.
http://www.slackware.com/changelog/c...php?cpu=x86_64