I've lost the ability to change the brightness of my monitor

[dragonfly41]

I don't understand what you are trying to achieve, though.

Sorry to drop you in the deepend without swimming lessons.
Better to forget about actexec command. Only required when running a batch of Actiona scripts.
All you require for experimenting is the GUI. Hit Alt + F2 dialogue and run .. actiona .. (no capital) to launch GUI. Each code can be run with System > Command widget.
The first line is simply the app .. xrandr
Then parameters follow on next line.
Set name of output .. e.g. output
This is a variable .. $output .. which can be printed in Console widget

But let me find time in next day or so to write a sample. You can think of each script as a mini workflow.

[Paddy Landau]

But let me find time in next day or so to write a sample. You can think of each script as a mini workflow.

Thank you. But, could I ask, what would be the point of this? The xrandr command works perfectly; it's something else in the background that changes the brightness every 60 seconds.

[dragonfly41]

Paddy, the suggested Actiona tool is no more than a repository of custom experiments. a testbed.

Often one is “scraping” forum discussions for ideas and running various commands to test ideas. I tend to "cherry pick" and place them in Actiona scripts to be run as "micro workflows".
If you are happy still copying and pasting code snippets then don't bother.
But I have created a little Actiona container which holds various experiments and links to their sources.

Some time back there was an app named clicompanion (still around) which held collections of commands.

Returning to your issue:
This thread for example cites the "60 seconds timeout" you cite.
https://askubuntu.com/questions/1247...ery-60-seconds

And the answer:

For anyone who comes through the same trouble : it was really caused by the night light setting.

This next thread suggests a bash script.
https://askubuntu.com/questions/1150...e-using-xrandr

This thread is interesting.
https://askubuntu.com/questions/1003...ght-like-usage

And here is a useful Python script

https://askubuntu.com/questions/672640/desktop-monitor-brightness-adjusting?noredirect=1&lq=1


I embedded these experiments into an Actiona container. Each within a Procedure.


I like the Python script since I can embed that into Albert (another useful tool).

...

If you are interested in how I build these cherrypicked ideas into Actiona scripts I can post a demo, or you can do it yourself. I use Actiona for all classes of experiments and workflows.

Another example is holding TheFu advice on rdiff-backup.

And for accessing and automating all types of services. Auto login.

[tea for one]

Some gnome extensions have been designed to control screen brightness.
A few of them mention https://www.ddcutil.com/

Paddy, not wanting to send you on a wild goose chase but maybe worth a little investigation.
I have no experience of these extensions nor ddcutil, just offering info.

[Paddy Landau]

This thread for example cites the "60 seconds timeout" you cite. … night light

That's interesting! It's been behaving today, but as soon as I manually enabled the Night Light, the problem returned!

I shall experiment a little with that, and add the information to the bug report. It might have been that I normally log into the computer before sunrise, so Night Light was on right from the start.

The other scripts are informative, thank you.

Some gnome extensions have been designed to control screen brightness.
A few of them mention https://www.ddcutil.com/

Thank you. I'll have a look.

[Paddy Landau]

Update:

This does indeed seem to be linked with the Night Light. When I turn Night Light either on or off, the problem immediately recurs. If the Night Light remains on, the problem happens every 60 seconds.

I haven't checked if it always happens while the Night Light is turned on, or if there are times when it takes a break, but this is extra information for the devs, so I'll add it to the bug report.

[dragonfly41]

I'll get back to chasing my own flock of wild geese. I did not get around to posting embedded experiments in Actiona but you get the point. It is a container for such multiple choice experiments but one of choice. I believe that if Redshift is disabled/uninstalled this eliminates Night Light. But I cannot see Night Light settings in my Settings. I understand that it depends on what session is chosen at desktop user login point (there are multiple choices and I started on "Ubuntu" but have tried others at login stage).

[Paddy Landau]

I cannot see Night Light settings in my Settings.

Settings > Screen Display (on the left) > Night Light (at the very top)

It should be present for both Wayland and X.Org.

[dragonfly41]

Sorry, I don't see that just now. I have been running my own experiments to track down cause of (a) wired mouse freezing and (b) no connection to Bluetooth Logitech Mouse/Keyboard (but ok with Bose audio). This wild goose entails trying different sessions and (without rebooting to check) I think my last boot was into Metacity. I'll try selecting Xorg again.

[P.S] adding more info. Since posting above I have tried three sessions.

Gnome Flashback (Metacity)
Gnome on Xorg
Ubuntu on Wayland .. current session

All on Ubuntu 20.04.

None show Night Light.

But this might be due to me using an ancient Philips screen. At a guess.

Oops. Mouse going crazy again.

[Paddy Landau]

None show Night Light.

What's your kernel version?

Good luck with your mouse!