Comment # 5 on bug 983900 from Wolfgang Bauer

(In reply to Cristiano Guadagnino from comment #4)
> The problem is that the new krdc uses the KF5 kde wallet subsystem. This
> wallet contained the wrong passwords for my RDP sessions. So the login was
> refused and the session was instantly closed.
> 
> After realizing this I opened kwalletmanager5 and deleted the wrong
> passwords. Now my rdp sessions are working correctly.

Great! So it works for you now at least...

I actually was going to suggest trying to disable the kwallet integration (i.e.
saving the password) as a test next. ;-)

> Previously they were working correctly because they used the old kde wallet
> subsystem, which contained the correct passwords.

Hm, actually kwallet/KF5 should migrate the passwords on first start.
But you probably changed it after first using kwallet/KF5 (plasma-nm5 maybe).

Unfortunately, if migrated once, the kwallets for KDE4 and KF5 are completely
independent and will diverge.
There were some talks about changing kwallet5 to replace kwallet4 completely,
i.e. also offering the service for KDE4 applications to prevent having two
separate wallets, but not much came out of this yet.

And syncing the wallets is not possible either (yet?), nor done automatically.

There's definitely room for improvement there...

OTOH it won't matter much any more when all applications have been ported to
KF5 (which might still take some time though).

> So it was my fault after all, HOWEVER I think it is not correct that a
> failed login in an rdp session simply closes the session without any kind of
> error message.
> 
> What do you think? Should I open a new bug for this erroneous behavior?

I do agree that there should be some error message.

But please report that upstream at http://bugs.kde.org/.

There are similar (I think) bug reports already (though they mention having a
blue screen in case of a wrong password, not just closing the session).

Anyway, I'm closing this as fixed now.
The two other problems you mentioned are indeed fixed (I submitted the
migration fix to Tumbleweed as well, should be in the next snapshot), and the
main one was actually caused by a wrong password (so not really a bug, except
for the missing error message maybe).