Puppy Linux Discussion Forum

[musher0]

Dec. 7, 2013. Please get latest version from here:
http://murga-linux.com/puppy/viewtopic.php?p=742075&sort=lastpost#742075
~~~~~~~~~~~~
Edit, Nov. 30, 2013. Effort to re-organize this initial post.
For the solutions and other comments that
used to be posted here, please read down from:
http://murga-linux.com/puppy/viewtopic.php?p=740519&sort=lastpost#740519
~~~~~~~~~~~~~~~~~~~~~~
What follows is the "thinking process".
~~~~~~~~~~~~~~~~~~~~~~
Edit: Please see message below this one. It seems that the wmreboot
and wmpoweroff scripts from wary-5.5 are the ones that make the
difference, since the /etc/rc.shutdown scripts from CE-3 and wary-5.5
are identical. See illustration.

musher0
~~~~~~~~~~~~~~~~~~~~~~
Hello, all.

Here's a copy of an exchange I just had with 01micko concerning said
bug. It explains the faulty process, and the solution, which is provided
as a pet file.
~~~~~~~~~~~~

[musher0]

Additional note:
~~~~~~~~~~
Hello again, all.

It seems that rather the wmreboot and wmpoweroff scripts from
wary 5.5 (included in this pet archive) make the difference.
In any case, all three scripts are included in the above pet.
Karl_Godt and o1micko are also on the case and should
report shortly.

Thanks for your understanding.

musher0

[musher0]

The problem:

[musher0]

Hello again, Puppyists.

I did a couple more tests, and I don't know what to tell you anymore...

Sometimes, installing the pet above did solve the problem, and the
pupsave file was created. At other times, it wasn't, with the same
replacement files loaded.

Is it a matter of the speed of entry of the variables in the successive
panels? (I can be a very fast typist...) I'm at a loss for a logical
explanation. Hopefully Karl or Mick will come up with something.

In any case, there remains the solution of "implanting" a ready-made
pupsave file, and that works without fail. Please see how-to and download
archive here:
http://murga-linux.com/puppy/viewtopic.php?p=737783&sort=lastpost#737783
You'll have to adapt the name of the pupsave files according to the name of your Puppy.

BFN.

musher0

[musher0]

Hello again.

For the sake of thoroughness, here are diff transcripts concerning
wmreboot and wmpoweroff for CE-3 and wary 5.5. Since it's the first
time I've used the Linux diff, I hope the significant information is
there. I'm used to parallel reading in other contexts (FreeDOS and
proof-reading/text-editing), but this is Martian to me. Hopefully this
will mean something to someone.

That's my maximum testing capacity. I can go no further. Someone
with more advanced skills will need to tackle and hopefully resolve
this problem. BFN.

musher0
~~~~~~~~~~~~~~~~

[musher0]

Hello, Puppyists.

I just tested 01micko's latest slacko-5.6.1 and discovered that if I
replaced this slacko's rc.shutdown script in /etc with the one in rerwin's
latest sulu, I got a pupsave file. Two actually, one created from the GUI
and one created from the CLI. Now, that's service!

So please find attached this replacement rc.shutdown file.
Replace/use at your own risk.

BFN.

musher0

[Karl Godt]

Yeah, the /usr/sbin/shutdownconfig is something new , and I still have to find out, which parts of the

DIALOGEXE="pupdialog"
DIALOGEXE2="Xdialog"

can be aborted by pressing ESC , so it gives a return value of likely 255 like the blue-screen dialog .

/usr/bin/wmreboot has code as

if [ $PUPMODE -eq 5 ];then #first shutdown.
shutdownconfig #dlgs for creating save-file.
#...writes results to /tmp/shutdownconfig_results, which /etc/rc.d/rc.shutdown reads.
[ $? -eq 255 ] && exit #abort shutdown. 130221

so would likely exit without confirmation message .

/usr/sbin/shutdownconfig can be run in rxvt terminal without actually not shutting down in the end .
So then it would be possible to examine the created files in /tmp :


orange_gtkrc${$}
shutdownconfig_deftag
tag.txt
shutdownconfig_encrypt_password
shutdownconfig_results

sizetag.txt
rc.shutdown_pupsave_fs
schoices.txt
ntfsmnterr.txt
savedlg



For now I suspect locale / LC_ALL settings somehow , since at the top of
shutdownconfig it is

if [ ! $DISPLAY ];then
export LANG=C #110928 console shutdown using 'dialog', disable i18n.
else
export OUTPUT_CHARSET=UTF-8
fi

and Lupu wasn't gettext 'ed at that time .

[musher0]

Finally. Help from Above!

[Karl Godt]

Yeah, Man !!

This applies to everything Puppy related :

grep -I -H -m3 WORD /usr/sbin/*

like

grep -I -H -m3 'shutdown' /usr/sbin/*

should give you some filenames that contain shutdown .

/usr/sbin/* because most of the Puppy scripts are there .

But few are in /bin and /sbin and /usr/bin and /usr/local/bin .

So grep there too, if unsure .

Then open the files in geany and become enlightened .

And post suggestions / patches .

HTH a bit .

[Flash]

Would this bug affect multisession Puppy?

[Karl Godt]

Since MS does not use a save-file, I guess not .

But by far am no Multi-Session expert . My current machine has no CD drive .

[musher0]

[musher0]

[Karl Godt]

What's that's for a high load ? P4-Cpu while performing mtpaint ?

[01micko]

musher0

From your screeny, there is a first bug which doesn't tell us the filesystem of the partition.. that will throw a mount error and therefore that filesystem will be reported as 0 (zero), then I think there is some weird thing in there that subtracts 1M for some reason. Barry's procedural approach is not very friendly to follow, I'd much rather decipher Shinobar's code, where everything is broken down into functions, much more maintainable.

Please tell us what filesystem is on sda2? Maybe the driver isn't loading? (not likely if it's linux, I can't tell from the reports you sent ). One remote possibility is that probepart is misreporting the filesystem (possibly a locale error? or do you do this with an English based locale? Oh, I guess you do as the other screeny, in GUI, has English as the displayed language.. just trying to eliminate possibilities).

Also, if you can produce a successful save just by running shutdownconfig in terminal can you post the log at /tmp/shutdownconfig_results

Thank you.