Bug 507512 - Users with certain privilege levels on an inspircd-3 server do not appear in user nickname list
Summary: Users with certain privilege levels on an inspircd-3 server do not appear in ...
Status: REPORTED
Alias: None
Product: konversation
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.10.25043
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-26 14:14 UTC by zwjghstdvg
Modified: 2025-07-26 14:19 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 zwjghstdvg 2025-07-26 14:14:19 UTC 
SUMMARY
On a certain private IRC network I use, the channel admin and the channel bot (both are IRCops/owners) do not appear in the list of usernames. They appear in the message list when they speak just like normal, but never show up in the userlist and their names cannot be tab completed. On other IRC clients such as hexchat and KVIrc they correctly appear in the list.

The server in question is running Inspircd-3 according to the motd, though I don't see any more specific versioning (I know the server admin and if it's needed I can find out). And I'm told the server uses ircv3.

STEPS TO REPRODUCE
1. Use Konversation to connect to a relevant server
2. See that no ircops appear in the userlist

OBSERVED RESULT
IRCop users do not appear in the userlist.

EXPECTED RESULT
IRCop users should appear in the userlist.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 42 Workstation, KDE Spin, Kinoite
KDE Plasma Version: 6.4.3, also observed on earlier versions.
KDE Frameworks Version: 6.16 (I think, whatever is current on Fedora)
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Tested on multiple installations of Fedora, though not any other operating systems. I'm only a regular user of two IRC servers and the other one has no ircop users so I can't tell if it's just this particular server or all of them. But the fact that other IRC clients do not exhibit this behavior indicates a Konversation bug.