[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#686274: krdc: incorrect state of meta (Alt) key in remote desktop



Package: krdc
Version: 4:4.8.4-1
Severity: normal

Dear Maintainer,

When using krdc to connect to remote Windows desktop, sometimes
connected session treats the state of my meta (Alt) key as 'pressed'. It
results for example in displaying properties of object instead selecting
it after click/double click.

It's quite simple to reproduce - I just need to switch windows in my
Linux session few times with Alt-Tab, ending with krdc as active window.
It works in both full screen and windowed mode.

The workaround is also simple - I just need to press and release Alt key
with focus inside krdc session, after that Windows can see that Alt is
actually not pressed.

It doest not happen when using directly rdesktop to connect, so I
believe it's bug in krdc.

I observed this behavior few months ago, hoping to be something
temporary that will disappear with next upgrade, but it's still there.

I'm using default KDE from current unstable, without any customizations
of fancy settings.

Best regards
Pawel

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages krdc depends on:
ii  kde-runtime        4:4.8.4-1
ii  libc6              2.13-35
ii  libkcmutils4       4:4.8.4-3
ii  libkdecore5        4:4.8.4-3
ii  libkdeui5          4:4.8.4-3
ii  libkdnssd4         4:4.8.4-3
ii  libkio5            4:4.8.4-3
ii  libknotifyconfig4  4:4.8.4-3
ii  libqt4-xml         4:4.8.2+dfsg-1
ii  libqtcore4         4:4.8.2+dfsg-1
ii  libqtgui4          4:4.8.2+dfsg-1
ii  libstdc++6         4.7.1-7
ii  libvncserver0      0.9.9+dfsg-1

Versions of packages krdc recommends:
ii  rdesktop  1.7.1-1

Versions of packages krdc suggests:
pn  khelpcenter4  <none>
pn  krfb          <none>

-- no debconf information


Reply to: