Bug 915006

Summary: startx errors instead of starting X
Product: [openSUSE] openSUSE Tumbleweed Reporter: Felix Miata <mrmazda>
Component: X.OrgAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED FIXED QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P3 - Medium    
Version: 201501*   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Felix Miata 2015-01-27 18:34:15 UTC
In mailing list thread http://lists.opensuse.org/opensuse-factory/2015-01/msg00407.html Dimstar requested I report this here.

I upgraded a 13.2 installation on host gx27b to Tumbleweed via zypper dup with KDE3 and Mozilla repos set to Factory, and oss, non-oss and update repos set to tumbleweed. /usr/bin/startx at 5643 bytes in 13.2 grew to 8584 bytes in TW. On booting the result to multi-user.target, startx instead of starting a KDE3 session produces this error message:

"There is no link /var/X11R6/bin/X to the correct X Server binary. Please configure the correct X Server..."

I tried correcting by chmod 4711 /usr/bin/Xorg, which didn't help. I found xorg-x11-libs had no longer been installed, but installing it did not help. Forced reinstall of xinit also did not help. Startx still starts KDE in Rawhide and Cauldron. KDM3 still works and starts KDE3 in TW.

Files:
# ls -l /var/X11R6/bin/X
ls: cannot access /var/X11R6/bin/X: No such file or directory
# ls -l /usr/bin/startx
-rwxr-xr-x 1 root root 8584 Jan 24 16:28 /usr/bin/startx (cyan?green on blue)
# ls -l /usr/bin/X
lrwxrwxrwx 1 root root 14 Nov 26 05:26 /usr/bin/X -> /var/lib/X11/X (white on red)
# ls -l /usr/bin/Xorg
-rws--x--x 1 root root 2275196 Nov 26 05:26 /usr/bin/Xorg (white on red)
# ls -l /var/lib/X11/X
lrwxrwxrwx 1 root root 13 Nov 26 05:26 /var/lib/X11/X -> /usr/bin/Xorg (white on red)
Comment 1 Stefan Dirsch 2015-01-28 10:27:31 UTC
Fixed in X11:XOrg and submitrequested for factory.
Comment 2 Stefan Dirsch 2015-01-28 10:30:24 UTC
*** Bug 915007 has been marked as a duplicate of this bug. ***