Bug 540956
Summary: | After upgrading from F11->F12, clicking on dialog buttons in Eclipse no longer works | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dimi Paun <dimi> |
Component: | eclipse | Assignee: | Andrew Overholt <overholt> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | akurtako, christof, overholt |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-23 19:41:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dimi Paun
2009-11-24 15:08:32 UTC
Are you using eclipse downloaded from upstream? The problem is fixed in Fedora's packages Yes, I'm using the upstream eclipse. I've tried to use the one that comes with Fedora, but everytime something broke. I need to be able to use the upstream version. A few people I know are affected by this problem. (In reply to comment #2) > Yes, I'm using the upstream eclipse. I've tried to use the one that comes with > Fedora, but everytime something broke. It would great to hear what broke in separate bug reports. > I need to be able to use the upstream version. A few people I know are affected > by this problem. There are a bunch of bugs at bugs.eclipse.org. Search for GTK2.18. Try setting the environment variable GDK_NATIVE_WINDOWS=true before running eclipse. Same for Azureus by the way. Maybe this should be assigned to GTK It is indeed a GTK behavioural change but it's really an upstream issue. Feel free to move this to GTK here in Red Hat bugzilla as we've worked around these issues in our Eclipse packages in Fedora. Since this was fixed in our packages and was reported as an upstream issue, I'm going to close this bug. Feel free to open a bug with GTK+. |