| 2012-06-02 12:33:56 |
Alexander Neumann |
description |
1) I'm using Ubuntu 12.04
3) When waking up from suspend by opening the lid of my laptop (Lenovo X200s), I expect to see my wallpaper and the login window asking for my password.
4) I only see the mouse cursor and a black background. Rarely I also see the upper panel of Unity. It is impossible to login or do any other action except clicking ctrl+alt+f1 which seems functional. This bug does not always occur but quite frequently, my guess is that it is a 50% chance
What I find interesting is, that it appears that other Thinpads of the X series are also affected. On AskUbuntu http://askubuntu.com/questions/124399/laptop-screen-goes-blank-after-waking-from-sleep somebody has the same problem with a Lenovo X200 and also somebody with a X220 has the same problem. It was suggested to report a bug. I could not find any regarding this issue, but in case Tojo has already reported the problem, this is a duplicate.
I never experienced the bug before Ubuntu 12.04 (9.04-11.10 worked fine), however, I am not sure whether the bug has been there the whole time after doing a fresh install of 12.04 |
1) I'm using Ubuntu 12.04
3) When waking up from suspend by opening the lid of my laptop (Lenovo X200s), I expect to see my wallpaper and the login window asking for my password.
4) I only see the mouse cursor and a black background. Rarely I also see the upper panel of Unity. It is impossible to login or do any other action except clicking ctrl+alt+f1 which seems functional. This bug does not always occur but quite frequently, my guess is that it is a 50% chance
What I find interesting is, that it appears that other Thinkpads of the X series are also affected. On AskUbuntu http://askubuntu.com/questions/124399/laptop-screen-goes-blank-after-waking-from-sleep somebody has the same problem with a Lenovo X200 and also somebody with a X220 has the same problem. It was suggested to report a bug. I could not find any regarding this issue, but in case Tojo has already reported the problem, this is a duplicate.
I never experienced the bug before Ubuntu 12.04 (9.04-11.10 worked fine), however, I am not sure whether the bug has been there the whole time after doing a fresh install of 12.04 |
|
