> I've found something that may be useful both for diagnosis and as a
> workaround.
>
> If you define a "display-setu-script" in the lightdm configuration, like
> this:
>
> [SeatDefaults]
> display-setup-script=/path/to/display-setup.sh
>
> and put this command in the "display-setup.sh":
>
> xset dpms 120 125 130
I tried this myself a while back and noticed the same thing: something
resets X server DPMS settings after the xset command has executed. Has
any Ubuntu representative considered the possibility that this bug may
cause burn-in-problems for displays over a longer period ? Not to
mention the obvious power waste.
I will be applying your delayed xset work-around script, thanks for that
idea.
Eugene Crosser <email address hidden> writes:
> I've found something that may be useful both for diagnosis and as a setu-script" in the lightdm configuration, like setup-script= /path/to/ display- setup.sh
> workaround.
>
> If you define a "display-
> this:
>
> [SeatDefaults]
> display-
>
> and put this command in the "display-setup.sh":
>
> xset dpms 120 125 130
I tried this myself a while back and noticed the same thing: something
resets X server DPMS settings after the xset command has executed. Has
any Ubuntu representative considered the possibility that this bug may
cause burn-in-problems for displays over a longer period ? Not to
mention the obvious power waste.
I will be applying your delayed xset work-around script, thanks for that
idea.
Øyvind