A bug has just been reported by 'repos':
I have fixed it, and uploaded the PET to the 'common' repo (61KB):
Comments:Posted on 16 Oct 2011, 8:22 by 01micko
I have actually further updated Dougal's network wizard with some fixes for gtkdialog4 (backward compatible with gtkdialog3) and an updated wag-profiles.sh for the brmsmac broadcom drivers, with thanks to tempestuous. This is relevant to to the newer kernels and does no harm with the older ones.
The gtkdialog4 fixes are simply replacing
<input file icon="some-stock-gtk-icon">
<input file stock="some-stock-gtk-icon">
The fix to which you refer is included.
Posted on 16 Oct 2011, 12:55 by 8-bit
Speaking of net-setup, I did a search of the Slackoxxx.sfs file and found that scanpci is missing from it. But it looks like net-setup.sh assumes that file exists.
I have already reported this on the forum as well as major other problems when booting from a Slacko CD with a pupsave on USB. The USB save appears to have problems and app problems start to happen that may be related to the periodic save to pupsave on USB.
Posted on 23 Oct 2011, 3:17 by 8-bit
It seemed that Slacko RC2 still had problems with the splash message "Saving RAM to 'pupsave' file".
But after some investigation, It was determined that a modified "/usr/bin/gtkdialog-splash" script was being used.
That modified version would break /sbin/pup_event_frontend_d as line 522, "YAFPID=$!" was returning two pid numbers.
The solution was to use the version of gtkdialog-splash from Puppy Racy, which shinobar provided in the Slacko RC2 thread.
Using it, "YAFPID=$i" returns only one pid and the yaf-splash message is removed once the save is complete.
Posted on 23 Oct 2011, 8:49 by BarryK
The gtkdialog-splash used in Racy and Wary is actually in Woof, in rootfs-skeleton/usr/bin. This is what gets used in Puppy builds.
Mick must be using some PET that has an alternate gtkdialog-splash that is overwriting the "proper" one.
Posted on 23 Oct 2011, 10:38 by 01micko
Nope, stock woof
Am now using shinobar's. I cannot reproduce the issue, I don't really get why. There are no calls to old yaf-splash that I can find :|