@Razvan, I’ve the same on 6.4. Does that mean that the previous MRs did not achieve what they purport to, or was this problem misidentified as another?
In retrospect, this can occur when the unattended and attended passwords are the same. Thereafter, if one differentiates them, they must disable password remembrance, or modify the stored password via KWalletManager.
This isn’t intuitive, and the ease of accidentally preventing unattended connection is undoubtedly a bug. If anyone knows of a report about this, please post a URI to it.
Environment
krfb-25.04.3-1.fc42.x86_64
1 Like
On 25.04 with X I can connect to krfb without any confirmation, but I remember doing a test a month ago, switched to wayland and krfb asked me for confirmation.
I use X on 25.04 with tigervncserver for now, till things get more usable and stable with wayland and krfb.
2 Likes
Here’s the same problem on Arch with KDE. I can’t access my PC if I don’t give a permission and I can’t give a permission because I don’t have access. Catch 22?
2 years and this bug isn’t solved and ut’s very important. it’s the only thing keeps me from migrating to wayland. I want to access my PC via VNC remotely and unattended. Please fix this bug.
1 Like
Ideally someone would of course fix the bug in krfb, but as a workaround you can also go to system settings > application permissions and permanently grant the permission there. Same for any other application that doesn’t handle this properly yet.
3 Likes
1 Like
I fixed the grayed out menu but the message is always here if you start Krfb with krfb --nodialog no matter the permissions settings. So we desperately need a fix for this bug.
1 Like