Public bug reported:
Binary package hint: displayconfig-gtk
Those with NVIDIA legacy graphics devices running the proprietary
nvidia-glx-legacy driver with Xgl cannot login once they have used the
Screens and Graphics program to make any kind of change.
(I believe those with these devices who wish to run compiz must run Xgl)
Unfortunately bulletproof-x is not started.
Related to bug 91064 because Xgl uses gl through xorg and the
proprietary nvidia drivers. Since gdm doesn't use glx there is no
problem until after login.
Another possible symptom:
Option "AddARGBGLXVisuals" "True" is also removed by the Screens and Graphics
program, so windows borders may disappear. I don't have a recent nvidia card so
I can't test this; it's only a suspicion.
Additional Information
In response to bug 91064 the above Option AllowGLXWithComposite line is
added to xorg.conf in the nvidia driver of the restricted-manager for
legacy nvidia devices. When anything is changed by the Screens and
Graphics program that program uses displayconfigabstraction.py in
guidance-backends to change the xorg.conf file. When it does so it drops
the option above because it basically creates a brand new device section
in that file.
The following test reveals the problem Xgl is having when one can't log
on:
sudo /usr/bin/Xgl vt9 :21
Fatal server error:
no GLX visuals available
If not running Xgl the problem manifests itself by discontinuing the ability to
run glx program. Running glxgears gives the following message:
glxgears
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual
This is because:
xserver-xorg's Xorg.0.log reports:
(EE) GLX is not supported with the Composite extension
I'm reporting this as a problem with guidance-backend, but another way
to address this problem would be for restricted manager to set this
option (as well as NoLogo and ARGBGLXVisuals) in the screen section
rather than in the device section since that isn't recreated by
displayconfigabstraction.py
Confirmation:
sudo dpkg-reconfigure -phigh xserver-xorg
System->Administration->Restricted Drivers Manager
Enable the proprietary driver and close
Confirm that the option Nolog and either AllowGLXWithComposite or
AddARGBGLXVisuals is now part of the device section of
/etc/X11/xorg.conf
System->Administration->Screens and Graphics
Change the monitor type and press ok
Confirm that the options have been removed from the device section of
/etc/X11/xorg.conf
If using nvidia-glx-legacy try to logo on.
To recover from this using nvidia-glx-new or nvidia-glx run:
sudo nvidia-xconfig -c /etc/X11/xorg.conf --allow-glx-with-composite --no-logo
--add-ARGB-GLX-Visuals
(I understand that the last option is valid with this configuration's
nvidia-xconfig)
or, if running a nvidia-glx-legacy, run from a console or failsave gnome
session:
sudo nvidia-xconfig -c /etc/X11/xorg.conf --allow-glx-with-composite
--no-logo
and logon normally. nvidia-xconfig moves these options, whether new or
whether it is adding them, to the session section of the xorg.conf file,
where they will be safe from the Screens and Graphics program in the
future.
The legacy driver is not harmed by having the AddARGBGLXVisual option
included--it only produces a warning.
This is only my second bug report so please forgive and correct me if
I'm reporting this incorrectly.
** Affects: displayconfig-gtk (Ubuntu)
Importance: Undecided
Status: New
** Tags: bug91064 guidance-backends nvidia-glx-legacy restricted-manager
** Tags added: bug91064 guidance-backends nvidia-glx-legacy restricted-
manager
** Description changed:
Binary package hint: displayconfig-gtk
Those with NVIDIA legacy graphics devices running the proprietary
nvidia-glx-legacy driver with Xgl cannot login once they have used the
Screens and Graphics program to make any kind of change.
(I believe those with these devices who wish to run compiz must run Xgl)
Unfortunately bulletproof-x is not started.
Related to bug 91064 because Xgl uses gl through xorg and the
proprietary nvidia drivers. Since gdm doesn't use glx there is no
problem until after login.
Another possible symptom:
Option "AddARGBGLXVisuals" "True" is also removed by the Screens and Graphics
program, so windows borders may disappear. I don't have a recent nvidia card so
I can't test this; it's only a suspicion.
Additional Information
In response to bug 91064 the above Option AllowGLXWithComposite line is
added to xorg.conf in the nvidia driver of the restricted-manager for
legacy nvidia devices. When anything is changed by the Screens and
Graphics program that program uses displayconfigabstraction.py in
guidance-backends to change the xorg.conf file. When it does so it drops
the option above because it basically creates a brand new device section
in that file.
The following test reveals the problem Xgl is having when one can't log
on:
sudo /usr/bin/Xgl vt9 :21
Fatal server error:
no GLX visuals available
If not running Xgl the problem manifests itself by discontinuing the ability
to run glx program. Running glxgears gives the following message:
glxgears
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual
This is because:
xserver-xorg's Xorg.0.log reports:
(EE) GLX is not supported with the Composite extension
I'm reporting this as a problem with guidance-backend, but another way
to address this problem would be for restricted manager to set this
option (as well as NoLogo and ARGBGLXVisuals) in the screen section
rather than in the device section since that isn't recreated by
displayconfigabstraction.py
Confirmation:
sudo dpkg-reconfigure -phigh xserver-xorg
System->Administration->Restricted Drivers Manager
Enable the proprietary driver and close
Confirm that the option Nolog and either AllowGLXWithComposite or
AddARGBGLXVisuals is now part of the device section of
/etc/X11/xorg.conf
System->Administration->Screens and Graphics
Change the monitor type and press ok
Confirm that the options have been removed from the device section of
/etc/X11/xorg.conf
If using nvidia-glx-legacy try to logo on.
To recover from this using nvidia-glx-new or nvidia-glx run:
sudo nvidia-xconfig -c /etc/X11/xorg.conf --allow-glx-with-composite
--no-logo --add-ARGB-GLX-Visuals
(I understand that the last option is valid with this configuration's
nvidia-xconfig)
or, if running a nvidia-glx-legacy, run from a console or failsave gnome
session:
sudo nvidia-xconfig -c /etc/X11/xorg.conf --allow-glx-with-composite
--no-logo
and logon normally. nvidia-xconfig moves these options, whether new or
whether it is adding them, to the session section of the xorg.conf file,
where they will be safe from the Screens and Graphics program in the
future.
The legacy driver is not harmed by having the AddARGBGLXVisual option
included--it only produces a warning.
+
+ This is only my second bug report so please forgive and correct me if
+ I'm reporting this incorrectly.
--
Cannot logon after using Screens and Graphics program with nvidia-glx-legacy
driver
https://bugs.launchpad.net/bugs/153800
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
