Bug 1200257

Summary: Login to this stupid bugzilla is completely broken
Product: [openSUSE] openSUSE.org Reporter: teo teo <php4fan>
Component: BugzillaAssignee: Martin Caj <mcaj>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <novbugzilla-bugs>
Severity: Major    
Priority: P5 - None CC: Andreas.Stieger
Version: unspecified   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description teo teo 2022-06-06 18:16:48 UTC
Steps to reproduce:

1. Be sure you are not logged in
2. Go to some bug(*), e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=776117
3. Use the embedded login form at the top of the screen to log in: enter your correct username and password and click the submit button.

(*) or at step 2 use the "New" link to enter a new bug, which will redirect you to log in. I face the same issue when I do that, although maybe some details may vary.

Expected: should log in. Or if there's something wrong, give an error message explaining what's wrong

Observed: it shows a new login page with no error message whatsoever. 

4. Re-enter the correct username and password

Expected: same as after step 3

Observed: keeps showing the same login form page with no error message.


For MONTHS I've been having this problem, and every single time I thought I wasn't remembering my password correctly, so first I would try with the email instead of the username (or the other way around if I had tried with the email first), because the prompt says "login" which is ambiguous and you can't know which one you are supposed to use. Then I would try different password that I thought might be the correct one. I would get either the error complaining about incorrect username and/or password or again the login prompt again with no error message, and of course it was seemingly random to me and I didn't know that in one case it's this stupid bug and in the other case I'm actually entering the wrong password or username.

So then, every time, I would attempted to do the "Reset password" or "Forgot password" thing, which is also broken in many ways that I don't even want to try and remember, and in the end I ended up creating a new user every time, which is also a f***ing mess (and I reached the point where I had to create a new gmail account each time), and then couldn't log in with the new user anyway, until between clearing cookies and going to the homepage (rather than a specific bug) and through the dedicated "log in" link (as opposed as using  the embedded form in any random page) I could finally log in with one user or another.

It is only now that I finally figured out (or at least think so) that what makes the difference is to go to the dedicated login page from the link in the home page (and maybe clearing cookies is also needed), and not clearing the cookies, at least not that alone.


I am not sure whether or not this has to do with the "restrict this session to this IP address" or not. I would never check that option if it was for me, but it's checked by default so most of the time I forget to uncheck it (or fail to realise it's not a "remember me" checkbox). Either way, this is obviously a bug. If I get logged out because I was already logged in via cookies but I'm connecting from a different IP, that should not prevent me from logging in again, and if it does for any reason, should show some error message and tell me what to do about it.

Note that I do NOT use any password manager, nor any of the browser's "remember passwords" features. The only way my username and password get entered from the client side (regardless of when *you* log me in automatically using a cookie) is when I type them with my hands. Not that you would be excused if the issue had to do with the browser remembering passwords (unless it was a bug in the browser) but that is not the case anyway.


Everything login-related in this bug tracker is a complete mess. Login, as described here, password reset, signing up.
Comment 1 Chenzi Cao 2022-06-07 08:15:54 UTC
Hi Martin, would you please help to take a look at this issue? I'm not sure whether it is correct to assign it to you, please feel free to reassign whenever necessary, thanks.
Comment 2 Felix Miata 2022-06-10 05:56:57 UTC
Which browser(s)???

Could this be one of those situations where clearing all bugzilla cookies before attempting login clears the problem?
Comment 3 teo teo 2022-06-10 09:16:01 UTC
> Which browser(s)???

Chrome on Linux. (but I'd be surprised if it made a difference)

> Could this be one of those situations where clearing 
> all bugzilla cookies before attempting login clears the problem?

It could be, in part.
At some point I was able to log in after clearing cookies, and I thought that was the definitive workaround. But then it also happened to me that clearing cookies didn't help.
Another thing that seemed to help (but I'm not so sure, it could be random), maybe in combination with clearing cookies, was to go to https://bugzilla.opensuse.org/index.cgi?GoAheadAndLogIn=1 and NOT use the embedded login form that is found in other pages.
Comment 4 Andreas Stieger 2022-08-02 17:09:36 UTC
> Login to this stupid bugzilla is completely broken

Looking at multiple of your bugs... You seem to have a complete and utter lack of ability to search for existing reports, file separate issues with cross-references for context, or even do some basic research about the part you have in causing the breakages... I think you have long overstayed your welcome.

In any case, resolving as duplicate of bug 1194193 which you should have seen already.

*** This bug has been marked as a duplicate of bug 1194193 ***
Comment 5 teo teo 2022-08-02 21:44:49 UTC
> You seem to have a complete and utter lack of ability to search for existing reports

Not ability, willingness.

In decent bug trackers, after you type the title and the description (whether it is upon submitting or it gets updated in real time as you type), a list of potentially similar bugs is shown.

When that happens, I do check them thoroughly.

If the people maintaining the code don't care enough to install bug tracking software that automates trivial (but tedious) tasks that can be automated, they're gonna have to deal with duplicate reports from time to time.

Also, when I do try to do a search on my own and the search engine is garbage, I won't ever use it again.
Comment 6 Andreas Stieger 2022-08-02 22:03:45 UTC
Search box is right on top, in addition to "Possible duplicates" when failing a new bug. But thank you for confirming you are unwilling.
Comment 7 teo teo 2022-08-02 22:11:31 UTC
> in addition to "Possible duplicates" when failing a new bug

Right, my bad, this is one of the bug trackers that does have that.

Then I didn't find one that looked related. I assure you, when a list of related bugs shows up I check. I can definitely miss one, honest mistake.


> Search box is right on top

The search engine _is_ crap, so that one I definitely didn't waste time trying.