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 >> http://download.qt.io/official_releases/qt/5.6/5.6.1/submodules/[http://download.qt.io/official_releases/qt/5.6/5.6.1/submodules/][http://download.qt.io/official_releases/qt/5.6/5.6.1/submodules/[http://download.qt.io/official_releases/qt/5.6/5.6.1/submodules/]] > >> In qtdeclarative-opensource-src-5.6.1/src/qml/qml.pro > >> edit the QMAKE_CXXFLAGS > > Thanks. > > 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. > One other thing. Is qtdeclarative part of QT or an add on? I see no > mention of it in BLFS. >Looking at my qt installation, I only see some header files in >/opt/qt-5.7.0/include. They are all labeled private in the path. >Yes I have files under the same. Got kinit-5.23.0 to compile without error by recompiling libcap with the Pam module. Cliff -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
