Bug 290266 - kde 4.7.2 r5 crashes after returning from screensaver
Summary: kde 4.7.2 r5 crashes after returning from screensaver
Status: RESOLVED UPSTREAM
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-31 15:23 UTC by Harald Brennich
Modified: 2012-01-02 16:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
glxinfo output (12.59 KB, text/plain)
2012-01-02 16:15 UTC, Harald Brennich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Brennich 2011-12-31 15:23:06 UTC
Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

When screensaver mode is left by entering a key, KDE seems to run amok: parts of the screen are repeatedly repainted, seemingly with the content it had when the screensaver was activated. Finally, after some time, mouse click and keyboard input fail. The system has to be rebooted via the power button.

Reproducible: Always

Steps to Reproduce:
1. Start the system
2. Enter screensaver by mode by not using input devices
3. Leave  screensaver by mode by entering a key


Actual Results:  
Parts of the screen are repeatedly repainted with old content (modifications are overwritten). Finally, after some time, mouse click and keyboard input fail. The system has to be rebooted via the power button.

Expected Results:  
The system should simply resume operation.

The bug occurs after upgrade from openSuse 11.4 to openSuse 12.1
Comment 1 Oswald Buddenhagen 2012-01-02 14:02:17 UTC
i can only imagine some "funny" interaction with kwin and the x server ...
maybe try disabling compositing?
Comment 2 Thomas Lübking 2012-01-02 14:56:47 UTC
"kcmshell kwincompositing", 3rd tab ("advanced") - is "suspend desktop effects for fullscreen windows" checked?
Try to uncheck it.
Comment 3 Harald Brennich 2012-01-02 15:28:36 UTC
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.
>
Comment 4 Thomas Lübking 2012-01-02 15:49:01 UTC
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")
Comment 5 Harald Brennich 2012-01-02 15:57:38 UTC
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")
>
Comment 6 Thomas Lübking 2012-01-02 16:09:42 UTC
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)
Comment 7 Harald Brennich 2012-01-02 16:15:54 UTC
Created attachment 67343 [details]
glxinfo output
Comment 8 Thomas Lübking 2012-01-02 16:29:48 UTC
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.
Comment 9 Harald Brennich 2012-01-02 16:46:40 UTC
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.