AVL 23.1: issue with backlight [Solved]

[Charlie Brown]

You can try this:

"Job Scheduler" , press Ctrl + U (start as root)

Time:

Code: Select all

@reboot

Command:

Code: Select all

echo 60 > /var/cache/brightness-settings-cache/sys/class/backlight/nv_backlight/brightness

Save, close, reboot.


(... Or whatever value you like rather than 60 )


That will be a fixed setting of course. Alternatively:

Code: Select all

echo $(cat /sys/class/backlight/nv_backlight/brightness) > /var/cache/brightness-settings-cache/sys/class/backlight/nv_backlight/brightness

[seriousness]

https://wiki.archlinux.org/title/Enlightenment says:

1.7.12 Backlight always dimmed

You may find that Enlightenment routinely dims the backlight to 0% on logout and will only restore it to 100% when you log into another Enlightenment session. Enlightenment assumes that whatever comes after it will set the backlight to whatever it prefers, if anything as this is what Enlightenment does at start. This is especially problematic when using another desktop environment alongside Enlightenment that cannot control backlight as the backlight will not automatically be restored to its normal level when using that desktop environment. To fix this issue, open the Enlightenment Settings Panel and, under the Look tab, click on the Composite option. Tick the Don't fade backlight box and click OK.

Will try that tomorrow...

[Charlie Brown]

Good info. Then probably that's due to DE.

[AVLinux]

I will say this as more and more Users report issues...

The Enlightenment developer is very outspoken about using systemd with Enlightenment, mentioning sysvinit on their IRC will get you lots of jeers and eye-rolling although in my experience Enlightenment by and large works OK for most purposes with the MX/antiX live system but it seems for the best performance it is probably recommended to switch to systemd once you install AV Linux, I had another post elsewhere about a User that couldn't get the Evolution mail client to work unless he switched boot to systemd and since Evolution is super Gnome-y that shouldn't be a big surprise I suppose. In some recent related experiments with Enlightenment's Moksha fork (ie Bodhi Linux) I found it is even more dependent on systemd to the point of needing a lot of duct tape to work at all with sysvinit..

To be clear I personally have absolutely no preference for any init system and AV Linux tries to be as apolitical as possible and just present a good workstation, my general stance is that if you find systemd boot works better, use it!

[Charlie Brown]

Meanwhile I notice just now that I overlooked one point:

To fix this issue, ... Tick the Don't fade backlight box and click OK.

If it was due to a setting (an unchecked setting ootb), then why is it ok on systemd ?

[dolphin_oracle]

systemd has the concept of user services, services that run when a user logs in. its possible that sort of thing is in play.

[seriousness]

I marked this as solved.

If anyone has the same problem and stumbles upon this thread:

To fix this issue, open the Enlightenment Settings Panel and, under the Look tab, click on the Composite option. Tick the "Don't fade backlight" box and click OK.

On your next boot with SysVinit, you have to login blindly once again, but from then on it will work.