Bug 340411

Confirmed in Kubuntu 14.10 (utopic) with krfb 4.14.2

*** Bug 341211 has been marked as a duplicate of this bug. ***

*** Bug 342377 has been marked as a duplicate of this bug. ***

Confirmed. This is problematic for me because I leave Krfb running in the background when I'm away from home, so I can access my PC from my laptop or smartphone. In case the power goes out, my system is configured to automatically log back in and Krfb is set to auto-start. But because of this issue it starts disabled, so I can no longer connect to my machine until I return home to fix it manually.

I confirm this bug. Very annoying :-(

I can confirm the case also persists in Krfb 4.14.7.  After a system reboot the "Enable Desktop Sharing" box needs to be checked again before remote access is possible.  All other settings appear to remain across reboots.

Also confirmed on OpenSUSE 13.2 with KRFB & KDE 4.14.2.

Also confirmed on Kubuntu 15.04 with KDE 5.2.2

*** This bug has been confirmed by popular vote. ***

Also confirmed on Kubuntu 15.10 (krfb 4:15.08.2-0ubuntu1 under KDE 15.08.2 with KDE Frameworks 5.15.0).
Could the KDE team consider reverting to krfb version 4.13.3 with the next KDE Applications Release?
The current version allows only very restricted use cases since settings are never saved.

Same problem occured under Debian 8.3 stable and KDE 4.14.2

This is still a bug on:
KDE Neon Latest
Plasma Version: 5.10.4
KDE Frameworks Version: 5.37.0
Kernel Version 4.10.0-32-generic

(In reply to Michael Earle from comment #12)
> This is still a bug on:
> KDE Neon Latest
> Plasma Version: 5.10.4
> KDE Frameworks Version: 5.37.0
> Kernel Version 4.10.0-32-generic

And krfb version is? Both from "About.." window and from package manager?

This seems to be solved in Kubuntu 17.10 (krfb 4:17.04.3-0ubuntu1 under KDE 17.04.3 with KDE Frameworks 5.38.0); now the check box "Enable Unattended Access" is saved.

It seems that this change fixed the issue:
https://cgit.kde.org/krfb.git/commit/?id=c83182f8d330dae70cd881a283a0fdbe24a029c5
This is why I added shadeslayer in the CC list, I think that he is the author of the commit.

I don't use krfb anymore, I use only one computer currently.
Can someone check if the issue is resolved in krfb 4:17.04.3-0ubuntu1?

The issue is solved and tested in Kubuntu 17.10 (artful) with krfb (4:17.04.3-0ubuntu1).

How to use unattended access:
- tick the option "Enable desktop sharing"
- set a password for desktop sharing
- tick the option "Enable Unattended Access"
- set the same password for unattended access

All settings will persist over KDE sessions; this way unattended access makes sense again.
In case the passwords cannot be changed in krfb change them in kwallet instead (happened to me).

This bug is back on KDE with Debian Buster. 
Clean install. 
I am not able to save the settings/password for "Unattended Access".
Putting "noWallet=true" in ~/.config/krfbrc does not help.  
After a reboot the setting is lost. 
This basically breaks a big portion of the functionality of this tool and either this should be fixed or krfb finally been removed after years of neglience.

I just updated my two PCs from Kubuntu 19.10 (eoan) to Kubuntu 20.04 (focal).
I tested krfb both before and after the update (4:19.04.3-0ubuntu2 and 4:19.12.3-1 respectively) and unattended access works as expected.

Regarding the previous comment: my test is not based on a clean install and buster uses an older version: 4:17.08.3-1. Version 4:17.08.3-1 is between two versions which are confirmed to work: 4:17.04.3-0ubuntu1 in Kubuntu 17.10 (artful) and 4:19.04.3-0ubuntu2 in Kubuntu 19.10 (eoan). So it is surprising to see a regression there. 

Is anyone else experiencing the same issue again in recent versions of krfb?

I was also able to replicate this with Ubuntu 20.04 LTS. 

I notice that if i start the krfb from Applications -> Internet -> krfb and go to Settings -> Security  and set the checkmark on "Do not store passwords using KDE wallet" and then close the bought windows. Then i notice that those settings are note saved into the ~/.config/krfbrc . The i decided to delete the "~/.config/krfbrc" file and start all over again, however this time instead of clicking on close i did File -> Quite. And then i saw that the "~/.config/krfbrc"  had my changes.  That's how i manage to get  krfb do what i need i.e. the file now looks like this [MainWindow]
######################################################################
State=AAAA/wAAAAD9AAAAAAAAAoAAAAGrAAAABAAAAAQAAAAIAAAACPwAAAAA
ToolBarsMovable=Disabled

[Security]
allowUnattendedAccess=true
desktopPassword=ﾴﾰﾱﾬﾫﾾﾱﾫ
noWallet=true
unattendedPassword=ﾴﾰﾱﾬﾫﾾﾱﾫ
##############################################################################


I am curios what those saved passwords are in a blowfish format or something else? And if one can disable those since i am suing this anyway with ssh port forwarding and do not need passwords.  
Anyway  it seems that there is some discrepancy between the GUI events responsible for saving the file.  

After that i had to add the krfb to the autostart and it all worked.

This does not fix the issue for me... I keep getting this issue:
https://bugs.kde.org/show_bug.cgi?id=288481

(In reply to Konstantin Hristov from comment #18)
> I am curios what those saved passwords are in a blowfish format or something
> else? And if one can disable those since i am suing this anyway with ssh
> port forwarding and do not need passwords.

It is using KStringHandler::obscure() from KCoreAddons ( https://api.kde.org/frameworks/kcoreaddons/html/namespaceKStringHandler.html#afa464f27b952f544619fd2059eab80b0 ).

No, there is no option to disable this.

> Anyway  it seems that there is some discrepancy between the GUI events
> responsible for saving the file.

I have never seen this bug personally, but I have a suspicion how this can happen. You *may* be right...

Git commit bc755b81d849198b034b4cdeec27711cb7d576e9 by Alexey Min.
Committed on 26/08/2020 at 12:55.
Pushed by alexeymin into branch 'fix_storing_config'.

Make sure to save security settings each time they are modified

Settings that are modified using normal settings window, which is
invoked using menu "Configure Desktop Sharing..." are always saved
correctly.

However some settings that are present on Krfb main window
(normal password, unattended password, checkbox "enable unattended
access") are not handled by KConfigDialog and there is a chance that
settings might not be saved correctly (for example if application
was suddenly terminated).

This hopefully fixes some bugs which are present since year 2011-2014
and have 110 votes, like https://bugs.kde.org/show_bug.cgi?id=340411,
maybe something else.
Related: bug 288481
CHANGELOG: Make sure to save passwords each time they are modified

M  +46   -21   krfb/invitationsrfbserver.cpp
M  +1    -0    krfb/invitationsrfbserver.h

https://invent.kde.org/network/krfb/commit/bc755b81d849198b034b4cdeec27711cb7d576e9

(this is not merged yet!)

Git commit fd362fd642491ee9b4ad42346776b2d4ec089b22 by Alexey Min.
Committed on 05/10/2020 at 05:07.
Pushed by alexeymin into branch 'release/20.08'.

Make sure to save security settings each time they are modified

Settings that are modified using normal settings window, which is
invoked using menu "Configure Desktop Sharing..." are always saved
correctly.

However some settings that are present on Krfb main window
(normal password, unattended password, checkbox "enable unattended
access") are not handled by KConfigDialog and there is a chance that
settings might not be saved correctly (for example if application
was suddenly terminated).

This hopefully fixes some bugs which are present since year 2011-2014
and have 110 votes, like https://bugs.kde.org/show_bug.cgi?id=340411,
maybe something else.
FIXED-IN: 20.08.2
CHANGELOG: Make sure to save passwords each time they are modified

M  +46   -24   krfb/invitationsrfbserver.cpp
M  +1    -0    krfb/invitationsrfbserver.h

https://invent.kde.org/network/krfb/commit/fd362fd642491ee9b4ad42346776b2d4ec089b22

*** Bug 288481 has been marked as a duplicate of this bug. ***

When updating from Kubuntu 23.04 (lunar, 4:22.12.3-0ubuntu1) to Kubuntu 23.10 (mantic, 4:23.08.1-0ubuntu1) I observe a regression.
With each start krfb needs local interaction to grant access to the screen and input devices, even if "Enable Unattended Access" is ticked.
Another way to put it is that "Enable Unattended Access" stays ticked but does effectively nothing (it does not enable unattended access).
This is a problem for remote machines without physical access.

Please submit a new bug report to report a new problem. Thanks!