bristol@mailman.lug.org.uk
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk
You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."
Today's Topics:
1. Re: Unable VNC into a Rpi Desktop (AJ)
2. Re: Unable VNC into a Rpi Desktop (Peter Hemmings)
3. Re: Unable VNC into a Rpi Desktop (Dave Addison)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Jan 2017 18:27:20 +0000
From: AJ <lists@g7kna.co.uk>
To: Peter Hemmings <peternsomerset@virginmedia.com>
Cc: BBLUG <Bristol@mailman.lug.org.uk>, AJ <lists@g7kna.co.uk>
Subject: Re: [bristol] Unable VNC into a Rpi Desktop
Message-ID:
<CAEMisWBCBeOa9Q_bVePub5h=1kHLt-B4jxq4GQFRMA=s9GNmNg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On 2 January 2017 at 17:35, Peter Hemmings
<peternsomerset@virginmedia.com> wrote:
> Andy,
>
> On 02/01/17 16:25, AJ wrote:
>>
>> Peter,
>>
>> Don't know how much of this you are familiar with so if I cover things
>> you know I apologise, I am not trying to teach granny, or anyone else
>> for that matter, how to suck eggs.
>
>
> OK
>
>>
>> VNC has two components:
>> 1. A VNC server running on the target machine that is to be
>> controlled, in this case your Pi
>> 2. A VNC client running on the machine you are operating usually a
>> tablet or other portable device
>>
>> You need to configure the server on the target machine and in doing so
>> will configure ports it listens on and the password to access the
>> server.
>>
>> Once the server is running on the target machine (Pi) you should be
>> able to connect to it by starting the VNC client on whatever device
>> you want to control the Pi from and pointing it at the IP address (or
>> hostname if your LAN supports that) of your Pi. The server on the Pi
>> will then prompt for the password which is entered and then the Pi
>> desktop should be seen within the VNC window.
>
>
> I did know most of the above but was reassurance that most of what I am
> doing is correct!
>
>>
>> Have a look here:
>>
>> https://www.realvnc.com/docs/raspberry-pi.html
>
>
> That is a bit better than what I was using!
>
> I originally was going to use either tightvnc or realvnc (cannot remember
> which) and read that I could not fully control the desktop and was advised
> to use x11vnc server.
Not sure why that should be the case but I have only limited use of
VNC and even less exposure to the Pi so there could be volumes that I
am unaware of. The link to RealVNC suggests that it is part of a
typical install so from an uninformed point of view why would they
give you something that only did half the job?
> I went through a procedure that "greyed out" the vnc option in rasp config,
> which is still "greyed out".
>
> If I log in via rdp I can see its still greyed out.
> If I ssh into a CLI and type:
>
> sudo systemctl enable vncserver-x11-serviced.service
>
> it seem to work without complaining but if I do a "Status" I get errors
> like:
>
> loaded enabled
> Active Failed (result: start limit) ...... Maind PID: 589 (code=exited,
> status=203/EXEC)
>
> and
>
> vncserver-x11-serviced.service start request repeated too quickly, refusing
> to start.
> Failed to start VNV Server in Service Mode Daemon.
>
> (sorry had to type the above as I cannot copy/paste from remote viewer
> window)
>
OK, that is well beyond my understanding
> I think I will start with a new raspian install to ensure any old config
> settings are not the cause of the problem!
>
That would be a good approach, and probably my own thoughts on the matte too
> BTW is tightvnc a fully functioning server or is it a cut down version?
>
I really don't know, I'm not sure I grasp what "fully functioning"
means. When I used it it would faithfully replicate the remote
machines desktop and I could operate as if sat in front of the remote
machine. I could also cut and paste out of the VNC and into
applications local to me. I haven't had to use it for a couple of
years or more so I really can't remember that much about the settings
available within the server but they seemed quite comprehensive at the
time.
<snip a bunch of stuff about how I used to implement VNC>
.
.
.
</snip>
> Thanks
>
> --
> Peter H
Regards
Andy
--
Andy Jenner
Q: What goes; "Pieces of seven, pieces of seven"?
A: A parroty error
------------------------------
Message: 2
Date: Mon, 2 Jan 2017 20:12:51 +0000
From: Peter Hemmings <peternsomerset@virginmedia.com>
To: bristol@mailman.lug.org.uk
Subject: Re: [bristol] Unable VNC into a Rpi Desktop
Message-ID: <5d9bef0e-10fe-e9d9-2c88-a4c179847c42@virginmedia.com>
Content-Type: text/plain; charset=utf-8; format=flowed
On 02/01/17 18:25, Sebastian via Bristol wrote:
> Also you can only use one graphical one at once as far as I know, can't
> use more than one I belive.
OK, if that's so I will stop/remove the rdp server before reverting to
a new install which is a bit of a "cop out"!
--
Peter H
------------------------------
Message: 3
Date: Tue, 03 Jan 2017 11:43:07 +0000
From: Dave Addison <dave@redmoor.org.uk>
To: bristol@mailman.lug.org.uk
Subject: Re: [bristol] Unable VNC into a Rpi Desktop
Message-ID: <20170103114307.188878wnpk4qb9e3@phaedra.homelinux.org>
Content-Type: text/plain; charset="iso-8859-1"
Quoting Peter Hemmings via Bristol <bristol@mailman.lug.org.uk>:
> On 02/01/17 18:25, Sebastian via Bristol wrote:
>> Also you can only use one graphical one at once as far as I know, can't
>> use more than one I belive.
>
> OK, if that's so I will stop/remove the rdp server before reverting
> to a new install which is a bit of a "cop out"!
>
>
>
> --
> Peter H
Hi
There's nothing stopping you from running multiple X displays on the same machine but they must have a different display number. The display number defines the unix sockets and network ports that the display software will try and use for connections from clients.
It's possible that vnc is attempting to set up using the same display number as the rdp server in which case it will fail repeatedly as you're seeing in the systemd output. It should be logging to either the system journal or a log file somewhere and this should provide a more helpful error message
ssh can be used to forward graphical clients. ssh -X user@hostname will provide an encrypted connection back to the X display on your local machine. I use the quite a lot with the pi as it offloads the running of the X-display software
Regards
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20170103/4799478d/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol
------------------------------
End of Bristol Digest, Vol 676, Issue 2
***************************************
Tidak ada komentar:
Posting Komentar