User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.10) Gecko/20071126 Ubuntu/7.10 (gutsy) Firefox/2.0.0.10 Build Identifier: If the mouse is hovering over a button while it is unclickable, then once it becomes clickable it is NOT in fact clickable until the mouse pointer has been moved outside the boundary of the button and back within the boundary again. Two easy examples are 'Add/Remove...' and 'Synaptic'. I've observed several others. Start up Synaptic from menu, and while it's checking installed and available packages, hover mouse over 'search' button. Once it becomes clickable, actually clicking on it has no visible effect whatsoever, until mouse pointer has moved outside the button and returned. Start up 'Add/Remove...' from menu, and while it is checking installed and available packages, and the main window is grayed out, hover mouse over 'cancel'. Once it becmoes clickable, if you click on it focus will be moved to the button like keyboard tab, but you cannot actually get it to click unless you move the pointer away and back to the button. Reproducible: Always Steps to Reproduce: 1. Open 'Add/Remove...' 2. while still grayed out, hover mouse over 'cancel' button 3. once clickable, try clicking it. Actual Results: Buttons are unclickable regardless of actual state/visual representation, until mouse has actually passed into their boundary. Expected Results: Buttons should always be clickable if 'clickable'... ;) fully updated Xubuntu 7.10. Xfce 4.4.1-1ubuntu1 gtk2 2.12.0-1ubuntu3 glib2 2.14.1-1ubuntu1 Posted previously in Ubuntu forums - http://ubuntuforums.org/showthread.php?t=621282 - where it received no response whatsoever.
This is a gtk deficiency; has nothing to do with us.
FYI, see here: http://bugzilla.gnome.org/show_bug.cgi?id=56070 Looks like it might finally be close to being fixed, after over 6 years.
Moving invalid bugs to the /dev/null product.