http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c2

Andreas Stieger Andreas.Stieger@gmx.de changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |Andreas.Stieger@gmx.de

--- Comment #2 from Andreas Stieger Andreas.Stieger@gmx.de --- Seen here for about a week

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c8

Ilgaz �cal ilgaz.nsa@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |ilgaz.nsa@gmail.com

--- Comment #8 from Ilgaz �cal ilgaz.nsa@gmail.com --- *** Bug 1195991 has been marked as a duplicate of this bug. ***

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c10

--- Comment #10 from Andreas Stieger Andreas.Stieger@gmx.de --- 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?

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c12

--- Comment #12 from Nikolay Sabelnikov 79625490833@yandex.ru --- In Yandex browser, which is based on chromium, it enters at both addresses.

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c14

Andreas Stieger Andreas.Stieger@gmx.de changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |php4fan@gmail.com

--- Comment #14 from Andreas Stieger Andreas.Stieger@gmx.de --- *** Bug 1200257 has been marked as a duplicate of this bug. ***

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c16

Andreas Stieger Andreas.Stieger@gmx.de changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?

--- Comment #16 from Andreas Stieger Andreas.Stieger@gmx.de --- 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.

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c18

--- Comment #18 from Andreas Stieger Andreas.Stieger@gmx.de --- 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?

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c22

hui sturm-fr@web.de changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |bugz57@top.geek.nz

--- Comment #22 from hui sturm-fr@web.de --- *** Bug 1204988 has been marked as a duplicate of this bug. ***

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c23

--- Comment #23 from Luciano Santos luc14n0@opensuse.org --- 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.

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193

Christian Boltz suse-beta@cboltz.de changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c25

--- Comment #25 from Frank Kr�ger fkrueger@mailbox.org --- (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!

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c26

Takashi Tamura tamuratak.9876@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |tamuratak.9876@gmail.com

--- Comment #26 from Takashi Tamura tamuratak.9876@gmail.com --- 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.

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193

Ales Novak alnovak@suse.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Assignee|vladimir.siman@suse.com |dmitrii.puzikov@suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 http://bugzilla.opensuse.org/show_bug.cgi?id=1194193#c29

--- Comment #29 from Joed L jlopez777+opensuse@gmail.com --- 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.