Hello,
I am investigating why the screen blanking won't work with labwc and I feel like I am very close in finding out why I just need some small help. Soo the problem is that labwc compared to wayfire that uses builtin screen blanking config, uses a command to turn off the screen, wlopm, but when I try to use this command to turn off my display I get Failed to set power mode for display DPI-1 in my case, the weird thing is that if I launch a new tty session (Ctrl+Alt+F6) and just type labwc in the terminal (or labwc-pi) the desktop loads fine and when I type wlopm --off DPI-1 the screen turns off! So here I am stuck trying to figure out why the labwc session being launched by lightdm doesn't work with wlopm (I am not sharing any logs because there aren't any even with the -d switch). Also a note, seems like the command raspi-config uses for screen blanking is incorrect, it uses while it should use .
I am investigating why the screen blanking won't work with labwc and I feel like I am very close in finding out why I just need some small help. Soo the problem is that labwc compared to wayfire that uses builtin screen blanking config, uses a command to turn off the screen, wlopm, but when I try to use this command to turn off my display I get Failed to set power mode for display DPI-1 in my case, the weird thing is that if I launch a new tty session (Ctrl+Alt+F6) and just type labwc in the terminal (or labwc-pi) the desktop loads fine and when I type wlopm --off DPI-1 the screen turns off! So here I am stuck trying to figure out why the labwc session being launched by lightdm doesn't work with wlopm (I am not sharing any logs because there aren't any even with the -d switch). Also a note, seems like the command raspi-config uses for screen blanking is incorrect, it uses
Code:
swayidle -w timeout 600 'wlopm --off \\*' resume 'wlopm --on \\*' &Code:
swayidle -w timeout 600 'wlopm --off \*' resume 'wlopm --on \*' &Statistics: Posted by steveiliop56 — Sun Jun 16, 2024 9:34 am