You are not logged in.
Hello everybody,
After having performed an update of my archlinux, I can not start kde (on X, not Wayland) anymore.
I used to start it following the "Rootless Xorg" procedure mentioned there: https://wiki.archlinux.org/index.php/Xo … 28v1.16.29
My .xinitrc:
#!/bin/sh
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi
if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
# start some nice programs
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
#twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login
exec startkde
When login, kde is not started (as it was the case before), I just end-up with the console prompt.
Typing "startx" in it (as current user) generates the following error:
xf86EnableIOPorts: failed to set IOPC for I/O (Operation not permitted)
dbus-update-activation-environment: error: unable to connect to D-BUS: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead.
startkde: Could not sync environnement to dbus.xinit: connection to X server lost
I tried several things, such as
"export DBUS_SESSION_BUS_ADDRESS" or reinstalling X and dbus without success.
To be noted that commenting the "startkde" command in the .xinitrc and commenting out the "xterm" stuff allows starting X as regular user.
Could somebody help me understand where the issue is? Not sure if it is coming from dbus, systemd or X...
Last edited by Laserpithium (2017-10-22 09:59:04)
Offline
Xorg log?
Offline
Sorry for late answer, not at home these last days.
I downgraded systemd from version 235 to 234, and that solved the issue.
Will stay like this for the moment and cross the fingers the issue will disappear with the next versions. Otherwise, will restart digging :-)
Offline