Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The "vncserver" script was removed in RHEL8.3. Now the non-root users are not able to manually start the vnc service. Please include the script again to restore the functionality.
Version-Release number of selected component (if applicable):
tigervnc-server-1.10.1-7.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install the tigervnc packages on the RHEL8.3.0 system
2. Login into the system as non-root user and try to run vncserver command
Actual results:
The "vncserver" script is not available.
Expected results:
The "vncserver" script should be available. So that the non-root user can manually start the vnc service
Additional info:
(In reply to Rik Theys from comment #10)
> Hi,
>
> Can we have the fixes also in RHEL/CentOS 8.3 ?
> The package from Stream requires a newer selinux-policy package :-/.
>
> Regards,
> Rik
The dependency on selinux-policy is always set to the version we build tigervnc against. I guess this is not necessary and we can drop the version requirement. I will check.
Hi Jan,
In the mean time, I wanted to rebuild the src.rpm on 8.3 but I can't find it anywhere.
Where can I find the src.rpm for the packages in Stream?
Regards,
Rik
(In reply to Rik Theys from comment #12)
> Hi Jan,
>
> In the mean time, I wanted to rebuild the src.rpm on 8.3 but I can't find it
> anywhere.
>
> Where can I find the src.rpm for the packages in Stream?
>
> Regards,
> Rik
I don't think these are publicly available. Also, I have been in touch with people working on SELinux and I've been told it's actually a good approach to rely on selinux-policy-%{version} we built Tigervnc against.
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 (Moderate: tigervnc security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:1783