https://bugs.kde.org/show_bug.cgi?id=480235
--- Comment #25 from Prajna Sariputra <[email protected]> --- I gave Lamco RDP Server a try myself, and while it is true that it keeps asking for permissions when the server is started, I noticed that initially 3 permission dialogs pop up, but after approving all 3 dialogs and restarting the server I see only 2 dialogs plus one notification saying a permission (control input devices) was automatically granted, so one of the permissions does get remembered. The Application Permissions page of System Settings also shows that the only remembered session is the one for controlling input devices, and revoking that session makes Lamco ask for 3 separate permissions dialogs again. Looking at what KDE Wallet stores in its Secret Service storage (had to use GNOME's Seahorse app to check that since KWalletManager seems to no longer be able to see Secret Service stuff?) I only see one token from Lamco labelled "lamco-rdp-session-libei-default". Libei is the input emulation library, so I suspect what is happening here is that Lamco only stores the token for the control input devices portal request, and not the other two requests. The fact that it asks for the "control input devices" permission twice (once by itself as the first dialog, once alongside the "see what's on the screen" permission) makes me think the problem is caused by the app rather than by the KDE portal, it should not be necessary to ask for the same permission repeatedly like that. The fact that the app asks for both a screen to share and the "see what's on the screen" permission is also suspicious to me, it should only ask for one of those and not both. For the third dialog (the one with both "see what's on the screen" and "control input devices" permissions) I also noticed that the "Allow restoring on future sessions" checkbox is missing entirely, so the app does not even ask for persistence for that dialog. That dialog certainly supports persistence from the KDE side, Krfb 25.12.3 asks for the same two permissions in one go and persistence works there. So, I would suggest reporting the issue to Lamco if you haven't already. I would also suggest filing a separate bug report if Lamco says it's a KDE bug since this one is for the persistence not working across reboots rather than not working at all. For reference I'm on Arch Linux with KDE Plasma 6.3.3 and Lamco 1.4.2 installed from AUR. -- You are receiving this mail because: You are watching all bug changes.
