Keep screen on all the time - Fluxbox [Solved]

[unklebonehead]

Good morning all!
I'm using AVLinux with KDE Plasma. I had previously removed XFCE and openbox about a month ago and it runs fine. No complaints so far. Yesterday I went wild and installed Fluxbox and I love it even better. The only thing I havent been able to figure out is how to keep the screen on all the time. I'm on a desktop and I'm the only one that uses this computer.
I also tried removing the battery from tint2 and starting xfce4-power-manager on start up.
Where do I find that setting for Fluxbox?

Code: Select all

System:    Kernel: 5.15.0-10.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable 
           BOOT_IMAGE=/boot/vmlinuz-5.15.0-10.1-liquorix-amd64 
           root=UUID=<filter> ro audit=0 intel_pstate=disable quiet 
           threadirqs splash 
           Desktop: Fluxbox 1.3.7 info: tint2 vt: 7 dm: SDDM 
           Distro: Debian GNU/Linux 11 (bullseye) base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: X370 Killer SLI/ac serial: <filter> 
           UEFI-[Legacy]: American Megatrends v: P5.80 date: 12/25/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 
           family: 17 (23) model-id: 71 (113) stepping: 0 microcode: 8701013 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86230 
           Speed: 4122 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 4122 
           2: 4198 3: 3901 4: 3590 5: 3593 6: 3599 7: 3592 8: 4021 9: 3597 10: 3601 11: 3452 
           12: 3717 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Baffin [Radeon RX 550 640SP / RX 560/560X] vendor: Gigabyte 
           driver: amdgpu v: kernel bus-ID: 0b:00.0 chip-ID: 1002:67ff class-ID: 0300 
           Device-2: Generalplus USB WEBCAM type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 1-5:2 chip-ID: 1b3f:1167 class-ID: 0102 
           Display: x11 server: X.Org 1.20.13 driver: loaded: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 3520x1080 s-dpi: 96 s-size: 931x285mm (36.7x11.2") 
           s-diag: 974mm (38.3") 
           Monitor-1: DisplayPort-0 res: 1600x900 hz: 60 dpi: 92 size: 443x249mm (17.4x9.8") 
           diag: 508mm (20") 
           Monitor-2: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 92 size: 531x298mm (20.9x11.7") 
           diag: 609mm (24") 
           OpenGL: renderer: Radeon RX 560 Series (POLARIS11 DRM 3.42.0 
           5.15.0-10.1-liquorix-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.5 direct render: Yes 
Audio:     Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 0b:00.1 chip-ID: 1002:aae0 
           class-ID: 0403 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel 
           v: kernel bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403 
           Device-3: Generalplus USB WEBCAM type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 1-5:2 chip-ID: 1b3f:1167 class-ID: 0102 
           Device-4: AKAI Professional M.I. LPK25 MIDI Keyboard type: USB driver: snd-usb-audio 
           bus-ID: 1-8:5 chip-ID: 09e8:0076 class-ID: 0103 
           Device-5: ZOOM R16 type: USB driver: snd-usb-audio bus-ID: 3-1:2 chip-ID: 1686:00dd 
           class-ID: ff00 
           Sound Server-1: ALSA v: k5.15.0-10.1-liquorix-amd64 running: yes 
           Sound Server-2: JACK v: 1.9.17 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel 
           bus-ID: 04:00.0 chip-ID: 8086:24fb class-ID: 0280 
           IF: wlp4s0 state: down mac: <filter> 
           Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel port: f000 
           bus-ID: 05:00.0 chip-ID: 8086:1539 class-ID: 0200 
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8 
           bus-ID: 1-9:4 chip-ID: 8087:0aa7 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 1100 hci-v: 4.2 rev: 1100 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff 
           link-mode: slave accept service-classes: rendering, capturing, audio 
Drives:    Local Storage: total: 931.52 GiB used: 194.07 GiB (20.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT500P5SSD8 size: 465.76 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: P4CR324 temp: 31.9 C scheme: MBR 
           ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Crucial model: CT500P5SSD8 size: 465.76 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: P4CR324 temp: 22.9 C scheme: MBR 
Partition: ID-1: / raw-size: 128 GiB size: 124.93 GiB (97.60%) used: 17.55 GiB (14.0%) fs: ext4 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-2: /home raw-size: 321.76 GiB size: 315.64 GiB (98.10%) used: 176.52 GiB (55.9%) 
           fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p3 maj-min: 259:3 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: 3162 note: see --pkg apt: 3147 lib: 1773 flatpak: 15 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/atom.list 
           1: deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
           Active apt repos in: /etc/apt/sources.list.d/sonobus.list 
           1: deb http://pkg.sonobus.net/apt stable main
Info:      Processes: 443 Uptime: 33m wakeups: 6 Memory: 15.56 GiB used: 1.69 GiB (10.9%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Shell: Bash v: 5.1.4 running-in: quick-system-info-mx 
           inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

[Jerry3904]

I don't know, so I went back to ]the Fluxbox documentation from 20 years ago. Try this in a terminal:

Code: Select all

xset s off

[unklebonehead]

Lol. 20 yrs ago! Thats a lot of research to go back through. Thanks @Jerry3904.
Last night I just did a log out & in after removing the battery from tint2 and adding the xfce4 power manager to the start up script.
I did a proper reboot this morning to see if maybe I needed to do that to get a proper start up script to run. So far it seems to be working since the screen should have shut off about 45 minutes ago.
I'll be watching it all day out of the corner of my eye since I am working today. We'll see if I got it set right.

If I do need to use the xset s off where do I put it to make it permanent? X11, sddm or can that be added to the startup script?

[Huckleberry Finn]

I was just going to say: /home/yourusername/.fluxbox/startup

beginning with an exec (I guess)

Even

Code: Select all

xset s off -dpms

Or, in /home/yourusername/.profile you can try adding :

Code: Select all

# Turn off screen blanking
xset s off -dpms

Or:

Code: Select all

sudo tee /etc/X11/xorg.conf.d/10-screen-always-on.conf <<!
Section "ServerFlags"
    Option "BlankTime" "0"
EndSection
!

(As you might already know: when pasting that into terminal it'll warn you about security, that's normal for it's a long command with multiple lines)

[unklebonehead]

Thank you @Huckleberry Finn.
Just for my own knowledge what does the flags -dpms do?

[Huckleberry Finn]

-dpms disables "Display Power Management Signaling" (that saves power (for monitors) when pc is idling)

-dpms The -dpms option disables DPMS (Energy Star) features.

+dpms The +dpms option enables DPMS (Energy Star) features.

dpms flags...

The dpms option allows the DPMS (Energy Star) parameters to be set. The option can take up to three numerical values, or the `force' flag followed by a DPMS state. The `force' flags forces the server to immediately switch to the DPMS state specified. The DPMS state can be one of `standby', `suspend', `off', or `on'. When numerical values are given, they set the inactivity period (in units of seconds) before the three modes are activated. The first value given is for the `standby' mode, the second is for the `suspend' mode, and the third is for the `off' mode. Setting these values implicitly enables the DPMS features. A value of zero disables a particular mode.

[unklebonehead]

Ok cool thank you.

I think it is safe to mark this as solved!