-
Notifications
You must be signed in to change notification settings - Fork 240
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
Cursor not hiding #15
Comments
I am not sure how to fix that, nor do I have the research time. A pull request would help. |
It would be enough if the cursor would move away, or just move a bit sometimes. Then the Chromium + css should know how to hide it.. I think.. |
There was a pull request fixing this issue. Is this fixed in the nightly? |
I have not downloaded the new nightly, but I'll get it tomorrow and check if everything is working! |
now it requires login and the chromium isn't starting.. :/ |
I just tested, it still does not work, try latest nightly |
@guysoft I found this solution on AskUbuntu: |
If you're getting "Could not open display" from unclutter, try the following. Hopefully that saves you a trip to this thread. |
If you want this done automatically on boot (or to be precise when X becomes available) you can add this to So your file might look like this:
|
Likely this has been fixed by #34 , if not then we are going to add in 0.7.0 unclutter |
We didn't add unclutter and this seems to be working. |
simply edited lightdm config in changing line |
Cool to know, but that would hide the cursor all together |
Tätä sähköpostiosoitetta ei enää käytetä! Löydät uuden sähköpostiosoitteen Jumppahullun nettisivuilta!
Ystävällisin terveisin
Samuli Lindgren
|
@guysoft yes but touch still works fine, it depends on what is the desired effect. |
I know that this is an old thread, but I'm still having a problem getting rid of the cursor in FullPageOS. G3z's solution of editing the lightdm.conf file doesn't do anything. |
I've noticed that the Cursor doesn't seem to be hiding itself after loading web page.
The text was updated successfully, but these errors were encountered: