ports/131016: xorg-7.4 renders system unusable!
ohartman at zedat.fu-berlin.de
Mon Jan 26 16:50:06 UTC 2009
>Synopsis: xorg-7.4 renders system unusable!
>Arrival-Date: Mon Jan 26 16:50:05 UTC 2009
>Originator: O. Hartmann
Symptomes: After guided (ports/UPDATING) upgrade to the xorg-7.4 port, rebuilt of sysutils/hal, sysutils/dbus and performing 'portupgrade -rf libxcb', cleaning up /etc/X11/xorg.conf several boxes rendered unusable. While with xorg-7.3 some could simply use the OS's input devices (mice, keyboards), xorg-7.4 now explicitely needs hald and dbusd. But this information is not provided in UPDATING and therefore some who isn't very familiar with changes in X11 will suffer from that fault.
More dramatic is the incabability of switching back to FreeBSD's console! Having ran the X server once, some will never get back to a console. Even when dbud and hald are not started accidentally (as happened to me), I expect killing the X server via CTRL-ALT-BS (when configured by commenting out DontZap in xorg.conf). That doesn't work anymore. Also there is no chance switching back to any of the console screens via CTRL-ALT-F1 to F7 (as in my case): consoles are black/dark/unresponsive, no keyboard, no output, monitor signals 'no signal'. I can switch back to the tty bound by the xdm/Xorg server, but when simply testing X this ends up in a deadend.
This behaviour occurs on three graphics card driver: nv, vesa and radeon/hd
and on these FreeBSD type/versions:
FreeBSD 8.0-CURRENT/amd64 (as builtworld today)
FreeBSD 7.1-STABLE/amd64/i386 (as builtworld today)
More information about the freebsd-ports-bugs