I would set up Synergy. It allows you to control multiple computers from a single keyboard. Simply move the mouse off the screen in the direction you choose and the input switches to that computer. I use it to control my Linux desktop and a Windows test box I have and it works great.
download remote mouse for linux
DOWNLOAD
https://t.co/MnM8pkuks0
I tried to connect my wireless mouse to my laptop (Dell), but it just doesn't move the mouse at all. I thought that my mouse has gone bust. But I connected it to my office laptop, which is Windows, and it does work just fine. The batteries are brand new, just put them on 10 mins ago. I Googled a bit a found that I need to install something called xf86-input-mouse. But I dont know how to. I tried using "pacman -S" command, but it didn't do anything. Any advice would be appreciated. Thanks.
It is a HP mouse (Bluetooth). I dont see any errors. I just connect the dongle to the USB slot and click the connect on the mouse. It should connect after about 10 seconds. But nothing happens. The mouse pointer just stays put.
You want to monitor "dmesg -w" when plugging the dongle (should yield an event) and connecting the mouse (more events)
Also check the output of "sudo libinput list-devices" after plugging the mouse.
I would like to remotely control my desktop from my phone when I'm sitting in front of my projector watching netflix / youtube. I would basically only need a spacebar and arrow keys, a full keyboard might already be a bit overkill.
I've seen that error a couple times in other posters' logs and those people never had any problem with their Microsoft / Logitech gear. If you look just before that error, you'll see other info about your receiver. I think it works OK but somehow your mouse doesn't.
I bought a Xiaomi MiMouse (XMSB01MW) which is wireless, I tried connecting it to a new laptop which I have with ArchLinux, it didn't work, the pointer does not move, though the mouse buttons indeed work.
Then I connected it to the PC I'm writing on now, it worked with no problems... After that I've updated packages through pacman (I did not update for a while, so did it yesterday). Now the mouse is showing the exact same behaviour, buttons work, pointer does not work.
Nope, though I suspect it will allow me to use the mouse. Sadly I can't use the linux-lts kernel, because I'm using a GPD WIN 2 (pretty recent additions have been made to the kernel in respect to this laptop) and that would break other features. I'll try linux-lts in other laptop and post results.
Oh, wait -- I missed that the buttons work. The example you showed has the mouse on /dev/input/event13. If that is still true, try od -Ax -x /dev/input/event13
You may need to run that as root. Move the mouse around -- when it moves, does that command spew hexadecimal numbers? If not, how about when you click buttons.
I suppose that when you say that, "you want to control the mouse remotely", you mean to control the mouse as displayed in the target graphical user interface. This is a service provided by the X-Windows server and can be easily and safely controlled via command line using ssh.
Excuse me but, I really do not know how netcat fits into this picture...
That is in case, you want to control the mouse cursor as seen in the target operating system. Because if your goal is to create a terminal application that uses the mouse (this is the mouse that is physically attached to the client) then you should definitely go for a program that is based on ncurses. ncurses makes use of an open source terminal mouse server and can also be used to provide an elaborate gui interface all over ssh and a simple terminal. Also, ncurses does not depend on x-server running, because it does not affect the server's mouse in any manner, it simply uses the client's mouse to control the application.
Thank you for information, i've edited my previous posts.
I've also created the udev rule, but without success. My mouse is still detected as tablet device...
Is there anything else I could try?
Does it help if you fish the udev/hwdb.d from the previous systemd package, ?
(We might be able to isolate the offensive change so you can report a bug, because ultimately the mouse is mishandled)
However, the app itself (Unified Remote) behaves somewhat strange. I can move the mouse cursor fine, also do commands like scrolling and long-pressing (e.g. for marking text). But not Left click or Right click.
I ran into this issue a while ago and found a way to make it work. I don't know exactly why this is a problem, but for me the issue is the mouse.click action used by UnifedRemote doesn't work. But fortunately, both the mouse.down and mouse.up actions do!
So if you're up for making some code changes, you can edit the mouse remote (make sure to make a backup copy of the file beforehand!) and replace the mouse.click actions with both mouse.down and mouse.up. I'm not sure exactly which remote file corresponds to the actual mouse remote, but it's probably either /opt/urserver/remotes/Unified/Core/Mouse/remote.lua or /opt/urserver/remotes/Unified/Core/Input/remote.lua.
I have a basic license and run synergy server on my MacBook Pro. I run synergy client on an nvidia tx2 dev board and also on a laptop with mint on ubuntu. Synergy works great. Exactly what I want. The mouse and keyboard work fine, copy-n-paste works fine. It's great.
Please also refer to the Linux installation instructions for the BladeCenter for additional information related to installing Linux. The installation instructions contain details on how to configure XFree86 for use with the BladeCenter management module remote control. Some of the problems that may be seen include:
Note: It is also necessary to set the mouse acceleration and threshold values to 1. The default settings in Linux will not allow the remote mouse to track properly. To change mouse acceleration and threshold values for the current session open a terminal window and type xset m 1 1 and press Enter.
See the instructions under section labeled "Remote and local mouse not synchronized during remote control session" for additional help if needed.
The change is not saved between sessions so you will have to repeat this every time you login.
If the remote and local mouse are not synchronized properly, there is a constant off set between them on the remote client window then move the mouse towards the bottom of the video screen in the remote client window. Then move the local mouse back in the window. This will fix the alignment between the two mice.
There are several keyboard shortcuts and commands that perform similar functions to using a mouse, however. And in most cases the arrow and Tab keys can be used to select items you want to interact with. Though while possible, using your computer without a mouse may feel sub-optimal and a little clunky.
To clean your computer mouse, turn it off (if applicable) and spray compressed air between the buttons and scroll wheel. Use a cleaning wipe on the surface of the mouse, and scrub at any stubborn areas. Gently brush out dust and dirt from the sensor with a cotton swab (dampened with cleaning solution) and dry using a dry swab.
"Actions/Disable Remote Input" is greyed out as an option. Remote computer is running Mojave, computer trying to access is running high sierra. I've run through the mac permissions and everything is set correct on both computers. Full disk access is allowed in Team Viewer Preferences. Unplugged the mouse on the remote computer, restarted both computers. Tried pressing the alt key. Enabled secondary click on mouse.
Actual result:"That someone was able to gain access to my PC and move the mouse around however, he was not able it to select icons and activate applications on my computer the. left click was effectively disabled.
I'm having the same problem. I can remote in just fine, see everything and move the pointer. I just can't click on anything. After about 2 minutes the pointer on remote computer gets very small. Can anyone help with this. I have uninstalled and reinstalled the software.
I am writing because I have a problem with Teamviewer: I have recently added a second monitor to the station that I have to remotely control. When I start the session I see both screens correctly but I can only interact with one of them during videocall. On one I can write, point with the mouse and click to open applications while on the other I can only write with the keyboard and move the mouse but without clicking. Due to this problem I cannot interact with the windows I open on the second monitor which then get stuck.
Experiencing the same issue on Catalina (and Big Sur). Permissions are are granted on remote desktop, but can only see desktop not control. Previously worked on machine...what happened with the latest Teamviewer update?
It was working fine before but since the upgrade, when the remote computer is connected to a secondary screen, keyboard interactions are working but mouse is not. I tried reinstalling on all computer but nothing helps.
Mouse clicks are not registering when the remote computer has more than one screen (video call is on). When I remotely switch the session to the other monitor (via the menu bar at the top of the screen), everything works fine. Mouse clicks are only registering on one monitor. Mouse movement, and scrolling with the scroll wheel works perfectly on all monitors.
I have the same issue for sometime, thought it is because of the connection, but it works if ones keep the mouse button down a little longer. Also, the touch screen works fine. Maybe some update messed this up, or it is as design?
I have an issue with after connecting from PC to remote PC (Windows 10 to Windows 10) machine where when I click on something it does not select what I clicked on. The mouse cursor moves, the items highlight the hover over, if i click and drag it works no problem, i can draw a select box and you can see the mouse button action that it is pressed and held down, and you can see the release, but when I click on a menu item or a file, I cannot select it. No double clicking responds to open a program or file. I have attached a recording of my issue below. If I EXIT teamviewer and restart TEAMVIEWER , and reconnect to the remote pc the mouse clicks will work but only for 1 session. If I close and reopen the same connection or any other I get the same problem back.
f448fe82f3