http://bugzilla.suse.com/show_bug.cgi?id=908519 Wolfgang Rosenauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lmb@suse.com, | |wolfgang@rosenauer.org Flags| |needinfo?(lmb@suse.com) --- Comment #1 from Wolfgang Rosenauer --- I have not seen that yet. What value you find in browser.startup.page? How exactly do you close Firefox? (to see if I can reproduce somehow) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 Lars Marowsky-Bree changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lmb@suse.com) | --- Comment #5 from Lars Marowsky-Bree --- Hrm. So the "ctrl-q is being ignored" seems to be due to the TabMix extension. Alas, disabling this does not help the session manager to work again. I tried disabling all extensions, that didn't help either, and re-enabled them one by one. --safe-mode unfortunately works. So it appears to be some random setting that changed its effects in 34.x. Is there any chance to get this back to working without having to reset everything? I don't really want to lose all my adblock etc settings :-/ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 Michal Svec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msvec@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 --- Comment #8 from Lars Marowsky-Bree --- (In reply to Wolfgang Rosenauer from comment #7)

(In reply to Lars Marowsky-Bree from comment #5)

...

I tried disabling all extensions, that didn't help either, and re-enabled them one by one.

--safe-mode unfortunately works. So it appears to be some random setting that changed its effects in 34.x.

puh, this is strange. -safe-mode is supposed to "only" disable all addons. Therefore having -safe-mode working while "disabling all extensions" still shows the problem is somewhat strange.

I was apparently speaking too soon. And not wearing my brown paper bag yet; I accidentally started FF with a different profile. :-( Indeed, safe-mode is not working for me either.

Do you have any user.js content (please check about:support). Also check if you find any "sessionstore" related prefs on that page.

I do have a user.js: # user_pref("font.FreeType2.enable", "true"); # user_pref("font.FreeType2.autohinted", "true"); # user_pref("font.FreeType2.printing", "true"); # user_pref("font.FreeType2.unhinted", "false"); (Probably time to drop that, but quite very likely unrelated.) sessionstore.prefs from the support page has only: # browser.sessionstore.upgradeBackup.latestBuildID = 2014110600 Just for kicks, I'm going to reset that and see what happens, and then enable the sessionstore debugging. No experimental features activated or anything. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 --- Comment #10 from Lars Marowsky-Bree --- (In reply to Wolfgang Rosenauer from comment #9)

You are now on 33 or 34? The latestBuildID suggests 33?

# rpm -q MozillaFirefox MozillaFirefox-34.0.5-1.3.x86_64 about: Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 So, I tried moving all my sessionstore.* files from my ~/.mozilla/firefox/xxx.default/ out of the way. No luck. It's not touching those files at all; no sessionstore.js gets written, only remotely relevant file is sessionCheckpoints.json. (Turns out that my old sessionstore.js from prior to the update is still around, so if I ever figure out why it's not working, I can go back to that ;-) I also read up on the mozilla knowledgebase and found the "browser.sessionstore.enabled" parameter and force set this to boolean - true. No effect. If I reset this parameter to default, it also just gets removed. Firefox seems to neither read nor write sessionstore.js for me :-/ Trying to find an upstream issue now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 --- Comment #12 from Michele Cherici --- (In reply to Wolfgang Rosenauer from comment #7)

...

System JS : ERROR resource://app/components/nsBrowserGlue.js:1529 - NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIPrefBranch.getComplexValue]

now this already confuses me. What is the content of your browser.startup.homepage pref (about:config)?

user_pref("browser.startup.homepage", "http://www.google.com");

...

System JS : ERROR resource:///modules/sessionstore/SessionStore.jsm:1508 - NS_ERROR_ILLEGAL_VALUE: Default view is not tracked System JS : ERROR resource:///modules/sessionstore/SessionStore.jsm:1508 - NS_ERROR_ILLEGAL_VALUE: Default view is not tracked

Seems unrelated at first look.

Do you have any user.js content (please check about:support). Also check if you find any "sessionstore" related prefs on that page.

No user.js file. In about:support I have: browser.sessionstore.upgradeBackup.latestBuildID 2014101000about:support I've solved my problem restoring the profile (and manually reinstalling all the addons). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 --- Comment #14 from Michal Svec --- Oddly enough, it got this "fixed" now by running FF from upstream directly: https://www.mozilla.org/en-US/firefox/new/ Then all thing suddenly work as before (session, tabs, passwords, PDFs). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=908519 Sergey Klyaus changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Sergey.Klyaus@Elcom.SPb.Ru --- Comment #17 from Sergey Klyaus --- I managed to find workaround for that issue. It seems that failing code does some migration tasks (updating prefs.js config according to newer firefox version I suppose). I simply set this configuration option: browser.migration.version = 25 Last checked migration version is 24 so I took following value and Firefox now thinks that migration is done. After that sessionstore recovered. NOTE: It can break some other migration processes so use my workaround with caution and backup your profile before you apply it. -- You are receiving this mail because: You are on the CC list for the bug.