Description of problem: I'm trying to add a comment to bugzilla entry 151334, leaving the status as "New". But when I click on the "Submit" button it gives me a "Not Allowed" error stating: "You tried to change the Resolution field from no value to NOTABUG, but only the owner or submitter of the bug, or a sufficiently empowered user, may change that field." Yes, it's true that the resolution field contains "NOTABUG" but I did not check the "Resolved" checkbox. The "leave as new" box is checked. And worse, the resolution status pull-down menu provides no option *other* than NOTABUG. So basically there's no escape and it's impossible to add a comment. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Try to add comment to 151334. 2. Leave bug status as "New" 3. Click "Submit" Actual results: Get above "not allowed" error. Expected results: No error and comment added. Additional info:
As I have not personnally been able to reproduce this, I have heard of several other people having a similar problem. Is it asking you to log in after submitting the comment and then giving the error or are you already logged in? Also which browser/version are you using?
Without logging in I did a query to see if anyone else had observed the kdeinit problem. I found entry #151334 that was very similar to what I was seeing, so I went to add some additional information I'd found while debugging the problem. After entering the comment and clicking on "Save Changes" it asked me to log in. I logged in and then I got the "not allowed" error. Subsequent attempts to add the comment also failed with the same error but it did not prompt for login information again. I've done this exact sequence many times before though it's been a while since the last one. That is, query/find/add-comment without logging in, prompt for login, and then comment accepted. The browser was Firefox on FC3. Now let's see what happens when I click "Save Changes"... (This time I'm already logged in using Mozilla on FC2.)
Well even though I was already logged in when entering that last comment, it prompted for login information anyway. Then it (obviously) it accepted the comment. I have cookies enabled so I'm not sure what's up with that.
The cookie format changed from the old bugzilla to the new bugzilla. I added code in to account for both formats which should keep people from having to remove their bugzilla.redhat.com cookies. But there has been a few people who still had trouble that removing their bugzilla cookies was able to fix. Can you try doing that in your Firefox preferences and see if Bugzilla remembers you are logged in for each page after that?
The login-again problem was with Mozilla, not Firefox. But I'll try this anyway. I deleted all my bugzilla.redhat.com cookies from Mozilla, I'm now logged in, and when I finished typing this I'll click on "Save Changes".
Okay, that time it didn't have me re-login. Progress is progress. When I get home I'll try deleting cookies in Firefox and see if that solves anything.
Back to Firefox, FC3, and trying to add a comment to #151334: - I deleted all bugzilla.redhat.com cookies. - I went to bug #151334 _without_ logging in to bugzilla. - I added a comment and submitted it. - bugzilla prompted for login information. - After accepting my login I got the same "not allowed" error as before. I logged out of bugzilla to start fresh. Then: - I logged in to bugzilla _before_ going to bug #151334. - Then I went to bug #151334 and added a comment. - Submitting the comment succeeded! So it would appear that the root of all evil is the intervening login. It gets bugzilla and/or Firefox all confused.
Ok, that does help to narrow it down a bit. Probably what is happening is that during the intervening login screen, all of the previous form values from the bug edit page, have to be listed as hiddden form values in the HTML generated for the login page. Something important is being either omitted or is getting shuffled somehow which is confusing Bugzilla. I will need to do some research into the code and hopefully come up with a fix. Thanks for all of your troubleshooting help.
Hello, I am running into the exact same problem. If there is any testing that I can do to help find a resolution, please let me know. I run into the issue exactly as Terry does, when I attempt to update a bug without first logging in... -Sean
It bit me too. Disabling cookies does not work. Clearing cookies does not work. Only thing that works is loging in first - then going to the bug. So its something with the login process - even when you clear all your cookies first.
*** Bug 151631 has been marked as a duplicate of this bug. ***
Ok, I found the problem and have made a code change to hopefully solve the issue. Can each of you please verify the fix somehow by adding test comments on a bug you do not own without being logged in first? Thanks for your patience.
Looks like it works for me :)
Works for me as well!
Ditto.
Three times the charm ;) Please reopen this issue if you still experience the problem. Thanks for all of the help and patience.