Bug 1400811

Summary:	Clipit can no longer capture hotkey over GTK3 windows
Product:	[Fedora] Fedora	Reporter:	Joe Doss <joe>
Component:	clipit	Assignee:	Nikos Roussos <comzeradd>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	comzeradd
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-28 18:59:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joe Doss 2016-12-02 07:04:29 UTC

Description of problem:
Clipit can't capture it's hotkey over some GTK3 based windows such as gnome-terminal, terminator and nautilus.

Version-Release number of selected component (if applicable):
gnome-terminal-3.22.1-1.fc25.x86_64
terminator-1.90-1.fc25.noarch

How reproducible:
Always

Steps to Reproduce:
1. Launch clipit
2. Launch gnome-terminal or terminator (or Files even)
3. Select terminal window and issue 

Actual results:
The clipit history hotkey does not work. Gnome Terminal issues an error bell sound. Terminator does nothing. Nautilus does nothing. Having Chrome as main focus, clipit will capture the hotkey and bring up the clipboard history. 

Expected results:
Clipit to capture the hotkey and bring up the clipboard history dialog window.

Additional info:

Downgrading to terminator-0.98-4.fc25 allows for clipit to capture it's hotkey when focused on terminator window and it brings up the clipboard history.

Comment 1 Joe Doss 2016-12-02 07:11:06 UTC

Looks like upstream has support for GTK3 and I am wondering if that will help with this issue, but when compiling it from source it segfaults on F25. I opened an issue https://github.com/CristianHenzel/ClipIt/issues/57 to see if I can get that sorted out and test things out on my end.

Comment 2 Joe Doss 2016-12-28 18:59:03 UTC

I got clarification on the issue from the GNOME devs. https://bugzilla.gnome.org/show_bug.cgi?id=775905

>This is the intended behavior; it's by design that arbitrary clients cannot eaves drop on keys from other clients. The reason why it happens to work sometimes is that GTK2 clients still use X11, meaning the eaves dropping still works when interacting with X11 clients via Xwayland. When focusing a GTK3 client, it connects via Wayland, and as a result, Xwayland will not be able to broadcast input to all clients wanting it any more, since it wont see the input events at all. In Wayland, the clipboard manager has to be part of the compositor.

Going to close this out since it seems that clipit will have to be rewritten to work with Wayland correctly.