If instead of logging out of the first seat I kill the first seat with kill -9 PID_OF_X_1st_SEAT, then the second seat is undisturbed. If I kill just with kill PID_OF_X_1st_SEAT, then the first seat locks up. Not always locks up with 100% CPU, sometimes just frezes with no CPU consumption. The point is that it might be that the fglrx is not honoring the isolateDevice and resets the second seat anyway? When the second seat exits the first is undisturbed.
-- user logs out in multiseat makes other seat lockup https://bugs.launchpad.net/bugs/158250 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
