[opensuse-factory] "There is no link /var/X11R6/bin/X to the correct X Server binary."
This is from trying to run startx after a fresh zypper ref/dup from 13.2 to TW. Startkde also doesn't work. "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. ls of /usr/bin/X points to /var/lib/X11/X with red background ls of /usr/bin/Xorg also has red background 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. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
Hello, Am Dienstag, 27. Januar 2015 schrieb Dimstar / Dominique Leuenberger:
On Tue, 2015-01-27 at 05:09 -0500, Felix Miata wrote:
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.
Well, broken symlinks also have a red background ;-) - and in theory someone could even change his $LS_COLORS ;-) Instead of guessing around, it's more useful to paste the ls -l output, and in case of a symlink also the ls -l output for the link target (or a note that the symlink points to a non-existing file). Regards, Christian Boltz -- [RAM] Du würdest Dir wahrscheinlich auch einen Schoko-Riegel mit 768 Kcal einbauen und dann zu Mandrake wechseln, weil die den BadRAM-Patch haben. [Rüdiger Meier in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-01-27 at 13:48 +0100, Christian Boltz wrote:
Hello,
Am Dienstag, 27. Januar 2015 schrieb Dimstar / Dominique Leuenberger:
On Tue, 2015-01-27 at 05:09 -0500, Felix Miata wrote:
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.
Well, broken symlinks also have a red background ;-) - and in theory someone could even change his $LS_COLORS ;-)
Serious? A user that reports 'I see this background color' is VERY unlikely of having changed his color setup; he solely relies on the fact that the reader can identify what his background color means. The 'broken symlink' argument I give you though. The foreground color would tell :) (white on red => SUID binary, yellow on red, broken symlink)
Instead of guessing around, it's more useful to paste the ls -l output, and in case of a symlink also the ls -l output for the link target (or a note that the symlink points to a non-existing file).
Sure... but in the end... in either way, it is broken.
--
Dimstar / Dominique Leuenberger
Dimstar / Dominique Leuenberger composed on 2015-01-27 12:17 (UTC+0100):
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.
https://bugzilla.opensuse.org/show_bug.cgi?id=915006
"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
https://bugzilla.opensuse.org/show_bug.cgi?id=915007
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.
https://bugzilla.opensuse.org/show_bug.cgi?id=866350 suggests Stefan Dirsch may want startx to go away. I use startx as it's what I know for quickly starting and restarting sessions between xorg.conf changes without any xdm getting in the way, and for starting sessions on :1 and :2 using different display configurations from that used for :0. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-01-27 at 13:40 -0500, Felix Miata wrote:
Dimstar / Dominique Leuenberger composed on 2015-01-27 12:17 (UTC+0100):
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.
https://bugzilla.opensuse.org/show_bug.cgi?id=915006
"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
https://bugzilla.opensuse.org/show_bug.cgi?id=915007
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.
https://bugzilla.opensuse.org/show_bug.cgi?id=866350 suggests Stefan Dirsch may want startx to go away. I use startx as it's what I know for quickly starting and restarting sessions between xorg.conf changes without any xdm getting in the way, and for starting sessions on :1 and :2 using different display configurations from that used for :0. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
As a temporary workaround, Comment out the following lines in /usr/bin/X I didn't do enough testing when I updated xinit to 1.3.4, and the current Xorg no longer uses things in /usr/X11R6 or /var/X11R6 like the suse startx script is expecting, which is causing the breakage. Working on an updated patch, and I will get it pushed to Tumbleweed just as fast as I can. #if [ ! -L /usr/X11R6/bin/X -a ! -L /usr/bin/X ]; then # echo "" # echo "There is no link /usr/X11R6/bin/X (/usr/bin/Xorg) to /var/X11R6/bin/X!" # echo "Please link the files as mentioned above or install the X-Server again." # echo "I'm aborting now." # exit 1 #fi #XCOMM #XCOMM check for the second link #XCOMM #if [ ! -L /var/X11R6/bin/X ]; then # echo "" # echo "There is no link /var/X11R6/bin/X to the correct X Server binary." # echo "Please configure the correct X Server with SaX/SaX2, which will create" # echo "the missing link. I'm aborting now." # exit 1 #fi #XCOMM #XCOMM check if the Xorg file is an executable or an accidentally copied #script or similar things #XCOMM #if [ ! -x /var/X11R6/bin/X ]; then # echo "" # echo "The file Xorg (binary of X-Server) doesn't seem to be a binary file." # echo "Please check it or / and install a new X-Server-binary." # echo "I'm aborting now." # exit 1 #fi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-01-27 at 11:03 -0800, Shawn W Dunn wrote:
On Tue, 2015-01-27 at 13:40 -0500, Felix Miata wrote:
Dimstar / Dominique Leuenberger composed on 2015-01-27 12:17 (UTC+0100):
As a temporary workaround, Comment out the following lines in /usr/bin/X
I didn't do enough testing when I updated xinit to 1.3.4, and the current Xorg no longer uses things in /usr/X11R6 or /var/X11R6 like the suse startx script is expecting, which is causing the breakage.
Working on an updated patch, and I will get it pushed to Tumbleweed just as fast as I can.
Ok, I just submitted sr#283058 to X11:XOrg, pending Maintainer acceptance. Verified that startx behaves as expected, and you end up in your window manager of choice. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Christian Boltz -
Dimstar / Dominique Leuenberger -
Felix Miata -
Shawn W Dunn