SUMMARY I am subscribed to some channels on Freenode that require a registered nick or have been modified within the past few months to do so. They no longer come up when I start Konversation. STEPS TO REPRODUCE 1. Register a nick with Freenode. 2. Join the channels #lojban, #ckule, #tahoe-lafs, and #android-dev. 3. Set up the server list to automatically join these channels on startup. 4. Exit Konversation. 5. Restart Konversation. OBSERVED RESULT #lojban, #ckule, and #tahoe-lafs are missing, and #android-dev is replaced with #android-unregistered. The startup messages in freenode look like this: [06:10] [Notice] -NickServ- This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify <password>. [06:10] [Notice] -freenode-connect- Due to the persistent ongoing spam, all new connections are being set +R (block messages from unidentified users) and will be scanned for vulnerabilities. This will not harm your computer, and vulnerable hosts will be notified. [06:10] [CTCP] Received Version request from freenode-connect. [06:10] [Channel] Cannot join channel (+r) - you need to be identified with services - see https://freenode.net/kb/answer/registration [06:10] [Channel] Cannot join channel (+r) - you need to be identified with services - see https://freenode.net/kb/answer/registration [06:10] [Channel] Cannot join channel (+r) - you need to be identified with services - see https://freenode.net/kb/answer/registration [06:10] [470] phma #android-dev #android-unregistered Forwarding to another channel [06:10] [Notice] -NickServ- You are now identified for phma. EXPECTED RESULT "You are now identified" should appear immediately after "This nickname is registered", and tabs for all subscribed channels in Freenode should appear to the right of the freenode tab. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 4:5.12.6 KDE Frameworks Version: Qt Version: 5.9.5
Same as https://bugs.kde.org/show_bug.cgi?id=258415 and https://bugs.kde.org/show_bug.cgi?id=132608 and many more. The solution is to use SASL (https://freenode.net/kb/answer/sasl and https://userbase.kde.org/Konversation/Configuring_SASL_authentication), everything else is a workaround. *** This bug has been marked as a duplicate of bug 397576 ***