Bug 290266

i can only imagine some "funny" interaction with kwin and the x server ...
maybe try disabling compositing?

"kcmshell kwincompositing", 3rd tab ("advanced") - is "suspend desktop effects for fullscreen windows" checked?
Try to uncheck it.

Hello Thomas, hello Oswald,
"kcmshell kwincompositing" at first left me wondering, as there is no  
kcmshell in my Linux installation and yast also does not offer it.  
However, in "Systemeinstellungen/Arbeitsflächeneffekte/Erweitert"  
"Arbeitsflächeneffekte für Fenster im Vollbildmodus aussetzen" was  
checked. Unckecking it, indeed did solve the problem. This also has the  
positive side effect that now resume from sleep works again - before going  
to sleep the screensaver seems to be activated, and that prevented a  
successful resume.
Thank you!
Harald


Am 02.01.2012, 15:56 Uhr, schrieb Thomas Lübking   
<thomas.luebking@gmail.com>:

> https://bugs.kde.org/show_bug.cgi?id=290266
>
>
> Thomas Lübking <thomas.luebking@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|                            |WAITINGFORINFO
>
>
>
>
> --- Comment #2 from Thomas Lübking <thomas luebking gmail com>   
> 2012-01-02 14:56:47 ---
> "kcmshell kwincompositing", 3rd tab ("advanced") - is "suspend desktop  
> effects
> for fullscreen windows" checked?
> Try to uncheck it.
>

my fault - is "kcmshell4" - numpad was probably deactivated... (oder so, "schwitz" ;-)
The setting is meanwhile defaulted off for that reason - what GPU/driver do you use?
(in doubt, attach "glxinfo" output - you can redirect it "glxinfo > my_glx_info.txt")

Am 02.01.2012, 16:49 Uhr, schrieb Thomas Lübking   
<thomas.luebking@gmail.com>:

> https://bugs.kde.org/show_bug.cgi?id=290266
>
>
> Thomas Lübking <thomas.luebking@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEEDSINFO                   |RESOLVED
>          Resolution|WAITINGFORINFO              |UPSTREAM
>
>
>
>
> --- Comment #4 from Thomas Lübking <thomas luebking gmail com>   
> 2012-01-02 15:49:01 ---
> my fault - is "kcmshell4" - numpad was probably deactivated... (oder so,
> "schwitz" ;-)
> The setting is meanwhile defaulted off for that reason - what GPU/driver  
> do you
> use?
> (in doubt, attach "glxinfo" output - you can redirect it "glxinfo >
> my_glx_info.txt")
>

FYI: You're replying to a bugtracker what means you
a) don't have to (and should not) quote mails
b) can unfortunately not attach to the bug by attaching to the mail (would be a great feature, though)

Created attachment 67343 [details]
glxinfo output

Thanks, please check
http://nouveau.freedesktop.org/wiki/MesaDrivers

While developing nicely, the nouveau/OpenGL support is not yet in a productive state and has to be used with *great* care (be aware that driver bugs /can/ longtime damage your HW, so you should at least have a constant eye on temperature - while the GPU is pretty robust, in a close environment like a notebook it can eventually kill the CPU)

"Joe user" should consider to use the nvidia blob for now (unless  prevented by religious attitudes ;-) but no testing also implies less development pace.
-> Rate yourself and act accordingly.

Thanks for the warning, but sensors normally show temperatures in the  
range between 50 and 70 °C. I have tried the nvidia drivers (mainly  
because hdmi sound does not work for my current Linux installation), but  
curiously the graphics was not better (nicer?) and I still did not get  
hdmi sound to work. So, I am sticking with the nouveau driver. Thats's  
what openSuse installs per default, anyway.