no we want the root to start the service, not your user accountā¦hmmm
This is weirdā¦are you sure when you did the make command there were no errors?
I mean what happens when you execute the vnc server manually ? Does it run ? can you connect to the pi remotely ?
I think the server wasnt copied in the /usr/bin folderā¦thats why there was a 203 error
Try this: sudo whereis dispmanx_vncserver
and give me the output.
You should see something like that. dispmanx_vncserver: /usr/bin/dispmanx_vncserver /etc/dispmanx_vncserver.conf
I started again from scratch (well not from scratch - from the beginning of the tutorial), but when I get to āmakeā, I get this message:
osmc@osmc:~/dispmanx_vnc-master$ make
make: Nothing to be done for āallā.
I looked back in the terminal and found these lines from the first time I ran the make command: https://i.imgur.com/9JbUlqo.png
This could go easier if you look at the file with winscp or filezilla or something make sure the executable is there, but do thisā¦this should work:
cd /home/osmc/dispmanx_vnc-master
sudo cp dispmanx_vncserver /usr/bin
sudo chmod +x /usr/bin/dispmanx_vncserver
then when you do sudo whereis dispmanx_vncserver again you SHOULD see that there is something in the /usr/bin folder as well. If it is you are doneā¦just start the service with
Worst case scenario, do : sudo passwd root and set up a password for the root account.
Then download Winscp and log in to your osmc with the local ip address, root (for username) and your new password, then go to /home/osmc/dispmanx_vnc-master and find the dispmanx_vncserver file and copy it to your desktop. (drag and drop to the left panel)
Then go to folder /usr/bin/ and drag the file from your desktop to that folder (from left side to right side).
Then do : sudo chmod +x /usr/bin/dispmanx_vncserver
and finally start the serviceā¦This should work 100%
hmmm now thats something differentā¦
try this before running the service:
sudo modprobe evdev
If no errors appear after when you start the service, then maybe you can skip pulling your hair out by just doing: sudo nano /etc/modules
and add evdev
alone on a separate line there under the ones with the # sign infront of them.
This guide works 100% on a pi2, maybe the pi3 has something different about it ? I dont knowā¦but so far you are 2nd with this kind of problem, and 1st time it was a case of wrong copy/paste
Again - manually starting the VNC server works fine.
Well this should meet my needs for now. I wonāt be needing VNC all the time when I connect the Pi with my TV (I hope), but if I do, Iāll just run it manually from the terminal.
I just wanted to thank you! This has been really great user support and I really appreciate it. If you wish to pursue this issue further, just let me know and Iāll do what I can from my side
Sorry i couldnt help any further with this maybe someone with more knowledge on this will reply. (it usually happens very fast great support team here).
You are welcome
First off I must point out I donāt use vnc server, but being as this seems to be a systemd issue now (as it runs manually); I thought Iād see if I could help.
Could you please issue the following command:
journalctl -xe | paste-log
Provide the url given.
Also could you please post the output of the following:
I was just writing to let you all know I have solved it by redoing the service file again. Iām not sure what but there seems to have been an issue there.
It now runs the VNC server on reboot so all is well.
nahh, they use dialog, blue windows
If you can make a script iād be happy to add it up in the thread since some people have problems doing it manually.
I also thought about making a shell script, but the whole thing takes 20 seconds to do. kinda pointless