On Tue, 2015-01-27 at 05:09 -0500, Felix Miata wrote:
This is from trying to run startx after a fresh zypper ref/dup from 13.2 to TW. Startkde also doesn't work.
Please raise a bug report. I know Stefan already had seen that the script was a 0-byte file in one snapshot and fixed that, but there seems to be more stuff wrong with it.
"Please configure the correct X Server with SaX/SaX2, which will create the missing link. I'm aborting now."
SaX, SaX2, sax & sax2 produce command not found.
Errmm.. yes, that's been a couple releases. Another bug report ahould probably ask to update the error mesasge
ls of /usr/bin/X points to /var/lib/X11/X with red background
ls of /usr/bin/Xorg also has red background
Red background indicates an executable with SUID bit set. So far so good.
I see /usr/bin/startx has grown from 5643 bytes in 13.2 to 8584 bytes in TW.
Systemctl isolate multi-user.target fails to stop xorg and kdm if booted to graphical.target, as does init 3, as does init 1.
What's it now take to get TW to start a KDE3 session without running kdm/xdm? Startx still starts KDE in Rawhide and Cauldron. KDM3 still works and starts KDE3.
I don;t think there was any deliberate change that this would not work
anymore; I'd say a bug report is the way forward in getting this
verified.
Cheers,
--
Dimstar / Dominique Leuenberger