[konversation] [Bug 400362] New: Add a note stating that identifying with nickserv may result in failures when auto-joining

Luca Carlon bugzilla_noreply at kde.org
Sat Oct 27 12:57:47 BST 2018


https://bugs.kde.org/show_bug.cgi?id=400362

            Bug ID: 400362
           Summary: Add a note stating that identifying with nickserv may
                    result in failures when auto-joining
           Product: konversation
           Version: 1.7.5
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: konversation-devel at kde.org
          Reporter: carlon.luca at gmail.com
  Target Milestone: ---

SUMMARY
I read some reports about the race condition that occurs when nickserv is used
for identification and join requests are sent before identification succeeds:
#397576, #382924... I also read that this is somehow the "intended" behavior.
Why not adding a red note in the "Identities" dialog, shown when "nickserv" is
selected, stating that this type of identification may make it impossible to
auto-join properly? Also, maybe, why not suggesting to use SASL, which seems to
work perfectly? This little text may spare hours of time to a user not
experienced with the IRC protocol like me.

STEPS TO REPRODUCE
1. In the identities dialog, select "Standard NickServ".
2. Join a channel and set auto-join.
3. Restart konversation.

OBSERVED RESULT
When channels require identification, join may fail.

EXPECTED RESULT
I'm suggesting to simply add a little static test, to be shown when "Standard
NickServ" is selected, stating that auto-join may not work reliably in this
configuration. This may prevent duplicated bugreports and waste of time looking
for the proper reason/solution, which seems to be considerably simple.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Konversation-devel mailing list