Red Hat Bugzilla – Bug 509973
Intel Mobile 4 Series: HW Cursor corrupted after resume from hibernate
Last modified: 2010-05-10 19:13:29 EDT
Created attachment 350743 [details]
Description of problem:
After resuming a Dell E4200 from hibernate, the hardware cursor is corrupted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
HW Cursor corrupted
HW Cursor being shown correctly.
Xorg log and screencam attached.
Created attachment 350752 [details]
Camshot of the corrupted cursor
I see the same problem on a Lenovo x300 after resuming from suspend-to-ram.
My cursor looks exactly the same as the attached camshot after hibernation. I have a Lenovo ThinkPad SL500 with integrated graphics running Fedora 11 x86-64. Interestingly, clicking on the link to the attached camshot caused the cursor to return to normal.
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 (at least F12Beta, but even better if the very latest versions).
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.]
I have tried hibernating my computer 2 or 3 times a day for the past several days, and I have not seen the corrupted cursor. The problem looks like it's fixed in Fedora 11.
(In reply to comment #5)
> I have tried hibernating my computer 2 or 3 times a day for the past several
> days, and I have not seen the corrupted cursor. The problem looks like it's
> fixed in Fedora 11.
Steve, according to comment #5, you are reporting that the original bug has been fixed. Thank you for your testing efforts.
Andreas, as the originating reporter, could you please update your system and attempt to reproduce your original issue and let us know if it has been resolved for your hardware? If it is we can close this issue (CLOSED RAWHIDE), or you can close it as (CLOSED WORKSFORME). If you are unable to test an updated system, please let use know, and in that case we can accept Steve's test results. If we do not hear from you in the time frame indicated by comment $4, we will close this bug as CLOSED INSUFFICIENT_DATA.
Fedora Bugzappers volunteer triage team
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.