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.
Bug 1342871 - After updating to RHEL6.8, it came to log out forcibly from the desktop on VNC.
Summary: After updating to RHEL6.8, it came to log out forcibly from the desktop on VNC.
Keywords:
Status: CLOSED DUPLICATE of bug 1218851
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gdm
Version: 6.8
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1269194 1363705
TreeView+ depends on / blocked
 
Reported: 2016-06-06 03:18 UTC by kyoneyama
Modified: 2020-04-15 14:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-01 14:39:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description kyoneyama 2016-06-06 03:18:49 UTC
Description of problem:

The customer was set up VNC screens via xinetd to reference the following knowledge.

  https://access.redhat.com/solutions/2516.

After updating from RHEL6.7 to 6.8, it came to log out forcibly from the desktop on VNC.


Version-Release number of selected component (if applicable):

- Red Hat Enterprise Linux 6.8
- tigervnc-server
- gdm
- Desktop Environment(GNOME/KDE)


How reproducible:

- Always

Steps to Reproduce:

1. install packages

  # yum install xinetd tigervnc-server

2. create a user for VNC

  # useradd vncuser
  # sudo -u vncuser vncpasswd 

3. Edit a configuration file

  -- /etc/sysconfig/desktop --
  DESKTOP=GDM

  -- /etc/xinetd.d/vnc-personal --
  service xvnc
  {
  	disable = no
  	protocol = tcp
  	socket_type = stream
  	type = UNLISTED
  	port = 5904
  	wait = yes
  	user = vncuser
  	flags = IPv4
  	server = /usr/bin/Xvnc
  	server_args = -inetd -query localhost -once -geometry 800x600 -depth 24 -PasswordFile /home/vncuser/.vnc/passwd
  	log_on_failure += USERID
  	cps = 50 10
  	instances = 50
  	per_source - 10
  }

4. activate desktop and xinetd service 

  # init 5
  # service xinetd start
  # chkconfig vnc-personal on


  For details, please refer to https://access.redhat.com/solutions/2516.


5. Connect port#5904 with VNC client from other host.

6. On VNC screen, log in to desktop as user and wait for a while.


Actual results:

log out forcibly from the desktop when the wait a little.

Expected results:

continue to log in.


Additional info:

- It occurs regardless of the kind of desktop such as GNOME and KDE.
- gdm seems to finish without permission.

Comment 5 Dan Astoorian 2016-08-31 14:02:04 UTC
This is probably the same issue as bug 1344137, and appears to be related to keepalive packets.  Note that downgrading to tigervnc-server 1.1.0-16.el6 (which was complied against the older xorg-x11-server-source 1.15.0-12.el6 package; note that the keepalive code was updated in xorg-x11-server-source 1.17.4-5.el6) works around the problem.

It looks to me as though the underlying problem might be that the SessionRunning flag in the keepalive packets is being set to 0 instead of 1; it might be the case that the older xorg-x11-server-source package didn't trigger the bug because it was not processing the keepalives correctly.


Note You need to log in before you can comment on or make changes to this bug.