|
|
Post by trawglodyte on Feb 6, 2024 18:10:59 GMT
Hi. I put Moksha Desktop on BookwormPup64_10.0.4 (a Puppy Linux distro). I've never tried something like this before, but it wasn't as hard as I thought and it's mostly working great! (Not as great as on Bodhi, there's a couple kinks to iron out) but I expected much more. I think it's going to work out quite well!
I'm going to dig into the documentation and figure it out, I just like to click around awhile first. There's some minor things with certain apps not displaying in a readable way that I know will be easy to remedy when I learn where the settings for that are. But there is also one issue with reboot and shutdown I discuss at 26:40 in the video that I need to figure out and haven't yet. If anyone has an idea on that, let me know. thanks!
|
|
|
|
Post by trawglodyte on Feb 6, 2024 18:24:23 GMT
Hello and welcome You apparently need to check /etc/enlightenment folder for sysactions.conf file. This is the file content: pastebin.com/xLM0MDp7Stefan Hi Stefan, I don't think /etc/enlightenment/sysactions.conf is the issue in this case. I am root in BookwormPup64 (as with all Puppy Linux by default). I did try commenting out the last line in sysactions.conf to make sure, and adduser root adm to make double-sure. I think it's something else. |
|
|
|
Post by thewaiter on Feb 6, 2024 18:36:50 GMT
Oh wait. I just briefly watched your video. I can see it now. I thought your both buttons are disabled. I think you simply need to close OBS app. OS can not reboot while it is running.
BTW, feel free to join us on discord forums. I can explain more for you. I can see some Moksha usage which can be more effective.
Stefan
EDIT: yes, I will add left and right windows borders in Ice theme for resizing.
|
|
|
|
Post by thewaiter on Feb 6, 2024 19:33:28 GMT
Left/Right border resize areas commited
|
|
|
|
Post by trawglodyte on Feb 6, 2024 22:25:57 GMT
I would not be surprised if the reboot/shutdown gliche is due to running Puppy Linux in "pupmode13". It's a unique thing to Puppy where the OS is loaded into RAM and prompts you at shutdown or reboot to ask if you want to save (write changes to disk) or not. You can opt to not save and then when you boot in the next time your file directory is in the exact condition as the last time you made a save. Anyway, it's not a problem with Moksha IMO. I'll do a workaround for a bit and if I come up with a real fix I'll put it here.
|
|
|
|
Post by ylee on Feb 7, 2024 19:46:04 GMT
... I don't think /etc/enlightenment/sysactions.conf is the issue in this case. I am root in BookwormPup64 (as with all Puppy Linux by default). I did try commenting out the last line in sysactions.conf to make sure, and adduser root adm to make double-sure. I think it's something else. If you look at the sysactions.conf file you will see the commands being run by default: action: halt /usr/bin/systemctl poweroff
action: reboot /usr/bin/systemctl reboot
action: suspend /usr/bin/systemctl suspend
action: hibernate /usr/bin/systemctl hibernate
I did a frugal install of BookwormPup64_10.0.4 and systemctl is not even installed and neither is systemd. This is the source of your problem. I am unsure even if systemd would do a proper puppy shutdown or reboot as I tested the reboot command and puppy thought that was a bad shutdown. What you need is commands for these four sysactions that work for puppy and I think the system controls would work. I think wmrestart to reboot and wmpoweroff to shut down works but I am unsure if this is a safe shutdown for puppy. Perhaps the file logout_gui_jwm holds some clues esp with regards to suspend. |
|
|
|
Post by ylee on Feb 7, 2024 19:58:10 GMT
A few more notes: ... I am root in BookwormPup64 (as with all Puppy Linux by default)... Yes I noticed that seems to be a puppy tradition but it is not at all safe and one should not run a WM as root. Besides that is a problem for moksha and our Mixer module. I am surprised it is even running. Last time I look at running moksha as root it goes into an infinite loop trying to start pulseaudio ... but that was on a Ubuntu install. That would be the moksha-menu package look in /etc/xdg/menus/ and edit as you would like or install and or use another menu package. |
|
|
|
Post by trawglodyte on Feb 8, 2024 21:10:36 GMT
"systemd is not even installed"
Puppy is unique! While a bit confusing for people from other Linux distros it also has some abilities other Linux distros don't, and it's really just a lot of fun! But, ummm, yah, Puppy people don't do systemd and I found out why we don't do gvfs either and use pmount for partitions and devices, and file directory only in the file manager. I did add gvfs and was using it with Thunar, but I decided against it.
It took me a few hours to realize I don't need a menu button, I can just click anywhere on the screen and get it with Moksha! I love that. And when I right-click I get my favorites, which are terminal, text editor, file manager, and pmount. Where has that been all my life!! Maybe other desktops do that and I just never figured it out before, but being able to right-click anywhere and get those just made me a lot speedier!
I also found the setting that lets me adjust how fast the menu scrolls! Hahaahaaaa!! I have it scrolling like lightning now.
|
|
|
|
Post by trawglodyte on Feb 8, 2024 21:21:11 GMT
I looked into jwm's shutdown and reboot stuff for a bit, and kind of have an idea what's going on. Right now I just open a terminal and type reboot or poweroff. I might just make a couple scripts and desktop entries to put buttons for that. I mean, that would drive a lot of people crazy to have buttons that actually shutdown or reboot without a warning or additional dialogue box. But I've done it before just for fun.
|
|
bumpus
Member
Posts: 16 
Likes: 6
|
Post by bumpus on Feb 8, 2024 21:48:28 GMT
For software that requires you run as user, in Puppy you start it with "run-as-spot" Thats the default user in Puppy. Though you can add users just like any other distribution. I think some have opted to run only as user in Puppy. Remember though you can theoretically do a full install of Puppy, its recommended to run Puppy in "frugal mode" with a save folder(recommended) or file. its not meant as a full on system for a business or something. On a computer owned by the user, that only has one user, running as root isnt that big of a deal, well if you have any common sense. The user thing was on multiuser computers where you dont want all users have root powers, and some users more powers than others. But each to their own, lot people feel strongly about not running as root. Its even possible to run as root in systems that dont allow you a root account, just give one "user" root powers. Still have to type sudo but dont have to enter password every little bit. You get used to Puppy running in root, it feels like big brother micromanaging with the passwords forcing you to give yourself permission to do something. But since nearly all linux except Puppy discourage running as root, you gotta get used to the sudo stuff. I swear I have even found myself typing sudo in Puppy. Its meaningless to do this, but it doesnt object.
|
|
|
|
Post by ylee on Feb 9, 2024 11:52:15 GMT
"systemd is not even installed"
Puppy is unique! While a bit confusing for people from other Linux distros it also has some abilities other Linux distros don't, and it's really just a lot of fun! But, ummm, yah, Puppy people don't do systemd and I found out why we don't do gvfs either and use pmount for partitions and devices, and file directory only in the file manager... I already knew puppy lacked systemd and used another init system. I only mention that because moksha is configured to use systemd for the sysactions that are not working. In the /etc/enlightenment/sysactions.conf file if you change: action: halt /usr/bin/systemctl poweroff
action: reboot /usr/bin/systemctl rebootto action: halt /bin/wmpoweroff
action: reboot /bin/wmrestart reboot and shutdown will work from Moksha menu as expected. You could probably also use the reboot or poweroff commands. Logout and lock screen work as expected. So that leaves suspend and hibernate not working. Hibernate is not going to work on Bodhi anyway unless the users configures the system to support it and probably we should have code somewhere that greys that menu item out UNLESS hibernation is possible. But I would think with Puppy you would use acpi stuff here to suspend. From the Puppy's file /usr/local/jwmdesk/logout_gui_jwm: # define Suspend option for laptops/notebooks (button-8)
if [ ! -x /tmp/suspend2ram.sh ]; then
if [ -f /etc/acpi/actions/suspend.sh ]; then # override restrictions imposed by suspend.sh when usb media mounted
if [[ $(grep 'DISTRO_TARGETARCH' /etc/acpi/actions/suspend.sh 2>/dev/null) ]]; then
cat /etc/acpi/actions/suspend.sh > /tmp/suspend2ram.sh
sed -i '0,/DISTRO_TARGETARCH/s/x86//' /tmp/suspend2ram.sh
else
grep -Ev 'mount|^USB|^for|^do' /etc/acpi/actions/suspend.sh > /tmp/suspend2ram.sh
fi
chmod 755 /tmp/suspend2ram.sh
else
echo '#!/bin/sh
echo -n mem > /sys/power/state' > /tmp/suspend2ram.sh
chmod 755 /tmp/suspend2ram.sh
fi
fi
export suspend2ram="/tmp/suspend2ram.sh"
func_suspend(){
usbmounted=""
USBS=$(probedisk2|grep '|usb' | cut -d'|' -f1 )
for USB in $USBS
do
mount | grep -q "^$USB" && usbmounted="true"
done
[ "$usbmounted" = "true" ] && $DIALOG -timeout 4 -text " $(gettext 'Do not remove USB flash drive !')" /
$DIALOG -timeout 2 -text " $(gettext 'Suspending to RAM...')" /
${suspend2ram} 2>/dev/null &
}
export -f func_suspendSo maybe one could just use the command /etc/acpi/actions/suspend.sh or create a script using the idea from this file and run it instead. |
|
enigma9o7
Crew Member
Posts: 1,437
Likes: 1,338
|
Post by enigma9o7 on Feb 9, 2024 16:18:57 GMT
looks like the youtube account from first post has been terminated. yikes
|
|
|
|
Post by trawglodyte on Feb 9, 2024 17:34:52 GMT
In the /etc/enlightenment/sysactions.conf file if you change: action: halt /usr/bin/systemctl poweroff
action: reboot /usr/bin/systemctl rebootto action: halt /bin/wmpoweroff
action: reboot /bin/wmrestart or create a script using the idea from this file and run it instead./bin/wmpoweroff and /bin/wmrestart didn't work, but the following does.
#cd /root/my-applications/bin
#nano reboot.sh #nano poweroff.sh #chmod a+x reboot.sh poweroff.sh
#nano /etc/enlightenment/sysactions.conf #save2flash
This does integrate a working reboot and poweroff into Moksha Desktop's graphical menu on BookwormPup64_10.0.4. But it will reboot/shutdown without giving the "save" option Puppy Linux users may be used to. You have to make your save before rebooting or shutting down this way. Either with the icon on the desktop or #save2flash in terminal.
|
|
|
|
Post by ylee on Feb 12, 2024 12:44:13 GMT
Not ignoring this, just I am rather occupied with other tasks. First I really do not understand the need to create scripts in /root/my-applications/bin which merely run one command. why not just use the commands themselves in /etc/enlightenment/sysactions.conf? Use a script to run a single command is harmless just a minor delay but it adds complexity. ''' /bin/wmpoweroff and /bin/wmrestart didn't work, ...
wmpoweroff, wmreboot and so on should work. They should have nothing to do with the windowmanager. It is a shell script did you look at it? In enlightenment for restart it should end up running echo -n "reboot" > /tmp/wmexitmode.txtand then logging out of enlightenment (by killing enlightenment). If PUPMODE is 13 or 66 it may run /sbin/asktosave_session --file. This is based on my reading of the file (NOTE wmexit and wmreboot wmpoweroff restartwm are all the same file, 3 are symlinks) Doesn't wmreboot et al work in terminal for you? This raises another question what is your PUPMODE and how did you install or how are you using Puppy? . /etc/rc.d/PUPSTATE
echo $PUPMODEPUPMODE seems to be based on how puppy was installed and all the various scripts used in the shutdown process check this and for odd-numbered PUPMODEs it may ask you to save the session (depends on ASKTOSAVE variable in /etc/eventmanager file). Way to much detail about all this here: HOW PUPPY WORKS. Again this is based on my limited understanding of all this and I only skimmed over that article on the inner workings of Puppy. Since I installed on a VM and installed on a clean HD my PUPMODE is 12. wmreboot and friends work fine in /etc/enlightenment/sysactions.conf. So clearly I am confused if wmexit and its symlinks do not work for you. Btw the save session stuff you want is /sbin/asktosave_session --fileWhatever scripts you end up if all else fails you can it directly to your scripts. And one more note: you can use /sbin/logout_gui Whatever scripts or commands you use SHOULD WORK regardless of PUPMODE. For more details look at /etc/rc.d/rc.shutdown which i take it is what is ran at shutdown. Really this shutdown process in Puppy seems to be a small maze of scripts executed and which scripts depends on the values of various variables set in config files. |
|
