Driver bug - did you enable OpenGL 3.1?

What's the output of
   qdbus org.kde.KWin /KWin supportInformation

Created attachment 90687 [details]
Output of qdbus

(In reply to Thomas Lübking from comment #1)
> Driver bug - did you enable OpenGL 3.1?
> 
> What's the output of
>    qdbus org.kde.KWin /KWin supportInformation

OpenGL 3.1 is enabled. After KWin crashed, desktop effects are off. Windows are wobbling. Logout seems also not to work. I see a black screen and the mouse cursor.

the support information indicate that
a) the compositor is active
b) the wobbly winow effect is not loaded (thus likely disabled)

please set the compositor backend to opengl 2.0, reboot and see whether the crash still occurs

theblack screen + cursor on logout indicates that the session is not terminated what may or maybe not related to this problem (we'll see ;-)

*** This bug has been marked as a duplicate of bug 339760 ***

(In reply to Thomas Lübking from comment #4)
> the support information indicate that
> a) the compositor is active
> b) the wobbly winow effect is not loaded (thus likely disabled)
> 
> please set the compositor backend to opengl 2.0, reboot and see whether the
> crash still occurs
> 
> theblack screen + cursor on logout indicates that the session is not
> terminated what may or maybe not related to this problem (we'll see ;-)
> 
> *** This bug has been marked as a duplicate of bug 339760 ***

The crash still occurs with compositor backend OpenGL 2.0 and reboot.
I changed the settings to OpenGL 3.1 again and did a reboot. At this time no crash of KWin, 3D effects are on. It seems that it some times works. By the way before KWin is crashing I can predict the crash, because the mouse cursor become smaller when KSplash has appeared (comparing to the Logon screen).

Regarding the wobbly window effect: That was a misunderstanding. I did not mean the nice wobbly effect. I wanted to say that it looks like a kind of wobbly effect when moving a window on the desktop, because the "repainting" of the window is very slow.

(In reply to Attila from comment #5)

> wobbly effect when moving a window on the desktop, because the "repainting"
> of the window is very slow.

That's "expectable" - w/o compositor every window needs to repaint newly exposed regions. Depending on the toolkit, gui style and actual content, that can be very slow.
Rather use XRender compositing in that case.

Other things you might want to check are
- Qt Graphics System: native -> raster
- whether you're using glamor or sna acceleration: "grep -i glamor /var/log/Xorg.0.log"

(In reply to Thomas Lübking from comment #6)
> (In reply to Attila from comment #5)

> Other things you might want to check are
> - Qt Graphics System: native -> raster
> - whether you're using glamor or sna acceleration: "grep -i glamor
> /var/log/Xorg.0.log"

Qt Graphics System is native.

Output of Xorg.0.log:
[    35.198] (II) LoadModule: "glamoregl"
[    35.562] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    35.564] (II) Module glamoregl: vendor="X.Org Foundation"

(In reply to Attila from comment #7)

> Qt Graphics System is native.
Yes - the idea was to try the raster graphcissystem instead.

> Output of Xorg.0.log:
> [    35.198] (II) LoadModule: "glamoregl"
> [    35.562] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
> [    35.564] (II) Module glamoregl: vendor="X.Org Foundation"

------- /etc/X11/xorg.conf.d/20-intel.conf ----------
Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"  "sna"
EndSection
-----------------------------------------------------------------

(In reply to Thomas Lübking from comment #8)
> (In reply to Attila from comment #7)
> 
> > Qt Graphics System is native.
> Yes - the idea was to try the raster graphcissystem instead.
> 
> > Output of Xorg.0.log:
> > [    35.198] (II) LoadModule: "glamoregl"
> > [    35.562] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
> > [    35.564] (II) Module glamoregl: vendor="X.Org Foundation"
> 
> ------- /etc/X11/xorg.conf.d/20-intel.conf ----------
> Section "Device"
>    Identifier  "Intel Graphics"
>    Driver      "intel"
>    Option      "AccelMethod"  "sna"
> EndSection
> -----------------------------------------------------------------

The Qt Graphics System is still nativ. I have created the file 20-intel.conf.
The output is now:
[    45.493] (**) intel(0): Option "AccelMethod" "sna"
[    45.493] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[    45.789] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend

Did my second reboot and it seems to work at every reboot. Please do not close this report. I will check tomorrow again.

No crash with SNA acceleration.
However the default setting for acceleration is glamoregl. Is it a KWin or driver bug by Intel?

The other thing I mentioned is that different mouse cursor size. For example when I point to the title bar the mouse cursor becomes smaller (see attached file "MouseCursorSmall"). Sometimes I reboot the system twice (to reproduce) and the mouse cursor has the same size (see attached file "MouseCursorDefault") pointing to the title bar or to somewhere else. This is a different behavior. I am not sure, is that a KWin bug or should I report it somwhere else?

Created attachment 90747 [details]
Mouse cursor small

Created attachment 90748 [details]
Mouse cursor default

(In reply to Attila from comment #10)
> No crash with SNA acceleration.
> However the default setting for acceleration is glamoregl. Is it a KWin or
> driver bug by Intel?

Intel. Glamor is still pretty new.

> The other thing I mentioned is that different mouse cursor size.
This is likely caused by the early start of KWin and a later change of the global cursor size (resp. ignorance of that by the early configuration)

Since the entire stuff around cursors changed *drastically* in KDE5, there won't be any fix in that regard for 4.x (only security bugsfixes are "permitted")

-> If that happens with 5.2, please report an extra bug.
If it happens with 5.1, please try 5.2 first ;-) (due to recent patches)

For 4.x it would likely be sufficient to
------ ~/.kde/env/set_cursor_size.sh ----------
#!/bin/sh
export XCURSOR_SIZE=32
---------------------------------------------------------

while that should be done by /usr/bin/startkde

*** Bug 347192 has been marked as a duplicate of this bug. ***

Created attachment 93454 [details]
New crash information added by DrKonqi

kwin (4.11.11) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed: Login to KDE

- Unusual behavior I noticed: Whenever I login The desktop is all black and displays the message "Kwin has crashed." After Desktop back to normal.

- Custom settings of the application: Bespin Theme

-- Backtrace (Reduced):
#7  KWin::Scene::paintSimpleScreen (this=this@entry=0x9a29748, orig_mask=orig_mask@entry=0, region=...) at ../../kwin/scene.cpp:261
#8  0xb7628987 in KWin::Scene::finalPaintScreen (this=0x9a29748, mask=mask@entry=0, region=..., data=...) at ../../kwin/scene.cpp:198
#9  0xb764fc53 in KWin::EffectsHandlerImpl::paintScreen (this=0x9dc1d20, mask=0, region=..., data=...) at ../../kwin/effects.cpp:375
#10 0xb762b3cc in KWin::Scene::paintScreen (this=this@entry=0x9a29748, mask=mask@entry=0xbf964870, damage=..., repaint=..., updateRegion=updateRegion@entry=0xbf964874, validRegion=validRegion@entry=0xbf964878) at ../../kwin/scene.cpp:148
#11 0xb7640287 in KWin::SceneOpenGL::paint (this=this@entry=0x9a29748, damage=..., toplevels=...) at ../../kwin/scene_opengl.cpp:389

See https://bugs.kde.org/show_bug.cgi?id=339760#c10