http://bugs.winehq.org/show_bug.cgi?id=14181
Summary: Mouse position in Steam is incorrect Product: WineHQ Apps Database Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: major Priority: P1 Component: appdb-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: alex_vip_1@hotmail.com
The position of the mouse in the aplication "Steam" is incorrect. Well... Is incorrect just in the menu that appears when right-clicking the trayicon. In the rest of the program it's fine ^^.
So, resuming: To reproduce the error: right click on the Steam trayicon and then try to click something ... You won't be able because the cursor is about 30pixes under the real position.
Screenshot: http://img117.imageshack.us/img117/2487/instantnea2dj9.jpg
http://bugs.winehq.org/show_bug.cgi?id=14181
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|appdb-unknown |winex11.drv Ever Confirmed|0 |1 OS/Version|other |Linux Priority|P1 |P2 Product|WineHQ Apps Database |Wine Platform|Other |All
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2008-06-29 13:19:15 --- This is not an AppDB bug. Please read where you assigning these bugs to.
The problem is (I don't know how many times I need to describe this problem in bugs that are being closed for some reason) absent synchronization of the pointer position between two different processes - steam and explorer.
http://bugs.winehq.org/show_bug.cgi?id=14181
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.1.0
http://bugs.winehq.org/show_bug.cgi?id=14181
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mouse position in Steam is |Mouse position in Steam tray |incorrect |menu is incorrect
http://bugs.winehq.org/show_bug.cgi?id=14181
Mike Seth me@mikeseth.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |me@mikeseth.com
--- Comment #2 from Mike Seth me@mikeseth.com 2008-07-27 14:53:02 --- Hi,
This or similar behaviour is observed in Ubuntu WINE 1.0.0-1ubuntu4~hardy1 and default Ubuntu GNOME setup. By default, GNOME was configured with a panel (menu bar) on top. This feature introduces offset in the viewport coordinates that WINE ignores, so WINE calculates pointer coordinates wrongly. Moving the application bar to the bottom solved the problem for me.
http://bugs.winehq.org/show_bug.cgi?id=14181
Evil wine@eternaldusk.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@eternaldusk.com
--- Comment #3 from Evil wine@eternaldusk.com 2008-09-25 06:42:32 --- I was about to report the same issue (selection in context menu of Steam systray icon is offset) before finding this bug.
This bug makes it impossible to choose the bottom menu item with the mouse, and clicking on others is problematic because the selection seems to jitter between the item you're actually over and the one above it.
As a workaround, you can use the keyboard arrows and enter to select the menu items. As long as you don't move the mouse, the selection will be steady.
I'm using KDE4.1 (Kubuntu 8.10 Intrepid Alpha-6), with my panel at the bottom edge of the screen.
http://bugs.winehq.org/show_bug.cgi?id=14181
AL3X alex_vip_1@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alex_vip_1@hotmail.com Platform|All |PC-x86-64
--- Comment #4 from AL3X alex_vip_1@hotmail.com 2008-11-05 08:09:12 --- I just tried it on my Kubuntu 8.10 x64 + KDE 4.1.2 + Compiz 0.7.8 + Crossover 7.1.0, and it works fine. So, Crossover has already fixed that. Crossover and Wine work together, right? So, you could just view the source code and fix it. Am I wrong?
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #5 from Evil wine@eternaldusk.com 2008-11-15 08:11:18 --- I'm not sure if it's due to a Steam update or a Wine update, but the arrow-key workaround no longer works for me. When I try to use the arrows on the system-tray icon's right click menu, the menu closes.
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #6 from Evil wine@eternaldusk.com 2008-11-16 11:43:31 --- (In reply to comment #5)
I'm not sure if it's due to a Steam update or a Wine update, but the arrow-key workaround no longer works for me. When I try to use the arrows on the system-tray icon's right click menu, the menu closes.
nm this comment of mind about the workaround no longer working for selecting right-click menu items. It's working fine (the cursor arrow workaround, that is) now, so it was either fixed in the latest git updates or I unknowingly had something else running that was screwing with the window focus.
You know what's weird? When you pop up that systray menu and move your mouse over it, it highlights the correct item for a split second (It's calculating the right offset), but when you stop moving the mouse it pops up to a selection of your mouse position minus the height of the system tray. Does the Window manager send different positions depending on if the mouse is at rest or not, or is Wine calculating the position in two different ways in two different places?
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #7 from Vitaliy Margolen vitaliy@kievinfo.com 2008-11-16 14:56:56 --- (In reply to comment #6) See comment #1
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #8 from AL3X alex_vip_1@hotmail.com 2008-12-05 22:38:20 --- This seems to be fixed in WINE 1.1.10 + KDE 4.2 beta1 ... I don't know if this works on other desktop environments, but it works on mine :)
Could somebody post a comment telling his experience?
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #9 from Evil wine@eternaldusk.com 2008-12-06 07:37:37 --- (In reply to comment #8)
This seems to be fixed in WINE 1.1.10 + KDE 4.2 beta1 ... I don't know if this works on other desktop environments, but it works on mine :)
Could somebody post a comment telling his experience?
Not fixed here: Kubuntu 8.10 + kde-nightly + Wine 1.1.10.
When moving over the tray, it correctly highlights the item under the cursor, but the second you stop moving the cursor the selection jumps to the item above the one you're on, as if the selection is offset by the height of the panel.
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #10 from AL3X alex_vip_1@hotmail.com 2008-12-07 18:16:27 --- Ok... I played arround with this, and I have to say that disabling the second and the third opcion in the "Graphics" tab in WINE's config (winecfg) makes the cursor position work fine.
Here is a screenshot: http://img512.imageshack.us/my.php?image=screen1cq2.jpg
Could someone confirm this, or its just my desktop that's crazy xD! ?
http://bugs.winehq.org/show_bug.cgi?id=14181
Chris Boyle chris@boyle.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chris@boyle.name
http://bugs.winehq.org/show_bug.cgi?id=14181
Andre Wisplinghoff andre.wisplinghoff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andre.wisplinghoff@gmail.com
--- Comment #11 from Andre Wisplinghoff andre.wisplinghoff@gmail.com 2009-02-13 20:21:30 --- (In reply to comment #10)
Could someone confirm this, or its just my desktop that's crazy xD! ?
Same here, disabling 'Allow the window manager to control the windows' is enough. I'm using KDE 4.2.
http://bugs.winehq.org/show_bug.cgi?id=14181
Tom Lloyd napalmllama@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |napalmllama@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=14181
Curtis Mackie curtmackevo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |curtmackevo@gmail.com
--- Comment #12 from Curtis Mackie curtmackevo@gmail.com 2009-02-22 20:48:32 --- I wouldn't recommend that as a solution, since it also seems to prevent programs from receiving keyboard input.
http://bugs.winehq.org/show_bug.cgi?id=14181
brooss.teambb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |brooss.teambb@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=14181
Matt Joiner anacrolix@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |anacrolix@gmail.com
--- Comment #13 from Matt Joiner anacrolix@gmail.com 2009-07-07 07:08:44 --- (In reply to comment #11)
(In reply to comment #10)
Could someone confirm this, or its just my desktop that's crazy xD! ?
Same here, disabling 'Allow the window manager to control the windows' is enough. I'm using KDE 4.2.
I can confirm this, only the 3rd option, 'Allow the window manager to control the windows', is necessary for me. Jaunty, GNOME 2.26.1.
http://bugs.winehq.org/show_bug.cgi?id=14181
Richardcavell@mail.com richardcavell@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |richardcavell@mail.com
--- Comment #14 from Richardcavell@mail.com richardcavell@mail.com 2009-07-31 18:50:15 --- I confirm that I am getting this bug. Macbook 2nd generation with Intel GMA945 chipset running Ubuntu Karmic alpha 3 (same thing happened with Jaunty too). The tray menu item highlighted is not the one that the pointer is pointing to. Changing the configuration doesn't alter the bug for me. I also get a huge amount of flickering with the tray icon and menu items, and changing the configuration does solve that to some extent.
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #15 from Richardcavell@mail.com richardcavell@mail.com 2009-07-31 18:54:48 --- Created an attachment (id=22748) --> (http://bugs.winehq.org/attachment.cgi?id=22748) Screenshot
http://bugs.winehq.org/show_bug.cgi?id=14181
3vi1 winehq.org@eternaldusk.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq.org@eternaldusk.com
--- Comment #16 from 3vi1 winehq.org@eternaldusk.com 2009-08-10 10:54:59 --- Here's a video demonstrating the bug: http://www.youtube.com/watch?v=IEqMO5_01hE
As others have said, disabling "Allow the window manager to control the windows" is not a workable solution: The games will no longer receive keyboard input.
But, at least on KDE3 disabling only "Allow the window manager to decorate the windows" seems to be a fine workaround (as long as you don't mind having the ugly Windows decorations instead of those of your WM.
After changing the decoration option: http://www.youtube.com/watch?v=z25v2P7RP4o
http://bugs.winehq.org/show_bug.cgi?id=14181
3vi1 winehq.org@eternaldusk.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq.org@eternaldusk.com
--- Comment #16 from 3vi1 winehq.org@eternaldusk.com 2009-08-10 10:54:59 --- Here's a video demonstrating the bug: http://www.youtube.com/watch?v=IEqMO5_01hE
As others have said, disabling "Allow the window manager to control the windows" is not a workable solution: The games will no longer receive keyboard input.
But, at least on KDE3 disabling only "Allow the window manager to decorate the windows" seems to be a fine workaround (as long as you don't mind having the ugly Windows decorations instead of those of your WM.
After changing the decoration option: http://www.youtube.com/watch?v=z25v2P7RP4o
--- Comment #17 from 3vi1 winehq.org@eternaldusk.com 2009-08-11 17:50:13 --- (In reply to comment #16)
Here's a video demonstrating the bug: http://www.youtube.com/watch?v=IEqMO5_01hE
As others have said, disabling "Allow the window manager to control the windows" is not a workable solution: The games will no longer receive keyboard input.
But, at least on KDE3 disabling only "Allow the window manager to decorate the windows" seems to be a fine workaround (as long as you don't mind having the ugly Windows decorations instead of those of your WM.
After changing the decoration option: http://www.youtube.com/watch?v=z25v2P7RP4o
*sigh* Nevermind what I said about that being an acceptable workaround. It doesn't work again after reboot. I'm guessing towards the end of my dozens of tests I still had the "control" option selected when steam started, but disabled when the HL2.exe started.
http://bugs.winehq.org/show_bug.cgi?id=14181
James Le Cuirot chewi@aura-online.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chewi@aura-online.co.uk
--- Comment #18 from James Le Cuirot chewi@aura-online.co.uk 2009-09-25 18:27:29 --- This has been bothering me for ages. It's affecting me in XFCE.
http://bugs.winehq.org/show_bug.cgi?id=14181
Thomas thomas-schwaig@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas-schwaig@web.de
--- Comment #19 from Thomas thomas-schwaig@web.de 2009-11-04 07:59:47 --- Hi dudes,
i can confirm that "Allow the window manager to decorate the windows" avoid the jumping cursor, but it's still not pointing to the correct position.
But without the jumping cursor it's much better ;)
http://bugs.winehq.org/show_bug.cgi?id=14181
Matheus Izvekov mizvekov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mizvekov@gmail.com
--- Comment #20 from Matheus Izvekov mizvekov@gmail.com 2009-12-20 14:58:17 --- Same issue here with wmii window manager. This bug is 6 months old, and still unconfirmed. Are the instructions here to reproduce it not good enough?
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #21 from 3vi1 winehq.org@eternaldusk.com 2009-12-20 15:30:21 --- (In reply to comment #20)
Same issue here with wmii window manager. This bug is 6 months old, and still unconfirmed. Are the instructions here to reproduce it not good enough?
Agreed - it should at least be confirmed. It's also still present with KDE4.4beta 1.
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #22 from Austin English austinenglish@gmail.com 2009-12-20 19:55:02 --- (In reply to comment #21)
(In reply to comment #20)
Same issue here with wmii window manager. This bug is 6 months old, and still unconfirmed. Are the instructions here to reproduce it not good enough?
Agreed - it should at least be confirmed. It's also still present with KDE4.4beta 1.
It is confirmed, which is why the status is "NEW".
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #23 from AL3X alex_vip_1@hotmail.com 2010-01-15 09:39:29 --- still present with 1.1.36
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #24 from Richardcavell@mail.com richardcavell@mail.com 2010-01-15 18:03:24 --- (In reply to comment #23)
still present with 1.1.36
And I want to point out that it's here on OS X (as well as Ubuntu). I'm using the winebottler build of 1.1.35.
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #25 from Austin English austinenglish@gmail.com 2011-03-29 19:30:07 CDT --- This is your friendly reminder that there has been no bug activity for 6 months. Is this still an issue in current (1.3.16 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=14181
--- Comment #26 from James Le Cuirot chewi@aura-online.co.uk 2011-03-30 03:04:15 CDT --- I think this has been fixed for a few versions now. Not affecting me any more.
http://bugs.winehq.org/show_bug.cgi?id=14181
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #27 from Dmitry Timoshkov dmitry@codeweavers.com 2011-03-30 04:13:23 CDT --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=14181
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #28 from Alexandre Julliard julliard@winehq.org 2011-04-01 12:40:05 CDT --- Closing bugs fixed in 1.3.17.