http://bugzilla.suse.com/show_bug.cgi?id=965738 Bug ID: 965738 Summary: Chromium: Impossible login on https://e-fibank.bg/ Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening@forge.provo.novell.com Reporter: studio@anchev.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.82 Safari/537.36 Steps to reproduce the problem: 1. Open https://e-fibank.bg/ 2. Enter login credentials 3. Click Login The browser simply refreshes the page and does not log in the user. No error messages, no problems in Network section Dev Console (all HTTP 200). NOTE: for testing you can use random credentials. Chromium will not give you an error message (as it should) and will refresh the page again. Please note - Chromium != Chrome. Everything worked fine in an earlier version. Not sure which one but right before Christmas 2015 it worked This works in other browsers (tested in official Google Chrome from Google's repo and Firefox). I know you cannot test without login credentials. Unfortunately the bank's tech support is very bad and they don't understand that in order to test this on your side they should provide some kind of log or at least a test account. But they don't respond when I ask for this. They simply say "We didn't make any changes on the server side" and don't reply any more. I understand that for security reasons they might be right but still I hope you can check what might have changed from previous version of Chromium when everything worked. NOTE2: This has been reported to code.google.com but they replied with a WONTFIX: https://code.google.com/p/chromium/issues/detail?id=585053 In summary: They say Chormium must have been modified/patched by the Linux distro and I should address this bug here, i.e. to openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.