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.

This bug was initially created as a copy of Bug #2062908

I am copying this bug because: 

to be in par between 8.7 and 9.1


Since TigerVNC moved to systemd-based operation with the 1.10 release, it has had configuration files that aren't collected by sos. This means more time spent collecting TigerVNC-specific configuration files.

As such, we'd like to request that sos collect all files under /etc/tigervnc, which contains the new configuration files we need. No passwords are shared in these files (they live in users' home directories).

Also, we like to ask that the status of tigervnc services be tracked. They can be found with "systemctl --list-units" under the designation tigervnc@:$VNCDISPLAY.service, where $VNCDISPLAY is a number starting at 1 stating the TigerVNC display number.

Hello,
as our QE might not have available systems for testing the fix, would you be able to verify the fix once available (as a candidate package for 9.1)?

Sorry for the delay. Yes, I can help test.

Thanks for committing to testing. I will ask you to verify once we have a candidate build with the fix ready (see ITM and DTM for estimations/plans).

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

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 (sos 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/RHEA-2022:8275