From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Description of problem:
On my HP pavilion ze4220 laptop (ATI IGP 340M video card). X appears
not to completly stop and or release the screen (sorry for not being
technical) when logging off, switching to another virtual terminal (
ex. ctrl-alt-f2 just incase i called it the wrong thing), stoping X
with ctrl-alt-backspace, exiting system-config-display on initial
boot, or when booting with rhgb in my grub.conf (x seems to load but
nothing is displayed). In all cases I get a black (blank) screen and
the computer won't respond to any combination of keystrokes. As I said
above this seems to happen any time X is stopped or no longer
accessing the display. This happens with both the vesa and radeon
drivers and did not occur in test 2 (with the exception of having to
remove rhgb from grub.conf for the first boot only).
- HP ze4220 laptop
- generic 1024x768 display
- unaltered clean install of fct3
- unaltered xorg.config (execpt adding 1024x768 res. by hand. bug
already open on the subject)
- fully up2dated from rawhide (default source)
- kernel 2.6.5-1.327
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install fc2t3 on a laptop with a IGP 340M video card (pos. others)
2. attempt to perform any of the actions listed above
Actual Results: blank black screen and no response from keybord or
Expected Results: X to play nice and restart, start, stop, or
whatever it should do depending on the action performed
Let me know if you need any other info i.e. my xorg.config, logs (they
dont show anything funny though - at least to me), or want me to run
any commands and post the results
Problem seems to have corrected itself over night. Nothing done to the
machine other than installing j2sdk1.4.2 and apt-get (unused) from
rpm. Will leave it up to the powers to be if they want to keep this
bug open and look into it.
Sounds odd, could be a duplicate of bug #123424.
Since it seems to have gone away, I'm closing the bug.
If you experience something like this again, please consider upgrading
the a more recent kernel RPM.