Description of problem: Intel HD Graphics card based system. Putting the system to sleep and then waking back up results in black screen. Can not see KDE desktop, can not log into KDE, can not enter tty. Must use ctrl+backspace twice to restart X in order to log into KDE. Causes loss of any work that was in process before putting to system to sleep. Version-Release number of selected component (if applicable): Mageia 3 beta 2. Intel HD Graphics card. KDE 4.10 Desktop How reproducible: Put system to sleep with any of the options on KDE. Wake system up from sleep and find black screen. Steps to Reproduce: 1. Log into desktop 2. Put system to sleep 3. Press any key on keyboard to wake system up. 4. Black screen is present. 5. Use ctrl+backspace twice in order to be presented KDM login. Reproducible: Steps to Reproduce:
CC: sysadmin-bugs => (none)Component: Release (media or process) => RPM PackagesWhiteboard: (none) => 3beta2
CC: (none) => mageia, tmb
Works fine with intel cards for me (on two systems). Can you detail which h/w you have. Can you also confirm that switching to tty2, logging in via text console, typing "systemctl suspend" and then resuming as before exhibits the same behaviour or if it works fine?
Oh and as an additional test, can you install pm-utils and run "pm-suspend" from within a terminal in your KDE session (just as your regular user). Does that help the resume situation?
Colin Guthrie, The hardware is a Intel HD Graphics video card. As per the label on the machine. Mageia list it as: Identification Vendor: âIntel Corporation Description: âCore Processor Integrated Graphics Controller Media class: âVGA compatible controller Connection Bus: âPCI PCI domain: â0 Bus PCI #: â0 PCI device #: â2 PCI function #: â0 PCI revision: â0x12 Vendor ID: â0x32902 Device ID: â0x0070 Sub vendor ID: â0x4133 Sub device ID: â0x0894 Misc Module: âCard:Intel 810 and later Other specs list the card as a GMP coprocessor Logging in to tty2 and doing as you asked gets the same results of a black screen. Only this time I can't even use a ctrl+backspace to get back to tty1 where kdm is. I can't get to another tty or anything I have to hard reset the machine.
Doing a pm-suspend as a regualar user from within terminal in kde gets same black screen results. No KDE, no tty, just a black screen that I have to ctrl+backspace twice out of.
When we spoke on IRC you said you found an error in dmesg Chas, could you show what that was please.
Confirmed for me. Exact same behavior as described A few info on my system: $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) $ uname -a Linux horus 3.8.0-desktop-3.mga3 #1 SMP Thu Feb 28 00:34:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa task-kde4 task-kde4-4.9.97-2.mga3 Used Xorg driver : i810 This is rather new as 3 days before suspend and wake up were working smoothly Dunno if it's the new kernel. I'll test with pm-suspend and systemctl suspend
CC: (none) => maat-ml
tested disabling dm then with command line (as root) pm-suspend and systemctl suspend Same behavior : the system suspends then at wake up the screen is black and no mean to recover excepted reboot or systemctl start dm
Erratum systemctl start dm is not enough by itself : After that i need CTRL+ALT+F1 and then CTRL+ALT+BKSPC to get back the login screen
Just checked something. With the previous kernel the problem disappears : $ uname -a Linux horus 3.8.0-desktop-2.mga3 #1 SMP Fri Feb 22 20:39:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Same 3.8.0 but -2 instead of -3 (Thanks erinmargault for the idea that it could be the kernel)
Just because i tested yesterday, and it worked for me. One more point : not only coming back after suspend that was not working for me but more wildely energy saving behavior : no more switch off of the screen or locking screen (i have to lock it by myself as long as i run the latest kernel). Switching back to the previous one correct all the managing powersave problems. I will try to fill a bug report against latest kernel tomerrrow evening if noone else do it in the meantime.
CC: (none) => erinmargault
I've started seeing this since updating to the latest kernel (3.8.3-desktop-1.mga3) - the previous 3.8.1-1 and all earlier ones have been fine. On resume I get a blank screen with a static cursor in the top-left corner. Ctrl-Alt-F12 switches to the kernel messages, and ctrl-alt-F2 gives a blank screen with cursor (but no login prompt). I can switch back and forth between these two. However ctrl-alt-F1 locks the keyboard and a power-cycle is necessary. The WiFi lamp on the machine does not light. Hardware is a no-name Clevo laptop, core i3 processor, 4Gb RAM, Intel integrated graphics, Intel N135 wifi. One oddity. In /var/log/messages I have these entries at the time of suspend: Mar 17 10:15:44 localhost systemd-logind[780]: Suspend key pressed. Mar 17 10:15:44 localhost systemd[1]: Starting Sleep. Mar 17 10:15:44 localhost systemd[1]: Reached target Sleep. Mar 17 10:15:44 localhost systemd[1]: Starting Suspend... Mar 17 10:15:44 localhost systemd-sleep[7897]: Suspending system... However on the ctrl-alt-F12 screen after resume there are two further lines AFTER those: Mar 17 10:15:35 localhost kernel: PM: syncing filesystems ... done Mar 17 10:15:36 localhost kernel: PM: preparing system for mem sleep Is the timestamp on these lines being *before* the suspend key was pressed relevant?
CC: (none) => mg
when you resume, do you still have a mouse curser than can be moved around? On my system, which is a multiseat system, on resume from suspend, the intel graphics card just shows a blank screen with a curser. I can move the curser around, and the other head (ATI card) resumes OK. Killing the users processers, or kill -HUP on the affected X instance brings it back from suspend. I wonder if any of this is related to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/966744
CC: (none) => nelg
I have similar issue with NVIDIA card. Sometimes it resumes perfectly (seems to be random), sometimes it gives me blank screen, or just puts me back to KDM (after Xorg restarts). The card: VGA compatible controller: NVIDIA Corporation G86M [Quadro NVS 140M] (rev a1) The driver: dkms-nvidia-current-319.60-4.mga4.nonfree Th Xorg log: [162084.226] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 [162084.226] (==) NVIDIA(0): RGB weight 888 [162084.226] (==) NVIDIA(0): Default visual is TrueColor [162084.226] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) [162084.226] (**) NVIDIA(0): Option "AddARGBGLXVisuals" [162084.226] (**) NVIDIA(0): Option "DynamicTwinView" "false" [162084.226] (**) NVIDIA(0): Enabling 2D acceleration [162084.233] (II) NVIDIA(GPU-0): Display (Lenovo Group Limited (DFP-0)) does not support NVIDIA [162084.233] (II) NVIDIA(GPU-0): 3D Vision stereo. [162084.235] (II) NVIDIA(0): NVIDIA GPU Quadro NVS 140M (G86) at PCI:1:0:0 (GPU-0) [162084.235] (--) NVIDIA(0): Memory: 131072 kBytes [162084.235] (--) NVIDIA(0): VideoBIOS: 60.86.3e.00.00 [162084.235] (II) NVIDIA(0): Detected PCI Express Link width: 16X [162084.239] (--) NVIDIA(0): Valid display device(s) on Quadro NVS 140M at PCI:1:0:0 [162084.239] (--) NVIDIA(0): CRT-0 [162084.239] (--) NVIDIA(0): Lenovo Group Limited (DFP-0) (boot, connected) [162084.239] (--) NVIDIA(0): DFP-1 [162084.239] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock [162084.239] (--) NVIDIA(0): Lenovo Group Limited (DFP-0): 330.0 MHz maximum pixel clock [162084.239] (--) NVIDIA(0): Lenovo Group Limited (DFP-0): Internal Dual Link LVDS [162084.239] (--) NVIDIA(0): DFP-1: 330.0 MHz maximum pixel clock [162084.239] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS [162084.239] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [162084.239] (**) NVIDIA(0): device Lenovo Group Limited (DFP-0) (Using EDID [162084.239] (**) NVIDIA(0): frequencies has been enabled on all display devices.) [162084.240] (WW) NVIDIA(0): No valid modes for "DFP-0:1280x800{}"; removing. [162084.240] (II) NVIDIA(0): Validated MetaModes: [162084.240] (II) NVIDIA(0): "DFP-0:1440x900{}" [162084.240] (II) NVIDIA(0): Virtual screen size determined to be 1440 x 900 [162085.527] (--) NVIDIA(0): DPI set to (121, 120); computed from "UseEdidDpi" X config [162085.527] (--) NVIDIA(0): option [162085.527] (**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals. [162085.527] (--) Depth 24 pixmap format is 32 bpp [162085.527] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access. [162085.536] (II) NVIDIA(0): Setting mode "DFP-0:1440x900{}" [162086.337] (EE) NVIDIA(0): Failed to allocate primary buffer: out of memory. [162086.337] (EE) NVIDIA(0): *** Aborting *** [162091.056] (EE) [162091.056] (EE) Backtrace: [162091.056] (EE) 0: /etc/X11/X (xorg_backtrace+0x3d) [0x57f51d] [162091.056] (EE) 1: /etc/X11/X (0x400000+0x183289) [0x583289] [162091.056] (EE) 2: /lib64/libpthread.so.0 (0x7f9df733c000+0xf760) [0x7f9df734b760] [162091.056] (EE) 3: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xd9388) [0x7f9df1779388] [162091.056] (EE) 4: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xbf53e) [0x7f9df175f53e] [162091.056] (EE) 5: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xaffa1) [0x7f9df174ffa1] [162091.056] (EE) 6: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xaa314) [0x7f9df174a314] [162091.056] (EE) 7: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xaa945) [0x7f9df174a945] [162091.056] (EE) 8: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0x64a8e) [0x7f9df1704a8e] [162091.056] (EE) 9: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xd702b) [0x7f9df177702b] [162091.056] (EE) 10: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0xaffde) [0x7f9df174ffde] [162091.056] (EE) 11: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0x7e29e) [0x7f9df171e29e] [162091.056] (EE) 12: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0x7f7ac) [0x7f9df171f7ac] [162091.056] (EE) 13: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f9df16a0000+0x4ebe86) [0x7f9df1b8be86] [162091.056] (EE) 14: /etc/X11/X (AddScreen+0x71) [0x435aa1] [162091.056] (EE) 15: /etc/X11/X (InitOutput+0x3df) [0x47623f] [162091.056] (EE) 16: /etc/X11/X (0x400000+0x24b5b) [0x424b5b] [162091.056] (EE) 17: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f9df61a9c85] [162091.056] (EE) 18: /etc/X11/X (0x400000+0x2508f) [0x42508f] [162091.056] (EE) [162091.056] (EE) Segmentation fault at address 0x30 [162091.056] (EE) Fatal server error: [162091.056] (EE) Caught signal 11 (Segmentation fault). Server aborting [162091.056] (EE) [162091.056] (EE) Cheers!
CC: (none) => fathom
I think i have the same issue on Thinkpads T61 and R61, Nvidia graphics, mga4 x86_64: Bug 12712, i see xorg log error as comment 13. I have on both systems found that it do not happen if i only have few programs open, but always happen if i have a lot going on. Do any of you also have an abnormally long delay when returning from hibernation? Bug 12706
CC: (none) => fri
I have the same issue as comment 13 and comment 14 with my laptop, an ThinkPad X200 with Intel graphics. Th issue is randomly and in my case the password window to unlock the session disappears, I see the screen's wallpaper. I'm using Mageia 4 x86 with KDE. Here's some kernel and lspci infos: [florin@localhost ~]$ uname -a Linux localhost 3.12.8-tmb-laptop-1.mga4 #1 SMP Sun Jan 19 15:02:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [florin@localhost ~]$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07) 00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection (rev 07) 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection [florin@localhost ~]$
CC: (none) => cfrussen
Version: Cauldron => 4
I have seen this problem on two laptops now, but only since upgrading to Mageia 4. On both laptops, the problem is this: on waking from sleep, the screen is momentarily black, with a cursor visible, then the screen saver image appears briefly, and then the screen goes black again--and this is where I'd expect to see the KDE locked screen dialogue. That dialogue isn't present, though, just a cursor (which can be moved) on a black screen. The only way out is to hit ctrl-alt-backspace to restart X, or to restart the computer. What kind of debug logs would be helpful in tracking this down?
CC: (none) => steve
I have also this problem. With Mageia 3 and after upgrade to Mageia 4 problem stays. Sleep mode works before but after some kernel update it start with wakeup failing after sleeping (in both cases, lid close or manual sleep). I am using HP4545s with Intel/Ati Radeon graphics.
CC: (none) => gjevremovic
This is the bug: https://bugs.kde.org/show_bug.cgi?id=327947#c5 I can confirm that, if I get the black-screen bug, I can switch to another VT and log in and kill kscreenlocker_greet, which then restarts and lets me log in.
me tooãI can conform this bug with nvidia gso9600 graphics in mageia4 x86_64 systemã
CC: (none) => shimingzhou1980
I see on the kds pug an update is Committed on 24/04/2014 at 22:11. Pushed by wbauer into branch 'KDE/4.11'. When will this land in mga4 (or has it??) I have seen different variants of problems when waking up: 1)mga background without login, 2) complete black but i can switch to VT and reboot, 3)cpmplete hang. mga4 on thinkpad T61 and R61, tried both nvidia and noveau. (also now seeing same on fedora 20 installed as test on the R61)
kds pug -> KDE bug (hey fingers, time to wake up!)
I have the same symptoms as comment 16, that is, when wakening from suspend, the power, etc lights flash as in booting, then normal displays (the previous session) for a second or 2 (this varies), and it goes to sleep again, the screen going blank, then the power, etc lights flashing again like rebooting, and stabilizing with lights indicating power + operating + battery (as normal when running), but the screen stays blank. My laptop has an amd processor with integrated radian mobility video. This problem has existed at least since mga2 (I was late upgrading), as well as mga3 and 4. Also a problem on another laptop (with the same graphics chip) that I haven't tested recently. I've been avoiding suspend because of this, except for occasional testing. I used gnome + gnome fallback for mga3 and before, mate with mga4. The symptoms may have been slightly different before mga4.
CC: (none) => andre999mga
FWIW sleep problems are for me gone on cauldron for all laptops i cater for 32 and 64 bit, Intel and Nvidia. (The Nvidia systems fail resuming from hibernation but sleep is OK) You may want to try cauldron, mageia 5 beta. I have already since about month switched all my systems, including production, to mga5.
I have this problem on mageia 5 beta 3 with KDE The screen gets crazy after sleep. It's not a true black screen, has rectangular stripped white elements in it. It happens randomly. Once it resume nicely, the other time not. I have an Nvidia Card. And i'm on a x86_64 Have to hard reset to get out of this kind of artistic canvas.
CC: (none) => amorthewada
I have that sometimes on mga4 also. On every 3rd-10th resume X either crashes, screen goes completely black (but plasma seems to work,except that everything is black but the mouse pointer) or totally scrambled and on mouse movement it hastly changes.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD
Under mga5 and Maté desktop, sleep/suspend works perfectly now. (Previous symptoms under mga4 & Maté listed in comment 16.)