Description of problem: Recently received updates with krfb-4.14.1-1.fc20.x86_64 and krfb-libs-4.14.1-1.fc20.x86_64 After taking this update krfb stopped working (obviously I use KDE). Upon investigation I noticed that the TCP listener port for krfb (usually 5900) was not open. Also every time that krfb starts a pop up that seems to be part of kwallet shows up. It wants me to define a wallet etc... (I actually have kwallet disabled.) Nothing I have done (incuding enabling kwallet) seems to make it happy such that it does not appear the next time krfb is started. This was not happening with krfb-libs-4.13.3-4.fc20.x86_64 and krfb-4.13.3-4.fc20.x86_64. krfb-libs.x86_64 4.11.3-1.fc20 @fedora krfb.x86_64 4.11.3-1.fc20 @fedora Version-Release number of selected component (if applicable): krfb-4.14.1-1.fc20.x86_64 and krfb-libs-4.14.1-1.fc20.x86_64 How reproducible: 100% on multiple machines. Steps to Reproduce: 1. update to krfb-4.14.1-1.fc20 2. start krfb (either with or without --nodialog) 3. try to connect to the vnc that krfb should have created. Actual results: connection refused. Expected results: that it would still work. Additional info: I did various bugzilla searches and did not get any hits. That included searching on the kde bugzilla list. I did not enter a bug on the kde bug system. I was able to get around this by yum downgrade krfb and ended up at krfb-4.14.1-1.fc20.x86_64 krfb-libs-4.14.1-1.fc20.x86_64. I expect that krfb-libs-4.13.3-4.fc20.x86_64 and krfb-4.13.3-4.fc20.x86_64 would also have worked. The actual command I used was "yum downgrade krfb krfb-libs kdenetwork kdenetwork-common".
If I were to venture a guess, krfb now supports saving passwords in kwallet, and doesn't gracefully handle the case when kwallet is disabled or non-functional. I'll try testing more myself soon, and file a bug upstream if fruitful.
https://projects.kde.org/projects/kde/kdenetwork/krfb/repository/revisions/c558eaf9b68114f47a7d6fe0dd392212e6e6dce1 confirmed, looks like the "Fall back to config file if KWallet not available" part isn't working as intended
Mind moving this bug to http://bugs.kde.org/ ? It's best if you do it, in case the developers need any feedback from you.
i entered a bug on bugs.kde.org. https://bugs.kde.org/show_bug.cgi?id=339528
Thanks!
This issue seems to have zero activity on the kde list. I just verified it still exists with latest and greatest krfb package (4.14.3-1.fc21) in fedora 21. I am surprised this is not bothering anyone else. I do not use kwallet because it issues popup asking for password on every boot which is a big pain.
I guess until this is fixed (upstream), you get to pick which is less pain: * living with this bug * re-enabling kwallet, and entering your password (at least once per session where you use krfb)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
this is still an issue in fedora 21. it may be an issue in fedora22/kde 5 as well but I have enough other serious issues with kde5 that i have not verified this yet.
Let's just continue tracking this upstream @ https://bugs.kde.org/show_bug.cgi?id=339528 No need to keep this downstream report open (is there?)