Discussion, talk and tips
https://forum.puppylinux.com/
This is 64 Xenial JWM.
It does not activate. My inclination is to remaster updating or removing jwmdesk which radky states contains sscontrol:
I did not change sscontrol but set pupx to 60 seconds (1 minute is not an option in this version).
Is JWMDesk 3.0 in Xenial the best idea?
Excusing my intermediate bumbling...
The execution command for SSC is sscontrol. It's not listed alphabetically in the Remove builtin packages list. JWMDesk is not builtin this distro (sscontrol ran from PupControl):
SSC version 2.1 in 32 Hirsute
Begging, what is sscontrol if not builtin as itself or a component of JWMDesk?
Why just update JWMDesk?: http://forum.puppylinux.com/viewtopic.p ... 534#p39534
I am sort of a broken record. Here rockedge mentions using xscreensaver:
viewtopic.php?p=17382&hilit=saver#p17382
bigpup writes about xset.
I just ran another test in 32-bit and it's not the same.
Setting pupX to 60 seconds also sets SSC to 1 minute, and it triggers.
When you have ScreenControl (SSC) you can change the time-steps to increments of 1 minute like this:
Open the sscontrol preferences file (normally found at /usr/local/sscontrol/preferences) by right-clicking it, open as text and edit the time settings in the following lines accordingly:
Code: Select all
<spinbutton width-request=\"100\" range-min=\"1\" range-max=\"300\" range-step=\"1\" range-value=\"1\"
tooltip-text=\"$(gettext ' Select an activation delay (1-300 minutes)
Notes:
1. Changing the time value in pupX is only persistent for the current session whilst the settings set in SSC can be saved during or at the end of the session.
2. I don't think radky (creator of the utility) will mind if you change the time settings in the script for your own personal use but it will be advisable to send him a personal message to inform him in this regard nevertheless.
That could be useful.
What accounts for the experience here?
a) pupX changes SSC's interval to a mark that cannot be done within the gui interface. 32-bit Xenial it works. 64-bit doesn't. The difference being???
If I could change SSC's interval without pupX, if it worked I still wouldn't understand the conflict and it would only exist where I edited the settings.
b) In my second post link Radky writes about a new version of JWMDesk with 1-minute SSC intervals. In Hirsute which is fairly new (peebea just posted a newer), it's still 5-minutes. I am not booting 64 often, but when I do again I'll check Fossa for the increment.
Hence, if you expected 1-minute intervals to be normal in all pups without conflicts, how would that be achieved?
Hacks just for me are better than nothing, but I'm thinking about a universal fix for the problem.
amethyst wrote: ↑Sat Oct 23, 2021 7:33 amWhen you have ScreenControl (SSC) you can change the time-steps to increments of 1 minute like this:
Open the sscontrol preferences file (normally found at /usr/local/sscontrol/preferences) by right-clicking it, open as text and edit the time settings in the following lines accordingly:Code: Select all
<spinbutton width-request=\"100\" range-min=\"1\" range-max=\"300\" range-step=\"1\" range-value=\"1\" tooltip-text=\"$(gettext ' Select an activation delay (1-300 minutes)Notes:
1. Changing the time value in pupX is only persistent for the current session whilst the settings set in SSC can be saved during or at the end of the session.
2. I don't think radky (creator of the utility) will mind if you change the time settings in the script for your own personal use but it will be advisable to send him a personal message to inform him in this regard nevertheless.
JASpup,
do u know something abt the screensaver in Slacko 7.0?
I do not.
My fable goes: Slacko 6 Puppy doesn't have lxrandr or lxtask builtin, two apps I use most. Then realizing significant compatibility differences with Upups, I decided I am not a Slackware user.
I would bet it can be a lot better but can't get over my first impressions.
Positively I found it good for alt-desktops.
I just turned off SSC in 32-Xenial and pupX works without it. Should probably check in reverse. If not architecture my compatibility dilemma might just be a kink in the distro.
Hence, if you expected 1-minute intervals to be normal in all pups without conflicts, how would that be achieved?
Why would 1 minute intervals be the norm or "normal"? It's a matter of personal preference and in fact most users will NOT prefer the screensaver to kick in after just 1 minute. If SSC works on your puppy, my suggestion will /should work. It's not a hack, the actual programming code is not changed but only the preference for the time interval. Radky decided on the 5 minute time step and that is how he released his application and to be fair most users will find that sufficient for their use but I do understand that some (like yourself) may want to specify a different time step and I have given that option/solution. If you use SSC and it works on your system there should not be any "conflicts".
New test:
This is 32-bit Tahr.
I began with pupX off and SSC set to 5 minutes. It activates.
I turned pupX on for 2 minutes. It changes SSC as expected, but does not activate in two. It still activates but takes 5.
Incompatibility bug.
Only use SSC and change the time-step as suggested. The command used by SSC is more comprehensive as far as power management goes.
PupX seems the same in Slacko 7.0, as is in 32 bit Tahr, though it lacks SSC, which has always worked for me in other Puppies.
If I set cycle to 0, is it gonna change the delay?
Not sure I understand your question, but you hit on Slacko's forte -- skipping the packages we expect in Upups, yet this time for the better.
Since both work alone, that's one solution.
Ideally we'd have one minute intervals in SSC or a more user-interface thoughtful pupX.
You'd have to ignore the 2nd screensaver after you determined how it activated which isn't very intuitive since SSC is a big button in JWMDesk.
Overarching issue is not that I cannot get any screensaver to work at all, but that the two coexisting create disfunctioning conflicts. How much should anyone have to think about how screensavers activate to use them?
'SSC is a big button in JWMDesk'
It's not in Slacko 7.0, not even in the buttons offered to add to the Desktop!
That's a problem!
pupX is in Fossa the new lone Screensaver settings tab
both gui windows open, SSC OFF
no trigger events
pupX:
10 sec Apply
60 sec Apply
60 sec "OK" instead of apply (closes gui)
SSC gui closed
pupX opened and reset to 60 seconds
SSC opened - display reads 1 minute ON
pupX reset to 15 seconds
Allow exposures unchecked
[all of the above would not activate screensaver]
trigger event
pupX disabled, SSC 5 min ON
preliminary verdict:
SSC will work in 64 Fossa independent of pupX at 5 min intervals
pupX will not trigger at all
pupX neither appears to interfere with SSC nor have any use since keyboard and mouse tabs are gone.
SSC will work in 64 Fossa independent of pupX at 5 min intervals
It will work independently from pupX nevernind what time interval.
If Slacko 7 has JWMDesk at all, I would be surprised if the screensaver button wasn't SSC.
like my first post:
That button is SSC.
I wouldn't be surprised if Slacko didn't have JWMDesk.
I think Slacko normally has Ptheme.
Other pups have PupControl:
top left window
It calls SSC just like JWMDesk.
Puppy Setup (wizardwizard) has a Graphics/Screen button which leads to a screensaver, which in Fossa's case is pupX (which isn't working).
The point being: there are several configuration utilities which lead to a screensaver which may or may not work, largely due to their being two of them.