https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #41 from Dan ---
Thanks Christopher, I'm stuck back on 5.9.5. Good to know that was already
taken care of - I should've thought to check Qt as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #40 from Christoph Feck ---
Dan, which Qt version are you using? The QxcbClipboard issue was fixed for Qt
5.12.3, see https://bugreports.qt.io/browse/QTBUG-65145
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=348569
Dan changed:
What|Removed |Added
CC||gandalfdagr...@gmail.com
--- Comment #39 from Dan ---
I'
https://bugs.kde.org/show_bug.cgi?id=348569
Martin Gräßlin changed:
What|Removed |Added
Version Fixed In||5.8.7
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=348569
Martin Gräßlin changed:
What|Removed |Added
Flags||ReviewRequest+
URL|
https://bugs.kde.org/show_bug.cgi?id=348569
Martin Gräßlin changed:
What|Removed |Added
CC||alang...@gmail.com
--- Comment #37 from Martin
https://bugs.kde.org/show_bug.cgi?id=348569
Moritz Augustin changed:
What|Removed |Added
CC|softw...@moritz-augustin.de |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #36 from Roland Pallai ---
(In reply to Thomas Lübking from comment #35)
> Sure you're facing *this* bug then? The particular problem is caused by
> clients (cssh in this very case) sending future timestamps around (causing a
> failure in gr
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #35 from Thomas Lübking ---
(In reply to Roland Pallai from comment #33)
> BTW I do not use clusterssh, not installed.
Sure you're facing *this* bug then? The particular problem is caused by clients
(cssh in this very case) sending future t
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #34 from Daniel Fussell ---
On 05/19/2016 07:33 AM, Thomas Lübking via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=348569
>
> --- Comment #32 from Thomas Lübking ---
> It's a bug in clusterssh and should have been fixed there
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #33 from Roland Pallai ---
Thank you, I understand. Some kind of protection against buggy clients would be
nice, the session should stay usable at least. I would be pleased even if the
workaround involves kwin restart.
BTW I do not use clus
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #32 from Thomas Lübking ---
It's a bug in clusterssh and should have been fixed there:
https://github.com/duncs/clusterssh/issues/46
For KWin there's nothing to actually "fix" - just to keep in mind that we might
want to seek for protection
https://bugs.kde.org/show_bug.cgi?id=348569
--- Comment #31 from Roland Pallai ---
(In reply to Roland Pallai from comment #30)
> Xorg session was started at Mar30, 19 days before.
Oops. So ~50 days before..
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=348569
Roland Pallai changed:
What|Removed |Added
CC||d...@rock.hu
--- Comment #30 from Roland Pallai
https://bugs.kde.org/show_bug.cgi?id=348569
Thomas Lübking changed:
What|Removed |Added
CC||softw...@moritz-augustin.de
--- Comment #29 fr
https://bugs.kde.org/show_bug.cgi?id=348569
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=348569
Thomas Lübking changed:
What|Removed |Added
Resolution|UPSTREAM|---
Summary|Cannot move any windows
17 matches
Mail list logo
