[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Michael Ummels
Ah, we had t he same idea. :-) -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- des

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Michael Ummels
Adding the check to the upstart script seems to be a good idea. I've created a patch for that. Ideally, the check whether GDM is default display manager should be in the "start on" condition, but I don't know how to do that. ** Attachment added: "Patch of the upstart script failsafe-x" http://l

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Philip Muskovac
Here's a debdiff for karmic-proposed that makes the failsave-x upstart task abort if gdm isn't enabled. Can you guys test it by editing your /etc/init/failsave-x.conf to look like this: start on stopped gdm EXIT_STATUS=[!0] stop on runlevel [06] script [ ! -f /etc/X11/default-display-manag

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Philip Muskovac
And the Failsave-X scripts are part of the xorg package and not xorg- server. ** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu) -- 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 no

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Kevin Christmas
So the fix that I'm using, post #30, works because KDM starts faster because it doesn't have to test drivers? -- 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

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Philip Muskovac
@Michael (and Urs): Why don't we just add the check to the failsave-x upstart script? That seems to be a better way to fix this IMHO, since that's the place where the bug is. -- after recent update which included xorg, xserver etc causes low-graphics mode error at start https://bugs.launchpad.n

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Michael Ummels
@Selenia: Have you looked at the patch provided by Urs Fleisch? It is a real fix, not a workaround, since it does not break failsafe-x when using GDM. -- after recent update which included xorg, xserver etc causes low-graphics mode error at start https://bugs.launchpad.net/bugs/491483 You receiv

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Selenia
Seems gdm and kdm have the required sanity checks to not start when not chosen, but failsafe-x always assumes gdm is chosen, by what you are saying. It could probably be patched in upstart but likely should really be fixed in failsafe-x, if this is what is indeed happening. Maybe I'll break it agai

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Philip Muskovac
@Selenia: what happens: k/ubuntu boots upstart finds gdm.conf and tries to start gdm upstart finds kdm.conf and tries to start kdm upstart finds failsave-x.conf and tries to start failsave-x gdm finds out that it's not the chosen WM and fails with exit status 1 kdm finds out that it's the chosen

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Selenia
I think another big question is one I try to suggest an answer to, but am not 100% positive. Why is it tripping into bulletproof X to begin with? Surely, Bulletproof or failsafe X should be fixed, but it shouldn't be loading in the first place in this case. As to fixing a broken X, I'm still used t

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Philip Muskovac
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 al

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Selenia
This bug affects me and I don't even use KDE, but do use the KDM login manager over GDM because I like it. A user called doctordruidphd on the Ubuntu forums has given a workaround that I have tested to work on several systems I have that are affected. cd /etc/init sudo mv failsafe-x.conf failsaf

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Michael Ummels
Thank you, Urs, for your patch, which works perfectly. Now, can we get this patch into karmic-updates as soon as possible? ** Changed in: gdm (Ubuntu) Status: New => Invalid -- after recent update which included xorg, xserver etc causes low-graphics mode error at start https://bugs.laun

[Bug 491483] Re: after recent update which included xorg, xserver etc causes low-graphics mode error at start

2009-12-06 Thread Michael Ummels
** Changed in: slim Status: New => Invalid ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server Status: Confirmed => Invalid -- after recent update which included xorg, xserver etc causes low-graphics mode error at start https://bug