On 15/07/13 11:34, Michael D. Setzer II wrote: > On 15 Jul 2013 at 10:00, Erik P. Olsen wrote: > > Date sent: Mon, 15 Jul 2013 10:00:34 +0200 > From: "Erik P. Olsen" <epod...@gmail.com> > Organization: EPO data > To: tigervnc-users@lists.sourceforge.net > Subject: Re: [Tigervnc-users] Getting "Connection Refused > (111)" at > vncviewer. > >> On 15/07/13 08:47, Michael D. Setzer II wrote: >>> Haven't done anything on f19 yet, and have done a little on f18, but >>> do have a system with vnc running with xfce. Did have to modify the >>> xstartup script though >>> >>> #!/bin/sh >>> >>> # Uncomment the following two lines for normal desktop: >>> unset SESSION_MANAGER >>> unset DBUS_SESSION_BUS_ADDRESS >>> exec /bin/sh /etc/xdg/xfce4/xinitrc # X11/xinit/xinitrc >>> >>> [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup >>> [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources >>> xsetroot -solid grey >>> #vncconfig -iconic & >>> xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP >>> Desktop" & >>> startxfce4 & >>> #twm & >>> >> >> xstartup in F19 is quite different, so I didn't do anything to it. >> > > You are talking about the xstarup file that is located in the users > home directory under .vnc directory. > > The only xstartup file there is. > > >>> That does work, and I was just vnced into the machine with no >>> problem, but he systemctl statusvncserver@:xx.service shows >>> that it failed? >>> >>> ps -ef | grep vnc show that it is running, but not sure what is >>> starting it. >> >> That shows on my system that vnc is NOT running. >> >>> >>> What happens if you manuall start a vnc session locally on >>> another port? >>> >>> vncserver :2 >>> vncviewer 127.0.0.1:2 >> >> Tried that and it works - also from the client! However I had to issue >> following on the client: >> >> vncviewer -SecurityTypes VncAuth,None 192.168.1.70:2 >> >> I found this parameter from bugzilla# 617973. Apparently I have to >> change encryption request on one of the systems. >> >> When I say it works that means that I get a connection but with an >> empty screen. How do I proceed from there?
I've come to the conclusion that there must be a serious bug in the F19 package. The systemctl way of managing vncserver does not work. The documentation is very scarce so it is difficult to point at what's wrong :-( -- Erik Concordia parvæ res crescunt discordia maximæ dilabuntur ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Tigervnc-users mailing list Tigervnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-users
