Comment 1 for bug 1199046

In 2.9.1:

Using a stock Chrome browser install (Debian/Ubuntu package, 64bit), I could not reproduce this bug. I stayed consistently logged in to the OPAC. I also couldn't reproduce the bug in my normal more-private Firefox configuration.

Using Chrome with "Remove local information on close" did reproduce the error.

How long are the patrons away from the OPAC site between visits? If they log in with "Stay logged in" selected, close the site, and then return, are they immediately logged out, or is there a 24-hour space between the visits, etc.?

Otherwise, it seems to be dependent on browser settings.