wdm expects "X" at wrong location: /usr/bin/X11/X

Bug #4599 reported by Bronsen
6
Affects Status Importance Assigned to Milestone
wdm (Ubuntu)
Invalid
Medium
MOTU

Bug Description

When I installed wdm it failed to start completely. I could see the wdm processes running, but wdm didn't display anything on vt7. Also it was impossible to stop wdm the "natural" way (sudo invoke-rc.d wdm stop). I had to manually "killall -9 wdm" and then "rm /var/run/wdm.pid"

After reading the log files it turned out that wdm expects the X executable to be in /usr/bin/X11/X instead of /usr/bin/X. I found no way of configuring this, but I might have overlooked it. To me it looks like the path to X is hardcoded, which in my book is a Bad Thing.

For now I symlinked /usr/bin/X11/X to /usr/bin/X. The preinst script could do this, if the path really is hardcoded in upstream...

The other display managers I tried -namely kdm and gdm- did not behave this way.

Changed in wdm:
assignee: nobody → motu
Revision history for this message
Barry deFreese (bddebian) wrote :

/usr/bin/X11 should be symlinked to ../bin by default. Can someone else confirm this problem? Maybe it was a temporary Xorg package issue?

Changed in wdm:
status: Unconfirmed → Needs Info
Revision history for this message
Daniel Holbach (dholbach) wrote :

Is this still a problem?

Revision history for this message
William Grant (wgrant) wrote :

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.

Changed in wdm:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.