-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invisible mouse display and impossible to use some keys #31
Comments
There may be discrepancy between the X11 display you are using and the default initialization command in xmouse. For me, when i run the command "echo $DISPLAY" from my Ubuntu terminal i get the output ":0" Make sure this corresponds correctly with the initialization command in the xmouse settings, eg. "export DISPLAY=':0' && unset HISTFILE" also, are you using bash as your shell? or sh/dash/zsh/csh/fish? If it is different from the default then you will need to change the init command more |
I am only using the app, with the default configuration. I didn't change anything. The only thing I did so far was installing the apps necessary for running the app in my ubuntu laptop and sync phone and laptop with app by ssh with my terminal. I have checked "echo $DISPLAY" output and I also get ":0". I also checked "env" command and I get: SHELL=/bin/bash . So, I am indeed using bash as my shell. I |
I also had some strange effects (see #35), but if the connection works, I do not have the issues described by you: mouse is visible, volume keys work, typing works. Ubuntu 18.04, xdotool installed via apt install xdotool. Lineage OS 15.1 on the phone. |
i also have the problem of keys not working and the visible mouse cursor is not moving, but some invisible cursor does (i can click and hover stuff, but see no cursor). |
I could connect everything, but I had some issues:
My SO is Ubuntu 18.04. It may be related to it. In the past, I was using a propietary app called remoteLinux, which didn't give me issues. But I want open apps,
The text was updated successfully, but these errors were encountered: