[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=372015

Andrew Crouthamel  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WORKSFORME

--- Comment #16 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The
bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=372015

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #15 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information as soon as possible and set the bug
status as REPORTED. Due to regular bug tracker maintenance, if the bug is still
in NEEDSINFO status with no change in 30 days, the bug will be closed as
RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug
status as REPORTED so that the KDE team knows that the bug is ready to be
confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Sven Eden]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #14 from Sven Eden  ---
(In reply to Martin Gräßlin from comment #13)
> > However, there was a time when GLES2 support was needed for EGL, which is 
> > needed for wayland. If that is no longer the case, we can eventually build 
> > everything without any OpenGL ES support? That would be so great! :-)
> (Honestly, GLES is a pain.)
> 
> This requirement went away years ago. EGL is not bound to OpenGL ES any more
> and can create an OpenGL context. That's how Wayland works today.

And it was the culprit. I have removed all support for OpenGL ES and Plasma
works fine with my Aurorae setup using mesa-13.0.1.


Martin, thank you very much!
Without your help I would not have suspected GLES support to be the problem
anytime soon! :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #13 from Martin Gräßlin  ---
> However, there was a time when GLES2 support was needed for EGL, which is 
> needed for wayland. If that is no longer the case, we can eventually build 
> everything without any OpenGL ES support? That would be so great! :-)
(Honestly, GLES is a pain.)

This requirement went away years ago. EGL is not bound to OpenGL ES any more
and can create an OpenGL context. That's how Wayland works today.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Sven Eden]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #12 from Sven Eden  ---
Unfortunately this was a no go. And the "Backtrace" is highly illuminating:

"Application: KWin (kwin_x11), signal: Aborted"

That's it. Nothing more. No backtrace, nothing.



(In reply to Martin Gräßlin from comment #11)
> @Sven: the only possibility that KWin picks EGL without any config set to it
> or env variable is that you compiled the Qt and KWin stack with OpenGL ES
> instead of OpenGL. This is something we see quite often for Gentoo users.

So there is a) the removal of the EGL/GLX choice, but b) a backdoor for EGL
slithering back in without any control of the user. I'd call that an oversight
that needs to be fixed? ;-)

However, there was a time when GLES2 support was needed for EGL, which is
needed for wayland. If that is no longer the case, we can eventually build
everything without any OpenGL ES support? That would be so great! :-)
(Honestly, GLES is a pain.)

But as I see now, libsdl2-2.0.5 wants mesa with GLES2 support for it to be able
to use wayland. Yes. It's configure script needs both video_opengl_egl and
video_opengles_v2 to allow to enable video_wayland.
...what a pity. No wayland support for libsdl2 then.

Everything else seems to have gotten rid of that ridiculous dependency. *yay*!

(In reply to Martin Gräßlin from comment #11)
> Concerning the Aurorae crash: no, nobody is working on it. While we see the
> crash happens for many users, we devs have never been able to reproduce it.

Well, I have no crash with mesa-12.0.4 and GLX. The whole damn thing is rock
solid here. The only way for me to reproduce this is when "EGL" is chosen.
(Which I just forced off anyway.)

Bt maybe your hint about OpenGL ES 2 is the key to solving this. I am
currently rebuilding everything that had GLES2 support without it.

The fine thing about gentoo is, that we can easily try these things out, and
even on a very fine grained scale. :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #11 from Martin Gräßlin  ---
@Sven: the only possibility that KWin picks EGL without any config set to it or
env variable is that you compiled the Qt and KWin stack with OpenGL ES instead
of OpenGL. This is something we see quite often for Gentoo users.

Concerning the Aurorae crash: no, nobody is working on it. While we see the
crash happens for many users, we devs have never been able to reproduce it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Sven Eden]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #10 from Sven Eden  ---
(In reply to Martin Gräßlin from comment #7)
> @Sven: because KWin writes out the current runtime configuration. It loads
> with that from your config and writes it back. If you manually want to
> change the config you need to stop KWin.

I am very sorry that I did not make this clear enough. I'll try with a list of
actions.

- Machine booted to console after one of those crashes.
- Edit ~/.config/kwinrc and set OpenGLIsUnsafe to "false" and
GLPlatformInterface to "glx". (Without the quotation marks of course)
- Start SDDM via xdm and log into Plasma.
- Compositor is off, systemsettings5 states that it crashed kwin in the past.
- Reactivate OpenGL detection.
- All decorations disappear with kwin crashing.
- Open Yakuake with F12 and "grep GLPlatform ~/.config/kwinrc" reveals, that it
is back to "egl".

So no, it did not write back a configuration it read, it just decided that egl
is a good thing to use.

I have scanned all my system and user files whether I have accidentally set
KWIN_OPENGL_INTERFACE="egl" somewhere, but my search revealed nothing.

So I have solved this particular part for me by simply adding
KWIN_OPENGL_INTERFACE="glx" to the environment.

I am back on mesa-12.0.4 and kwin uses the glx back end. Everything is stable.

But another question: Is the "Standard Aurorae/QML" thing something that is
worked on? 
Actually I do use Oxygen with Helium Design and air-oxygen decorations.
It is okay if people like Breeze, but I do not. It is too flat, too
monochromatic and is more in my way than it helps. The desings based on Breeze
do not mix well with the Oxygen icons, and the breeze icons are a nightmare. It
is like being back on an Amiga 500 Workbench 1.3 with a monochrome monitor.

However, kwin crashes too with everything set to "Breeze" when mesa-13+ is
installed. But I guess forcing "glx" might fix that, I'll try this out today
and report back.
Meaning: kwin-5.8.3 + mesa-13.0.1 + forced "glx" PlatformInterface + "Breeze
everywhere".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Wayne]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #9 from Wayne  ---
I have been experiencing a similar, but somewhat sporadic "crash" on boot-up,
since an upgrade ~3-4+(?) months ago.  It happens ~50-75% of the time, closer
to 100% the last week.  This crash happens, but then the machine apparently
recovers and restarts kwin and then works without kwin re-crashing.

System: Debian "testing" net install late last year (new HD but I5/MB built
about 5 yr ago), upgraded regularly. While it has extra software
(video/audio/office/Myth/radio) and now debug files installed, it has not
really been modified other than for auto login on boot.  

I am a neophyte on backtraces, but these backtraces/problems are not
consistent.  This was the first today of two consecutive crashes on a single
boot.  The second, is similar. I can provide that trace if wished.

Earlier crash reports were much more extensive, along the lines of the original
report reported here, but were incomplete and the kcrash handler reported them
as needing additional debug files for:
/usr/bin/kwin_x11
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

Other reported similar bugs seem to require user input/or are related to other
programs which I have not provided to the operating system/do not seem to be in
these traces.  But, I leave windows/programs open to expedite startup and those
restart with the boot.

General Symptoms (may not be related to this kwin crash, but have been around
since that upgrade).
-alt tab keyboard shortcut between programs no longer works. 
-very slow window responsiveness to changing among running programs-mainly
libreoffice/iceweasel/icedove (lately several seconds or more).  That seems to
be fixed by a memory transplant last week (to 16Gb from 8Gb). 

Other erratic symptoms which may or may not be related:
-after this crash kate's title bar was mostly above the top screen edge, that
operating program behaviour does not happen all the time. After moving the
window and a change in focus to another program and back, it went back up
mostly above the screen a couple of times. Reducing the size of the kate window
apparently stopped that behavior, even after re-maximizing the window.  
-sometimes the widgets (? in the task bar ? not sure those are the right names)
for running programs do not show up and one has to close or kill the top
program to see/switch to the window underneath.
-A second boot (occasionally a third) will clear problems up.

Other:  systemd gives messages on shutdown, maybe ~15-20% of the time, about
failure to unmount swap (4x) and a couple of times I have noted an extra
similar message for the rpc file system.  Again this swap thing started up
about the same time as the upgrade. Changes to the originally installed fstab
(by the net install disk which used /dev/sdx rather than the uuid for the swap)
seemed to have fixed that swap issue a few weeks ago, but that restarted
recently. 

Current software is 
Linux debian 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64 GNU/Linux
Package: qt5-default  Source: qtbase-opensource-src (5.6.1+dfsg-3)
Package: breeze  Version: 4:5.8.2-1
Package: kde-full Source: meta-kde  Version: 5:91
Package: kwin-x11 Source: kwin  Version: 4:5.8.2-1

I installed breeze from Jessie a month or so ago, that did not seem to help so
have changed apt back to point to Stretch.


Wayne

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

Thread 3 (Thread 0x7fa57298c700 (LWP 2261)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:73
#1  0x7fa5b31702a5 in select () at ../sysdeps/unix/syscall-template.S:84
#2  0x7fa5b0fd5d3f in qt_safe_select (nfds=16,
fdread=fdread@entry=0x7fa56c000a78, fdwrite=fdwrite@entry=0x7fa56c000d08,
fdexcept=fdexcept@entry=0x7fa56c000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#3  0x7fa5b0fd77e4 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7fa56c000f98, writefds=0x7fa56c000d08, readfds=0x7fa56c000a78,
nfds=, this=0x7fa56c0008c0) at
kernel/qeventdispatcher_unix.cpp:320
#4  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa56c0008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#5  0x7fa5b0fd7cfa in QEventDispatcherUNIX::processEvents
(this=0x7fa56c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#6  0x7fa5b0f8219a in QEventLoop::exec (this=this@entry=0x7fa57298bc60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fa5b0da7e53 in QThread::exec (this=this@entry=0x22e8130) at
thread/qthread.cpp:500
#8  0x7fa5abf88a55 in QQmlThreadPrivate::run (this=0x22e8130) at
qml/ftw/qqmlthread.cpp:141
#9  

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #8 from Gregory M. Turner  ---
(In reply to Martin Gräßlin from comment #7)
> @Gregory: you are hitting the standard Aurorae/QML crash. Use breeze window
> decoration.

Ah, good.  Sorry for the noise, I'll give it a shot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #7 from Martin Gräßlin  ---
@Gregory: you are hitting the standard Aurorae/QML crash. Use breeze window
decoration.

@Sven: because KWin writes out the current runtime configuration. It loads with
that from your config and writes it back. If you manually want to change the
config you need to stop KWin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Sven Eden]

https://bugs.kde.org/show_bug.cgi?id=372015

Sven Eden  changed:

   What|Removed |Added

 CC||sven.e...@gmx.de

--- Comment #6 from Sven Eden  ---
It's mesa.

I have tried a few times to upgrade to mesa-13.0.1, but kwin does not like it.
Or it is the other way round.
Downgrading to mesa-12.0.4 solved the issue for me.

@Gregory: Find an ebuild of the missing 12.0.4 version of mesa in my overlay
layman/seden.

My System:
Gentoo Linux
Kernel-4.8.9
QT-4.7.0
KDE-Frameworks-5.28.0
KDE-Plasma-5.8.3
KDE-Apps-16.08.3
Init System: OpenRC
Session Tracker: elogind

@Martin: btw, in august you blogged that in plasma 5.8 the EGL/GLX selection
was removed, and that "on X11 the default will stay GLX".
Why is it, then, that whenever I re-activate compositing it will write
"GLPlatformInterface=egl" into my kwinrc?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #5 from Gregory M. Turner  ---
Ok, got it.  However I'm not sure if this is the same as OP's crash or not
anymore.  Anyhow I'll let the experts judge.  If you guys want more details I'd
be happy to provide them.

My box is not terribly interesting, but neither is it totally standard.  In
addition to the usual Gentoo rice, my system is shockingly ancient -- much
older than my hardware -- and somewhat cavalierly maintained.

Either way, I seem to have established my issueis not fully reproducible but
close enough that I can probably reproduce the problem on demand by just
rebooting a few times.


--
Application: kwin_x11 (5.8.3)

Qt Version: 5.6.2
Frameworks Version: 5.28.0
Operating System: Linux 4.8.9-gentoo-gmt-00 x86_64
Distribution: "Gentoo Base System release 2.3"

-- Information about the crash:


The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f9c3faf5840 (LWP 3112))]

Thread 11 (Thread 0x7f9b9f7fe700 (LWP 3356)):
#0  0x7f9c3f58b853 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x0030f1084fff in qt_safe_select (nfds=17,
fdread=fdread@entry=0x7f9b9a58, fdwrite=fdwrite@entry=0x7f9b9ce8,
fdexcept=fdexcept@entry=0x7f9b9f78, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:65
#2  0x0030f10863e9 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f9b9f78, writefds=0x7f9b9ce8, readfds=0x7f9b9a58,
nfds=, this=0x7f9b9013d6a0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f9b98c0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x0030f10868ea in QEventDispatcherUNIX::processEvents
(this=0x7f9b9013d6a0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x0030f103a71a in QEventLoop::exec (this=this@entry=0x7f9b9f7fdd60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:206
#6  0x0030f0ea01e4 in QThread::exec (this=this@entry=0x7a09a0) at
thread/qthread.cpp:500
#7  0x0031024be115 in QQmlThreadPrivate::run (this=0x7a09a0) at
qml/ftw/qqmlthread.cpp:141
#8  0x0030f0ea459b in QThreadPrivate::start (arg=0x7a09a0) at
thread/qthread_unix.cpp:365
#9  0x7f9c3c004362 in start_thread (arg=0x7f9b9f7fe700) at
pthread_create.c:333
#10 0x7f9c3f59296d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f9b967fc700 (LWP 3332)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b9d800b43 in cnd_wait (mtx=0xb41168, cond=0xb41190) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x8362c0) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f9b9d8009a7 in impl_thrd_routine (p=) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:87
#4  0x7f9c3c004362 in start_thread (arg=0x7f9b967fc700) at
pthread_create.c:333
#5  0x7f9c3f59296d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f9b96ffd700 (LWP 3331)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b9d800b43 in cnd_wait (mtx=0xb41168, cond=0xb41190) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x8cbcf0) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f9b9d8009a7 in impl_thrd_routine (p=) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:87
#4  0x7f9c3c004362 in start_thread (arg=0x7f9b96ffd700) at
pthread_create.c:333
#5  0x7f9c3f59296d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f9b977fe700 (LWP 3329)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b9d800b43 in cnd_wait (mtx=0xb41168, cond=0xb41190) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x8d0130) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f9b9d8009a7 in impl_thrd_routine (p=) at
/usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:87
#4  0x7f9c3c004362 in start_thread (arg=0x7f9b977fe700) at
pthread_create.c:333
#5  0x7f9c3f59296d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f9b97fff700 (LWP 3328)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b9d800b43 in cnd_wait 

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #4 from Gregory M. Turner  ---
hm, wierd.  now, after logging in, no crash.

Pretty sure the only thing I changed was to add this to konsole:

>From e434862050abe2ec48a0c506faf8e2a5f0fe99a9 Mon Sep 17 00:00:00 2001
From: "Martin T. H. Sandsmark" 
Date: Sun, 4 Sep 2016 14:12:02 +0200
Subject: [PATCH] Make the config of file filters and url filters separate

REVIEW: 128828
BUG: 368234

Which I haven't carefully looked at.  If it recurs I'll do my best to grab a
trace.  In the meanwhile I'll try to look into whats up with my coredumpctl.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

https://bugs.kde.org/show_bug.cgi?id=372015

--- Comment #3 from Gregory M. Turner  ---
P.S.: I have gentoo ~amd64 not Arch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

https://bugs.kde.org/show_bug.cgi?id=372015

Gregory M. Turner  changed:

   What|Removed |Added

 CC||g...@be-evil.net

--- Comment #2 from Gregory M. Turner  ---
Looks damn familiar to me.  Every time I log in, decorations are zapped and
replaced, and I get what sure looks to me like OP's trace.  Unfortunately,
drkonqui likes to crash and/or lock up soon afterwards.  Are they stored
somewhere?  Even somewhere temporary that would persist after a drkonqui
segfault?  I seem to have disabled coredumpctl too for some stupid reason :(.

I have lots and lots of symbols for you if I can just manage not to fumble ball
one time.

So long as kwin successfully respawns, which it does about 90% of the time,
everything is more-or-less fine after this.  If I had to pick a likely culprit
I'd tend to suspect it's something to do with some fancy xrandr footwork I
allow to race with my sddm login.

I guess, it's taken me several recurrences to learn that (a) it's not some sort
of transient thing that will magically go away, and (b) drkonqi is never going
to work his usual magic and I'll need to do something other than ask him to
automate my telemetry.

Pretty sure this only started as of 5.8.2 or 5.8.3.  I didn't have any 5.8.x
for long, so, in truth, I could have missed earlier incidents or presumptively
attributed crashes to other stuff.  Anyhow, I'm quite sure the drkonqi report
was not happening two weeks ago.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=372015

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols. We see it's a crash on
tear-down but not where it really crashes.

In case you are not using the Breeze window decoration please switch to it.

-- 
You are receiving this mail because:
You are watching all bug changes.