After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681303 - Maximizing Netbeans IDE Window Breaks Cursor Positioning
Maximizing Netbeans IDE Window Breaks Cursor Positioning
Status: RESOLVED DUPLICATE of bug 650512
Product: gnome-shell
Classification: Core
Component: general
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-08-06 14:13 UTC by Nebojša Kamber
Modified: 2012-08-06 16:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nebojša Kamber 2012-08-06 14:13:41 UTC 
Steps to reproduce:
1. Open Netbeans 7.2
2. Maximize main window

Results:
- Mouse cursor postioning is broken, trying to click an item from the main menu
or the context menu is practically impossible. It's as if there's an offset between the postion of the cursor and the position that IDE window detects.

Expected results:
- Main menu and context menus should work normally.

Workaround:
- Not maximizing the window. Cursor and menus work fine.
Comment 1 Milan Bouchet-Valat 2012-08-06 14:36:17 UTC 
Does this work correctly in fallback mode or with other desktop environments?
Comment 2 Nebojša Kamber 2012-08-06 16:45:11 UTC 
In fallback mode, the bug cannot be reproduced.
I haven' tried with other desktop environments, but a member of Netbeans staff using Linux/Ubuntu 12.04 couldn't reproduce the bug either, which led us to the conclusion that the problem might be in Gnome Shell.
The bug reported is: http://netbeans.org/bugzilla/show_bug.cgi?id=215155
Comment 3 Jasper St. Pierre (not reading bugmail) 2012-08-06 16:51:01 UTC 
Java has known problem with mice and maximized windows. They're breaking the ICCCM, not us.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 650512 ***