Monitor goes black when power UPS cable (energy) is plugged on/off

My problem is the same as here:

I have the same problem in latest TW and latest Plasma 6.3. Screen goes blank every time UPS goes to battery, cable plugged in/out or powered on/off. Very boring! As electricity sometimes very unstable, it blinks every few seconds. Definitely software problem. How to solve this?

There are many things which need to be checked:
https://www.google.com/search?q=screen+blank+when+ups+is+on

Add X11 or Plasma to your Google request - and you’ll see no useful results. PC does not power off, only Monitor becomes blank - 4K TV on hdmi and it does not power off either. So it is a software problem!

Not sure why you limit your search to software (the results hints that you need to check the hardware). The search results also explain the difference why your computer doesn’t power off whilst the monitor may turn off for a short period.

  • is the monitor connected at the same HDMI port for the test?
  • is the monitor power cable connected to the UPS
  • is the TV power cable connected to the UPS

If you believe it is a software issue, you need to provide informations regarding UPS make/model and which software is used to configure the UPS.

I have only TV, no monitor.

Both: it blinks when connected to UPS and when outside of UPS - reproducible in both cases. It does not power off in both cases.

APC UPS, detected automatically and handles with Plasma battery icon/software.

People are saying power management was broken in Plasma 6.2.

Tumbleweed already ships Plasma 6.3.4. But you should definitely check the power management settings in systemsettings. If you have your UPS connected via USB/serial/ethernet or whatever, the interuption my be detected as running on battery (which is communicated to the Plasma power profile) and the monitor shuts off/goes into sleep mode.

As you did not provide the model of your APC UPS, i googled a little bit. I found quite some articles and threads with the same symptoms independent from the used OS (so no software issue of the OS). Dependend from the used UPS model, the issues where caused by suboptimal configured UPS (UPS config menu) or computers/monitors connected to the wrong outlets of the UPS. This should also be checked.

Tried to solve like mentioned here: Reddit - The heart of the internet - helped temporarily.

1 Like

Back-UPS BX2200MI FW:378700G -302202G, American Power Conversion. Not clear what power management settings should I check?! I have not used UPS for a 1-2 years, now started again, and such symptoms never happened earlier. So seems some new Plasma issues.

All the outlets are interchangeable. If power disappears on the TV it always shows splash screen and then main menu on next power on - this never happens, so this is software problem.

Plugged off USB cable which controls UPS state - still happens. So seems hardware problem.

With apctest set UPS sensitivity to LOW - will see what result it will produce. This is the only reasonable setting I’ve found: Reddit - The heart of the internet

Possibly battery issue.

Connect monitor power cord to UPS.

It is connected to UPS, batteries are new: replaced old defective ones. UPS allows to keep PC + TV workability for 30-40 min now on power outage as it should.

Post

inxi -aFz

why do you need my hardware info? :wink: It prints mouse battery info for some reason, not UPS.

If you know what is better then DIY.

sudo apcaccess

prints UPS info - could it give more info?

> inxi -aFzB

System:
  Kernel: 6.14.1-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.14.1-1-default
    root=UUID=24fbaf81-79f0-4b37-b08e-b1d709ed97e7 splash=silent
    resume=/dev/disk/by-uuid/a58af199-9a71-4f77-9547-30a7871438e8 quiet
    security=apparmor nosimplefb=1 nvidia_drm.modeset=1 mitigations=auto
    rd.driver.blacklist=nouveau
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.12.0
    wm: kwin_x11 tools: xscreensaver,xscreensaver-systemd vt: 2 dm: SDDM
    Distro: openSUSE Tumbleweed 20250410
Machine:
  Type: Desktop System: Gigabyte product: X570S AORUS ELITE AX v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: X570S AORUS ELITE AX v: x.x
    serial: <superuser required> uuid: <superuser required> BIOS: American
    Megatrends LLC. v: F6a date: 02/08/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Anywhere 3 serial: <filter>
    charge: 90% rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 16 threads: 32 tpc: 2
    smt: enabled cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB
    desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3375 min/max: 550/3401 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3375 2: 3375 3: 3375
    4: 3375 5: 3375 6: 3375 7: 3375 8: 3375 9: 3375 10: 3375 11: 3375 12: 3375
    13: 3375 14: 3375 15: 3375 16: 3375 17: 3375 18: 3375 19: 3375 20: 3375
    21: 3375 22: 3375 23: 3375 24: 3375 25: 3375 26: 3375 27: 3375 28: 3375
    29: 3375 30: 3375 31: 3375 32: 3375 bogomips: 217605
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: ASUSTeK driver: nvidia
    v: 570.133.07 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
    status: current (as of 2025-01; EOL~2026-12-xx) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
    lanes: 8 link-max: lanes: 16 ports: active: none off: HDMI-A-1
    empty: DP-1,DP-2,DP-3 bus-ID: 09:00.0 chip-ID: 10de:2507 class-ID: 0300
  Device-2: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2
    chip-ID: 046d:08e5 class-ID: 0102
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,vesa
    alternate: fbdev,nouveau,nv gpu: nvidia,nvidia-nvswitch display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 192 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Samsung
    serial: <filter> built: 2021 res: N/A dpi: 103 gamma: 1.2
    size: 950x540mm (37.4x21.26") diag: 1093mm (43") ratio: 16:9 modes:
    max: 3840x2160 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia nouveau drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: nouveau device: 2 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.133.07
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.4.309 layers: 3 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3050 driver: N/A device-ID: 10de:2507
    surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 20.1.2 256
    bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 09:00.1 chip-ID: 10de:228e class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2
    chip-ID: 046d:08e5 class-ID: 0102
  API: ALSA v: k6.14.1-1-default status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 14c3:0608
    class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Info: services: NetworkManager,wpa_supplicant
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-5:2 chip-ID: 0e8d:0608
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
  Local Storage: total: 9.1 TiB used: 2.21 TiB (24.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD2001FFSX-68JNUN0 size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 0A81 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 8TB
    size: 7.28 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 260 GiB size: 260 GiB (100.00%) used: 54.6 GiB (21.0%)
    fs: btrfs dev: /dev/sdb1 maj-min: 8:17
  ID-2: /home raw-size: 7.01 TiB size: 7.01 TiB (100.00%)
    used: 1.86 TiB (26.5%) fs: btrfs dev: /dev/sdb3 maj-min: 8:19
  ID-3: /opt raw-size: 260 GiB size: 260 GiB (100.00%)
    used: 54.6 GiB (21.0%) fs: btrfs dev: /dev/sdb1 maj-min: 8:17
  ID-4: /var raw-size: 260 GiB size: 260 GiB (100.00%)
    used: 54.6 GiB (21.0%) fs: btrfs dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdb2 maj-min: 8:18
Sensors:
  System Temperatures: cpu: 37.1 C mobo: 34.0 C gpu: nvidia temp: 53 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
  Memory: total: 64 GiB note: est. available: 62.68 GiB
    used: 10.59 GiB (16.9%)
  Processes: 658 Power: uptime: 7h 52m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.04 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 18 pm: rpm pkgs: N/A note: see --rpm tools: yast,zypper
    pm: flatpak pkgs: 6 pm: snap pkgs: 12 Compilers: clang: 20.1.2 alt: 19
    gcc: 14.2.1 alt: 13 Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.37

Upgrade BIOS. At least it will help with SMM vulnerabilities.

Check system behaviour with Leap or Windows.

You can get incompatibility with computer PSU + UPS, but this is doubtful.

Risky and not sure it will help:

Warning:
Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.

Also issue reproducible with detached USB cord from UPS and TV unplugged from UPS - plugged directly to a home outlet.

Attach monitor via DP.