Argh, this is an utter pain to debug, but that's what I found out: * When this happens, gdm only writes a "failsave.log" with a single number in it. No other logs.
* Wrapping gdm-binary into strace in the upstart script introduces enough slowdown to make gdm startup succeed. Yay heisenbug. * Similar to starting gdm by hand or other slowdown, it works when there's no ureadahead pack, i. e. when reprofiling. (This might explain why it works for me sometimes) * The failsave X.org server is on VT2 (!). This means that it started to launch an X.org server at vt7 first (due to 05_initial_server_on_vt7.patch), and then started another (failsafe) one on the next free VT, which apparently was 2. As I already said, all other VTs are disfunctional (black screen and "frequency not supported") Is there a possibility to add more verbosity to upstart event/job processing? Can this be single-stepped somehow? -- gdm starts too early, X.org/VTs fail https://bugs.launchpad.net/bugs/502838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
