Closed Bug 346793 Opened 19 years ago Closed 19 years ago

"You need to be an operator" error after joining channel

Categories

(Other Applications Graveyard :: ChatZilla, defect)

defect
Not set
trivial

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dbachran-bz, Assigned: rdmsoft)

References

Details

(Keywords: fixed1.8.1, regression, Whiteboard: [cz-0.9.76])

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 After upgrading to CZ 0.9.75 I noticed some possible regression (which wasn't there w/ 0.9.74, or any other previous version). I have setup CZ to auto-join 4 channels upon startup. In one of those channels I became op (since I created that channel). In all other channels I've seen the following error message some time after joining (i.e. not immediately): [ERROR] You need to be an operator in #<channel> to do that. This also happens when I manually join a channel where I'm not op. This happened with every channel I tested (only a few), regardless of the network. Being op in one channel or not doesn't seem to make a difference. Reproducible: Always Steps to Reproduce: 1. Join some channel where you're not op 2. Wait some seconds 3. Error message "You need to be an operator" appears Actual Results: Error message "You need to be an operator" appears Expected Results: No error message should appear. I didn't do anything which warrants op status. CZ did it. Honestly, mom.
Do you have any scripts installed? Does this happen on the moznet network? Can you use debugMode to figure out what's being sent that makes the server go "Oh no you don't" ? Frankly, this is WFM until there's better steps to reproduce. I've never had problems, neither in channels where I'm op, nor where I'm halfop, nor where I have no privileges at all. For debugMode, use /pref debugMode t to turn it on. You will need to have the pref browser.dom.window.dump.enabled set to true (you can do so in about:config), and you'll need a console started with Firefox (start Firefox with a -console switch on startup). Pasting all the output *here* won't be much use, but if you'd come into the support channel (#chatzilla on moznet), perhaps one of the people there can help figure out what's going on when looking at the raw output (which you'd probably www.pastebin.ca for us).
Version: unspecified → Trunk
Assignee: rginda → rdmsoft
Depends on: 338710
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
As explained in irc.js (server.on482), some servers require ops to see the except list. This suppresses the error if we just automatically asked for the list.
Attachment #231565 - Flags: review?(silver)
Comment on attachment 231565 [details] [diff] [review] check for pending except list Except that I'm not a peer, this seems fine to me. I'd actually like to get this on branch. Are we going to manage a .96 before SM 1.1, or should we try to get approval for this separately?
Attachment #231565 - Flags: review+
uh, .76 Duh.
Keywords: regression
OS: Windows XP → All
Hardware: PC → All
Attachment #231565 - Flags: review?(silver) → review+
Please land this on MOZILLA_1_8_BRANCH as well, but change __cz_version to 0.9.75.1 so we can identify the non-released version specifically (don't touch the locale version).
Attachment #231565 - Flags: approval-seamonkey1.1a+
Fixed on trunk and branch.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Thanks for the prompt response, folks! Do I need to mark this bug as VERIFIED as soon as the update is available via u.m.o and -- erm -- I verified it? Or is this usually done by somebody else? ciao, g0ph3r
You are welcome to mark the bug verified when you have tested a version with the fix. If you can't wait for the next official release, you can get the latest automatic build from http://twpol.dyndns.org/mozilla/chatzilla/nightly/
Whiteboard: [cz-0.9.76]
Verified that this bug is fixed with cz 0.9.76. thx, daniel :)
Status: RESOLVED → VERIFIED
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: