Bug 1194193

*** Bug 1194210 has been marked as a duplicate of this bug. ***

Seen here for about a week

(In reply to Andreas Stieger from comment #2)
> Seen here for about a week

I can observe this problem for 2 months, just no one gave it to me.

Gave what to you, exactly?

Hi Daniel, is the problem still existing please?

(In reply to Chenzi Cao from comment #5)
> Hi Daniel, is the problem still existing please?

There is still a problem.

Hi Martin, would you please help to take a look at this issue? Please feel free to reassign whenever necessary, thanks.

*** Bug 1195991 has been marked as a duplicate of this bug. ***

This is a daily occurrence here.

Still a problem. Will the part of SUSE that still cares about community distributions please show some sense of ownership and fix annoyances that prevent people from contributing?

This still happens to me as well, but only on Firefox. With Chromium I seem to be able to login every time. At first I thought that might be related to extensions, since in Firefox I have a lot, but when I disable all of them and try again it's the same thing. Extensions haven't interfered with other logins so far. My guess is it's not that. The weird bit is, in Firefox sometimes randomly it works, but rarely. It's very hard to tell what the cause is, but if I find a clue I'll post it here.

In Yandex browser, which is based on chromium, it enters at both addresses.

Now it started happening in Chromium as well :/ I wrote my password probably 5 times, I don't think it was the wrong password, there was no error as well.

*** Bug 1200257 has been marked as a duplicate of this bug. ***

ping, this gets re-reported occasionally by users with varying degree of capability to debug. Please give this bug it's due attention.

Anyone, the last report for this was in July, and I do not recall this happening to me any later. So this may have disappeared? Setting needinfo to anyone, if we can re-confirm, if not we can probably close after 1w.

I tried to report bugs day or two ago and I still needed to use workaround with login on bugzilla.suse.com first and then on bugzilla.opensuse.org twice to login here

Thanks Daniel. So Martin, it looks like this issue is reoccurring, for multiple people but not reliably so. But if it does it is noticeable. Do you need anything else to look into this?

Issue still exists, I could only login to bugzilla via bugzilla.suse.com.

Hi,

Our team is responsible ONLY for the infrastructure part the the Bugzilla service
Not for the application it self.

I FW this ticket to vladimir.siman@suse.com From the Legacy application team.

Martin

*** Bug 1204497 has been marked as a duplicate of this bug. ***

*** Bug 1204988 has been marked as a duplicate of this bug. ***

I've been running into this issues on and off for a while too. On the best days I can login to bugzilla.o.o, and on worse days, not even in bugzilla.s.c.

Can't say much of what's going on though. When the issue occurs, I prompt my username and password, hit enter and the forms get cleared. And it fails to show any message of what went wrong.

If anyone has any idea on how to debug this, please speak up.

Relevant ticket in Redmine: https://progress.opensuse.org/issues/113069

(In reply to Luciano Santos from comment #24)
> Relevant ticket in Redmine: https://progress.opensuse.org/issues/113069

Nice to have some screenshots, but the issue dated Dec 2021 hasn't been solved yet. I am really upset, because today I have tried to login to bugzilla many times, without success. It is really disappointing that openSUSE is not capable of solving this issue!

I see the same issue.

In Browser Console of Firefox, I see the following error messages:

> Cookie “Bugzilla_login_request_cookie” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
> Cookie “Bugzilla_login” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
> Cookie “Bugzilla_logincookie” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

Firefox 109.0.1
macOS 11.7.3

See also

https://hacks.mozilla.org/2020/08/changes-to-samesite-cookie-behavior/

I wish it would help.

Just emailed Vladimir requesting assistance. If this requires added resources, requesting what pocket of resources might be a good next go to (opensuse heroes?). 

The ultimate goal - remove any friction for new users/contributors.

Had the same issue yesterday.

UPDATE for those who didn't see it in the other portal: 

WORK AROUND UNTIL FIX LANDS: 

UPDATE:

WORKING THEORY on Source of the Bug "Doc Type Not Set Correctly..."

I noticed when digging in that it complained in Chrome over "quirky" mode. It reads out when I use the web-dev console tools:

*Page layout may be unexpected due to Quirks Mode
One or more documents in this page is in Quirks Mode, which will render the affected document(s) with quirks incompatible with the current HTML and CSS specifications.

Quirks Mode exists mostly due to historical reasons. If this is not intentional, you can add or modify the DOCTYPE to be <!DOCTYPE html> to render the page in No Quirks Mode.....*

On a hunch, I "converted" the layout to simulate a touch mobile device via the browser's "dev tools" in chrome (see instructions below)

It was a long shot, but if I can get bugzilla to "KNOW" what type of page it was - then maybe it would go through?

I then changed it to mobile, and BOOM, instantly signed in.

This might be my work around - just change the "hardware agent" and you may not have to face the RANDOM bug being denied access to bugzilla.

Not sure how keeping the checkmark checked or UNcheck the "Restrict this session to this IP address plays a role here, if any... 


DEV TOOSL INSTRUCTIONS: 
FIRST before trying to sign in via Device Toggle (which is found when you press F12 or if you go to Chrome settings icon (three dots). More Tools ---> Dev Tools. And the side bar opens and you can toggle to a "mobile" touch rendered page.

THIS lets you in all the time. Just confirmed again that it works today after not getting in.

Since Bugzilla version has been bumped up is this still an issue?

seems a lot better since the switch to "IDP Log In"

Agreed, I think we can close this now. 

If there are issues with logging in after this point, it is likely it is a new and separate issue altogether, we can then open a new bug report at that point. 

Big thanks to those who made this upgrade happen!

(In reply to Joed L from comment #32)
> Agreed, I think we can close this now. 
> 
> If there are issues with logging in after this point, it is likely it is a
> new and separate issue altogether, we can then open a new bug report at that
> point. 
> 
> Big thanks to those who made this upgrade happen!

I've opened a new bug report, since the login issue is not solved for me: #1210608

(In reply to Frank Krüger from comment #33)
> (In reply to Joed L from comment #32)
> > Agreed, I think we can close this now. 
> > 
> > If there are issues with logging in after this point, it is likely it is a
> > new and separate issue altogether, we can then open a new bug report at that
> > point. 
> > 
> > Big thanks to those who made this upgrade happen!
> 
> I've opened a new bug report, since the login issue is not solved for me:
> #1210608

bug 1210608

Since I opened bug 1210608, this one can be closed.