Bug#951645: krdc: connect is sometimes unsuccessful and hang on login screen of remote computer
Package: krdc
Version: 4:18.04.1-1
Severity: important
Dear Maintainer,
In certain cases, connecting to remote W2008r2 or W2012r2 computers,
where the user has already been logged in, the krdc will hang on the
login screen, with nothing happening. The only solution is to log to
another computer, user native windows rdp to connect to the server with
the problem, logout the user and krdc will connect. Another solution is
to use rdesktop which has no problems. No obvious error or warning is
logged on the server side.
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages krdc depends on:
ii libc6 2.28-10
ii libkf5bookmarks5 5.54.0-1
ii libkf5completion5 5.54.0-1
ii libkf5configcore5 5.54.0-1+deb10u1
ii libkf5configgui5 5.54.0-1+deb10u1
ii libkf5configwidgets5 5.54.0-1
ii libkf5coreaddons5 5.54.0-1
ii libkf5dnssd5 5.54.0-1
ii libkf5i18n5 5.54.0-1
ii libkf5kcmutils5 5.54.0-1
ii libkf5notifications5 5.54.0-1
ii libkf5notifyconfig5 5.54.0-1
ii libkf5service-bin 5.54.0-1
ii libkf5service5 5.54.0-1
ii libkf5wallet-bin 5.54.0-1
ii libkf5wallet5 5.54.0-1
ii libkf5widgetsaddons5 5.54.0-1
ii libkf5xmlgui5 5.54.0-1
ii libqt5core5a 5.11.3+dfsg1-1+deb10u3
ii libqt5gui5 5.11.3+dfsg1-1+deb10u3
ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3
ii libqt5xml5 5.11.3+dfsg1-1+deb10u3
ii libstdc++6 8.3.0-6
ii libvncclient1 0.9.11+dfsg-1.3+deb10u2
Versions of packages krdc recommends:
ii freerdp2-x11 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u1
Versions of packages krdc suggests:
ii khelpcenter 4:18.04.0-1
pn krfb <none>
-- no debconf information
Reply to: