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.
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.
https://access.redhat.com/errata/RHSA-2017:2000
Created attachment 1181888 [details] workaround Description of problem: vncviewer creates a shared memory segment for MIT-SHM. It is not removed when vncviewer is killed by signal. Version-Release number of selected component (if applicable): tigervnc-1.3.1-4.el7_2.x86_64 How reproducible: Always Steps to Reproduce: 1. Check initial shared memory information. $ ipcs -m ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x011456ac 0 root 600 1000 6 0x00000000 229377 user1 600 524288 2 dest 0x00000000 262146 user1 600 4194304 2 dest 0x00000000 360451 user1 600 4194304 2 dest 0x00000000 458758 user1 600 4194304 2 dest 2. Run vncviewer. -display to local Xorg(using MIT-SHM). $ vncviewer -display :0.0 192.168.0.100:5900 3. Check shared memory information. shmid 753668 is created and attached. $ ipcs -m ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x011456ac 0 root 600 1000 6 0x00000000 229377 user1 600 524288 2 dest 0x00000000 262146 user1 600 4194304 2 dest 0x00000000 360451 user1 600 4194304 2 dest 0x00000000 753668 user1 777 5242880 2 0x00000000 458758 user1 600 4194304 2 dest 4. Kill the vncviewer by SIGTERM (or SIGINT). $ killall vncviewer Actual results: shmid 753668 still exists. $ ipcs -m ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x011456ac 0 root 600 1000 6 0x00000000 229377 user1 600 524288 2 dest 0x00000000 262146 user1 600 4194304 2 dest 0x00000000 360451 user1 600 4194304 2 dest 0x00000000 753668 user1 777 5242880 0 0x00000000 458758 user1 600 4194304 2 dest Expected results: shmid 753668 should be removed. $ ipcs -m ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x011456ac 0 root 600 1000 6 0x00000000 229377 user1 600 524288 2 dest 0x00000000 262146 user1 600 4194304 2 dest 0x00000000 360451 user1 600 4194304 2 dest 0x00000000 458758 user1 600 4194304 2 dest Additional info: PlatformPixelBuffer destructor is never called after CleanupSignalHandler(). Workaround: Mark the shared memory as "destroyed" as soon as possible. It will be invisible soon after the vncviewer is killed. See attachment.