Bug 191536 - swt bug: buttons on ON_TOP shells aren't clickable
swt bug: buttons on ON_TOP shells aren't clickable
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ben Konrath
Depends On:
Blocks: 189582
  Show dependency treegraph
Reported: 2006-05-12 15:30 EDT by Anthony Green
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: libswt3-gtk2-3.1.2-1jpp_15fc
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-06-01 12:13:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kludgy patch (690 bytes, patch)
2006-05-24 09:15 EDT, Anthony Green
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Eclipse Project 142861 None None None Never

  None (edit)
Description Anthony Green 2006-05-12 15:30:05 EDT
Description of problem:
This was found in Azureus.  The following page contains a sample program
that creates an ON_TOP shell with a close buttont on it.  The close button
doesn't not appear to be receiving mouse events.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Compile and run the referenced test case.
Actual results:
Window with close button appears.  Close button doesn't work.

Expected results:
Close button should work.

Additional info:
Comment 1 Anthony Green 2006-05-19 14:11:09 EDT
Rolling gtk2 back to gtk2-2.8.15-1 solves the problem.
Comment 2 Anthony Green 2006-05-24 09:15:21 EDT
Created attachment 129928 [details]
Kludgy patch

This patch (suggested by the upstream bugzilla) seems to solve the problem.
Comment 3 Ben Konrath 2006-06-01 11:26:44 EDT
I added the patch to the latest FC5 update (3.1.2-1jpp_15fc). Can you please
verify that this is fixed and close the bug if is? Thanks.
Comment 4 Anthony Green 2006-06-01 12:13:10 EDT
Yes, this is fixed - thanks!   

Note You need to log in before you can comment on or make changes to this bug.