Bug 167268 - ATI Drivers cause lockups with xscreensaver.
Summary: ATI Drivers cause lockups with xscreensaver.
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-09-01 03:36 UTC by redhat admin
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-08-14 15:40:54 UTC

Attachments (Terms of Use)

Description redhat admin 2005-09-01 03:36:36 UTC
Description of problem:

While not specifically a "Fedora" issue I thought I'd alert you guys to this one.

I have the latest ATI opengl drivers from LIVNA repository;


When I lock my screen, the screensavers work perfectly, but when I try and
unlock the screen, by typing my password, the system locks up. It is not
pingable and I cant change to a VT.

PS - this was also the case on the older version of the drivers and the older

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. Install ATI drivers
2. lock screen, 
3. try and unlock.
Actual results:

Machines locks up.

Expected results:

Access to machine is granted.

Additional info:

Comment 1 Ray Strode [halfline] 2005-09-01 13:09:04 UTC

I don't think there is much we can do if this is being caused by an unsupported

Does it happen if you don't use the livna ati drivers?

Comment 2 redhat admin 2005-09-01 22:34:11 UTC
Correct, however, I forgot to mention that the screensavers work perfectly in
'Demo' or 'Preview' mode of xscreensaver. So I'd suggest that maybe the problem
is with the "password input dialog"/"screen unlocking" part of the xscreensaver
code ?

No it doesnt happen without the livna ati drivers.

Comment 3 Christian Iseli 2007-01-22 10:40:00 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?


Comment 4 Ray Strode [halfline] 2007-08-14 15:40:54 UTC
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thank you in advance.

(this message is mass message)

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