1 - yeah we stripped out all the funky heuristics that dpkg-reconfigure
used to do. They fixed some problems but cause others, and was a PITA
to maintain.
2 - actually it's not gdm but the failsafe-x code kicking in. It is set
up to work with gdm but not other display managers. I consider xdm to
be more of a "bare metal" window manager, and users who prefer it want
to have more hands-on control and fewer helper tools getting in the way,
so failsafe-x seems inappropriate there. YMMV. failsafe-x itself is
actually part of xorg, not gdm; I think it's totally feasible to hook it
into use for xdm as well, but I don't have plans to implement that
myself. (It's just bash code and an upstart script, so I think it
shouldn't be hard to get into hacking on it.)
3 - It could be an xdm issue. The Ubuntu-X team focuses on gdm since
that's the default we ship. We do accept patches for xdm though, if you
are motivated to chase down the issue. Otherwise, you're welcome to
file a bug against xdm, but no promises it'll get investigated, I don't
think we have any maintainers looking at those bugs regularly.
Thanks for your feedback and analysis into the problem, and narrowing it
to a configuration issue using xdm instead of gdm. I'll close out the
bug at this point, but feel free to file a new one against xdm if you
can narrow down the defect more specifically.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Fix Released
--
Xserver does not start due to drm problem
https://bugs.launchpad.net/bugs/565643
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
