https://bugs.kde.org/show_bug.cgi?id=405592
Vlad Zahorodnii changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=405592
Paraddi changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=405592
Paraddi changed:
What|Removed |Added
CC||spara...@gmail.com
--- Comment #5 from Paraddi ---
https://bugs.kde.org/show_bug.cgi?id=405592
Martin Flöser changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=405592
--- Comment #3 from Dmitry Osipenko ---
I opened libx11 bug here:
https://gitlab.freedesktop.org/xorg/lib/libx11/issues/93
I also reproduced the problem with other desktop environments, so please feel
free to close this bug since very likely it's not
https://bugs.kde.org/show_bug.cgi?id=405592
--- Comment #2 from Dmitry Osipenko ---
Thank you for the comment, Martin. Yes, it looks like the problem should be in
libx11. I'll try to hack the x11 library, avoiding the offending recursive
_XReply().. will see what will be the result. I'll also
https://bugs.kde.org/show_bug.cgi?id=405592
--- Comment #1 from Martin Flöser ---
>From the backtraces it looks like a problem in xlib. In both cases we do an
xlib call which then triggers an error which goes back into xlib. I can
understand how that can end up deadlocking in xlib. In both cases
