Bug 1195991 - I can't login via firefox and google chrome however it works with current Falkon (KDE)
Summary: I can't login via firefox and google chrome however it works with current Fal...
Status: RESOLVED DUPLICATE of bug 1194193
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-15 18:00 UTC by Ilgaz Öcal
Modified: 2022-02-16 05:31 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilgaz Öcal 2022-02-15 18:00:05 UTC
I try to login via login name/password, it simply falls back to the same page rather than logging me in and showing me homepage.

Steps to produce:

1) open firefox or google chrome
2) open https://bugzilla.opensuse.org/index.cgi
3) click login
4) fill your nickname and password

Expected results
1) I am logged in
2) Main page shown

Actual results:
1)I am back to same page it shows https://bugzilla.opensuse.org/index.cgi?GoAheadAndLogIn=1 in addressbar.
2)If I try reloading, browser warns me that the form will be reposted. Doesn't change, same page appears.

On openSUSE TW Falkon (Application version 3.2.0 QtWebEngine version 5.15.2) there is no issue. (I am using it to report)

I used webcompat bug report wizard built into Firefox to report it to Mozilla too. See https://github.com/webcompat/web-bugs/issues/99642
Comment 1 Andreas Stieger 2022-02-15 20:36:02 UTC
Check if this is the same as bug 1194193 ?
Comment 2 Ilgaz Öcal 2022-02-16 05:31:28 UTC
(In reply to Andreas Stieger from comment #1)
> Check if this is the same as bug 1194193 ?

It looks like it. However, in first try that workaround didn't work, launched Firefox second time it worked.

*** This bug has been marked as a duplicate of bug 1194193 ***