TigerVNC on Fedora 17

[hlfmanhlfamzng]

So I'm trying to setup remote administration on a computer that's not at my house, but I'm finding that all of the FAQs on this are out of date.

As far as I'm concerned, an FAQ like this:

http://fedorasolved.org/Members/zdenek/tigervnc-server

Is highly informative, yes. But if all these hoops have to be jumped through? Then this software is by default broken. It's broken. When I do a yum - install _____________________ whatever the software happens to be, it should work after it's installed. I did the install, and it doesn't work. It's broken. I did an install of libreoffice earlier, and it was great. It worked after install. Firefox works after install.

This isn't the mid 90's anymore. We actually like software that works once installed, don't we?

Anyways, this FAQ says to go to the file "/etc/sysconfig/vncservers" but when I get there, this is what I see:

# THIS FILE HAS BEEN REPLACED BY /lib/systemd/system/vncserver@.service

Ok. So I go to the file specified. It looks nothing like what I'm supposed to look for. I don't see a specification for software resolution, usernames, and so forth.

Anybody want to take a stab at this or point to a better FAQ which I missed? This is frustrating. It should've worked after Yum install. Type in the IP address, specify the user IDs, passwords, and go. That's not a lot to ask.

[smr54]

Heh. (Not laughing at you). There's another thread. Yes, it's involved, and convoluted, and at least two people, (one other forum member and myself) consider it indicative of how most people in Fedora development and packaging don't seem to do system administration, but that's a rant for another time.....

http://forums.fedoraforum.org/showth...=272137&page=3

That should take you to page 3. Post 37 should help.

That FAQ seems to have last been updated in February of last year and should be marked as deprecated.

[MotherDawg]

Ouch bud,

Maybe it's time to get involved and do something about it.
Ya know... Linux is user supported as in You ! ("sorray")

For your information, TigerVNC server actually runs pretty good on F17. It is not broken, I'm using it through TightVNC from an M$ box to write this.

You kind of need to search for treads on the subject before posting flames.

And in vncserver@.service it goes :

Quick HowTo:
# 1. Copy this file to /etc/systemd/system/vncserver@:<display>.service
# 2. Edit <USER> and vncserver parameters appropriately
# ("runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2")
# 3. Run `systemctl daemon-reload`

Have you tried something along those lines ?

Here, a silver spoon for you :
Tiger VNC server on F16 & F17

Hey 54! You beat me to it... took a long time to find an appropriate quote. LoL.

You must be the change you wish to see in the world. -- Mahatma Gandhi

[hlfmanhlfamzng]

It's not personal, I've just gotten so used to things being easy, as time has gone on in linux. This was a throwback and I was voicing my frustrations. Having a visual confirmation that what I just did worked is a good thing, IMHO.(as I proceed through multiple step processes)

filename and path:

/etc/systemd/system/vncserver@:1.service

This is what's in the file:

[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=forking
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l user -c "/usr/bin/vncserver %i"
ExecStop=/sbin/runuser -l user -c "/usr/bin/vncserver -kill %i"

[Install]
WantedBy=multi-user.target

Yes, the username for now is just user. I wasn't sure if I was going to screw this up once I saw all these config files.

And systemctl daemon-reload doesn't do anything when I run it.

[MotherDawg]

Hey,

systemctl daemon-reload just reloads the configs. Since you are only changing the vncserver one, and you do... did systemctl stop vncserver@:1.service before, it reloads the changed config of a stoped service.

After you edit the config, systemctl daemon-reload then systemctl start vncserver@:1.service.

Go to the the Tiger VNC server on F16 & F17 thread and read page 2 and 3. SMR54 and me posted the link.

In my "retort", I could have mentioned that vncserver is kind of an System Administrator app.
We always edit config files all day long. Make yourself one or two backups of vncserver@.service and xstartup.

I have vncserver@.service.org.MyName and xstartup.org.MyName in the original folders and in a config folder in my home directory plus I have a GiT hub to make sure.

Cya

[Doward]

So after fighting with this tonight, I got what I wanted - XFCE4 used when VNC'd on a KDE-F17 system.

Ugh.

I couldn't get the 'User=' variable to work, so I pulled it out.

Here's my setup:

[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=forking
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l vncuser -c "/usr/bin/vncserver %i"
ExecStop=/sbin/runuser -l vncuser -c "/usr/bin/vncserver -kill %i"

[Install]
WantedBy=multi-user.target

Once I did that, I logged in locally as my vncuser, and ran vncserver :1, which created my xstartup scripts and such. I modified them to such:

#!/bin/sh

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
        eval `dbus-launch --sh-syntax .exit-with-session`
        echo "D-BUS per-session daemon address is: \
        $DBUS_SESSION_BUS_ADDRESS"
fi
exec  xfce4-session

Now I can vnc into my system on port 5901 and get my XFCE4 desktop!

MAJOR PITA COMPARED TO THE OLD WAY.