Registered Member
|
Hello,
with the help of Arch Linux KDE maintainer, Andrea Scarpino, I am packaging and building KDE Frameworks 5 from git repositories. To start a new KF5 session I use lightdm and the provided startkde script modified as follows (I added the environment variables mentioned in the "Building frameworks" community page to take into account that KF5 is installed in /opt/kf5):
However, this results in running the X server, setting the oxygen mouse cursor and blocking in a black screen. This is with fresh user account. .xsession-errors contains:
Any idea about how to better investigate and solve this issue? Many thanks |
Registered Member
|
By playing with /etc/dbus-1/{session,system}-local.conf (as described in a tutorial on techbase.kde.org), I managed to remove a lot of errors from .xsession-errors, which now looks like:
However, logging into a KDE Frameworks 5 session still leads to a black screen with the oxygen mouse cursor. I think the most worrisome message is "kdeinit5: Communication error with launcher. Exiting!" Any idea? Thanks. |
Administrator
|
Based on what I can see there:
1) kbuildsycoca5 --noincremental has not been run for this session. 2) The dbus-daemon for the session has not been started - which is why kdeinit5 fails to start.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks for your reply. However, it seems that the dbus daemon for the session has been started:
output of 'ps aux | grep dbus' before log in:
output of 'ps aux | grep dbus' after log in: (kde is the user logged in)
Looks like a session bus has been created, isn't it? Is it possible that kdeinit5 does not "find" the session bus? Thanks again. |
Administrator
|
Could you please check that the command "qdbus" works from a terminal in this KF5 environment?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
In the startkde script I replaced the line:
if $qdbus >/dev/null 2>/dev/null; then with if $qdbus > qdbus.out 2>qdbus.err; then qdbus.err is empty, while qdbus.out only contains:
Unfortunately I cannot open a terminal in the KF5 session because what I get is a black screen with the oxygen mouse cursor and I cannot launch anything. I tried to add the line: exec xterm -geometry 80x66+0+0 -name login in the startkde script just before the drkonqi section, but I didn't get anything as well. Any other suggestion? Thanks a lot for your help. |
Registered Member
|
A few more bits of information.
Within the startkde script, I moved the line "exec xterm -geometry 80x66+0+0 -name login" *before* the block that launches ksmserver. That allowed me to get the terminal emulator. I checked the existence of a session bus (the env variable DBUS_SESSION_BUS_ADDRESS is set). From within the terminal emulator I can launch konsole and kate (KF5 version). I can also run "kwin --replace" and "plasma-shell" and I get a (sort of) working environment. After launching some applications, the qdbus output grows:
Hence, I suspect that my problems are caused by ksmserver not properly starting, which prevents kdeinit5 from running. If I run "kdeinit5" from the terminal emulator I get:
Any suggestion how to investigate further? Many thanks in advance. |
Administrator
|
I've just reviewed the logs again. Can you check that all processes are running under the correct user?
This seems to imply that Qt 5 code is running as root, instead of the user it is supposed to be running as - which would explain why it is unable to access the D-Bus session, among other things.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
This is the output of 'ps auxf' from the terminal:
There is a special file created in the root (/) directory:
Does this suggest that kdeinit is run as root? Any other suggestion about what to check? Many thanks in advance. |
Administrator
|
I'm afraid I don't have much idea here - that all looks fine, however there is a total lack of any trace indicating that KDE is even running on that system. In terms of the /kdeinit5__0 socket, I would suggest removing it. The permissions on it are very unusual, but are consistent to a certain extent with what would occur if you were to run a key KDE process as root.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
That's a known pam_systemd bug. See also: http://lists.freedesktop.org/archives/s ... 14370.html https://bugzilla.redhat.com/show_bug.cgi?id=753882#c71 |
Registered Member
|
Hmm any progress on this or workaround?
|
Registered Member
|
I was pointed here from this topic: viewtopic.php?f=287&t=121306
I worked around my problem (to a point where I could run plasma-workspace, not where it worked well, although I don't yet know what my other problems are caused by) by adding export XDG_RUNTIME_DIR=/var/run/$UID to the top of /usr/bin/startkde. The folder /var/run/$UID may have to be created and given the correct permissions. |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft