| Summary: | X Selection gets overwritten by some entry-fields on Linux/KDE | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Ariel Garcia <aog-ecl> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse.felipe, ericwill, ob1.eclipse, remy.suen |
| Version: | 3.6 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
Ariel Garcia
Correction to "Steps to reproduce:", last item: the X-selection contains the filename of the to be renamed file (as you can check in klipper or by pasting into a console) but nothing is pasted back in the Eclipse rename dialog. Might be related to the bug 240257. Platform=PC Linux QT is that correct ? Hi, well in my case it is clearly Platform="PC Linux QT", but I can't say if the same problem happens on a pure "Linux GTK" environment for instance. As i said in the original report, my system is KDE/QT based; however i use the gtk-qt-engine (version 1:1.1+svn5-4+b1the on Debian) theme engine package for GTK. So Eclipse uses SWT uses GTK uses QT... ;-) As Oleg mentioned above it might be related to Bug #240257, if that was an SWT-GTK bug then it would probably explain both reports. Thanks, Ariel On Linux the most common SWT port is GTK. We also have a motif port for Linux (for testing only), and there is also a qt port from the comunity (which is not distribute from eclpse.org). What is the name of the file you download ? Sorry for my mess up! yes of course it is the GTK based package, i didn't even know that there was now a QT port available somewhere. I was confused by the "linux QT" platform menu entry and the fact that i run it on my KDE desktop. Concretely, i tested with the Yoxos 5 distribution, C++ configuration profile, but a colleague of mine tested with some EPP package, same results. Is this bug still relevant? (In reply to Alexander Kurtakov from comment #7) > Is this bug still relevant? No response, closing this ticket. Please reopen it if the issue persists on GTK3.22 with 4.8. |