I try add comment to bug 94075, but get error: "You tried to change the OS field from other to All, but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field." But I didn't change the field. When I enter the bug OS field is "All". I just type "Additional Comments" and press "Commit" Changing OS to "Other" doesn't help either.
I dont see any activity on that bug other than the committer. To edit the bug, you would need to add yourself onto the CC of the bug, so you can take part in its discussion. -Jeffrey
(In reply to comment #1) > To edit the bug, you would need to add yourself onto the CC of the bug I didn't know this. Thank you. But I can't add myself to CC. When I try I get the same error "You tried to..."
Maxim, Just try adding something in the comment box and clicking "add $me to CC list" and committing. not sure why it wont let you. -jeffrey
(In reply to comment #3) > Just try adding something in the comment box and clicking "add $me to CC list" > and committing. not sure why it wont let you. I did, but result is the same. "You tried to change the OS field from other to All, but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field." Can you add yourself? May it be because current value for OS is "other" (in lower case), but no such value in choses for this field? Only ("All", "Other", "Linux"... values started with upper letter.
I'm getting the same problem for Bug #94955 . In this case, it says: You tried to change the OS field from other to Other, but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field. Note the caps change: 'other' to 'Other'. Clearly, this is pure crap. And this bug does have activity; it's on the list for the next bugday, so it's not something to just be dropped. :)
The exact same error as in comment #5 on Bug #94579 blocks for update of the bug. I would say that this bug blocks 94579 (but I am not allowed to make such a desicion;))
Err.. too early in the morning. My comment #6 is valid, but it is ambiguous. Comment #5 refers to comment #5 in this bug. And the error stated in comment #5 is the same error as I have discovered when I tried to update Bug 94579
(In reply to comment #6) > The exact same error as in comment #5 on Bug #94579 blocks for update of the > bug. Bug 94579 and Bug 94955 fixed.
What's about bug 94075?
(In reply to comment #9) > What's about bug 94075? Fixed.