Bug 519197 - krfb does not save unattended password
Summary: krfb does not save unattended password
Status: RESOLVED DUPLICATE of bug 458191
Alias: None
Product: krfb
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.2
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: George Goldberg
URL:
Keywords:
Depends on:
Blocks: 520505
  Show dependency treegraph
 
Reported: 2026-04-21 03:18 UTC by hal
Modified: 2026-06-23 21:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hal 2026-04-21 03:18:35 UTC
STEPS TO REPRODUCE
1.  Run krfb
2. Change unattended password
3. Try to save - oh, wait - there's NO SAVE BUTTON
4. Check ~/.config/krfbrc and see that it didn't bother to save your password

I'm ranking this as major. Without this, it is, in real life, impossible to use krfb for remote access. Every time it starts or every time KDE restarts, the password is changed. So you have to have someone at the computer when krfb is started so set it for that session. The whole purpose of krfb is remote access, but that is lost when someone has to be there to enter a new password every time krfb is run or KDE starts. If my system reboots at work, I cannot access it remotely until I go into work (or have someone else go) and set the password, since it's not saved.

OBSERVED RESULT
The unattended password is not saved

EXPECTED RESULT
The unattended password should be saved in ~/.config/krfbrc

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Trixie
KDE Plasma Version:  6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 TraceyC 2026-06-23 21:38:17 UTC
I can reproduce this on Plasma & krfb built from git-master
Comment 2 TraceyC 2026-06-23 21:53:44 UTC
I found an older bug for this, so I'm merging this into that report. You can follow the older report for updates. Thanks!

*** This bug has been marked as a duplicate of bug 458191 ***