[solved] Xgl with GDM or KDM

[Admiral_Trigger_Happy]

I've been having all sorts of headaches with Xgl not playing nice with GDM or KDM.
I had it working before, but when I turned my box on this morning GDM just wouldn't start properly, it starts X with the wonderful grey background with the watch Icon, the it waits for awile and then dies, tries this a couple of times and gives that wondeful Blue GDM can't start box.
KDM doesn't seem to work at all, tried various things none work.

The annoying thing is Xgl + compiz etc work just fine if I use my script to start KDE, the problem with that is I can't use KDE with my normal user and have to use KDE as root, something I prefer not to do.

I don't care if I use GDM or KDM, as long as one works with Xgl so I can start KDE as a normal user.

Anyone had any joy here?

PS. I am running the testing branch of the coffe-buzz's overlay, it worked fine before I rebooted.
_________________
Admiral Trigger Happy
-------------------------------
www.kiba-dock.org

[Gnufsh]

Well, you can start xgl as a user using the startxgl script in coffeebuzz's overlay (that's what I've been doing).

[Admiral_Trigger_Happy]

Sure, but thats a pain in the Arse.

I want it to work with GDM or KDM, I don't care which as long as one will start KDE for me
_________________
Admiral Trigger Happy
-------------------------------
www.kiba-dock.org

[omidxo]

ohhh........it's just my annoyance.
"Rename GLX module to libglxext"caused X won't up with GDM since Mar 28 that I believe.

[Admiral_Trigger_Happy]

[saffsd]

I am having the same problem here. Gdm and xdm both dont work properly. Basically calling either only brings up Xgl and nothing else. They both work properly with good ol X, but no luck with Xgl. startxgl works just fine though. the link provided is to a diff between two versions of a makefile. can't really tell how it helps either...

[Aggamemnon]

I have a similar problem. When

[SneakyPete]

This fix worked for me.

Step 1: Downloading and emerging the new gdm ebuild

Download the new ebuild here.
Code:
cp gdm-xserver-timeout.tar.gz /usr/local/xgl-coffee
cd /usr/local/xgl-coffee
tar -zxvf gdm-xserver-timeout.tar.gz
echo "=gnome-base/gdm-2.14.0-r1" >> /etc/portage/package.unmask
emerge -av gdm


If you are getting digest errors do this, if not proceed to the next step:
Code:
cd /usr/local/xgl-coffee/gnome-base/gdm
ebuild gdm-2.14.0-r1 digest
emerge -av gdm

Now, the length of time GDM will wait for the Xserver to timeout is configurable in gdm.conf! I am going to submit this to the gdm bugzilla so I had to put the needed line in an intelligent place. Make sure you put the config line in the right place in gdm.conf (ie. put it in the [daemon] section, not just at the end of the file).

Step 2: Configuring gdm to wait longer

In your /etc/X11/gdm/gdm.conf file, find the [daemon] section. At the end of it you should see something like this:Code:
# This determines whether gdm will send notifications to the console
#ConsoleNotify=true


After that, add the following lines:Code:
# How long gdm should wait before it assumes a started Xserver is defunct and
# kills it. 10 seconds should be long enough for X, Xgl may need 20 or 25.
GdmXserverTimeout=25

This is your Xserver timeout.

Restart gdm! Send me flowers and take me to dinner

ps. If you are not using gnome 2.14, you will have to unzip the tarball and modify the ebuild to match your version number. I haven't tried applying the patches to any versions of gdm prior to 2.14 but I assume this stuff hasn't changed much in awhile so the patches should apply.

EDIT: Yay me. The patch is going to be committed to gdm 2.14.1 which should be released next week. Once 2.14.1 hits portage, we won't need to use my ebuild, we'll just need the extra gdm.conf variable See http://bugzilla.gnome.org/show_bug.cgi?id=337670.

Last edited by star.dancer on Fri Apr 07, 2006 4:16 pm; edited 3 times in total

This is from Page 30, of the XGL Part 3 Thread.

[Admiral_Trigger_Happy]

Yeah, I used Star.Dancers patch a little while ago and then it work, but I broke it again and then I fixed it again.

I find that whilst Xgl will start via the startxgl script fine on screen 0 and 1, gdm will only start properly with Xgl if I use screen 0.

So its all working now, although a few updates a long the way have broken a few things, Its all fixed now
_________________
Admiral Trigger Happy
-------------------------------
www.kiba-dock.org