Ok, a comment how I understand this issue: failsave-x only supports use cases where gdm is not DISABLED. Setups where gdm is used or isn't installed aren't affected. So... although I understand that the patch described above works, I get the feeling this is fixed at the wrong place.
First of all, why does failsave-x even assume that gdm and kdm aren't installed at the same time? There are users that I know that like to have both gnome and kde installed. And even if that wasn't the case, with the current startup check start on stopped gdm EXIT_STATUS=[!0] what happens for kubuntu users that have a broken X Server? Kubuntu isn't supported? Second: Why does a 'Disabled' status justify an exit status !0? In that regard both gdm and kdm are broken since they both have the same check. IMHO this should be fixed in the failsave-x upstart script so that we have proper support for both gdm and kdm (failing or not). -- after recent update which included xorg, xserver etc causes low-graphics mode error at start https://bugs.launchpad.net/bugs/491483 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
