-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/rc.d/rc.shutdown: unresponsive Save/No Save' dialog #3986
Comments
Is the woof-CE tree used to build F96 available anywhere? |
I already encountered that problem. My workaround for that (for now) was show dialog whether the user wants to save this session or not right at bootup. I hope there is a better workaround or fix |
dimkr wrote: The original Woof-CE focal64 build used to generate F96 is the following: The current F96 puppy_fossapup64_9.6.sfs is a manual update of the above Woof-CE build, i.e. jwm_config, ptheme, etc are removed and replaced with JWMdesk and companion apps. The F96 init is generated by the recent Woof-CE commit 4a23874 However, the unresponsive 'Save/No Save' dialog is not unique to F96. Also reported, in vanilla dpup https://forum.puppylinux.com/viewtopic.php?p=62654 and @rizalmart has noted the same issue in his builds (presumably QuickPup64 based on the Woof-CE generated ScPup64 21.04). |
@dimkr
My apologies if this issue is partially duplicative of prior issues.
In F96 and vanilla dpup there have been reports of an unresponsive 'Save/No Save' dialog box called by /etc/rc.d/rc.shutdown when the savefile is on USB. This has been reported also for the current F96-CE_3 which has the most recent Woof-CE init (commit 4a23874: search all drives for Puppy files and save when using pmedia=cd).
See following link:
https://forum.puppylinux.com/viewtopic.php?p=83207#p83207
I and several other users can't replicate this issue, but there are now several reports where this is an issue (for some users) when saving to USB via rc.shutdown.
Your thoughts are welcome.
The text was updated successfully, but these errors were encountered: