[konversation] [Bug 471940] New: Konversation does not send CAP END if no CAP REQ is required

[Thomas Jepp]

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

            Bug ID: 471940
           Summary: Konversation does not send CAP END if no CAP REQ is
                    required
    Classification: Applications
           Product: konversation
           Version: Git
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: protocol
          Assignee: konversation-devel at kde.org
          Reporter: kde at tomjepp.co.uk
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Connect to irc.aachat.net (SSL/6697)
2. Konversation will start connecting, and hang after CAP LS

OBSERVED RESULT
Konversation will start connecting, and hang after CAP LS

EXPECTED RESULT
Konversation continues to get the MOTD and then join channels

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux - 5.27.6
(available in About System)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
This happens because as per
https://ircv3.net/specs/extensions/capability-negotiation.html, servers are
required to wait for CAP END after CAP LS or CAP REQ. Konversation never sends
CAP END.

Merge request will be submitted on Gitlab shortly.

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