I've just discovered something interesting, after some time experimenting in Karmic -- somehow, I managed to catch a line about "failed to connect to acpid" just before the crash.
Apparently, the acpi-services part of the fglrx driver explicitly depends on having acpid up and running by the time Xorg starts, or else it fails rather inelegantly, as this bug report discusses.
I've managed to fix the problem on my system, by adding an explicit upstart dependency of 'acpid' for gdm.
I've edited /etc/init/gdm.conf as follows:
start on (filesystem
and started hal
and started acpid <=== Add this line.
and tty-device-added KERNEL=tty7
and (graphics-device-added or stopped udevtrigger))
stop on runlevel [016]
I've just discovered something interesting, after some time experimenting in Karmic -- somehow, I managed to catch a line about "failed to connect to acpid" just before the crash.
Apparently, the acpi-services part of the fglrx driver explicitly depends on having acpid up and running by the time Xorg starts, or else it fails rather inelegantly, as this bug report discusses.
I've managed to fix the problem on my system, by adding an explicit upstart dependency of 'acpid' for gdm.
I've edited /etc/init/gdm.conf as follows:
start on (filesystem device- added or stopped udevtrigger))
and started hal
and started acpid <=== Add this line.
and tty-device-added KERNEL=tty7
and (graphics-
stop on runlevel [016]