Sometimes, usually when updates are installed, after booting, I get a gdm screen similar to this - http://lippolweblog.files.wordpress.com/2009/09/gdm.png. It uses the same animations as the new black gdm, but it just has the plain white layout as of the old gdm 2.x. Has anyone experienced this? What is the cause?
On Thu, 2013-02-28 at 16:13 +0000, Marco Scannadinari wrote:
Sometimes, usually when updates are installed, after booting, I get a gdm screen similar to this - http://lippolweblog.files.wordpress.com/2009/09/gdm.png. It uses the same animations as the new black gdm, but it just has the plain white layout as of the old gdm 2.x. Has anyone experienced this? What is the cause?
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails. That includes a timeout. If your machine is starting a lot of services at boot, and if your hard drives are too busy loading stuff to run the test tool as quickly as they should, this may happen. It likely won't be shown if you get a faster hard disk. Clearly a bug though.
Dan
On Thu, Feb 28, 2013 at 5:06 PM, Dan Williams dcbw@redhat.com wrote:
On Thu, 2013-02-28 at 16:13 +0000, Marco Scannadinari wrote:
Sometimes, usually when updates are installed, after booting, I get a gdm screen similar to this - http://lippolweblog.files.wordpress.com/2009/09/gdm.png. It uses the same animations as the new black gdm, but it just has the plain white layout as of the old gdm 2.x. Has anyone experienced this? What is the cause?
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails. That includes a timeout. If your machine is starting a lot of services at boot, and if your hard drives are too busy loading stuff to run the test tool as quickly as they should, this may happen. It likely won't be shown if you get a faster hard disk. Clearly a bug though.
I'm not sure the speed of the HDD makes much difference. I've got a SSD and on occasion I get it as well. I also occasionally get a fall back to the old style dialog when logged into the desktop. One minute I'll get the new one when I need to unlock a ssh key, the next the old one when I need to put in some network details and then back to the new one (not saying it's network, that's an example, can be any dialog) when it's running g-s fine. Tends to happen more when the machine has been up for longer.
Peter
On Thu, 2013-02-28 at 18:06 +0100, Dan Williams wrote:
On Thu, 2013-02-28 at 16:13 +0000, Marco Scannadinari wrote:
Sometimes, usually when updates are installed, after booting, I get a gdm screen similar to this - http://lippolweblog.files.wordpress.com/2009/09/gdm.png. It uses the same animations as the new black gdm, but it just has the plain white layout as of the old gdm 2.x. Has anyone experienced this? What is the cause?
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails. That includes a timeout.
Can it not, please? Seriously, what a terrible idea.
- ajax
On 02/28/13 18:49, Adam Jackson wrote:
On Thu, 2013-02-28 at 18:06 +0100, Dan Williams wrote:
On Thu, 2013-02-28 at 16:13 +0000, Marco Scannadinari wrote:
Sometimes, usually when updates are installed, after booting, I get a gdm screen similar to this - http://lippolweblog.files.wordpress.com/2009/09/gdm.png. It uses the same animations as the new black gdm, but it just has the plain white layout as of the old gdm 2.x. Has anyone experienced this? What is the cause?
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails. That includes a timeout.
Can it not, please? Seriously, what a terrible idea.
Perhaps the most profound feature of the gdm, discreet way of telling you to switch over. ;)
poma
On Thu, 2013-02-28 at 12:49 -0500, Adam Jackson wrote:
On Thu, 2013-02-28 at 18:06 +0100, Dan Williams wrote:
On Thu, 2013-02-28 at 16:13 +0000, Marco Scannadinari wrote:
Sometimes, usually when updates are installed, after booting, I get a gdm screen similar to this - http://lippolweblog.files.wordpress.com/2009/09/gdm.png. It uses the same animations as the new black gdm, but it just has the plain white layout as of the old gdm 2.x. Has anyone experienced this? What is the cause?
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails. That includes a timeout.
Can it not, please? Seriously, what a terrible idea.
The magic file is /usr/share/gnome-session/sessions/gdm-shell.session and the magic line is IsRunnableHelper. It's actually run by *gnome-session*, not gdm. And if that line fails (due to issues in kernel DRM or the graphics stack or your slow disk), or takes longer than 3000ms, then you get the fallback session instead of the fancy one.
IsRunnableHelper=bash -c 'gnome-shell --help | grep -q gdm-mode && /usr/libexec/gnome-session-check-accelerated'
--- /* See https://bugzilla.gnome.org/show_bug.cgi?id=641992 for discussion */ #define GSM_RUNNABLE_HELPER_TIMEOUT 3000 /* ms */ ---
Dan
Hi,
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails.
Can it not, please? Seriously, what a terrible idea.
Colin dropped support for the older UI upstream yesterday:
https://bugzilla.gnome.org/show_bug.cgi?id=695414
And I moved the acceleration check outside of the timeout code a few days before that:
https://bugzilla.gnome.org/show_bug.cgi?id=672943
--Ray
On Fri, 2013-03-08 at 11:56 -0500, Ray Strode wrote:
Hi,
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails.
Can it not, please? Seriously, what a terrible idea.
Colin dropped support for the older UI upstream yesterday:
https://bugzilla.gnome.org/show_bug.cgi?id=695414
And I moved the acceleration check outside of the timeout code a few days before that:
I still don't understand why that timeout is there at all. What is it meant to fix?
- ajax
On Fri, 2013-03-08 at 12:33 -0500, Adam Jackson wrote:
On Fri, 2013-03-08 at 11:56 -0500, Ray Strode wrote:
Hi,
The "older" UI is shown when detection that your graphics card has the necessary OpenGL support fails.
Can it not, please? Seriously, what a terrible idea.
Colin dropped support for the older UI upstream yesterday:
https://bugzilla.gnome.org/show_bug.cgi?id=695414
And I moved the acceleration check outside of the timeout code a few days before that:
I still don't understand why that timeout is there at all. What is it meant to fix?
Hanging for 10 seconds waiting to see if your GPU supports enough GL to run the shell before falling back to the classic one. All that wait time delays showing the GDM greeter, so faster bootup pretty much requires a bound of some sort on this operation.
Dan
On Fri, 2013-03-08 at 12:00 -0600, Dan Williams wrote:
On Fri, 2013-03-08 at 12:33 -0500, Adam Jackson wrote:
I still don't understand why that timeout is there at all. What is it meant to fix?
Hanging for 10 seconds waiting to see if your GPU supports enough GL to run the shell before falling back to the classic one. All that wait time delays showing the GDM greeter, so faster bootup pretty much requires a bound of some sort on this operation.
I don't think that argument makes sense.
One: if GL initialization takes meaningful time, it can really only be because the kernel decided not to schedule you yet. Because, presumably, your disk is busy with whatever, readahead maybe or maybe you have a mail queue and sendmail is busy shoving stuff out. Or you're in a VM and it's a busy machine. At any rate that test does not hang forever, it merely takes time to complete. There's really not a sense in which you will display things _faster_ if you decide to time out. The pure-X window you create, modulo a few million instructions of GL context creation, will show up at about the same time the GL-composited window you would otherwise create, because whatever it is you're contending with _is still going on_ and is the whole reason you might bump into the timeout.
Two: Why is there still a classic greeter if there's no fallback mode?
- ajax
desktop@lists.fedoraproject.org