https://bugzilla.novell.com/show_bug.cgi?id=359460 User dreveman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=359460#c22 --- Comment #22 from David Reveman <dreveman@novell.com> 2008-04-03 14:08:36 MST --- (In reply to comment #16 from Casual J. Programmer)
Re: comment #12
It sounds OK to disable Xgl if it keeps crashing, I think there should additionally be some mechanism that restarts gdm explicitly.
Yes, I agree and I think this is already taken care of by my patch as executing gnome-xgl-switch seem to somehow make gdm restart the X server after displaying the "Desktop effects disabled" message instead of just shutting it down. A gdm package with this patch can be downloaded from here: http://w3.suse.de/~dreveman/359460 (In reply to comment #13 from Casual J. Programmer)
The quality has changed somewhat. On issuing Xgl :0 -ac from a Terminal I get:
Xgl :0 -ac /etc/sysconfig/displaymanager: line 160: unexpected EOF while looking for matching `"' /etc/sysconfig/displaymanager: line 161: syntax error: unexpected end of file
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
Which, apart from telling me gdm is still running, looks somewhat weird with respect to /etc/sysconfig/displaymanager
Sorry, I forgot to tell you to stop gdm first.
ps -A | grep gdm 10245 ? 00:00:00 gdm 10246 ? 00:00:00 gdm
After shutting gdm down ( not sure why there are two instances running ) and issuing Xgl :0 -ac 2> xgloutput.txt the screen turns into a crude structured grey pattern and the mouse pointer is visible and can be moved. Nothing more.
That's the expected behavior and means that Xgl starts up correctly. Not sure why it doesn't work through gdm. I suspect that direct rendering is not provided by the Xorg server for some reason. Can you please attach the output from running 'glxinfo' when desktop effects are disabled. Thanks, -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.