Sent: Tuesday, June 28, 2016 at 4:07 PM From: "Bruce Dubbs" <bruce.du...@gmail.com> To: "BLFS Support List" <blfs-support@lists.linuxfromscratch.org> Subject: Re: [blfs-support] Plasma starts with black screen Cliff McDiarmid wrote: > *Sent:* Tuesday, June 28, 2016 at 1:05 AM > *From:* "Bruce Dubbs" <bruce.du...@gmail.com> > *To:* "BLFS Support List" <blfs-support@lists.linuxfromscratch.org> > *Subject:* Re: [blfs-support] Plasma starts with black screen > Cliff McDiarmid wrote: > > > > From: "Cliff McDiarmid" <cliffhan...@gardener.com> > > To: "BLFS Support List" <blfs-support@lists.linuxfromscratch.org> > > Subject: Plasma starts with black screen > > Sent: Thursday, June 23, 2016 at 11:00 PM > > From: "Cliff McDiarmid" <cliffhan...@gardener.com> > > To: "BLFS Support List" <blfs-support@lists.linuxfromscratch.org> > > Subject: Plasma starts with black screen > > Cliff McDiarmid wrote > >>>> I'm resurrecting this thread because this is the 4th time of > >>>> building Plasma(nothing unusual), but this time it is into a brand > >>>> new 7.9 systemd box. The new LFS is running fine using the nouveau > >>>> driver and boots into Xorg. But once again, after installing all > >>>> dependencies for Frameworks and Plasma 5.6.2, it will not boot. I > >>>> can't tell you the frustration involved here. An error log is > >>>> attached. > >>>> > >>>> I'm not using any login manager. This error log is from the the > >>>> command line after 'startx' and I'm getting a message saying > >>>> > >>>> "All shell packages missing. This is an installation issue, please > >>>> contact your distribution" > >>>> > >>>> If I boot into twm I can run konsole from an xterm window which > >>>> seems okay. If I then run plasmashell from xterm I get similar > >>>> errors refering to "All shell packages missing". > >>>> > >>>> How is this whole thing possible? KDE4 seemed so easy. Any ideas > >>>> here, I've trawled the internet with no real success. > >>>> > >>>> thanks > >>>> > >>>> Cliff Got something very similar to you the other day when I built > >>>> plasma 5.6.4. After a little bit of digging found out it was a gcc > >>>> 6.x issue in qtdeclarative (part of qt-5.6). Fixed using > >>>> -fno-delete-null-pointer-checks -fno-lifetime-dse in C(XX)FLAGS see > >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1331593 which is very > >>>> similar to what you describe > >>> Just updated Qt 5.6.0 to 5.6.1 without the additional flags > >>> suggested. Still same result with Plasma , i.e. black screen with > >>> mouse pointer and "All shell packages missing" message and nothing > >>> more. > >>> > >>> Do I now recompile 5.6.1 with the flags Martin suggested or update > >>> Plasma yet again to 5.6.5! You takes your pick it seems. > >>> > >>> Cliff > >>> > >>> > >> > >>> Try just downloading the individual package qtdeclarative-5.6.1 and > >>> compiling that from here > > > >>> I've taken the rebuild route once again using latest frameworks/plasma > >> into the new LFS. > >> > >> So far when I get to installing kinit-5.23.0 I get: > >> > >> Failed to set capabilities on file > >> `/opt/kf5/lib/libexec/kf5/start_kdeinit' (Operation not supported) > > > >> Do you have /sbin/setcap? Is it in root's path when you install? I admit > >> that I have /sbin and /usr/sbin in my normal user path so I don't know if > >> this is an issue or not. > > > >> Yes have that under /usr/sbin and it's in roots path. I sourced > >> /etc/profile > as well but I still get the 'error'. > > > >> What I have is: > > > >> $ getcap /opt/kf5/lib/libexec/kf5/start_kdeinit > >> /opt/kf5/lib/libexec/kf5/start_kdeinit = cap_sys_resource+ep > > > >> I'd makes sure that setcap is in root's path and reinstall. > > > >> Is this a concern in respect of the infamous black screen I've had? > > > >> I can't really say. > > > > Right. I'm back where I started. You may know I compiled 5.23.0/5.6.5 into a > brand new LFS system. > > > > I still get the same black screen and movable cursor and a warning about > > "All > shell packages missing". The short error file is attached, but it seems to > contain the same 'errors' as before. > > > > What I have got is a fully functional Xorg where I can run konsole in xterm. > > > > If I then start plasmashell from xterm I get: > > > > org.kde.kwindowsystem: Could not find any platform plugin > > org.kde.kwindowsystem: Could not find any platform plugin > > Service started, version: 7.0.0 > > Failed to load the OSD QML file file from "" > > detected kglobalaccel restarting, re-registering all shortcut keys > > We have no shell handlers installed. > > > > I resisted Martins suggestion concerning qtdeclarative-opensource-src-5.7.0 > until the end. When installed with the editing of the QMAKE_CXXFLAGS, it made > no > difference. > > > > I have a non functioning Plasma yet again > > >What is your kf5 environment? I set up the environment with: > > >$ cat /etc/profile.d/kf5.sh > ># Begin /etc/profile.d/kf5.sh > > >export KF5_PREFIX=/opt/kf5 > > >pathappend $KF5_PREFIX/bin PATH > >pathappend $KF5_PREFIX/lib/pkgconfig PKG_CONFIG_PATH > > >pathappend /etc/xdg XDG_CONFIG_DIRS > >pathappend $KF5_PREFIX/etc/xdg XDG_CONFIG_DIRS > >pathappend /usr/share XDG_DATA_DIRS > >pathappend $KF5_PREFIX/share XDG_DATA_DIRS > > >pathappend $KF5_PREFIX/lib/plugins QT_PLUGIN_PATH > > >pathappend $KF5_PREFIX/lib/qml QML2_IMPORT_PATH > > >pathappend $KF5_PREFIX/lib/python2.7/site-packages PYTHONPATH > > ># End /etc/profile.d/kf5.sh > > Thanks Bruce mine is not identical but surely sufficient > export KF5_PREFIX=/opt/kf5 > pathappend $KF5_PREFIX CMAKE_PREFIX_PATH > pathappend $KF5_PREFIX/bin PATH > pathappend $KF5_PREFIX/lib/pkgconfig PKG_CONFIG_PATH > pathappend $KF5_PREFIX/lib/python2.7/site-packages PYTHONPATH > pathappend /etc/xdg XDG_CONFIG_DIRS > pathappend $KF5_PREFIX/etc/xdg XDG_CONFIG_DIRS > pathappend /usr/share XDG_DATA_DIRS > pathappend $KF5_PREFIX/share XDG_DATA_DIRS > pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH > pathappend $QT5DIR/lib/qt5/plugins QT_PLUGIN_PATH > pathappend $KF5_PREFIX/lib/qt5/plugins QT_PLUGIN_PATH > pathappend /usr/lib/qt5/qml QML_IMPORT_PATH > pathappend $QT5DIR/lib/qt5/qml QML_IMPORT_PATH > pathappend $KF5_PREFIX/lib/qt5/qml QML_IMPORT_PATH > pathappend /usr/lib/qt5/qml QML2_IMPORT_PATH > pathappend $QT5DIR/lib/qt5/qml QML2_IMPORT_PATH > pathappend $KF5_PREFIX/lib/qt5/qml QML2_IMPORT_PATH
>Yes, that looks OK. About the only other thing I can think of is to see >if the proper symlinks are in place: >I have: >./plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js >./plasmoids/org.kde.plasma.activitypager/contents/ui/utils.js >./plasmoids/org.kde.plasma.pager/contents/ui/utils.js >./plasmoids/org.kde.plasma.kicker/contents/ui/tools.js >./plasmoids/org.kde.plasma.analogclock/contents/ui/logic.js >./plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js >./plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js >./plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js >./plasmoids/org.kde.plasma.systemtray/contents/ui/Layout.js >./plasmoids/org.kde.plasma.volume/contents/ui/icon.js >./plasmoids/org.kde.plasma.kickoff/contents/ui/tools.js >./plasmoids/org.kde.panel/contents/ui/LayoutManager.js >./plasmoids/org.kde.plasma.quicklaunch/contents/ui/layout.js >./plasmoids/org.kde.plasma.lock_logout/contents/ui/data.js >./plasmoids/org.kde.plasma.battery/contents/ui/logic.js >./plasmoids/org.kde.plasma.taskmanager/contents/ui/layout.js >./plasmoids/org.kde.plasma.taskmanager/contents/ui/tools.js >./plasmoids/org.kde.plasma.colorpicker/contents/ui/logic.js >./plasmoids/org.kde.milou/contents/ui/globals.js Mine are: ./plasmoids/org.kde.milou/contents/ui/globals.js ./plasmoids/org.kde.plasma.lock_logout/contents/ui/data.js ./plasmoids/org.kde.plasma.kicker/contents/ui/tools.js ./plasmoids/org.kde.plasma.pager/contents/ui/utils.js ./plasmoids/org.kde.plasma.colorpicker/contents/ui/logic.js ./plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js ./plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js ./plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js ./plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js ./plasmoids/org.kde.plasma.quicklaunch/contents/ui/layout.js ./plasmoids/org.kde.plasma.volume/contents/ui/icon.js ./plasmoids/org.kde.plasma.kickoff/contents/ui/tools.js ./plasmoids/org.kde.plasma.battery/contents/ui/logic.js ./plasmoids/org.kde.plasma.activitypager/contents/ui/utils.js ./plasmoids/org.kde.panel/contents/ui/LayoutManager.js ./plasmoids/org.kde.plasma.analogclock/contents/ui/logic.js ./plasmoids/org.kde.plasma.taskmanager/contents/ui/layout.js ./plasmoids/org.kde.plasma.taskmanager/contents/ui/tools.js ./plasmoids/org.kde.plasma.systemtray/contents/ui/Layout.js >About the only other thing I can think of is to compare your build tree to >mine. See >http://anduin.linuxfromscratch.org/~bdubbs/files/kf5-ls-lR[http://anduin.linuxfromscratch.org/~bdubbs/files/kf5-ls-lR] Looks the same >And this is how I start plasma using startx (.xinitrc) >ck="ck-launch-session dbus-launch --exit-with-session" >exec $ck /opt/kf5/bin/startkde Tried that, same result. Head banging stuff, but thanks Bruce Cliff -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
