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:
Removing tigervnc-server shows the following warning:
Running transaction
Preparing : 1/1
Running scriptlet: tigervnc-server-1.11.0-20.el9.x86_64 1/1
Failed to stop xvnc@.service: Unit name xvnc@.service is missing the instance name.
See system logs and 'systemctl status xvnc@.service' for details.
Erasing : tigervnc-server-1.11.0-20.el9.x86_64 1/1
Running scriptlet: tigervnc-server-1.11.0-20.el9.x86_64 1/1
This is likely caused by
preuninstall scriptlet (using /bin/sh):
if [ $1 -eq 0 ] && [ -x /usr/bin/systemctl ]; then
# Package removal, not upgrade
if [ -d /run/systemd/system ]; then
/usr/bin/systemctl --no-reload disable --now xvnc@.service || :
else
/usr/bin/systemctl --no-reload disable xvnc@.service || :
fi
fi
if [ $1 -eq 0 ] && [ -x /usr/bin/systemctl ]; then
# Package removal, not upgrade
if [ -d /run/systemd/system ]; then
/usr/bin/systemctl --no-reload disable --now xvnc.socket || :
else
/usr/bin/systemctl --no-reload disable xvnc.socket || :
fi
fi
I'm not a systemd expert, but AFAIK the '@' syntax is for starting multiple instances from one defined service, ie. 'xvnc@first' , 'xvnc@second', etc.
Not sure if it makes sense stopping these from preuninstall, but if you want to do so, use a wildcard:
systemctl stop 'xvnc@*.service'
systemctl disable xvnc@.service
Version-Release number of selected component (if applicable):
tigervnc-server-1.11.0-20.el9
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 (tigervnc 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/RHBA-2022:7986
Description of problem: Removing tigervnc-server shows the following warning: Running transaction Preparing : 1/1 Running scriptlet: tigervnc-server-1.11.0-20.el9.x86_64 1/1 Failed to stop xvnc@.service: Unit name xvnc@.service is missing the instance name. See system logs and 'systemctl status xvnc@.service' for details. Erasing : tigervnc-server-1.11.0-20.el9.x86_64 1/1 Running scriptlet: tigervnc-server-1.11.0-20.el9.x86_64 1/1 This is likely caused by preuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ] && [ -x /usr/bin/systemctl ]; then # Package removal, not upgrade if [ -d /run/systemd/system ]; then /usr/bin/systemctl --no-reload disable --now xvnc@.service || : else /usr/bin/systemctl --no-reload disable xvnc@.service || : fi fi if [ $1 -eq 0 ] && [ -x /usr/bin/systemctl ]; then # Package removal, not upgrade if [ -d /run/systemd/system ]; then /usr/bin/systemctl --no-reload disable --now xvnc.socket || : else /usr/bin/systemctl --no-reload disable xvnc.socket || : fi fi I'm not a systemd expert, but AFAIK the '@' syntax is for starting multiple instances from one defined service, ie. 'xvnc@first' , 'xvnc@second', etc. Not sure if it makes sense stopping these from preuninstall, but if you want to do so, use a wildcard: systemctl stop 'xvnc@*.service' systemctl disable xvnc@.service Version-Release number of selected component (if applicable): tigervnc-server-1.11.0-20.el9