Bug 442122 - Connection registration gets stuck when server supports no capabilities
Summary: Connection registration gets stuck when server supports no capabilities
Status: REPORTED
Alias: None
Product: konversation
Classification: Applications
Component: protocol (show other bugs)
Version: 1.8.21081
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-07 11:42 UTC by Alois Wohlschlager
Modified: 2021-09-07 11:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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