[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#777263: marked as done (kde-window-manager: KWin crashes at logon on i965 graphics system with desktop effects enabled)

Your message dated Thu, 23 Mar 2017 13:25:03 +0100
with message-id <20170323121440.yof3o4vmekglw7hq@gnuservers.com.ar>
and subject line Re: Bug#777263: kde-window-manager: KWin crashes at logon on i965 graphics system with desktop effects enabled
has caused the Debian Bug report #777263,
regarding kde-window-manager: KWin crashes at logon on i965 graphics system with desktop effects enabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
777263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777263
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kde-window-manager
Version: 4:4.11.13-2
Severity: important

After a recent update to one of my Debian Jessie laptops (the one where I
actually use KDE all the time), I started to get annoying KWin crashes at
logon, with undesired consecuences (desktop effects partially working, the
panel appears at the wrong edge of the screen, panel is rendered completely
opaque instead of the partial transparency effect I've set).

Here is one of many of the stack dumps I get on one of those many crashes.
Looks like the KWin compositor is doing something that disturbs the i965
driver, therefore leading to a crash.

Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdb27abb800 (LWP 3259))]

Thread 4 (Thread 0x7fdb019c2700 (LWP 3260)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
.../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb21448924 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x00007fdb2143b9a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x00007fdb214483ef in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007fdb1eebd0a4 in start_thread (arg=0x7fdb019c2700) at
pthread_create.c:309
#5  0x00007fdb272adccd in clone () at
.../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fdb008ad700 (LWP 3262)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
.../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb21448924 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x00007fdb2143b9a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x00007fdb214483ef in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007fdb1eebd0a4 in start_thread (arg=0x7fdb008ad700) at
pthread_create.c:309
#5  0x00007fdb272adccd in clone () at
.../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fdb27abb800 (LWP 3259)):
[KCrash Handler]
#6  0x00007fdafb145ab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#7  0x00007fdafb13dbdd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#8  0x00007fdafb11e8ee in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#9  0x00007fdafb0d92b0 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#10 0x00007fdafaf2f588 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#11 0x00007fdafaf30977 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#12 0x00007fdafaf30dd5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#13 0x00007fdb222d34fb in KWin::GLVertexBuffer::draw(QRegion const&, unsigned
int, int, int, bool) () from /usr/lib/libkwinglutils.so.1abi2
#14 0x00007fdb27656149 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#15 0x00007fdb2765a032 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#16 0x00007fdb2765a1e9 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#17 0x00007fdb27665929 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#18 0x00007fdafa0d7db9 in ?? () from /usr/lib/kde4/kwin4_effect_builtins.so
#19 0x00007fdb276658c1 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#20 0x00007fdb27640d71 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#21 0x00007fdb2766576a in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#22 0x00007fdb26d87ae1 in KWin::Effect::paintWindow(KWin::EffectWindow*, int,
QRegion, KWin::WindowPaintData&) () from /usr/lib/libkwineffects.so.1abi5
#23 0x00007fdb27665711 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#24 0x00007fdb27644cd2 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#25 0x00007fdb27642eed in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#26 0x00007fdb27640b95 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#27 0x00007fdb276654f0 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#28 0x00007fdb26d87a4f in KWin::Effect::paintScreen(int, QRegion,
KWin::ScreenPaintData&) () from /usr/lib/libkwineffects.#29 0x00007fdb2766549f
in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#30 0x00007fdb27643399 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#31 0x00007fdb2765744f in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#32 0x00007fdb27639f7b in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#33 0x00007fdb2156b513 in QObject::event(QEvent*) () from /usr/lib/x86_64
-linux-gnu/libQtCore.so.4
#34 0x00007fdb208a629c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#35 0x00007fdb208acda8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#36 0x00007fdb25ec11aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#37 0x00007fdb21551f8d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#38 0x00007fdb21583b6b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#39 0x00007fdb21584628 in
QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#40 0x00007fdb2094b4bb in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#41 0x00007fdb21550ae1 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#42 0x00007fdb21550e45 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64
-linux-gnu/libQtCore.so.4
#43 0x00007fdb215568b9 in QCoreApplication::exec() () from /usr/lib/x86_64
-linux-gnu/libQtCore.so.4
#44 0x00007fdb275ee1e8 in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#45 0x00007fdb271e9b45 in __libc_start_main (main=0x4006e0, argc=1,
argv=0x7fff80b6b4e8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fff80b6b4d8) at libc-start.c:287
#46 0x000000000040070e in _start ()
so.1abi5

Changing the composition type between OpenGL 1.3/2.0/3.1 on Desktop Effects
advanced settings does absolutely nothing.

Temporary workaround #1: Logoff then logon again. Unfortunately that's not
working anymore after a few logons, and I can get a crash on every new KDE
Plasma Workspace session.
Temporary workaround #2: Disable desktop effects. Ugh, not something I want to
do. I love my eyecandy, and it was working just fine until recently.
Temporary workaround #3: Set GL rendered to EGL (KWIN_OPENGL_INTERFACE=egl)
somewhere in my .xprofile. This seems to fix the issues, but there are some
minor graphical glitches with EGL on Intel hardware (at least on my Sandy
Bridge HD3000 system). Still, I prefer minor graphic glitches over a unusable
desktop, but then, things used to work just nicely, so...

While this seems to be a common bug that was fixed upstream months ago (from
what I've found on a quick search, it was a Mesa bug), I am not getting either
DRM errors from i965 on dmesg, or other OpenGL-related woes (everything else
seems to work just fine, from glxgears up to heavy 3D games)



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-window-manager depends on:
ii  kde-runtime                             4:4.14.2-2
ii  kde-style-oxygen                        4:4.11.13-2
ii  libc6                                   2.19-13
ii  libegl1-mesa [libegl1-x11]              10.3.2-1
ii  libgcc1                                 1:4.9.1-19
ii  libgl1-mesa-glx [libgl1]                10.3.2-1
ii  libgles2-mesa [libgles2]                10.3.2-1
ii  libice6                                 2:1.0.9-1+b1
ii  libkactivities6                         4:4.13.3-1
ii  libkcmutils4                            4:4.14.2-5
ii  libkdeclarative5                        4:4.14.2-5
ii  libkdecorations4abi2                    4:4.11.13-2
ii  libkdecore5                             4:4.14.2-5
ii  libkdeui5                               4:4.14.2-5
ii  libkio5                                 4:4.14.2-5
ii  libknewstuff3-4                         4:4.14.2-5
ii  libkwineffects1abi5                     4:4.11.13-2
ii  libkwinglesutils1                       4:4.11.13-2
ii  libkwinglutils1abi2                     4:4.11.13-2
ii  libkworkspace4abi2                      4:4.11.13-2
ii  libplasma3                              4:4.14.2-5
ii  libqt4-dbus                             4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-declarative                      4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-script                           4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore4                              4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4                               4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libsm6                                  2:1.2.2-1+b1
ii  libstdc++6                              4.9.1-19
ii  libwayland-client0                      1.6.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]  10.3.2-1
ii  libx11-6                                2:1.6.2-3
ii  libx11-xcb1                             2:1.6.2-3
ii  libxcb-composite0                       1.10-3+b1
ii  libxcb-damage0                          1.10-3+b1
ii  libxcb-image0                           0.4.0-1
ii  libxcb-keysyms1                         0.4.0-1
ii  libxcb-randr0                           1.10-3+b1
ii  libxcb-render0                          1.10-3+b1
ii  libxcb-shape0                           1.10-3+b1
ii  libxcb-shm0                             1.10-3+b1
ii  libxcb-sync1                            1.10-3+b1
ii  libxcb-xfixes0                          1.10-3+b1
ii  libxcb-xtest0                           1.10-3+b1
ii  libxcb1                                 1.10-3+b1
ii  libxcursor1                             1:1.1.14-1+b1
ii  libxext6                                2:1.3.3-1
ii  libxrandr2                              2:1.4.2-1+b1
ii  libxxf86vm1                             1:1.1.3-1+b1
ii  perl                                    5.20.1-5

kde-window-manager recommends no packages.

kde-window-manager suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
¡Hola Tom!

El 2015-02-07 a las 01:19 -0430, Tom Maneiro escribió:
Package: kde-window-manager Version: 4:4.11.13-2 Severity: important 

Sorry that it took so long to get back to you.
Since this bug was reported kwin has been ported to kf5/qt5, and is now a core component of plasma 5, making this issue relevant for jessie, but at the same time I haven't seen more users affected by this. My random guess is that the issue is actually external to kde-window-manager or that is specific to an effect being used (that's not enabled by default).
After a recent update to one of my Debian Jessie laptops (the one where I actually use KDE all the time), I started to get annoying KWin crashes at logon, with undesired consecuences (desktop effects partially working, the panel appears at the wrong edge of the screen, panel is rendered completely opaque instead of the partial transparency effect I've set).
Here is one of many of the stack dumps I get on one of those many crashes. Looks like the KWin compositor is doing something that disturbs the i965 driver, therefore leading to a crash.
Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdb27abb800 (LWP 3259))] 


Thread 1 (Thread 0x7fdb27abb800 (LWP 3259)):
[KCrash Handler]
#6 0x00007fdafb145ab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #7 0x00007fdafb13dbdd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #8 0x00007fdafb11e8ee in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #9 0x00007fdafb0d92b0 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #10 0x00007fdafaf2f588 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #11 0x00007fdafaf30977 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #12 0x00007fdafaf30dd5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #13 0x00007fdb222d34fb in KWin::GLVertexBuffer::draw(QRegion const&, unsigned int, int, int, bool) () from /usr/lib/libkwinglutils.so.1abi2
This would suggest me that the problem is either in the i965_dri.so, in the GLVertexBuffer or in the QRegion. Sadly the rest of the backtrace is missing the symbols resolution.
Temporary workaround #2: Disable desktop effects. Ugh, not something I want to do. I love my eyecandy, and it was working just fine until recently.
It might be useful to do a binary search of the effects, it's quite possible that the cause of this issue was a single effect.
Temporary workaround #3: Set GL rendered to EGL (KWIN_OPENGL_INTERFACE=egl) somewhere in my .xprofile. This seems to fix the issues, but there are some minor graphical glitches with EGL on Intel hardware (at least on my Sandy Bridge HD3000 system). Still, I prefer minor graphic glitches over a unusable desktop, but then, things used to work just nicely, so... 

That would point to a problem in the i965 driver.
I doubt that you will be still affected by this issue, so I'll close it, based on this assumption and my previous guess. Please reopen if you are still affected by this. 

Happy hacking,
--
"There are two ways of constructing a software design.  One way is to make it
so simple that there are obviously no deficiencies. And the other way is to
make it so complicated that there are no obvious deficiencies."
-- C.A.R. Hoare
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: