Created attachment 390664 [details] emerge --info The following sets are installed without a problem in my Gentoo @kde-frameworks-live @kde-plasma-live @kde-applications-live (Not to mention Qt5.4.0_rc and it's sets) The problem seems to be irrelevant with other packages and/or Kf5 re-install. I have written in ~/xinitrc "spnavd_ctl x11 start exec startkde" but when I enter xinit a screen with a bar filling apears and then just a black screen with a cursor, that is not showing up any menu or something. I don't know a way to log my tty1 so that I can show it to you. I will write down a few messages so that you can get an idea. I am afraid that this message: "ecompressdir: bzip2 -9 /usr/share/doc scanelf: rpath_security_checks(): Maybe? sec problem with DT_RUNPATH='lib64' in /var/tmp/portage/kde-base/plasma-workspace-9999/image/usr/lib64/qt5/plugins/phonon_platform/kde.so scanelf: rpath_security_checks(): Maybe? sec problem with DT_RUNPATH='lib64' in /var/tmp/portage/kde-base/plasma-workspace-9999/image/usr/lib64/qt5/plugins/phonon_platform/kde.so" after compilation of kde-base/plasma-workspace-9999:5::kde is relevant and warns me about something I dont understand. emerge -pv1 kde-base/plasma-workspace-9999:5::kde [ebuild R *] kde-base/plasma-workspace-9999:5::kde USE="X dbus gps qalculate -debug -prison {-test}" 0 KiB
Is plasma-shell runnig? Does it work if you launch via a display manager (eg. lightdm)?
I think it is still problematic with sddm. I am not sure about this. I will check on this later this evening. Also I have to mention that it reports (tty1) errors about xcb and Bad Windows. Anyway I will post later with more info.
Well I had no luck trying with SDDM. Although I had notications from Skype and Yakuake it did not manage to go beyond the screen with the bar, not even to get the a black screen. Some messages from tty1 when opened with xinit: "_get_desktop_bg_surface: assertion 'iRootPixmapID !=0' failed" "QInotifySystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory." After I press the Ctrl-C combination to tty1 I get: "Error could not contact kdeinit5!" which seems normal to me, because it is printed after kdeinit5 has exited but it is printed as an error. Command #ps aux | grep plasma in tty2 (root account) showed up with these: -> petros 6028 0.5 1.6 505600 65700 ? Sl 20:46 0:00 /usr/bin/plasmashell --shut-up root 6229 0.0 0.0 4332 732 tty2 S+ 20:46 0:00 grep --colour=auto plasma <- PS. KDE had been "launched" via SDDM in this example.
Just like I did two weeks ago, I had to remove *each and every* folder and file in ~/.config and ~/.local. It did the trick but I am with an entirely "new" user. Everything is lost. Again. Maybe when I see it stable in portage I will consider using KDE5. Till then...thanks for the help :)
Unfortunately KDE has a pretty bad rep for breakage with old configs. It could be interesting to try and narrow down which KDE config caused the breakage though.
It definatelly was not plasmarc, plasmashellrc, systemsettingsrc, kwinrc, another kactivities-related file. I can not recall other files. I deleted a lot of them and the problem even was present after the whole ~/.config was gone. After the deletion of ~/.local I could log in and see KDE. Of cource in a totaly default DE.
If you are interested in debugging, it could be worth filing a bug with upstream. There's not much we can do downstream about it sorry.
Some times cairo-dock and tilda are running in a black screen, without any widgets being around (various control + F combinations work). Then I start konsole via cairo-dock or Alt-F2 and I type -- $eval `dbus-launch` $ kdeinit5 $ plasma-shell -- After a minute KDE is up and running. The error message if I don't run "eval..." is this "QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to /tmp/petros". Google gave me this result -> https://bbs.archlinux.org/viewtopic.php?id=164647. It is(?) only a cheap workaround but someone may find it helpfull. PS.Should I add "exec eval 'dbus-launch'" in ~/.xinitrc?
Does it work if (In reply to Petros from comment #8) > Some times cairo-dock and tilda are running in a black screen, without any > widgets being around (various control + F combinations work). Then I start > konsole via cairo-dock or Alt-F2 and I type > -- > $eval `dbus-launch` > $ kdeinit5 > $ plasma-shell > -- > > After a minute KDE is up and running. Does startx work if you put those commands in your xinitrc instead of startkde? Also, does startkde run or return any interesting output when run from console?
In both cases a message about "$DISPLAY not set" is shown.
