Going back to the problem of lifeograph refusing to run,
While experimenting a bit with Gnome MPV which is also GTK3, I discovered that the issue seems to be that icon resources are missing.

The default icon theme for GTK3 is adwaita-icon-theme
If I install this in Bionic32 via PPM, lifeograph from PPM will then run.
There is a cut-down version of this icon theme in Ubuntu, but it drags in other icon theme stuff as "dependencies" and ends up quite large.

We seem to get away with just having libgtk-3 on board to get the browsers running, but if we want Puppy to be able to run other GTK3 stuff in future I think someone will need to take a look at the issue of themes and icons for it. Even with the browsers there are missing icons in the chooser dialogs. Maybe I will start another thread about this, but it will be in the hope that others with better understanding than me can suggest what could be included without adding too much unnecessary bloat._________________Oscar in England

I'm now having to manually run the wizard in this Pup and some other Pups that I felt sure I did not have to do not long ago.

I am changing from an ethernet connection on the home network to wifi.

This does slow down the connecting process a bit so could it be a timing issue - the wizard gives up too soon.

The Simple Network Setup (SNS) wizard is definitely affected, and I'm now trying Frisbee (haven't restarted yet). I think Dougals wizard is also in the 'now won't start at boot-up' camp.

SOLUTION (Cause): I had made links of the wizard config files residing in /etc to my data partition to share the profiles between Pups.
Alas, I now see that the wifi connection process starts up before the data partition is mounted by the script in /root/Startup .
So there is effectively no profile for the wizard to use during booting.
I have to find a way to do this perhaps in one of the Pup's sfs drv files, or create just one for these links to include with each Pup - a l-drv (links drive)
maybe?

I'm now having to manually run the wizard in this Pup and some other Pups that I felt sure I did not have to do not long ago.

I am changing from an ethernet connection on the home network to wifi.

This does slow down the connecting process a bit so could it be a timing issue - the wizard gives up too soon.

The Simple Network Setup (SNS) wizard is definitely affected, and I'm now trying Frisbee (haven't restarted yet). I think Dougals wizard is also in the 'now won't start at boot-up' camp.

SOLUTION (Cause): I had made links of the wizard config files residing in /etc to my data partition to share the profiles between Pups.
Alas, I now see that the wifi connection process starts up before the data partition is mounted by the script in /root/Startup .
So there is effectively no profile for the wizard to use during booting.
I have to find a way to do this perhaps in one of the Pup's sfs drv files, or create just one for these links to include with each Pup - a l-drv (links drive)
maybe?

David s.

David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.

David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.

If you do, remember that scripts in /etc/init.d get called during startup with a parameter of "start" and again at shutdown with a parameter of "stop".

David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.

Thanks for the advice.
I had already seen the name "0_" prefix idea and use it with my mount script in Startup for all my Pups.

I've now tried your tip with /etc/init.d in today's first Pup (LxPupSc-19.04 with the 64-bit 5.0.5 kernel) and it is looking fine. I also added to /etc/init.d a script to load a temperature module now that Boot manager is broken in quite a few Pups (most Bionics I think, Sc (Slackos) are still OK, but this is simpler than running Boot manager anyway).

So I'll slowly work through my Pups with this init.d refinement, and add to new Pups as they come along.

When I try to copy the updated files (usually just puppy*.sfs) to frugal install directory, I get "protected file system, won't copy" or something like that. I'm on an older BionicPup, so how do I force the copy?

Actually I'm using a fresh iso and delta.
Also, I tried to delete the adrv file, wouldn't let me do that either.

Um....You need EITHER the latest ISO, OR the ORIGINAL ISO plus the latest delta. If you have the latest ISO, you do not need the delta. If you only have the ORIGINAL ISO and the latest delta, you have to apply the delta to the ISO to produce the latest ISO.

Um....You need EITHER the latest ISO, OR the ORIGINAL ISO plus the latest delta. If you have the latest ISO, you do not need the delta. If you only have the ORIGINAL ISO and the latest delta, you have to apply the delta to the ISO to produce the latest ISO.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum