Bug 40650 - vncviewer -fullscreen does not kbd input under KDE
Summary: vncviewer -fullscreen does not kbd input under KDE
Keywords:
Status: CLOSED DUPLICATE of bug 63853
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-15 06:00 UTC by Aleksey Nogin
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-06-29 18:08:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Aleksey Nogin 2001-05-15 06:00:53 UTC
Description of Problem:

When I run "vnc -fullscreen" from under KDE, the VNC would not get keyboard
input (mouse still works fine).

How Reproducible:
 - Under KDE - always. In particular, all four possible settings of window
focus behaviour produce the same result.
 - Under Gnome this problem does not occur.
 - If I first start vncviewer in a window and than go to fullscreen mode
using the menu (through F8), the problem does not occur.

Steps to Reproduce:
1. Start a KDE session
2. Start a VNC session
3. Start a vncviwer -fullscreen under your KDE session

Actual Results:

All keyboard input goes to the window that used to have focus before
vncviewer was started, even though the mouse works fine.

Expected Results:

Both mouse and keyboard events go to vncviwer

Additional Information:
  In case it matters, I am running XFree v4 with a XkbLayout "ru"
(actually, a modification of "ru").

Comment 1 Tim Waugh 2001-05-15 10:54:56 UTC
I see this too, about 50% of the time.  At first glance, this looks like a 
kwin bug.


Comment 2 Aleksey Nogin 2002-01-03 17:51:39 UTC
I still see this with 7.2, 100% of the time. Pretty annoying...

Comment 3 Aleksey Nogin 2002-06-29 18:08:47 UTC
Dup of bug 63853?

Comment 4 Tim Waugh 2002-07-03 15:16:50 UTC
I think so. 

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


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