Puppy Linux Discussion Forum

I installed Fossapup64 and it seems to work quite well. I have one small problem though. I configured PUPMODE=13. On shutdown the dialog box to save session data ignores all keyboard input including Esc. After 60 seconds it continues without saving.

I read /etc/rc.d/rc.shutdown and the dialog command seems correct. I then tested the dialog command in a console window under X and it works. I then tried to test the dialog command in the raw console (after exiting X). However after exiting X using the menu the raw console is dead, i.e., not responding to keyboard input. I then tried CTRL + ALT + BACKSPACE to exit X and again the raw console is dead.

This is not a big problem as I just save using the desktop save icon before shutting down and I changed the timeout on the dialog to 5 so I don't have to wait 60 seconds.

This problem may be specific to my hardware which is a Dell Inspiron 11 model 3180 laptop with a AMD A6-9220e CPU running Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] (rev eb).

ADDENDUM

I should have mentioned that on this same machine I run BionicPup64 with PUPMODE=13 and the save session dialog works every time and exiting from X using CTRL + ALT + BACKSPACE (which I do often) always gives a working raw console. Something has changed from BionicPup64 to Fossapup64.

ANOTHER ADDENDUM

Well if you are like me and use multiple versions of Puppy and only for FossaPup64 do you need to manually save before shutting down you will forget to do this and end up losing an entire session worth of data! My workaround for this is to remind me to save when I shutdown. To do this I edited /usr/sbin/logout_gui changing the line

  poweroff)exec wmpoweroff ;;

to

  poweroff)exec mc-wmpoweroff ;;

and adding two files to /usr/bin.

/usr/bin/mc-wmpoweroff:

#!/bin/sh

rxvt -e mc-have-you-saved-session-dialog
PRESHUTDOWNCHECK="`cat /tmp/mc-pre-shutdown-check.txt`"
[ "$PRESHUTDOWNCHECK" != "session saved" ] && exit
exec wmpoweroff

/usr/bin/mc-have-you-saved-session-dialog

#!/bin/sh

echo -n "session not saved" > /tmp/mc-pre-shutdown-check.txt
dialog --title 'Session Saved Confirmation' --colors --yesno '\Z1Have you saved the session? No will abort the exit.' 5 60
[ $? -eq 0 ] && echo -n "session saved" > /tmp/mc-pre-shutdown-check.txt

m-cuda wrote: ↑Fri Sep 25, 2020 5:41 pm I installed Fossapup64 and it seems to work quite well. I have one small problem though. I configured PUPMODE=13. On shutdown the dialog box to save session data ignores all keyboard input including Esc. After 60 seconds it continues without saving.

I read /etc/rc.d/rc.shutdown and the dialog command seems correct. I then tested the dialog command in a console window under X and it works. I then tried to test the dialog command in the raw console (after exiting X). However after exiting X using the menu the raw console is dead, i.e., not responding to keyboard input. I then tried CTRL + ALT + BACKSPACE to exit X and again the raw console is dead.

This is not a big problem as I just save using the desktop save icon before shutting down and I changed the timeout on the dialog to 5 so I don't have to wait 60 seconds.

This problem may be specific to my hardware which is a Dell Inspiron 11 model 3180 laptop with a AMD A6-9220e CPU running Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] (rev eb).

I configured PUPMODE=13

• initrd.gz and vmlinuz has been loaded into RAM.

• vmlinuz has started executing.

• vmlinuz has mounted the partition where the *.sfs exists.

• vmlinuz has created the loopbacks for the *.sfs files and mounted these loopbacks.

menu item "Exit" -> "Exit to Prompt" I again get a dead console.

used Rufus to create a UEFI bootable drive

menu item "Exit" -> "Exit to Prompt" I again get a dead console.

That is a different problem.

Hi all,
I'm a new Puppy Linux user (fossapup64 9.5), experiencing exactly the same issue described at the beginning of this post (dialog box to save session at shutdown ignoring all keyboard input). Thanks to m-cuda for the hint on setting the timeout to 5! I haven't tried the workaround yet.

It occurs on only one of my two laptops, a Lenovo V145 (AMD A4-9125 RADEON R3, 4 COMPUTE CORES 2C+2G).
Originally, I discovered it booting from an iso USB setting boot parameter pmedia=usbflash, i.e. PUPMODE=13, in order to avoid writing continuously the save file onto the USB.
Then I tried a frugal install on a HD directory (this time I used pmedia=ataflash) and the same thing happened.
I haven't twecked anything else and the system is working just fine, especially on the other, much older, HP laptop (not experiencing this problem).
Just willing to check if I can use it in this way also on the Lenovo one.

For what it's worth, I just want to add my voice to this issue in the hope that someone will eventually address it.
I am experiencing this same problem on multiple machines, two are Dells and one an Acer. I have no fix or workaround except (as suggested) to change the timeout and manually save before a shutdown. (Which saves a lot of time -- thank you.)
I do find that every once in a while the dialog IS responsive, which seems to occur if I haven't done much or been running very long. But if I've been doing anything for any length of time then the dialog is completely unresponsive.

I am running Fossapup64 9.5 in pupmode 13.
Fully updated by Quickpet->Info->Fossapup Updates
A frugal install on a USB flash drive.
I have it running in pupmode 13 by using the correct pmedia=usbflash in the boot loader menu config file entry.

In Puppy Event Manager->Save Session
First it says I am in pupmode 13.
Save interval st to 0.
Ask at shutdown to save is checked.

Save icon on desktop works.
Ask at shutdown works.

Always save at shutdown also works.

If you have it set to always save at shutdown.
Do understand it could take a long time to completely update the save.
Depending on the speed of the drive and amount of stuff.
It could take several minutes.
All you will see is saving to save message........

It can look like it is hung, because there is no moving indicator saving writes are being done.

Where are the savefiles being stored? What type of device?