channel modes for users after reconnect

Bug #717076 reported by gakse
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shroudBNC
New
Medium
Unassigned

Bug Description

when i get op in some channel, sometimes when i reconnect it seems like for others i still have the +o mode(@), and my messages are prefixed with @, but for me it shows as if i'm with a regular nickname.

ADDITIONAL INFORMATION:
in some channels in which i have +a mode(&) when i reconnect, i'm with +o(@) only, and again it seems like for others i have that +a(&) mode.

Tags: core
Revision history for this message
gakse (gakse) wrote :

I mean I have those modes, but sbnc doesn't show them.

Revision history for this message
Ze0de (i-admin-my-bnc-net) wrote :

I too have this problem on 1.3 beta5.

Sometimes when I reconnect to a session, users that don't actually exist in the name list any more show in the user list, and I have to /hop to update the list.

User modes seem to be a problem too. Often I reconnect to my BNC session and user modes +q and +a never show up on my own nick until I /hop. With other users sometimes they show when I reconnect, sometimes not. This seems to be intermittent and also applies to +h and +o on occasions.

As above, although it appears to other users as though all user modes are showing correctly, to me they do not until I /hop the channel.

No idea why.

Revision history for this message
Ze0de (i-admin-my-bnc-net) wrote :

Also I just noticed, that while connected to the BNC session, if I do /names #my-channel, the name list is echoed in the server status window, and my user mode prefix(s) is removed as far as I can see, but to other users it is not.

Revision history for this message
Ze0de (i-admin-my-bnc-net) wrote :

Sorry for multiple post, I forgot to add this to the last comment.

This is the output of the /names #my-channel command.

#my-bnc &My-BNC!<email address hidden> Ze0de!<email address hidden> %Howdy!<email address hidden> Guest_4047!<email address hidden> ~@Ze0de
#my-bnc End of /NAMES list.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.