Sax is *not* dropped, it's icon only go out of yast control center. This just makes users try the new method (via KDE/Gnome/xrandr/whatever). If sax would stay in yast, many users would use it in *first place* -> no migration to new mechanism even though it would work for them in most cases.
If the "new mechanism" is not good for you for any reason (something not working), you can still use sax2! It's not dropped, you can still call it from commandline, etc.
Later, when the "new mechanism" is mature and tested, than the xorg.conf support will/can be dropped (maybe).
IMHO this seems to be the correct way, enable new feature, that shoud be working, but make it possible to fallback to the old behaviour.
Just my 2cents
Best regards,
Yes, it would be great if it really were like this. What I have experienced was - besides the p&p autodetection bug - that my previously working xorg.conf has become infunctional. The support for old style xorg.confs seems having been totally dropped without the p&p mechanism to work. SaX2 did not even start (https://bugzilla.novell.com/show_bug.cgi?id=539008). It could not produce usable xorg.confs. After downgrading radeonhd & Xorg SaX2 did its job well again. I would really appreciate support for old style xorg.confs because I do now have to install the new radeonhd for every test and then to downgrade my whole Xorg again to enter graphics mode. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org