Description of problem:
On Test3, attempting to preview the "discrete" screensaver immediately locks
system up, requiring a reboot.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Will attach sysreport collected after crashing system, it should show my
hardware config and with luck any errors that might have been logged (although
its locked up so tight I doubt it).
Hmm. My machine loves to make a fool of me. It hung on a different screen saver,
the next one after discrete, iirc.
do you have xscreensaver-gl-extras installed?
Created attachment 124931 [details]
xscreensaver-gl-extras == no.
when it locks up, does pressing caps lock make the keyboard light come on? Does
ctrl-alt-backspace recover the system and bring you back to the login screen?
Can you ssh remotely?
Caps/Numlock: No (and not flashing, either)
ssh: no system available to try from.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release 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.]
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)