http://bugs.winehq.org/show_bug.cgi?id=20024
Summary: mouse and keyboard input using crossloop doesn't work Product: WineHQ Apps Database Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: bob.l.lewis@gmail.com
I use Crossloop a lot to help others with their administrative issues on Linux machines. Current tests with wine-1.1.29-1.1 and the latest crossloop works to see the other persons desktop. Mouse movement works and is in focus. The other desktop even identifies what I am hovering over. However, no mouse clicks or keyboard entry will work. Actually the F1 key for help seems to work but that is all.
When I use Wine with Crossloop to between a Linux machine to a Vista or XP machine to help them with their desktop then everything works as expected.
For some reason the mouse and keyboard entries are not being detected properly on the receiving Linux machine. I have multiple friends needing this to work and would really appreciate any help to resolve this.
http://bugs.winehq.org/show_bug.cgi?id=20024
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.crossloop.com/ Component|appdb-unknown |-unknown Product|WineHQ Apps Database |Wine Severity|major |normal
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-12 14:38:07 --- Not AppDB bug, not major (only one program affected).
http://bugs.winehq.org/show_bug.cgi?id=20024
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.1.29
http://bugs.winehq.org/show_bug.cgi?id=20024
matti salmiset@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |salmiset@gmail.com
--- Comment #2 from matti salmiset@gmail.com 2009-09-12 14:56:28 --- True, only one program affected from your perspective. From our perspective, many, many users are affected, judging by calls for help in various forums.
If it is not AppDB problem, could you kindly point us to right direction to try to narrow the problem area down. It would be extremely valuable to us and perhaps over time, help us to find a kind soul in the right place who might take pity on us users and at least look at this "not major problem".
To those of us who drive and support transitioning from Windows to Linux, not only is this a major problem, it is a show stopper.
Thanks for your understanding.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-12 17:12:59 --- (In reply to comment #2)
True, only one program affected from your perspective. From our perspective, many, many users are affected, judging by calls for help in various forums.
It doesn't work like that. Read the definition of severity levels: http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
It would help if you describe the problem clearly. Does that happen when you connect to Linux PC running crossloop under Wine from Windows PC using this program? Or the other way around?
Keyboard / mouse doesn't work where? In programs running under Wine? Or regular Linux programs?
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #4 from matti salmiset@gmail.com 2009-09-13 01:54:17 --- Crossloop is a Windows application from www.crossloop.com which allows properly authorized remote control of another pc over internet through NAT routers.
Crossloop appears to install fine under Wine.
Crossloop works 100% when using a Windows pc to take over another Windows pc. That is it's purpose. It also works 100% under Linux/Wine when you wish to take over and control a pc running Windows.
It fails to work the other way around, i.e. it is impossible to take control of a Linux/Wine/Crossloop pc either from another Linux/Wine/Crossloop or from a Windows pc running Crossloop.
It is very easy to replicate the problem. 1. Download and install Crossloop from www.crossloop.com and install it in a Windows PC as well as in a Linux PC with Wine. 2. To see it's normal behavior, use the Linux pc to access and control the Windows pc. 3. Then reverse it. Access and try to control the Linux PC from the Windows pc. The following will happen as seen from the Windows pc:
Connection is established, the Windows PC can see the Linux desktop. If you hover your mouse from Windows pc over buttons or objects on Linux desktop that are designed to react and respond to mouse hovering over them, they will 100%. That means that the mouse, it's location, and movements sent from Windows are seen and handled correctly in Linux/Wine.
Two things are not working, the reason for the bug report: 1. the mouse clicks from the Windows PC are not recognized by Crossloop running under Wine in Linux. Which means that you can not open menus, open or close, start or stop anything remotely. 2. the key presses from the Windows PC keyboard are not recognized by Crossloop running under Wine in Linux. Which means that you can not operate the Linux PC using keyboard shortcuts, nor can you type anything, including passwords or whatever.
Since it works the other way around, i.e. you can control a Windows pc from a Linux/Wine machine, it appears that the fault is not in Crossloop but somewhere between Crossloop, Wine and Windows.
I am very happy to make myself available for any help that you may need to resolve this.
Regards matti
http://bugs.winehq.org/show_bug.cgi?id=20024
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #5 from André H. nerv@dawncrow.de 2009-09-13 06:53:03 --- Another Question: Are you trying to control Linux Apps with it, or do you have that behavior with programs running in wine that you wish to control?
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #6 from Robert Lewis bob.l.lewis@gmail.com 2009-09-13 09:29:13 --- (In reply to comment #5)
Another Question: Are you trying to control Linux Apps with it, or do you have that behavior with programs running in wine that you wish to control?
crossloop is a desktop sharing utility. This means the local user authorizes the incoming access to their machine via crossloop security mechanisms. To answer your question directly we are trying to control everything, apps, system administration etc.
We want all incoming mouse and keyboard events passed through to Linux so that the remote user can do anything the local user can do. For example fix their system, teach them how to use their system or collaborate in the creation of a document. We believe this can help expand the adoption of Linux usage because it will allow knowledgeable people to assist those still in the learning curve. Many of us need this and stand ready to help anyone at wine who is willing to look at this.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #7 from André H. nerv@dawncrow.de 2009-09-13 09:52:27 --- i wanted to know whats working, not what you want to work, is the mentioned problem affecting also apps running in wine or only nativ linux apps?
Also why dont you use an platform independent open source tool like VNC? it runs on MacOS, Palm, Linux, Windows and does everything you want.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2009-09-13 10:44:12 --- (In reply to comment #6)
We want all incoming mouse and keyboard events passed through to Linux so that the remote user can do anything the local user can do.
Wine can't do that. All you can achieve is control Windows applications running under Wine.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #9 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-13 11:19:52 --- You still haven't answered the question, does it work within Wine instance that running crossloop client?
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #10 from matti salmiset@gmail.com 2009-09-13 12:36:44 --- (In reply to comment #9)
You still haven't answered the question, does it work within Wine instance that running crossloop client?
The Wine instance running crossloop does not work. It does not recognize or pass mouse clicks or key presses from remote Crossloop to local Crossloop running under Wine.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #11 from matti salmiset@gmail.com 2009-09-13 12:48:12 --- (In reply to comment #7)
i wanted to know whats working, not what you want to work, is the mentioned problem affecting also apps running in wine or only nativ linux apps?
Also why dont you use an platform independent open source tool like VNC? it runs on MacOS, Palm, Linux, Windows and does everything you want.
It affects all programs. The issue is that mouse clicks and key presses are not recognized/passed from Wine and therefore all programs are affected as you can not start them or interact with them.
The people that need help at a remote location typically are new Linux users who can not deal with NAT and VNC setup issues. If they could, they probably wouldn't need our help in the first place. With Crossloop, they don't have to.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #12 from matti salmiset@gmail.com 2009-09-13 12:59:58 --- To sum up - Linux desktop recognizes mouse movements and hovering over hover- sensitive regions/objects through Crossloop. But mouse clicks and key presses are not seen by or passed on from Wine. Only thing between Crossloop and the operating system is Wine. Therefore we suspect there is a bug in Wine.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #13 from Austin English austinenglish@gmail.com 2009-09-13 13:03:44 --- (In reply to comment #12)
To sum up - Linux desktop recognizes mouse movements and hovering over hover- sensitive regions/objects through Crossloop. But mouse clicks and key presses are not seen by or passed on from Wine. Only thing between Crossloop and the operating system is Wine. Therefore we suspect there is a bug in Wine.
Right, but you can't control non-wine apps from wine. E.g., you can't have Crossloop on your Linux desktop and have it run/control amarok. You need something native, e.g., vnc or ssh.
http://bugs.winehq.org/show_bug.cgi?id=20024
--- Comment #14 from André H. nerv@dawncrow.de 2009-09-13 13:05:07 --- (In reply to comment #12)
To sum up - Linux desktop recognizes mouse movements and hovering over hover- sensitive regions/objects through Crossloop. But mouse clicks and key presses are not seen by or passed on from Wine. Only thing between Crossloop and the operating system is Wine. Therefore we suspect there is a bug in Wine.
You still haven't answered the question, does a windowsapp or maybe just winecfg running in the same wine instance recognize mouse clicks or key input?
http://bugs.winehq.org/show_bug.cgi?id=20024
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #15 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-13 15:58:32 --- We running around in the circles here. Duplicate.
*** This bug has been marked as a duplicate of bug 11727 ***
http://bugs.winehq.org/show_bug.cgi?id=20024
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-13 16:00:18 --- Closing duplicate.