562669 – service vncserver start only starts one display

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 562669 - service vncserver start only starts one display

Summary: service vncserver start only starts one display

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	tigervnc
Sub Component:
Version:	6.0
Hardware:	All
OS:	Linux
Priority:	low
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Tim Waugh
QA Contact:	qe-baseos-daemons
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	782183 949522 994246
TreeView+	depends on / blocked

Reported:	2010-02-07 22:43 UTC by Saar
Modified:	2014-10-14 04:38 UTC (History)
CC List:	3 users (show)
Fixed In Version:	tigervnc-1.1.0-9.el6
Doc Type:	Bug Fix
Doc Text:	When more than one display was configured in /etc/sysconfig/vncservers, the vncserver initscript would stop on error. This meant a problem with one display would prevent other displays from being started. The initscript now attempts to start each configured display.
Clone Of:
Environment:
Last Closed:	2014-10-14 04:38:44 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
Here is the change I plan to make (677 bytes, patch) 2014-04-03 15:26 UTC, Tim Waugh	no flags	Details \| Diff
Here is the change I plan to make (sorry, missed a bit in the last one) (1.87 KB, patch) 2014-04-03 15:34 UTC, Tim Waugh	no flags	Details \| Diff
Show Obsolete (1) View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2014:1412	0	normal	SHIPPED_LIVE	tigervnc bug fix update	2014-10-14 01:11:08 UTC

Description Saar 2010-02-07 22:43:34 UTC

Assuming in /etc/sysconfig/vncservers you have 2 displays configured, they are running and are actively being used.  Adding a 3rd display, and typing:

# service vncserver start
Starting VNC server: 1:root A VNC server is already running as :1
                                                           [FAILED]

fails...   This is because in /etc/rc.d/init.d/vncserver:

    for display in ${VNCSERVERS}
    do
        NOSERV=
        echo -n "${display} "
        unset BASH_ENV ENV
        DISP="${display%%:*}"
        export USER="${display##*:}"
        export VNCUSERARGS="${VNCSERVERARGS[${DISP}]}"
        runuser -l ${USER} -c "cd ~${USER} && [ -f .vnc/passwd ] && vncserver :${DISP} ${VNCUSERARGS}"
        RETVAL=$?
==>>    [ "$RETVAL" -ne 0 ] && break
    done

There is an exit from the loop upon the first error.  If you comment out that line, the output looks more reasonable:

# service vncserver start
Starting VNC server: 1:root A VNC server is already running as :1
2:root A VNC server is already running as :2
3:root A VNC server is already running as :3
4:root 
New 'mynode:4 (root)' desktop is mynode:4

Start should follow through for all displays.

you could do restart, but that kills all currently used displays which is bad.

Comment 3 RHEL Program Management 2010-08-09 18:30:43 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2011-01-11 20:51:43 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2011-01-12 15:18:53 UTC

This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 6 RHEL Program Management 2011-05-31 13:32:57 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2012-06-12 01:06:23 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 8 Adam Tkac 2013-03-18 13:09:41 UTC

Since RHEL 5 is now in production phase 2 (only important/critical issues are addressed) and this is not important issue, I'm moving this ticket to RHEL-6 because issue is still present there.

Comment 11 Tim Waugh 2014-02-05 18:13:40 UTC

*** Bug 768405 has been marked as a duplicate of this bug. ***

Comment 13 Tim Waugh 2014-04-03 15:26:17 UTC

Created attachment 882346 [details]
Here is the change I plan to make

Comment 14 Tim Waugh 2014-04-03 15:34:14 UTC

Created attachment 882360 [details]
Here is the change I plan to make (sorry, missed a bit in the last one)

Comment 18 errata-xmlrpc 2014-10-14 04:38:44 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1412.html

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