[Bug 345035] New: problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository

bugzilla_noreply＠novell.com

29 Nov 2007 29 Nov '07

19:42

https://bugzilla.novell.com/show_bug.cgi?id=345035 Summary: problem with Xsetup for compiz in xorg 7.3 from Xorg74 sndirsch repository Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: sebastien.rohaut@free.fr QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: Customer Created an attachment (id=185317) --> (https://bugzilla.novell.com/attachment.cgi?id=185317) Xorg.0.log details Hi, Due to a mail exchange between Matthias Hopf and me here is a bug report. I'm using your Xorg74 experimental repository (from Stefan Dirsch) for Opensuse 10.3 to test your lastest packages. I put Severity to Blocker because of this bug xdm/kdm/gdm is not launched and users can't connect. It seems that /etc/X11/xdm/Xsetup in xorg-x11-7.3-24.1 has a "little" problem. I'm using the lastest flgrx ATI driver (8.43.2) on a ATI RADEON XPRESS 200M (II) fglrx(0): VESA VBE OEM: ATI RADEON XPRESS 200 Series (II) fglrx(0): VESA VBE OEM Software Rev: 1.0 (II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) fglrx(0): VESA VBE OEM Product: RS48 (II) fglrx(0): VESA VBE OEM Product Rev: 01.00 and when I start X11, it stops loading just before launching xdm or other graphical session manager (in fact kdm for me). Under a console (Ctrl+Alt+F1), I can see two process : glxinfo grep -q GLX_EXT_texture_from_pixmap launched by Xsetup, especially here, line 233-245 : if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then if test "$gdm" = "yes" ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi If I manually kill glxinfo kdm/xdm/gdm is launched and all is working well. It don't know why theses instructions are not working here, because when I'm logging and opening a X console (xterm, kconsole), it works : seb@p64p17bicb3:/etc/X11/xdm> glxinfo | grep -q GLX_EXT_texture_from_pixmap echo $? 0 Another thing, it seems that this code is used only if gdm is used, not kdm, so it is possible to modify as this to test it (it works for me because I use KDE) : # # Compiz # if test "$gdm" = "yes" ; then if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi Last : This problem occurs on my professional desktop computer (with ATI). At home, with the same Xorg release and a Nvidia card (with the lastest commercial nvidia driver), it works perfectly. It seems it's an issue with this release of Xorg and the use of fglrx driver. I will make some additional tests tomorrow at work as described by Matthias Hopf in his answer (in the next comment). I also have a notebook (HP NC6000) with Radeon 9600, I will upgrade it to this bugging release of Xorg and fglrx driver to see if I have the same problem. -- 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.

Show replies by date

bugzilla_noreply＠novell.com

29 Nov 29 Nov

19:44

New subject: [Bug 345035] problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository

https://bugzilla.novell.com/show_bug.cgi?id=345035#c1 --- Comment #1 from Sebastien ROHAUT 2007-11-29 12:44:23 MST --- Created an attachment (id=185318) --> (https://bugzilla.novell.com/attachment.cgi?id=185318) xorg.conf file used with fglrx driver -- 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.

bugzilla_noreply＠novell.com

19:45

New subject: [Bug 345035] problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository

https://bugzilla.novell.com/show_bug.cgi?id=345035#c2 Sebastien ROHAUT changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastien.rohaut@free.fr --- Comment #2 from Sebastien ROHAUT 2007-11-29 12:45:57 MST --- Here is the answer (by mail) from Matthias Hopf : On Nov 29, 07 11:40:40 +0100, sebastien.rohaut@free.fr wrote:

...

It seems that /etc/X11/xdm/Xsetup in xorg-x11-7.3-24.1 has a little problem.

In your case, yes, pleas open a bug report. This is serious.

...

if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then if test "$gdm" = "yes" ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi

If I manuallay kill the glxinfo process, then kdm is lauched and then all is working well.

Thanks for analyzing.

...

It don't know why Xsetup waits here, because when I'm logging and opening a X console, it works :

seb@p64p17bicb3:/etc/X11/xdm> glxinfo | grep -q GLX_EXT_texture_from_pixmap; echo $? 0

This buggers me as well. I have *no* clue what is happening here. If you create an according bug report, we could assign this to ATI. You might want to check some variables and linking: echo $DISPLAY ldconfig $glxinfo in the script just before calling glxinfo. If the output differs to the one you get from the shell, this would indicate something. Alternatively, add a sleep 2 in the script before the call to glxinfo. Maybe we have a race condition here.

...

Another thing, it seems that this code is used only if gdm is used, not kdm, so is it possible to modify as this to test if :

Ok, this is probably the Gnome people not speaking to the KDE people and vice versa. This change sounds reasonable, but it should rather be discussed whether a) we still need compiz on login manager time anyway (this used to work around another fglrx bug) b) if we need it why don't to start it for kdm as well?

...

# # Compiz # if test "$gdm" = "yes" ; then if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi

Thanks Matthias -- 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.

bugzilla_noreply＠novell.com

20:53

New subject: [Bug 345035] problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository

https://bugzilla.novell.com/show_bug.cgi?id=345035#c3 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sebastien.rohaut@free.fr --- Comment #3 from Stefan Dirsch 2007-11-29 13:53:22 MST --- Please try, what Matthias proposed =============================================================================== You might want to check some variables and linking: echo $DISPLAY ldconfig $glxinfo in the script just before calling glxinfo. If the output differs to the one you get from the shell, this would indicate something. Alternatively, add a sleep 2 in the script before the call to glxinfo. Maybe we have a race condition here. =============================================================================== Does the issue also happen after uninstalling the fglrx driver? Unfortunately I can't remember why we enabled compiz at login manager for gdm but not for kdm. -- 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.

bugzilla_noreply＠novell.com

30 Nov 30 Nov

15:23

New subject: [Bug 345035] problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository

https://bugzilla.novell.com/show_bug.cgi?id=345035#c4 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com Component|X.Org |X.Org Product|openSUSE 10.3 |openSUSE 11.0 Version|Final |unspecified --- Comment #4 from Matthias Hopf 2007-11-30 08:23:16 MST --- I'm setting this to openSUSE 11.0, because Xorg 7.4 won't be a package of 10.3. -- 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.

bugzilla_noreply＠novell.com

23:28

New subject: [Bug 345035] problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository

https://bugzilla.novell.com/show_bug.cgi?id=345035#c5 Hans-Peter Holler changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |holler@nefkom.info --- Comment #5 from Hans-Peter Holler 2007-11-30 16:28:38 MST --- Maybe this helps: as sebastien mentioned in comment #2

...

if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then if test "$gdm" = "yes" ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi seems to hang booting into graphics. Killing glxinfo at this state is the trick to go on further.

1st: the first test returns 1 _if_ $glxinfo _and_ $compiz can be resolved as existing executables. if one of them are not found the insided statements will not be executed and evaluated. 2nd: if $compiz is _not_ installed this test gives 0 and $glxinfo is _not_ executed (next inner if). 3rd: that's the item for SUSE/ATI: glxinfo hangs at the first invocation after boot, you have to ^C (or kill) this first run. All other runs will run fine. As I don't use compiz on my particular hardware (9700 Mobility) I did a rpm -e compiz and then I could start my notebook into graphics. Please note: this has nothing to do with the compiz package. Just removing it leads to "-x $compiz" evaluating to 0. The crux is the first call of glxinfo. It just hangs. BUT: IMO this is an ATI/AMD issue. glxinfo with the radeon driver returns without hang. This is with fglrx 8.42 and 8.43. -- 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.