K-Meleon :: Bugs

Bugs : K-Meleon Forum

You can talk about issues with k-meleon here. But please, for confirmed bugs, use the bug tracker to report and give feedback on bugs.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=siria]
Yes it looks very much like the [b]*storing* is okay, only the re-opening has some problem[/b].
Still no idea if it's only my old system??

Not 100% sure, but it seems to happen mainly if trying to restore from cache, in that case only the still stored pages get a tab, the others are ignored completely. It's like gecko19 would only open a tab after checking if the page exists at all.... But only if loading from cache, not from the web... unless you're on KM1.5x

To get all tabs (not the content, just tab with URL), it's also possible to stay online until all tabs have opened, and while they are now waiting to finish loading, the browser can be set "offline" and clicked "reload all tabs". Problem is, the cache is deleted this way too, but at least the URL is still remembered and not tons of pages downloaded again.

Two things I noticed: Local pages like the default homepage "readme.html" always opens okay, cache or not.
And if cache is completely empty, those single remaining tabs in each restored window seem to be the last tabs in the list. Nothing special about them, just the last in list.

Just to be clear, that's not just about crash restoring or faulty pages, the bug is the same also when opening [b]any other stored session[/b]:
- If you don't have any sessions stored yet, just create a new one of the current tabs
- set browser to "File/Work Offline", delete cache, and try to open any stored session --> gives me only 1 tab per window
- set browser "online" again and open that same session - it works

[hr]
[hr]

Something general, [b]NOT  KM1.6 or bug related:[/b]

I always have that problem, with old KM versions too, that [b]"crash sessions" don't allow to change any settings first[/b]. E.g. if for the last used tab I had allowed javascript, it will now be allowed for ALL tabs while restoring. But if I first decline the automatic crash session restore, in order to check and adapt some 'shields' first, or to set the browser "offline" in order to load from cache, the last session is already forgotten. Only the "previous session" can be restored now, but looks like that's the version from the last "clean" shutdown, not the crashed one.
It seems only possible to change any settings before the browser is opened, by [b]manually editing the prefs.js in the profile folder[/b].

Have now tried to find some workaround to "remember" crash sessions with macros or such, but after examining closer how those sessions are saved, that seems way to difficult for me:

As soon as the browser is started, a brand new "Last Session" gets stored in the prefs, which actually is the 'current session', and so is empty at first. That is, this happens if the browser was shut down orderly the last time. If it was crashed however, if offers to restore the crash session ("Last Session") at startup, but if you decline, that previous "Last Session" is instantly deleted and reset again to zero, to be used for storing the current session again. Which is empty, if you declined restoring the old session.

Now I'm using a rather complicated [b]workaround to manually rename the last crash session into an ordinary stored one[/b]. Just in case anyone could use that too: 
While browser is still closed, open profile folder, make a backup copy of prefs.js, then edit the original in a notepad. Click Edit>Replace and automatically replace all ".Last Session." with e.g. ".0Last Session.".
If it's the first time you try that trick, also update the menu list by replacing "Previous Session," with "Previous Session,0Last Session,"
Save and start browser.
Now it's possible to decline crash restore, adapt settings or do some other surfing first if you like, doesn't matter anymore, since "0Last Session" is an ordinary stored session like all others, and can be opened whenever you like.

The new name of that session doesn't really matter, can also be "Crash Session" or whatever, it just must come alphabetically before "Last", or it won't work a second time. 
That's because the prefs.js automatically gets sorted alphabetically after browser start, and identic entries further down will overwrite the same ones higher up and delete them. That also means there may be remnants in prefs.js of previous "0Last Sessions" if those had more pages stored, but if I get this right it doesn't matter, they are ignored, since the browser will only open the number of pages that gets updated in the counter each time...[/quote]

K-Meleon forum is powered by Phorum.