Description of problem: When I restore the computer after a hibernate, then the characters in Firefox, the Menu bar and Nautilus appear all broken, Only in edit screen they show up readable. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start Firefox 2. Click 'System-Shutdown' and select 'Hibernate'. 3. Restart the computer after having it turned off It does not even help to log out and in again. The characters are all broken.
Created attachment 549 [details] Firefox screenshot after restore from Hibernate
+1 With me happens on all desktop text. Screensaver text also affected. i810 based card (Aspire 2920). As a workaround, I restart X server (CTRL-ALT-BKSP twice) after resume to refresh video memory.
CC: (none) => luzemario
Is this still valid with all latest updates installed?
CC: (none) => stormi
Keywords: (none) => NEEDINFOWhiteboard: (none) => check
It works! Great!
Ok so closing, thanks for the reply
Status: NEW => RESOLVEDResolution: (none) => FIXED
Created attachment 963 [details] The characters are broken again after awake from hybernate.
still not always working
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
CC: (none) => lohmaier+mageia
Can you attach the output of dmesg ? Thierry is this bug related to Xorg ?
Keywords: NEEDINFO => (none)CC: (none) => thierry.vignaudWhiteboard: check => (none)
Created attachment 1032 [details] dmesg after recover from hibernate
I guess the kernel isn't restoring all of the gfx card state
Assignee: bugsquad => tmbSource RPM: (none) => kernel
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. Is this bug still valid?
CC: (none) => marja11
I have reopened this issue. But now it is fixed. So close this.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
After upgrade to Mageia 2 and GNOME this error is back again.
Version: 1 => 2
What's the result of the following commands: uname -r lspcidrake|fgrep Card
Keywords: (none) => NEEDINFO
[root@localhost ~]# uname -r 3.3.6-1.mga2 [root@localhost ~]# lspcidrake|fgrep Card Card:Intel 810 and later: Intel Corporation|Mobile 4 Series Chipset Integrated Graphics Controller [DISPLAY_VGA] (rev: 07)
So the culprit would be intel drm driver then. You could try to enable the "Core Updates Testing" medium and try kernel-desktop-3.3.8
Summary: characters broken after restart from hibernate => characters broken after restart from hibernate (drm intel)
The recover from Hibernate works with kernel-desktop-3.3.8! [franz@localhost ~]$ uname -r 3.3.8-desktop-2.mga2
Created attachment 2623 [details] Mageia 2 GNOME after awake from hibernate
I have tried hibernate a second time and the characters are all wrong.
Keywords: NEEDINFO => (none)
No need to hibernate to see the corruption, the more memory is used, the more likely it is for the corruption to occur. Restarting gnome-shell with <alt>+<F2>, r, <enter> does work as a workaround. (except for the corruption in the desktop-background, but that might be because I enabled desktop-icons and I think nautilus does the rendering of the background in that case) Much more annoying than the corruption is non-smooth video playback (jerky pans). After a reboot or after restarting gnome-shell the rendering is almost OK, but the longer the uptime the worse it gets. Video playback is flawless in gnome's fallback mode. (intel GM965)
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 Mageia version prior to Mageia 2'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 Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
still occurs in Mageia 3, but as I don't expect a fix from mageia itself anyway... More a task for upstream kernel/intel driver developers
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD