Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"Your submission could not be processed because the token has expired.
Please push the back button and reload the previous window."
I do tend to have LQ pages open on my browser(s) on a virtually perpetual basis. Nothing else that I routinely do elicits any such messages. Reloading the window as suggested doesn't seem to produce any remedial effect.
I am using Mozilla Seamonkey, version 2.0.11, and other recent versions.
Is there some sort of timeout that makes a session go 'stale', or something related to the length of a LQ login? As I say, I leave LQ open on a browser, sometimes on multiple browsers on different hosts at different locations (home & work) virtually all of the time. I use the same username in each case. The nature of the message seems to suggest something related to that. Are you able to replicate my scenario, or is there some more info you would like, or something else I should try to shed more light on it?
--- rod.
I think I must have. I open a window in the browser by middle clicking a bookmark, and it opens about 5 tabs on various forums' summary pages, and all are automatically logged in. I don't remember the last time I had to type a password to login.
--- rod.
old thread, but I've seen something like this.
the fix: go to browser options, turn on cookie request alerts.
the alerts may not show, but whatever action was "blocked" will now work.
iirc, once the "stubborn" action proceeds in the browser session, i can turn off request alerts, and same action won't be "blocked".
Hmm. For now, at least, the problem seems to have vanished. It does follow a couple of reboots, so maybe there is a connection there. I looked long and hard, and can't see anything resembling a 'cookie request alerts' setting. Basically I can accept/disallow cookies (I allow all), and a 'Cookie Retention Policy' (I 'accept normally'). All of this under /Edit/Preferences/Cookies in Seamonkey.
Its baaaaaaack.... I think it may have happened after 24 hours of being logged in (at least, having logged in, and with multiple tabs open on various forums).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.