Last modified: 2014-09-30 15:46:38 UTC
From https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Problems_logging_in : I get loggged out extremely often (more often on Safari than on Firefox) and when I try to log in, whatever my current password is, is not acceptable, so I have to hit "forgot my password", get a new temporary one via email, and then use that to be able to create a new password, which also only lasts perhaps a day at maximum despite hitting the button that says "remember me for 30 days". I should clarify that this problem happens every single time I open a new window in Wikipedia or Wikimedia Commons. The default is that I am logged out, even if I am successfully logged in on another window at the same time. And every time I have to log in, I always have to create a new password as the old one is not accepted even though I created and used it successfully an hour before when opening the first window. Having to reset the password very frequently is what is most time-consuming and frustrating. Using Firefox I am doing a little better than I was with Safari, but still the problem persists at an annoying level. In the last day or two I have had more luck staying logged-on to Wikipedia compared to staying logged-on to Wikimedia Commons. If I get onto Wikipedia and am careful to keep one window open all day long, I can usually get on OK without having to get a new password more than once a day. With Wikimedia Commons that is not true; if I am gone for several hours, even though I left one window open, I have to get a new password if I want to open another window. Can anyone ask about this problem anywhere else where someone might recognize what is happening? This problem is really slowing me down and holding me back from a lot of things I want to do. It's very discouraging.
The problems are appearing on a relatively new iMac. When she logs in on a MacBook Air, it is working better (possibly correctly?). She normally runs Safari 7.1 and Firefox 32.
User reports: ANOTHER UPDATE - SOLVED. As far as I can tell everything is OK now. It seems that DiskUtility fixed the problem.