Red Hat Bugzilla – Bug 86158
ignoring keyboard and mouse inputs
Last modified: 2013-04-30 19:33:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux)
Description of problem:
the vnc server suddenly starts ignoring all mouse/keyboard inputs. this has happened across multiple machines (all running RH8) and with many different vnc clients. after reconnecting it continues to ignore inputs. it happens when 1 or more clients are connected, but we haven't seen it without a client connected. it also only seems to happen when a client is actually active i.e somebody is moving the mouse or typing.
we also run RH 7.3/7.1 and have not seen this bug.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Please attach the log file that the server creates (in ~/.vnc).
Created attachment 90640 [details]
vnc log after server goes into yuck mode
here is the log after the server goes into the no-input mode.
We've noticed we can recover the session by killing the application in the
foreground. As soon as that application is dead, mouse/kbd input is accepted
Also seen in RH9 on a completely up2date machine. Killing the application in
the foreground (evolution) seemed to bring everything back again.
Well here's an update.
We switched to KDE on our Redhat 8 box and never had it happen again (only in
However, recently we did have exactly the same symptoms occur on a RHEL3 WS U4
completely up2date box running KDE, so I guess this bug is still around :(?
The recent 4.1 release of VNC has some changes to
xc/programs/Xserver/vnc/XserverDesktop.cc which look like they might be aimed at
this problem: specifically, the addition of a XserverDesktop::deferUpdate function.
Please, test if this problem is in latest release of vnc
Hi. We've seen it with the latest release of VNC on RHEL 4 WS i386 (running KDE
in the VNC). It happens pretty infrequently now (once every six months or so).
It happened twice in the last two weeks, so I'd like to re-open the bug.
Comment #7 confuses me. Is this bug still for RHEL3 or RHEL4?
We upgraded to RHEL4 from RHEL3 and continue to see the bug. We've seen it in
every release since good old RH8.
(In reply to comment #7)
Moving to RHEL 4
I've tried backport patch for this issue to rhel4. Could you please test
proposed update package and tell me your impressions?
I'll take a look, but unfortunately we mostly see this bug in production where I
can't easily update the VNC. I'll give it a try on a non-production box though.
Created attachment 158509 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.