I searched for this in bugs.kde.org but no matches.. Since upgrading to Kubuntu Precise, often (not all the time) when resuming from suspend the desktop comes back as normal except there is no mouse cursor and the only key strokes that function are Ctrl+Alt+Del (I tried Alt+F4 to close applications) The desktop works as normal, I can see Plasma widgets doing their thing and various applications showing notifications. When I move the mouse, while there is no mouses cursor I can see various elements on the desktop appearing in their mouse over state, so it looks like the mouse is working without the cursor. The only way to fix it is to reboot the system with Ctrl+Alt+Del. I don't think there is a keystroke to restart X. Hardware: Dell XPS 1330 laptop, Kubuntu 12.04 with 4.8.3 packages, Nvidia 8600, nouveau driver, second monitor via HDMI managed by krandr, USB mouse plugged into laptop, USB Apple keyboard plugged into laptop. Reproducible: Sometimes Steps to Reproduce: 1.Suspend using the battery icon in systray 2.Resume from suspend by pressing power button 3.Sometimes the events happening in "Details" happen Actual Results: See Details Expected Results: Mouse cursor should appear and keyboard should work beyond Ctrl+Alt+Del after resume all the time. Not sure if this is a kwin bug, please move if it isn't.
Should add that the system was running KDE 4.8.2 before the upgrade, maybe that is relevant.
That is neither a KWin nor likely even a KDE bug - the issue is in either the kernel, udev or X11 (or ubuntu) Wild guess: remove the external input devices before going to STR. Some tests if the above fails (leave the external devices away for testing to rule them out as secondary points of failure): Since you say you can see mouse over effects (and likely will be able to click as well) the absent cursor image is likely a bug in the framebuffer of the graphics driver - there's a good chance that this is induced by the running OpenGL compositor (or any other OpenGL application/context) -> Try suspending the compositor (shift+alt+f12) before suspending to ram (you can use the same shortcut to reactivate it after wake up) Regarding the keyboard: ctrl+alt+del should open the process manager (ksysguard, to be more precise) and certainly NOT restart the computer (it's not windows) If enabled in xorg.conf, ctrl+alt+backspace will "zap" the X11 server, ctrl+alt+F[1-6] should allow you to switch to VT0 - VT5 *Iff* only zapping and switching to some VT does work, there's pot. sth. grabbing the keyboard - unfortunately it's not easily possible to figure what that is. Another option would be that the auto-added keyboard is not of the same type as the one that was present before the STR. If you can switch to VT0 and log in there, "export DISPLAY=:0" and then use setxkbmap to set the correct model, layout and variant (use "setxkbmap -print" to see them before STR) If you figure the issue, it's possible to automatize workarounds with pmtools.
Thomas, this appears to be mostly sorted with 4.9. There is another dual monitor / suspend issue on a fresh 4.9 install but I think that's unrelated so I'll open a new bug report. And Ctrl+Alt+Del *does* restart in this instance unless I'm hallucinating (something crashing, allowing that keystroke to work ?). Yes it's not Windows, have been using KDE since 2003 ;)
a) is this tied to a multiscreen setup, and in case, of what kind (xrandr, xinerama, multihead) b) do VT shortcuts (ctrl+alt+F<n>) usually work and do they work when this happens? c) do you have access to a second machine that you could use to ssh into the "broken" one? I frankly doubt that the KDE version is related to this unless you are sure to _only_ have updated KDE and not other parts (such as the kernel, udev, X11, nouveau, etc.)
Hi Thomas Not sure if what's happening now is the same as before but I'll note it down here anyway and we can go from there. Would be great to get this squashed. It is related to a multi-screen setup, using xrandr: cat ~/.kde/share/config/krandrrc [Display] ApplyOnStartup=true StartupCommands=xrandr --output LVDS-1 --pos 0x0 --mode 1280x800 --refresh 59.9913\nxrandr --output VGA-1 --off\nxrandr --output VGA-1 --primary [Screen_0] OutputsUnified=false UnifiedRect=0,0,0,0 UnifiedRotation=1 [Screen_0_Output_HDMI-1] Active=true Rect=0,0,0,0 RefreshRate=0 Rotation=1 [Screen_0_Output_LVDS-1] Active=true Rect=2048,0,1280,800 RefreshRate=59.9913482666016 Rotation=1 [Screen_0_Output_VGA-1] Active=false Rect=0,0,2048,1152 RefreshRate=59.9087333679199 Rotation=1 [Screen_0_Output_default] Active=true Rect=0,0,0,0 RefreshRate=50 Rotation=1 Worth noting: defaults are never applied on startup and have never been applied on startup but this appears to be a separate issue ( #183143 ) The issue that now occurs seems to happen with these steps: 1. Using two monitors (laptop screen LVDS and a large flatscreen - HDMI or VGA) 2. Open Krandr, disable the external, set the origin to 0,0 for LVDS, apply. 3. Go to STR on the laptop 4. Unplug monitor, close laptop lid 5. Any time later, open lid, resume laptop without an external monitor. 6. The laptop screen looks to be turned off, although power, network (wlan) and disk activity lights are working. It looks like the backlight is off. No mouse cursor. 7. Keyboard inputs: Ctrl+Alt+Del restarts the machine sometimes (yes it does) - I can see disk activity light then after a while it reboots into the BIOS screen then into KDE login 8. If the power-off button is pressed, shuts down the machine - disk activity light. 9. After restart the screen works as expected. Other notes: 1. Sometimes when returning from suspend I get a warning that kded has crashed. If I continue on past that point, the external screen will not come up even though krandr detects it. Only a restart will bring everything back. 2. This has happened across Kubuntu OS reinstalls and KDE versions. Currently on 12.04.1 and KDE 4.9.1 from PPA packages. Answering you questions: a) is this tied to a multiscreen setup, and in case, of what kind (xrandr, xinerama, multihead) - yes, krandr / xrandr as above b) do VT shortcuts (ctrl+alt+F<n>) usually work and do they work when this happens? - ctrl+alt+f1 worked once for a second I got a shell login prompt then the system shut down c) do you have access to a second machine that you could use to ssh into the "broken" one? - I will try. How would we decide whether this is an OS or KDE issue ? Thanks