Discussion, talk and tips
https://forum.puppylinux.com/
Running Fossa64, Frugal on ext4 drive. Firefox is up to date. I see this window on almost every launch despite setting my launch page. The image below has 3 images to show my settings too.
Is there a flag or something I can launch with so that it does not do that so often?
As always, thanks for your time.
theroar84 wrote: ↑Sat Nov 25, 2023 6:53 pmRunning Fossa64, Frugal on ext4 drive. Firefox is up to date. I see this window on almost every launch despite setting my launch page. The image below has 3 images to show my settings too.
....Is there a flag or something I can launch with so that it does not do that so often?
As always, thanks for your time.
I think this happens only when Firefox is not properly closed (crashed), just closing [X] Firefox before reboot or shutdown will probably prevent such message next time launching Firefox.
Other way (only way AFAIK, but anyone correct me if I'm wrong) to prevent is to configure Firefox in the settings to not remember history, but that may not be what you want.
Thank you. Sounds like I am the culprit then as I have pSchedule set to run #poweroff at a specific time... hence the crash. Thanks tons for the info!
@theroar84 / @fredx181 :-
Heh. I get occasional spells when Pale Moon seems to always try and do this at every launch. There's the odd occasions when FF will do this, but for me it's far more common with Pale Moon.....
It seems to be endemic to the 'zilla-based browsers. I've never seen it happen with ANY of the Chromium-based browsers, which I use most of the time. With these, I employ the snippet of code Marv developed for use with Ungoogled Chromium, which lets you clear the cache at session's end; UGC can't do this for itself, since it's part of one of the many Google APIs that this browser lacks. It works just as well for all of the 'clones', however; I just tack it on to the end of the launch wrapper script.
I have it set to bring up a wee YAD GUI, which just asks if I want to clear the cache or not, as the case may be.....
Mike. 
What is the specific version of Firefox?
despite setting my launch page.
What is the home page?
There is a setting for this in the about:config page: browser.sessionstore.resume_from_crash.
AFAIK this happens under PUPMODE 13 (pmedia=usbflash) when using aufs. snapmergepuppy saves the browser state and deletes the files from RAM. If the browser is running while it's saving, there's a race condition between the browser's writing to the files in RAM and the copying from RAM to disk. Often, the result of the copying is a mix of two versions of the same file, before and after the modification by the browser, and sometimes this produces corrupt files (especially when copying binary files like the SQLite databases most browsers use to store things like history and bookmarks).
If you're running Puppy from a flash drive, try to close the browser before you save changes and see if the problem goes away.
snapmergepuppy.overlay, the overlay implementation, doesn't suffer from the same problem because it doesn't delete files and allows you to save again (and fix corrupt files). This is what Bookworm Pup64 uses by default.
Not quite sure if this makes a big difference here, but would you mind to change your cronjob from poweroff to wmpoweroff?
Thanks for the additioanl tips.
I am using wmpower off in the cron. Sorry about the misstype on that. I had initally copied the #poweroff to the desktop... then ya'll shared the #wmpoweroff via chron which is amazing. Just lost my brain when explaining that step.
The Firefox is updated.
This is the start page https://www.tinkercad.com/users/bSyYydQ ... de=default
Will give the settting on the about page a look too. 
I have this puppy frugal off a EXT4 hard drive. I do have a question I had wanted to ask about pup modes though... Where do I track that down? I found it once, then when I wanted to post about it I could not track it down again.
As per usual, you are all amazing! Thanks tons for your time.
The Firefox is updated.
That is no information about what version it is?
There are several different Firefox releases.
Not exactly sure what you want to know about pupmodes?
How to find out what pupmode you are running in?
What the different ones are and how they work?
That start page address could be some of your issue.
I have had similar startup issues, if the startup page address is a long complicated address.
It does seem to depend on what the web site is and location to get to it.
Could try this address and see if that has an affect.
https://www.tinkercad.com/
@theroar84
I think pupmode can be found here > /etc/rc.d/PUPSTATE
To get the version of Firefox
click the Firefox menu > help > about Firefox
As per @bigpup advice you could also try using a local home page. One on the hard drive or usb. That would tell you if it's a network issue or not.
bigpup wrote: ↑Tue Nov 28, 2023 12:24 amThe Firefox is updated.
That is no information about what version it is?
There are several different Firefox releases.
Not exactly sure what you want to know about pupmodes?
How to find out what pupmode you are running in?
What the different ones are and how they work?
It was 105 something... I said your FF was updated that morning. Sorry I did not give you the number
It was 105 something...
The current consumer version of Firefox is 120.0.1
The current enterprise version of Firefox is 115.4.0esr
Have you solved your problem?
Firefox usually only asked to restore if it crashed. As mentioned above.
To make sure what version of Firefox you have.
In the Firefox window have it set to show the menu bar.
Click on help -> About Firefox
Good call on the version. It is not the PC where I am tying this, so just checked with that one was fired up and it is 120.1 now. It shows the "browser has been updated" quite often though.
I still see the error a ton, but I have just added a line to my xdotool script where it clicks the "Start New Session" button for me.
The issue may still be there, but it is not a bother anymore.
Thanks again for all the tips!
Good point. So.. the issue was for one PC the shutdown did not autosave... I could not figure out what I had done differently. The clues that were shared allowed me to make a smarter search and find out that I simply needed uncheck the "ask box" Puppy Save Session tab in Puppy Event Manager.
No idea when I messed that up, but it been annoying me forever. All fixed now.
Thanks again for all the support.