On 9/21/18 11:14 PM, Robert Moskowitz wrote:
On 9/21/18 11:02 AM, Ed Greshko wrote:
> On 9/21/18 9:14 PM, Robert Moskowitz wrote:
>> I have had this problem pre beta images. This is the F29-armfhp code base.
>> I am running vnc server as a service. I have edited the xstartup to have:
>> # exec /etc/X11/xinit/xinitrc
>> exec /bin/sh /etc/xdg/xfce4/xinitrc
>> xrdb $HOME/.Xresources
>> startxfce4 &
>> Note that currently, the is no .Xresources file.
> I do not know why you're doing that. But, I haven't.
>> When I connect to the system after a fresh boot or vncserver restart I get a
>> Error XFCE PolicyKit Agent
>> Ed Greshko reported on the Fedora list (as I thought this was a more general
>> VNC/Xfce error having nothing to do with the beta) that he does not get this
>> but he is NOT running vncserver as a service. Rather from an SSH session.
> I have configured by f28 system to run vncsever as a service and I see the error
> you're reporting.
> I believe I understand why the error is presented.
> If you start the vncserver you'll see something like this
> polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd --no-debug
> egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit
> When you make a vnc client connection, you get the error and then you'll see
> polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd --no-debug
> running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at 23:00.
My F28 install is right now doing its dnf update which will take a bit. But I was
setting what starts at startup via Settings > Session and Startup
And I noticed that polkit is started there. I bet if you turn that off, things MAY
get better. Of course then console login will not have polkit. So perhaps
vncserver should NOT be running polkit?
After a bit of testing and a bit of googling the answer is.....
vncserver and polkit don't play nice when vncserver is started as a service as
described in /lib/systemd/system/vncserver@.service. The issue is not
confined to Xfce. The same basic problem exists when the spin used in KDE.
As mentioned elsewhere, if you ssh into the system and start vncserver manually then
everything works "normally" for the most part.
It seems nobody has done much to attempt to fix the problem from what I can tell.
That being said, a workaround is described
With the other alternative to be having your vnc client (remmina can do it) issue a
pre-command via ssh to start the vncserver manually. Of course you'll
to have "authorized_keys" on the vncserver system side to make this seamless.
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."