[blfs-support] Errors while fixing plasmoids at the end of Plasma5

[Ken Moffat via blfs-support]

I do not usually build kde, but I thoiught I might as well check
that my scripts are up to date, and that nothing new has broken it.

At the end of Plasma5 the book has:

cd $KF5_PREFIX/share/plasma/plasmoids

for j in $(find -name \*.js); do
as_root ln -sfv ../code/$(basename $j) $(dirname $j)/../ui/
done

But for me, running as root that failed quickly:

'./org.kde.plasma.colorpicker/contents/ui/../ui/logic.js' -> '../code/logic.js'
'./org.kde.plasma.lock_logout/contents/ui/../ui/data.js' -> '../code/data.js'
ln: target './org.kde.plasma.kicker/contents/ui/code/../ui/' is not a directory: No such file or directory

Changing 'ln -sfv' to 'ls -l' and capturing the errors, I got:

ls: cannot access '../code/logic.js': No such file or directory
ls: cannot access '../code/data.js': No such file or directory
ls: cannot access '../code/tools.js': No such file or directory
ls: cannot access './org.kde.plasma.kicker/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/FolderTools.js': No such file or directory
ls: cannot access './org.kde.desktopcontainment/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/LayoutManager.js': No such file or directory
ls: cannot access './org.kde.desktopcontainment/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/tools.js': No such file or directory
ls: cannot access './org.kde.plasma.kickoff/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/layout.js': No such file or directory
ls: cannot access '../code/uiproperties.js': No such file or directory
ls: cannot access '../code/tools.js': No such file or directory
ls: cannot access './org.kde.plasma.taskmanager/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/layout.js': No such file or directory
ls: cannot access './org.kde.plasma.taskmanager/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/LayoutManager.js': No such file or directory
ls: cannot access '../code/logic.js': No such file or directory
ls: cannot access '../code/logic.js': No such file or directory
ls: cannot access '../code/globals.js': No such file or directory

For the moment I've added '|| true' to the ln command, to allow me
to move on.

ĸen

[Bruce Dubbs via blfs-support]

Post by Ken Moffat via blfs-support
I do not usually build kde, but I thoiught I might as well check
that my scripts are up to date, and that nothing new has broken it.
cd $KF5_PREFIX/share/plasma/plasmoids
for j in $(find -name \*.js); do
as_root ln -sfv ../code/$(basename $j) $(dirname $j)/../ui/
done
'./org.kde.plasma.colorpicker/contents/ui/../ui/logic.js' -> '../code/logic.js'
'./org.kde.plasma.lock_logout/contents/ui/../ui/data.js' -> '../code/data.js'
ln: target './org.kde.plasma.kicker/contents/ui/code/../ui/' is not a directory: No such file or directory
ls: cannot access '../code/logic.js': No such file or directory
ls: cannot access '../code/data.js': No such file or directory
ls: cannot access '../code/tools.js': No such file or directory
ls: cannot access './org.kde.plasma.kicker/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/FolderTools.js': No such file or directory
ls: cannot access './org.kde.desktopcontainment/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/LayoutManager.js': No such file or directory
ls: cannot access './org.kde.desktopcontainment/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/tools.js': No such file or directory
ls: cannot access './org.kde.plasma.kickoff/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/layout.js': No such file or directory
ls: cannot access '../code/uiproperties.js': No such file or directory
ls: cannot access '../code/tools.js': No such file or directory
ls: cannot access './org.kde.plasma.taskmanager/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/layout.js': No such file or directory
ls: cannot access './org.kde.plasma.taskmanager/contents/ui/code/../ui/': No such file or directory
ls: cannot access '../code/LayoutManager.js': No such file or directory
ls: cannot access '../code/logic.js': No such file or directory
ls: cannot access '../code/logic.js': No such file or directory
ls: cannot access '../code/globals.js': No such file or directory
For the moment I've added '|| true' to the ln command, to allow me
to move on.

I'm planning on updating to plasma 5.14.4, kf5 5.53, and kde apps 18.12
when they are all released. That should be around Dec 13. I will check
that out then. I do not know for sure if those symlinks are still
needed or not.

-- Bruce

[Ken Moffat via blfs-support]

I'm planning on updating to plasma 5.14.4, kf5 5.53, and kde apps 18.12 when
they are all released. That should be around Dec 13. I will check that out
then. I do not know for sure if those symlinks are still needed or not.
-- Bruce

I'll just wish you luck. My .xinitrc is set up to let me pass
various known WM= values, including kde.

On the first attempt, X appeared to hang with a black screen, so I
used Ctrl-Alt-BackSpace to get back to the tty.

Adding 2>errors, it quickly dropped back to the tty when I retried
and the errors were (underlining '^^^' errors which might be
important, if anybody cares - I've now given up on kde)

dbus[30102]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/ken" not available: Permission denied
dbus[30117]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/var/run/user/1000" not available: Permission denied/opt/kf5/bin/startkde: line 106: kapplymousetheme: command not found
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
startkde: Starting up...
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
kdeinit5: Aborting. bind() failed: Permission denied
Could not bind to socket '/kdeinit5__0'
^^^
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
kdeinit5_wrapper: Warning: connect(/kdeinit5__0) failed: : No such file or directory
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
Qt: Session management error: networkIdsList argument is NULL
Configuring Lock Action
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
org.kde.kf5.ksmserver: KSMServer: cannot open /KSMserver__0: Permission denied
^^^
org.kde.kf5.ksmserver: KSMServer: Aborting.
startkde: Shutting down...
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/var/run/user/1000', please create it with 0700 permissions.
kdeinit5_wrapper: Warning: connect(/kdeinit5__0) failed: : No such file or directory
Error: Can not contact kdeinit5!
startkde: Done.
xinit: connection to X server lost

To start with I assumed that the /var/run/user/ken/1000 (I use 1000
for my UID, ISTR lfs itself uses 1001) and maybe /run/user/ken
directories were the problem. So I ran
mkdir -pv /var/run/user/1000
chmod 700 /var/run/user/1000

But of course that symlinks to /run. Looking there, I have

***@origin /home/ken #ls -l /run/user
total 0
drwx------ 2 root root 40 Nov 28 03:17 0
drwx------ 2 ken root 40 Nov 28 02:58 1000
drwx------ 4 ken users 80 Nov 27 05:46 ken

and /run/user/ken is of course present.

Retrying 'startx --wm=kde' made no difference.

And my xinitrc using that results in (pruned to remove a lot of
conditional stuff for other WMs or other things I normnally run):

-- start items from .xinitrc --
WM=/opt/kf5/bin/startkde

echo $PATH | grep -q kf5 || export PATH=/opt/kf5/bin:$PATH
export XDG_CONFIG_DIRS=/etc/xdg:/opt/kf5/etc/xdg
export XDG_DATA_DIRS=/usr/share:/opt/kf5/share
echo $QT_PLUGIN_PATH | grep -q kf5 ||
export QT_PLUGIN_PATH=/opt/kf5/lib/plugins
echo $QML_IMPORT_PATH | grep -q kf5 ||
export QML_IMPORT_PATH=/opt/kf5/lib/qml

# if qt5 is in both /usr and /opt, the /usr version should go
# because with qt-5.5 I get build problems!
echo $PATH | grep -q qt5 || export PATH=/opt/qt5/bin:$PATH
echo $QT_PLUGIN_PATH | grep -q qt5 ||
export QT_PLUGIN_PATH=/opt/qt5/plugins:$QT_PLUGIN_PATH
echo $QML_IMPORT_PATH | grep -q qt5 ||
export QML_IMPORT_PATH=/opt/qt5/qml:$QML_IMPORT_PATH
export QML2_IMPORT_PATH=$QML_IMPORT_PATH

# if building libreoffice after kde, startkde eventually craps out in dbaccess
# and suggests this export
export $(dbus-launch)

echo "invoking startkde"
exec ck-launch-session dbus-launch --exit-with-session startkde
-- end items from .xinitc --

Summary: I'm giving up on kde. I last used it when my kaveri was
working properly, and over the years it has caused me a lot of pain.
Enough.

ĸen

[Bruce Dubbs via blfs-support]

Post by Ken Moffat via blfs-support
# if building libreoffice after kde, startkde eventually craps out in dbaccess
# and suggests this export
export $(dbus-launch)
echo "invoking startkde"
exec ck-launch-session dbus-launch --exit-with-session startkde
-- end items from .xinitc --

This is what I use:


[ ~ ]$ cat .xinitrc
session=${2:-xfce}

dbus="dbus-launch --exit-with-session"
ck="ck-launch-session dbus-launch --exit-with-session"

case $session in
fluxbox ) exec startfluxbox ;;
icewm ) exec icewm-session ;;
openbox ) exec openbox-session ;;
sawfish ) exec sawfish ;;
kde5|plasma ) exec $ck /opt/kf5/bin/startkde ;;
xfce|xfce4 ) exec startxfce4 --with-ck-launch ;;
lxde ) exec ck-launch-session startlxde ;;
lxqt ) $dbus /opt/lxqt/bin/startlxqt ;;
lxqt2 ) exec /opt/lxqt/bin/startlxqt ;;
gnome ) $dbus /usr/bin/gnome-session ;;

twm ) xterm -g 80x40+0+0 &
xclock -g 100x100-0+0 &
twm
;;

# No known session, just say so
*) echo "Cannot run $1" ;;
esac


-- Bruce

[Ken Moffat via blfs-support]

Post by Ken Moffat via blfs-support

I'm planning on updating to plasma 5.14.4, kf5 5.53, and kde apps 18.12 when
they are all released. That should be around Dec 13. I will check that out
then. I do not know for sure if those symlinks are still needed or not.
-- Bruce

I'll just wish you luck.

I've now archived my own kde scripts, so I won't be retesting this
until (hopefully next year) I start using jhalfs to build-test (but
not necessarily run) the current book.

But in the meantime I've finally got to the end of the sysv gnome
packages I can build (loads of issues with my own scripts of course:
lingering CMMI commands on packages which now use meson, forgetting
to 'cd build' ("fun error message"), and forgetting to update some
package versions. And then I ran update-desktop-database:

Error in file "/opt/kf5/share/applications/org.kde.kfontview.desktop": "font/otf" is an invalid MIME type ("font" is an unregistered media type)
Error in file "/opt/kf5/share/applications/org.kde.kfontview.desktop": "font/ttf" is an invalid MIME type ("font" is an unregistered media type)

Hopefully that is either already fixed, or else will be fixed in
next month's version.

ĸen