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 example of the tigervnc server's service cannot get session id for the session , which leads to lacking of some menus and improper visualization.

Version-Release number of selected component (if applicable):
tigervnc-server-1.8.0-2.el7_4.x86_64
tigervnc-server-minimal-1.8.0-2.el7_4.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Copy sample service to "/etc/systemd/system":
# cp /usr/lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@:1.service
2.Replace the "<USER>" with your user
3.Login as that user and create a password via "vncpasswd"
4.Start your systemd.service

Actual results:
Improper visualization and missing menus.
Error message is generated as follows:
gnome-session-binary[PID_NUMBER]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.

Expected results:
Successful start of the service.

Additional info:
Adding "PAMName=login" in the "[service]" stanza of the systemd service file solves the issue.

The description should be read as:
The tigervnc service (as per the example in "/usr/lib/systemd/system") leads to improper visualization and missing menus,while the vnc server not being able to obtain the session id.

*** This bug has been marked as a duplicate of bug 1506273 ***