[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

2017-05-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=371862

Martin Gräßlin  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/572f730e8ecd39767390d9a15
   ||68a8cb50625965b
 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Martin Gräßlin  ---
Git commit 572f730e8ecd39767390d9a1568a8cb50625965b by Martin Gräßlin.
Committed on 05/05/2017 at 17:17.
Pushed by graesslin into branch 'master'.

[helper] Terminate xclipboardsyncer if kwin_wayland goes down

Summary:
Normally the xclipboardsyncer should terminate because the socket
becomes unusable. But we have reports of it not really going down and
running amok.

In order to prevent such situations this change registers SIGTERM to be
sent to xclipboardsyncer when the parent process (that is kwin_wayland)
dies in whatever way. This ensures that xclipboardsyncer cannot become
an orphan.

Test Plan: Only compile tested, no way to get into the problematic situation

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5589

M  +1-0CMakeLists.txt
M  +1-0config-kwin.h.cmake
M  +9-0helpers/xclipboardsync/main.cpp

https://commits.kde.org/kwin/572f730e8ecd39767390d9a1568a8cb50625965b

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

2017-04-26 Thread Thomas Lübking
https://bugs.kde.org/show_bug.cgi?id=371862

Thomas Lübking  changed:

   What|Removed |Added

 CC||thomas.luebk...@gmail.com

--- Comment #5 from Thomas Lübking  ---
Kai, what state does the org_kde_kwin_xclipboard_syncer process take when this
happens? If it's not waiting for some IO response ("D"), can you stop it
(before attaching gdb, in order to prevent stalling that)?

If the process turns into a zombie you could attach "strace -p $PID" to it
before sending it to the world of the undead to watch the trailing actions.

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

2017-04-25 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=371862

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||Wayland+, X11-,
   ||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D5589

--- Comment #4 from Martin Gräßlin  ---
Possible patch at: https://phabricator.kde.org/D5589

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

2016-10-30 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=371862

Martin Gräßlin  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|INVALID |---

--- Comment #3 from Martin Gräßlin  ---
In that case I need a backtrace of the process running amok. For me it always
terminated.

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

2016-10-30 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=371862

--- Comment #2 from Kai Uwe Broulik  ---
Without xwayland KWin doesn't even start. I consistently experienced the
aforementioned behavior with kwin_wayland --xwayland --windowed --socket
wayland-1

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

2016-10-30 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=371862

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Martin Gräßlin  ---
The xclipboard syncer is bound to the X11 session. Given bug #371861 I assume
this is related to running a kwin_wayland without --xwayland. Due to that the
xclipboard syncer used the wrong X server.

When kwin_wayland goes down, the Xwayland server goes down, which in turn also
takes down the syncer process. Given that the error is not using --xwayland.

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