Bug 984588 - Unable to start vncserver
Summary: Unable to start vncserver
Keywords:
Status: CLOSED DUPLICATE of bug 983232
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 19
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-15 14:03 UTC by Erik P. Olsen
Modified: 2013-07-16 10:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-16 10:25:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Erik P. Olsen 2013-07-15 14:03:25 UTC
Description of problem:
Following the HOWTO in file vncserver@.service leads to installing file vncserver@:1.service:

[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 erik -c "/usr/bin/vncserver %i"
ExecStop=/sbin/runuser -l erik -c "/usr/bin/vncserver -kill %i"

[Install]
WantedBy=multi-user.target

systemctl status vncserver@:1.service gives:

vncserver@:1.service - Remote desktop service (VNC)
   Loaded: loaded (/usr/lib/systemd/system/vncserver@:1.service; enabled)
   Active: inactive (dead) since Mon 2013-07-15 15:35:08 CEST; 8s ago
  Process: 22919 ExecStop=/sbin/runuser -l erik -c /usr/bin/vncserver -kill %i (code=exited, status=0/SUCCESS)
  Process: 22861 ExecStart=/sbin/runuser -l erik -c /usr/bin/vncserver %i (code=exited, status=0/SUCCESS)
  Process: 22858 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)

Jul 15 15:35:03 epohost.epolan.dk systemd[1]: Starting Remote desktop service (VNC)...
Jul 15 15:35:08 epohost.epolan.dk systemd[1]: Started Remote desktop service (VNC).

ps -ef | grep vnc shows that it is not running.

Version-Release number of selected component (if applicable):

tigervnc-1.2.80-0.16.20130314svn5065.fc19.x86_64
kernel-3.9.9-302.fc19.x86_64
xfce4 4.10.0-5.f19


How reproducible: all the time.


Steps to Reproduce:
1. See above description.
2.
3.

Actual results:
vncviewer from my laptop also running F19 gets connection refused (111)

Expected results:


Additional info:
I can start the server manually by entering vncserver :1 and check with ps shows it working.

This time the error using vncviewer is "No matching securitt types".

Comment 1 Tim Waugh 2013-07-16 10:25:30 UTC

*** This bug has been marked as a duplicate of bug 983232 ***


Note You need to log in before you can comment on or make changes to this bug.