9:25 a.m.
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome. Definitely not Xfce that I use. The work around is nasty:
Connect via SSH and run vncserver from the command line. But probably
can do it better via SCREEN and just forget about that screen session...
So it is time to look at the alternatives. I know they are out there
and have been talked about on this list, but my search foo is weak (as
always). So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
thanks
11:43 a.m.
On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz wrote:
So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
I use x2go, but it operates in a completely different fashion
from VNC (and I don't think it can allow you to share the
physical screen, it is always a separate X session).
2:12 p.m.
On 9/26/18 12:43 PM, Tom Horsley wrote:
On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz wrote:
> So can I have a bit of help in figuring out what to replace my
> decades-old connection to VNC?
I use x2go, but it operates in a completely different fashion
from VNC (and I don't think it can allow you to share the
physical screen, it is always a separate X session).
I just got a private message on using rc.local that looks a lot like
what others have hacked at connecting with ssh to start vncserver and
avoid the polkit problem that systemd seems to make. So I am going to
give this a try first before abandoning ship....
11:59 a.m.
On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz <rgm(a)htt-consult.com> wrote:
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome. Definitely not Xfce that I use. The work around is nasty:
Connect via SSH and run vncserver from the command line. But probably
can do it better via SCREEN and just forget about that screen session...
So it is time to look at the alternatives. I know they are out there
and have been talked about on this list, but my search foo is weak (as
always). So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
I was having problems with vnc not always being able to connect. I have
now switched to x2go. It has been working well for about 2 weeks.
One note -- sometimes I have to change the window size for the text to look
good. It has not been enough of a problem to get me to look for a config
error or some other condition that will fix it.
David
> thanks
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
3:15 p.m.
On 9/26/18 7:25 AM, Robert Moskowitz wrote:
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome. Definitely not Xfce that I use. The work around is nasty:
Connect via SSH and run vncserver from the command line. But probably
can do it better via SCREEN and just forget about that screen session...
So it is time to look at the alternatives. I know they are out there
and have been talked about on this list, but my search foo is weak (as
always). So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
thanks
I use XRDP a lot. It's downfall or upside however you want
to look at it, is that it opens a separate session to the remote
viewer, meaning you can't assist someone at the other end
and the other end can't see what you are doing ("You pay who
how much more than me!!!!").
For clients, I use xfreerdp on Linux and mstsc on Windows
3:37 p.m.
On 9/26/18 10:25 PM, Robert Moskowitz wrote:
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome.
Definitely not Xfce that I use. The work around is nasty: Connect via SSH and run
vncserver from the command line. But probably can do it better via SCREEN and just
forget about that screen session...
So it is time to look at the alternatives. I know they are out there and have been
talked about on this list, but my search foo is weak (as always). So can I have a
bit of help in figuring out what to replace my decades-old connection to VNC?
As discussed on the test list, the actual problem with tiger vncserver and polkit
arises when it is started via the supplied vncserver@.service systemd file.
If started manually that problem doesn't exist.
Just like in all things Linux, there are multiple ways to accomplish having the
server manually started.
1. Manually ssh into the remote system and start the server before starting your client.
2. Use a vnc-client such as remmina which has a "pre" and "post"
command that will
automate #1 above.
3. Use the rc.local method you mentioned in another post to start the server at boot
time.
4. Use a custom vncserver.service file such as the one I pointed you to on the test
list. The advantage of this over #3 is that it stays in the systemd
framework and can easily "enabled", "disabled", "stopped",
and "started". It is
really no more "ugly a hack" as the rc.local route.
The "problem" with seeking alternatives is that you'd have to "lean new
tricks" and
may run into new things you'll have to get used to or workaround.
While that can be "fun" it seems to me (just an opinion) invoking an alternate
method
of starting the server provides you with less changes to deal with.
--
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."
4:46 p.m.
On 9/26/18 4:37 PM, Ed Greshko wrote:
On 9/26/18 10:25 PM, Robert Moskowitz wrote:
> It seems Tiger-vncserver is broken WRT polkit for any spin other than gnome.
> Definitely not Xfce that I use. The work around is nasty: Connect via SSH and run
> vncserver from the command line. But probably can do it better via SCREEN and just
> forget about that screen session...
>
> So it is time to look at the alternatives. I know they are out there and have been
> talked about on this list, but my search foo is weak (as always). So can I have a
> bit of help in figuring out what to replace my decades-old connection to VNC?
As discussed on the test list, the actual problem with tiger vncserver and polkit
arises when it is started via the supplied vncserver@.service systemd file.
If started manually that problem doesn't exist.
Just like in all things Linux, there are multiple ways to accomplish having the
server manually started.
1. Manually ssh into the remote system and start the server before starting your
client.
2. Use a vnc-client such as remmina which has a "pre" and "post"
command that will
automate #1 above.
3. Use the rc.local method you mentioned in another post to start the server at boot
time.
Yes. I am getting mixed personal feelings about stepping back to SysV
approach. I realize I still have a ClearOS6 system running that uses
SysV for me to look at, but still. Got to move forward. I really tried
to embrace Systemd when it came out.
4. Use a custom vncserver.service file such as the one I pointed you to on the test
list. The advantage of this over #3 is that it stays in the systemd
framework and can easily "enabled", "disabled", "stopped",
and "started". It is
really no more "ugly a hack" as the rc.local route.
For others here the one Ed and I are talking about is:
https://forums.fedoraforum.org/showthread.php?316905-PolicyKit-failed-ove...
I have to study this more to get the 'feel' of it and what exactly the
setup steps are.
The "problem" with seeking alternatives is that you'd have to "lean
new tricks" and
may run into new things you'll have to get used to or workaround.
While that can be "fun" it seems to me (just an opinion) invoking an alternate
method
of starting the server provides you with less changes to deal with.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
8:28 p.m.
New subject: VNCserver seems to be working - Re: VNC alternatives
Per the instructions from the Fedoraforum. Took a bit, but I am
mounting USB drive. Polkit is prompting me for my password and that
lets me mount the drive. Probably because I am in group wheel.
So call is off for alternative to vnc and to remember how to do it with
SysV. I am staying with Systemd, but
What a MESS!
On 9/26/18 5:46 PM, Robert Moskowitz wrote:
On 9/26/18 4:37 PM, Ed Greshko wrote:
> On 9/26/18 10:25 PM, Robert Moskowitz wrote:
>> It seems Tiger-vncserver is broken WRT polkit for any spin other than gnome.
>> Definitely not Xfce that I use. The work around is nasty: Connect via SSH and
run
>> vncserver from the command line. But probably can do it better via SCREEN and
just
>> forget about that screen session...
>>
>> So it is time to look at the alternatives. I know they are out there and have
been
>> talked about on this list, but my search foo is weak (as always). So can I have
a
>> bit of help in figuring out what to replace my decades-old connection to VNC?
> As discussed on the test list, the actual problem with tiger vncserver and polkit
> arises when it is started via the suppliedvncserver@.service systemd file.
> If started manually that problem doesn't exist.
>
> Just like in all things Linux, there are multiple ways to accomplish having the
> server manually started.
>
> 1. Manually ssh into the remote system and start the server before starting your
client.
>
> 2. Use a vnc-client such as remmina which has a "pre" and "post"
command that will
> automate #1 above.
>
> 3. Use the rc.local method you mentioned in another post to start the server at
boot
> time.
Yes. I am getting mixed personal feelings about stepping back to SysV
approach. I realize I still have a ClearOS6 system running that uses
SysV for me to look at, but still. Got to move forward. I really
tried to embrace Systemd when it came out.
> 4. Use a custom vncserver.service file such as the one I pointed you to on the test
> list. The advantage of this over #3 is that it stays in the systemd
> framework and can easily "enabled", "disabled",
"stopped", and "started". It is
> really no more "ugly a hack" as the rc.local route.
For others here the one Ed and I are talking about is:
https://forums.fedoraforum.org/showthread.php?316905-PolicyKit-failed-ove...
I have to study this more to get the 'feel' of it and what exactly the
setup steps are.
> The "problem" with seeking alternatives is that you'd have to
"lean new tricks" and
> may run into new things you'll have to get used to or workaround.
> While that can be "fun" it seems to me (just an opinion) invoking an
alternate method
> of starting the server provides you with less changes to deal with.
>
>
> _______________________________________________
> users mailing list --users(a)lists.fedoraproject.org
> To unsubscribe send an email tousers-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedora...
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
8:47 p.m.
New subject: VNCserver seems to be working - Re: VNC alternatives
On 9/27/18 9:28 AM, Robert Moskowitz wrote:
Per the instructions from the Fedoraforum. Took a bit, but I am
mounting USB
drive. Polkit is prompting me for my password and that lets me mount the drive.
Probably because I am in group wheel.
So call is off for alternative to vnc and to remember how to do it with SysV. I am
staying with Systemd, but
What a MESS!
FWIW, I use "remmina" as my VNC client. I also use public key authentication
for
ssh. So, with remmina I simply put
ssh egreshko(a)192.168.1.80 vncserver as a "pre-command" to start the
vncserver and
ssh egreshko(a)192.168.1.80 vncserver -kill :1 as a "post-command" to stop the
vncserver
For me this is an optimal solution since I can just, basically, use copy/paste into
the various profiles for all the test systems that I
tend to create and destroy frequently. This way I don't need to fuss and muss with
making changes to systemd files to get this working.
Basically, it saves me time, keystrokes, and use of my memory. :-)
--
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."
7:51 a.m.
Il giorno mer, 26/09/2018 alle 10.25 -0400, Robert Moskowitz ha
scritto:
So it is time to look at the alternatives.
Xpra ?
https://www.xpra.org/
Xpra is an open-source multi-platform persistent remote display server
and client for forwarding applications and desktop screens.
It gives you remote access to individual applications or full
desktops.
On X11, it is also known as screen for X11: it allows you to run
programs, usually on a remote host, direct their display to your local
machine, and then to disconnect from these programs and reconnect from
the same or another machine, without losing any state.
It can also be used to forward full desktops, from X11 servers, MS
Windows, or Mac OS X.
Xpra also allows forwarding of sound, clipboard and printing services.
Sessions can be accessed over SSH, or password protected over plain TCP
sockets with or without SSL.
Xpra is usable over reasonably slow links and does its best to adapt to
changing network bandwidth constraints.
--
Dario Lesca
(inviato dal mio Linux Fedora 28 Workstation)
1:56 a.m.
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
Robert Moskowitz wrote:
> It seems Tiger-vncserver is broken WRT polkit for any spin other
than
> gnome.
I think that adding the following in the vncserver@.service and/or
xvnc@.service, in the [service] section, may solve that problem:
PAMName=login
You may want also to add:
UtmpIdentifier=%I
UtmpMode=user
to have the users listed for example by the who command.
Is this documented anywhere, ideally in a bug report?
I don't know.
--
francis
8:35 a.m.
On 9/30/18 2:56 AM, Francis.Montagnac(a)inria.fr wrote:
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
> Robert Moskowitz wrote:
>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>> gnome.
I think that adding the following in the vncserver@.service and/or
xvnc@.service, in the [service] section, may solve that problem:
PAMName=login
You may want also to add:
UtmpIdentifier=%I
UtmpMode=user
to have the users listed for example by the who command.
I will give this a try. It will be later in the week and I will post my
findings.
where are those 3 variables defined and documented? I did a little
googling and only found where people used them successfully. Not how
they knew to use them...
> Is this documented anywhere, ideally in a bug report?
I don't know.
11:58 a.m.
On Sun, 30 Sep 2018 09:35:06 -0400 Robert Moskowitz wrote:
On 9/30/18 2:56 AM, Francis.Montagnac(a)inria.fr wrote:
> On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
> PAMName=login
> UtmpIdentifier=%I
> UtmpMode=user
where are those 3 variables defined and documented?
In "man systemd.exec"
In addition, there is since recently the "man systemd.directives" that
gives a full index of the systemd configuration directives.
--
francis.
8:34 a.m.
Francis.Montagnac(a)inria.fr wrote:
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
> Robert Moskowitz wrote:
>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>> gnome.
..
> Is this documented anywhere, ideally in a bug report?
I don't know.
OK, so, for anyone experiencing this... if you want it fixed, the best way
to help make that happen is to formally report it as a bug.
When/if you do, following up here with a link would be greatly appreciated,
thanks.
-- Rex
7:04 a.m.
On 10/1/18 9:34 AM, Rex Dieter wrote:
Francis.Montagnac(a)inria.fr wrote:
> Hi
>
> On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
>
>> Robert Moskowitz wrote:
>>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>>> gnome.
..
>> Is this documented anywhere, ideally in a bug report?
> I don't know.
OK, so, for anyone experiencing this... if you want it fixed, the best way
to help make that happen is to formally report it as a bug.
When/if you do, following up here with a link would be greatly appreciated,
thanks.
https://bugzilla.redhat.com/show_bug.cgi?id=1633805
I am going to try out Francis' recommendations shortly.
and
https://bugzilla.redhat.com/show_bug.cgi?id=1633811
4:10 p.m.
On 9/30/18 2:56 AM, Francis.Montagnac(a)inria.fr wrote:
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
> Robert Moskowitz wrote:
>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>> gnome.
I think that adding the following in the vncserver@.service and/or
xvnc@.service, in the [service] section, may solve that problem:
PAMName=login
I changed my service file to have:
[Service]
Type=forking
WorkingDirectory=/home/rgm
User=rgm
Group=rgm
PAMName=login
PIDFile=/home/rgm/.vnc/%H%i.pid
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 ||
:'
...
stopped and restarted vncserver and it failed:
# systemctl -l --no-pager status vncserver@:1
● vncserver@:1.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:1.service; disabled;
vendor preset: disabled)
Active: failed (Result: protocol) since Thu 2018-10-04 17:02:22 EDT;
5min ago
Process: 2806 ExecStart=/usr/bin/vncserver -autokill :1 (code=exited,
status=0/SUCCESS)
Process: 2788 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill :1 >
/dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Oct 04 17:02:13 localhost systemd[1]: Starting Remote desktop service
(VNC)...
Oct 04 17:02:22 localhost systemd[1]: vncserver@:1.service: New main PID
2830 does not belong to service, and PID file is not owned by root.
Refusing.
Oct 04 17:02:22 localhost systemd[1]: vncserver@:1.service: New main PID
2830 does not belong to service, and PID file is not owned by root.
Refusing.
Oct 04 17:02:22 localhost systemd[1]: vncserver@:1.service: Failed with
result 'protocol'.
Oct 04 17:02:22 localhost systemd[1]: Failed to start Remote desktop
service (VNC).
so back to using ssh for now unless you have other suggestions?
thanks for this one.
You may want also to add:
UtmpIdentifier=%I
UtmpMode=user
to have the users listed for example by the who command.
> Is this documented anywhere, ideally in a bug report?
I don't know.
12:42 a.m.
Hi.
On Thu, 04 Oct 2018 17:10:54 -0400 Robert Moskowitz wrote:
On 9/30/18 2:56 AM, Francis.Montagnac(a)inria.fr wrote:
> Hi
> On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
>> Robert Moskowitz wrote:
>>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>>> gnome.
> I think that adding the following in the vncserver@.service and/or
> xvnc@.service, in the [service] section, may solve that problem:
> PAMName=login
I changed my service file to have:
[Service]
Type=forking
WorkingDirectory=/home/rgm
User=rgm
Group=rgm
PAMName=login
PIDFile=/home/rgm/.vnc/%H%i.pid
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i >
/dev/null 2>&1 || :'
...
stopped and restarted vncserver and it failed:
...
(VNC)...
Oct 04 17:02:22 localhost systemd[1]: vncserver@:1.service: New main PID
2830 does not belong to service, and PID file is not owned by root.
Refusing.
Oct 04 17:02:22 localhost systemd[1]: vncserver@:1.service: New main PID
2830 does not belong to service, and PID file is not owned by root.
Refusing.
...
so back to using ssh for now unless you have other suggestions?
Can you try to set Type to simple and thus get rid of the pid stuff.
So try:
[Service]
Type=simple
WorkingDirectory=/home/rgm
User=rgm
Group=rgm
PAMName=login
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 ||
:'
...
--
francis
12:58 a.m.
On Fri, 05 Oct 2018 07:42:16 +0200 Francis.Montagnac(a)inria.fr wrote:
Can you try to set Type to simple and thus get rid of the pid stuff.
So try:
[Service]
Type=simple
WorkingDirectory=/home/rgm
User=rgm
Group=rgm
PAMName=login
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i >
/dev/null 2>&1 || :'
...
This will not work since vncserver go by default in the
background. Fortunately it provides a -fg option.
Replace thus:
ExecStart=/usr/bin/vncserver -autokill %i
by:
ExecStart=/usr/bin/vncserver -fg %i
-autokill is useless with -fg
--
francis
10:07 a.m.
On 10/5/18 1:58 AM, Francis.Montagnac(a)inria.fr wrote:
On Fri, 05 Oct 2018 07:42:16 +0200 Francis.Montagnac(a)inria.fr wrote:
> Can you try to set Type to simple and thus get rid of the pid stuff.
> So try:
> [Service]
> Type=simple
> WorkingDirectory=/home/rgm
> User=rgm
> Group=rgm
> PAMName=login
> ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1
|| :'
> ...
This will not work since vncserver go by default in the
background. Fortunately it provides a -fg option.
Replace thus:
ExecStart=/usr/bin/vncserver -autokill %i
by:
ExecStart=/usr/bin/vncserver -fg %i
-autokill is useless with -fg
Thank you. I will review this.
I updated bug 1633805
Actually the service is running, no pid file. At least by the standard
name. I looked in the whole file system, not just under my user.
definitely weird.
10:57 a.m.
On Fri, 05 Oct 2018 11:07:28 -0400 Robert Moskowitz wrote:
> Type=simple
...
> Replace thus:
> ExecStart=/usr/bin/vncserver -autokill %i
> by:
> ExecStart=/usr/bin/vncserver -fg %i
> -autokill is useless with -fg
Thank you. I will review this.
I updated bug 1633805
Actually the service is running,
Does it work?
Are you able to connect to it with vncviewer?
no pid file. At least by the standard name. I looked in the whole
file system, not just under my user.
definitely weird.
This is normal: there is no pid file for a service of Type simple:
systemd controls it simply as a child process.
--
francis.
11:04 a.m.
On 10/5/18 11:57 AM, Francis.Montagnac(a)inria.fr wrote:
On Fri, 05 Oct 2018 11:07:28 -0400 Robert Moskowitz wrote:
>> Type=simple
...
>> Replace thus:
>> ExecStart=/usr/bin/vncserver -autokill %i
>> by:
>> ExecStart=/usr/bin/vncserver -fg %i
>> -autokill is useless with -fg
> Thank you. I will review this.
> I updated bug 1633805
> Actually the service is running,
Does it work?
Are you able to connect to it with vncviewer?
I am able to connect and do useful stuff.
When I first connect, it goes directly to the session. No additional
log in. Screensaver does work, so if I come back later, I have to
unlock the session.
> no pid file. At least by the standard name. I looked in the whole
> file system, not just under my user.
> definitely weird.
This is normal: there is no pid file for a service of Type simple:
systemd controls it simply as a child process.
I did not change to simple. Still using forking.
I have not really looked into your latest recommendations.
2029
days inactive
2038
days old
21 comments
9 participants
participants (9)
-
D&R -
Dario Lesca -
Ed Greshko -
Francis.Montagnac＠inria.fr -
Rex Dieter -
Rex Dieter -
Robert Moskowitz -
ToddAndMargo -
Tom Horsley