Last modified: 2014-10-21 07:24:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58842, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56842 - Mailman administration frequently fails on Chrome.
Mailman administration frequently fails on Chrome.
Status: NEW
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
: 56843 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-09 16:40 UTC by Niklas Laxström
Modified: 2014-10-21 07:24 UTC (History)
10 users (show)

See Also:
Web browser: Google Chrome
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Niklas Laxström 2013-11-09 16:40:38 UTC
I'm trying to add new members to Wikimedia-fi mailing list with the mass subscribe feature. It always fails with white page (empty response) after long wait.
Comment 1 Nemo 2013-11-09 16:42:58 UTC
*** Bug 56843 has been marked as a duplicate of this bug. ***
Comment 2 Thehelpfulone 2013-11-09 16:59:54 UTC
Are you trying to do this using Chrome? Please can you try using another browser?
Comment 3 Nemo 2013-11-22 18:10:42 UTC
(In reply to comment #2)
> Are you trying to do this using Chrome? 

Yes. Thehelpfulone, as there is no indication that this is specific to subscribing, maybe this should be made a general bug about the well known Chrome-mailman problemsm, if there isn't another one?
Comment 4 intracer 2014-01-10 22:26:35 UTC
Any admin action most probably will give ERR_EMPTY_RESPONSE in Chrome for days and so will not succeed.
Comment 5 James Alexander 2014-01-11 03:23:00 UTC
Adjusting the header on this, this is sadly a very well known issue and I know we've talked about it off and on for a long time. My understanding is that it's an upstream issue that does not appear like it is any priority but I have no idea how difficult it would be for us to try and dig in at it.
Comment 6 Nemo 2014-01-11 08:02:23 UTC
I can't however find any report mentioning chrome/chromium in https://bugs.launchpad.net/mailman/ or any report mentioning mailman against chromium, unless it's one of these: https://code.google.com/p/chromium/issues/list?can=2&q=ERR_EMPTY_RESPONSE
Did this happen also before lists.wikimedia.org was made HTTPS-only? Among those there are several mentioning TLS forms issues.

Please identify the correct upstream bug or file one, after reading those above, and link it here.
Comment 7 Nemo 2014-01-11 08:05:06 UTC
If you file a new bug (or find one with incomplete information), remember to follow this procedure, they want it: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details (make sure it doesn't contain your password or non-spam private data; or that you terminate your session if it contains your cookie).
Comment 8 Andre Klapper 2014-02-27 12:05:43 UTC
Apart from https://code.google.com/p/chromium/issues/list?can=2&q=ERR_EMPTY_RESPONSE I could only find https://code.google.com/p/chromium/issues/detail?id=80427 ("Chromium does not save passwords for Mailman list admin pages") which is marked as a duplicate of https://code.google.com/p/chromium/issues/detail?id=111705 ("Chrome doesn't save password without an associated username").
Comment 9 Tisza Gergő 2014-10-21 07:24:09 UTC
A strange but (for me) reliable workaround is to close the browser tab after clicking submit.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links