Bug 494918 - glxgears freezes on fastuserswitch
glxgears freezes on fastuserswitch
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
: Reopened, Triaged
Depends On:
  Show dependency treegraph
Reported: 2009-04-08 13:46 EDT by Amit Shah
Modified: 2018-04-11 02:51 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 07:44:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Amit Shah 2009-04-08 13:46:08 EDT
Running the fastuserswitch test for the Intel driver from a Live USB of the Beta release. The hardware is


ThinkPad X200, Intel graphics.

The Live CD has one LiveUser and one xguest user. I select 'Live System User' on the top gnome panel, click on 'Quit...', switch user, go to the Guest user. Spend some time there and with the same set of steps, come back to the Live User session. This is the output from glxgears.

$ glxgears 
2715 frames in 5.0 seconds = 542.823 FPS
940 frames in 38.3 seconds = 24.526 FPS
2596 frames in 5.0 seconds = 519.190 FPS
2914 frames in 5.0 seconds = 582.750 FPS
3135 frames in 5.0 seconds = 627.000 FPS

Note how it froze for the 2nd entry when I switched to the 'Guest' user.
Comment 1 Matěj Cepl 2009-04-10 11:05:04 EDT
And the bug is what? Computer is pretty busy while switching users, so it is now wonder glxgears gets slower. Meanwhile, glxgears is pretty bad as far as testing speed of graphics goes, try fire instead.

Closing as NOTABUG for now, if you disagree please reopen with some more additional information.
Comment 2 Amit Shah 2009-04-14 04:59:41 EDT
I understand glxgears will get slower while the computer is busy switching. The computer, however, shouldn't be busy after the switching has taken place. When nothing else happens, the computer would be idle and glxgears should be able to run at full speed, yes?

I was running the test from the QA page for the Intel test day which mentions the glxgears test.
Comment 3 Amit Shah 2009-04-14 05:00:48 EDT
BTW glxgears proceeded to 940 after I switched *back* to the live user session. Note that 38s had passed when I was in the other session and nothing else was happening.
Comment 4 Bug Zapper 2009-06-09 09:29:54 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 6 Matěj Cepl 2009-11-05 13:25:46 EST
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Comment 7 Bug Zapper 2010-04-27 09:34:09 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 8 Bug Zapper 2010-06-28 07:44:49 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.