Bug 442122

Summary: Connection registration gets stuck when server supports no capabilities
Product: [Applications] konversation Reporter: Alois Wohlschlager <alois1>
Component: protocolAssignee: Konversation Developers <konversation-devel>
Status: REPORTED ---    
Severity: normal    
Priority: NOR    
Version: 1.8.21081   
Target Milestone: ---   
Platform: Flatpak   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alois Wohlschlager 2021-09-07 11:42:59 UTC 
SUMMARY

When connecting to a server which supports capability negotiation but no capabilities, Konversation never resumes the connection registration process, so the connection gets stuck.

STEPS TO REPRODUCE
1. Write an IRC server which sends "CAP * LS :" as response to "CAP LS 302"
2. Connect to that server

OBSERVED RESULT

Konversation sends NICK, USER, then connection registration gets stuck.

EXPECTED RESULT

Konversation sends NICK, USER and then CAP END to resume (and finish) connection registration with the server.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: n/a
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3