-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 19 Aug 2014 09:20:31 -0400
Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> On 08/19/2014 08:43 AM, Robert Moskowitz wrote:
>> First, I have gotten tigervnc-server working on the Fedora20 remix
>> for my cubieboard2, so I have the steps down. At least for F20.
>>
>> I am running Fedora-Minimal-armhfp-21-20140815-sda.raw.xz on my
>> cubieboard2. I have done basic setup and have only moved ssh to a
>> non-standard port (see my posts on selinux issues, but not germaine
>> here).
>>
>> I installed Xfce: yum groupinstall "Xfce Desktop" --nogpgcheck
>>
>> This took 640 rpms?! And installed tigervnc-server.
>>
>> I logged in as me an created my .vnc/passwd file with vncpasswd.
>>
>> I then configured the start script with:
>>
>> cp /lib/systemd/system/vncserver@.service
>> /etc/systemd/system/vncserver@:3.service
>> vi /etc/systemd/system/vncserver@:3.service
>> where I replaced <user> with my userid.
>>
>> I also opened tcp port 5903 with: firewall-cmd --permanent
>> --add-port=5903/tcp
>>
>> Now wanting to be 'clean', I rebooted then:
>>
>> # systemctl enable vncserver@:3.service
>> Created symlink from
>> /etc/systemd/system/multi-user.target.wants/vncserver@:3.service to
>> /etc/systemd/system/vncserver@:3.service.
>>
>> # systemctl start vncserver@:3.service
>> Job for vncserver@:3.service failed. See 'systemctl status
>> vncserver@:3.service' and 'journalctl -xn' for details.
>>
>> # systemctl -l status vncserver@:3.service
>> ● vncserver@:3.service - Remote desktop service (VNC)
>> Loaded: loaded (/etc/systemd/system/vncserver@:3.service; enabled)
>> Active: failed (Result: exit-code) since Tue 2014-08-19 08:06:13
>> EDT; 1min 4s ago
>> Process: 980 ExecStart=/sbin/runuser -l rgm -c /usr/bin/vncserver
>> %i (code=exited, status=126)
>> Process: 976 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i >
>> /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
>>
>> Aug 19 08:05:47
cb2.htt-consult.com systemd[1]: Starting Remote
>> desktop service (VNC)...
>> Aug 19 08:06:13
cb2.htt-consult.com systemd[1]:
>> vncserver@:3.service: control process exited, code=exited status=126
>> Aug 19 08:06:13
cb2.htt-consult.com systemd[1]: Failed to start
>> Remote desktop service (VNC).
>> Aug 19 08:06:13
cb2.htt-consult.com systemd[1]: Unit
>> vncserver@:3.service entered failed state.
>>
>> I rebooted and checked again:
>>
>> # systemctl -l status vncserver@:3.service
>> ● vncserver@:3.service - Remote desktop service (VNC)
>> Loaded: loaded (/etc/systemd/system/vncserver@:3.service; enabled)
>> Active: activating (start) since Thu 1970-01-01 00:00:22 EST; 44
>> years 7 months ago
>> Process: 608 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i >
>> /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
>> Control: 615 (runuser)
>> CGroup: /system.slice/system-vncserver.slice/vncserver@:3.service
>> ‣ 615 /sbin/runuser -l rgm -c /usr/bin/vncserver :3
>>
>> Looks like it is running! Great, so I check for the pid under my
>> userid:
>>
>> # ls /home/rgm/.vnc/
>> passwd
>>
>> What? Only passwd that I had earlier created? Where is the pid,
>> log, and the xstartup files?
>>
>> So I restarted vncserver:
>>
>> # systemctl restart vncserver@:3.service
>> Job for vncserver@:3.service failed. See 'systemctl status
>> vncserver@:3.service' and 'journalctl -xn' for details.
>>
>> # systemctl -l status vncserver@:3.service
>> ● vncserver@:3.service - Remote desktop service (VNC)
>> Loaded: loaded (/etc/systemd/system/vncserver@:3.service; enabled)
>> Active: failed (Result: exit-code) since Tue 2014-08-19 08:26:17
>> EDT; 25s ago
>> Process: 999 ExecStart=/sbin/runuser -l rgm -c /usr/bin/vncserver
>> %i (code=exited, status=126)
>> Process: 995 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i >
>> /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
>>
>> Aug 19 08:26:17
cb2.htt-consult.com systemd[1]:
>> vncserver@:3.service: control process exited, code=exited status=126
>> Aug 19 08:26:17
cb2.htt-consult.com systemd[1]: Failed to start
>> Remote desktop service (VNC).
>> Aug 19 08:26:17
cb2.htt-consult.com systemd[1]: Unit
>> vncserver@:3.service entered failed state.
>>
>> So one of the following (or something I have not guessed):
>>
>> I missed installing something else needed like tigervnc client?
>> Something broken for using vncserver in F21.
>> Because no video for Allwinner, this is somehow impacting vncserver
>> startup. And thus no remote graphical access at all (that is a
>> scary thought, why would it matter anyway?).
>>
>> So any assistance on trouble shooting this? I am going to install
>> all of tigervnc stuff now to see if it makes a difference, but I
>> don't see why it would. Anyone with working video, if they could
>> see if vncserver works for them?
>>
> Installing the tigervnc client did not make a difference. Still
> failing to start.
you might be best off asking on the users list, most of your questions
are not at all arm specific but just general running things on fedora,
and the wider audience of the users list would likely be better suited
to help you.
There is a lot to what you are saying, and in fact I did that back a
while ago to even figure out how to run tigervnc with systemd, and how
to get it to work with Xfce when I have only used Gnome previously. The
reason I have not, yet, is that since it works fine on F20 x86, and F20
arm remix, I was suspecting it was more the F21 minimal + Xfce used here
that is the source of the problem. I will first try Andy's
recommendation on a dummy xorg.conf, provided I can get one and where to
put it. Then try on the Fedora user list.