Fresh Garuda install, Hyprland desktop idle inhibit module on waybar does nothing

Issues & Assistance Hyprland
1 
System:
  Kernel: 6.8.9-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=ecfb0dcf-b1fc-49eb-a70e-4c1ae4e56aef rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: Hyprland v: 0.40.0 with: waybar tools: swayidle
    avail: hyprlock,swaylock vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Mini-pc System: AZW product: SER v: Version 1.0
    serial: <superuser required>
  Mobo: AZW model: SER v: Version 1.0 serial: <superuser required>
    part-nu: Default SKU uuid: <superuser required> UEFI: American Megatrends
    LLC. v: 113 date: 02/22/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 2S
    serial: <filter> charge: 10% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x44 (68) stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 462 high: 1397 min/max: 400/4829 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 400
    4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
    14: 400 15: 1397 16: 400 bogomips: 102212
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3,
    DP-4, DP-5, HDMI-A-2, Writeback-1 bus-ID: 74:00.0 chip-ID: 1002:1681
    class-ID: 0300 temp: 45.0 C
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.7
    compositor: Hyprland v: 0.40.0 driver: X: loaded: amdgpu
    unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: 1
  Monitor-1: HDMI-A-1 model: Samsung LS24AG32x serial: <filter> built: 2021
    res: 1920x1080 hz: 144 dpi: 93 gamma: 1.2 scale: 1
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV REMBRANDT) driver: mesa radv v: 24.0.7-arch1.3
    device-ID: 1002:1681 surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
    v: 24.0.7-arch1.3 (LLVM 17.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 74:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x
    v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir,
    snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63 pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 74:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 74:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.8.9-zen1-2-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp3s0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:2 chip-ID: 8087:0029
    class-ID: e001
  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: 6c0104
Drives:
  Local Storage: total: 931.52 GiB used: 17.57 GiB (1.9%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S500G
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: SBJ00101 temp: 44.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT500MX500SSD1
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B type: USB
    rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    fw-rev: 0104 scheme: GPT
Partition:
  ID-1: / raw-size: 217.29 GiB size: 217.29 GiB (100.00%)
    used: 17.4 GiB (8.0%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 168 MiB (32.9%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 217.29 GiB size: 217.29 GiB (100.00%)
    used: 17.4 GiB (8.0%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-4: /var/log raw-size: 217.29 GiB size: 217.29 GiB (100.00%)
    used: 17.4 GiB (8.0%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-5: /var/tmp raw-size: 217.29 GiB size: 217.29 GiB (100.00%)
    used: 17.4 GiB (8.0%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 28.14 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A gpu: amdgpu temp: 47.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 28 GiB note: est. available: 28.14 GiB used: 2.19 GiB (7.8%)
  Processes: 349 Power: uptime: 1h 27m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 11.24 GiB services: upowerd Init: systemd
    v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1409 libs: 426 tools: pacseek,paru,yay
    Compilers: gcc: 14.1.1 Shell: garuda-inxi default: Bash v: 5.2.26
    running-in: terminator inxi: 3.3.34
Garuda (2.6.26-1):
  System install date:     2024-05-15
  Last full system update: 2024-05-17
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

My waybar config has this module:

"idle_inhibitor": {
        "format": "{icon}",
       "format-icons": {
            "activated": "ļ®",
            "deactivated": "ļ°"
        }

Should there be an ā€œon-clickā€ action defined in this module for the idle_inhibitor to work?
Right now it does nothing whether activated or deactivated.
What am I missing?
Swaylock and Swayidle are installed and working.
The screen will lock after timeout and the monitor goes black after another timeout.
Moving the mouse or keyboard activity turns on the monitor and presents the login circle.
All this is functioning as expected. The only thing not working is the idle_inibitor. Any help is greatly appreciatedā€¦

2

It keeps your computer from going to suspend, in case you want to watch a movie or something.
KUDOS to

A one second google search:
The idle_inhibitor module can inhibiting the idle behavior such as screen blanking, locking, and screensaving, also known as ā€œpresentation modeā€ ā€¦

3

I know that the idle_inhibitor is supposed to keep the computer from locking the screen or going into suspend. My problem is that the idle_inhibitor does not do that. It does not matter if the eye icon is activated or deactivated. The idle_ inhibitor does absolutely nothing except change the waybar icon from open eye to closed eye. I included the idle_ inhibitor module configuration in the waybar config file .

"idle_inhibitor": {
        "format": "{icon}",
       "format-icons": {
            "activated": "ļ®",
            "deactivated": "ļ°"

There is no ā€œon-clickā€ line here to execute an action. Therefore I am assuming that this is the problem?
Any advice ? Thanks

4

Try

"idle_inhibitor": {
	"format": "{icon}",
	"format-icons": {
		"activated": "ļ®",
		"deactivated": "ļ°"
	},
	"timeout": 30.5
}

timeout:
typeof: double The number of minutes the inhibition should last.

To be more clear, it does not need an on-click function, it is a waybar module that works like a light switch.

2 Likes
5

It definitely works here. I am on Sway but my config for this module looks the same.

    "idle_inhibitor": {
        "format": "{icon}  ",
        "format-icons": {
            "activated": "ļ®",
            "deactivated": "ļ°"
        },
        "tooltip-format-activated": "Idle Inhibitor Activated",
        "tooltip-format-deactivated": "Idle Inhibitor Deactivated"
    },

I added a tooltip to help people figure out what the module actually is if they are new to Sway, other than that itā€™s the same.

I can confirm that clicking the module toggles the state. Adding an additional on-click action is not necessaryā€“although it is supported; see the man page:

 āÆ man waybar-idle-inhibitor | grep -A2 on-click:
       on-click:
            typeof: string
            Command to execute when clicked on the module. A click also toggles the state

As long as you are in a partially upgraded state, there is no sense troubleshooting the issue because even if everything is configured perfectly you may still have things out of whack. You should run garuda-update to bring the system fully up to date, then reboot, and test again afterward.

Note: when the idle inhibitor is activated, the eye is ā€œopenā€ (not with a line through it).

3 Likes
6

Unfortunately, I can confirm that the idle inhibitor doesnā€™t work for me either on Hyprland, and this install is quite new as well. It worked on my old laptop though. Iā€™ll have to check another day if it still works.
I tried Swayidle and Hypridle, but both donā€™t respond to it. My system still continues to lock my screen at specified intervals in my config, which can be really annoying when watching videos etc.

There are ways around it, which are to create window rules, or use a different inhibitor altogether such as Matcha. I havenā€™t tried these though.

garuda-inxi:

System:
  Kernel: 6.8.9-lqx2-4-lqx arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm parameters: audit=0
    intel_pstate=disable root=UUID=968a1abf-95d6-4303-83bb-a9c61fbf70c8 rw
    rootflags=subvol=GHyprland loglevel=3 ibt=off radeon_modeset=1
    driver=nonfree nvidia_drm.modeset=1 pci=noaer
    nvidia.NVreg_PreserveVideoMemoryAllocations=1 nowatchdog
    initrd=\GHyprland\boot\initramfs-linux-lqx.img
  Desktop: Hyprland v: 0.40.0 with: waybar tools:
    avail: hyprlock,swayidle,swaylock vt: 1 dm: SDDM Distro: Garuda
    base: Arch Linux
Machine:
  Type: Mini-pc System: Micro (HK) Tech product: Venus series v: N/A
    serial: <superuser required>
  Mobo: Shenzhen Meigao Equipment model: F7BSC serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: 1.07
    date: 09/01/2023
Battery:
  Device-1: wacom_battery_1 model: Wacom Intuos Pro M serial: N/A charge: 9%
    status: not charging
CPU:
  Info: model: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics bits: 64
    type: MT MCP arch: Zen 4 gen: 5 level: v4 note: check built: 2022+
    process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x74 (116) stepping: 1
    microcode: 0xA704103
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1234 high: 4680
    min/max: 400/5263:6228:5583:5743:5423:5903:6067 scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 3751 2: 4680
    3: 2903 4: 3616 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 bogomips: 127761
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA AD107 [GeForce RTX 4060] vendor: ASUSTeK driver: nvidia
    v: 550.78 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-04) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 2 speed: 5 GT/s lanes: 4
    link-max: gen: 4 speed: 16 GT/s lanes: 8 ports: active: none off: DP-2
    empty: DP-1,DP-3,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2882
    class-ID: 0300
  Device-2: AMD Phoenix1 driver: amdgpu v: kernel arch: RDNA-3 code: Phoenix
    process: TSMC n4 (4nm) built: 2023+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: none empty: DP-10, DP-4, DP-5, DP-6, DP-7, DP-8, DP-9,
    HDMI-A-2, HDMI-A-3, Writeback-1 bus-ID: c5:00.0 chip-ID: 1002:15bf
    class-ID: 0300 temp: 32.0 C
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
    compositor: Hyprland v: 0.40.0 driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
    gpu: nvidia,nvidia-nvswitch display-ID: 1
  Monitor-1: DP-2 model: Dell P2423D serial: <filter> built: 2023
    res: 2560x1440 hz: 60 dpi: 123 gamma: 1.2 scale: 1
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: radeonsi x11: drv: radeonsi
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4060/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.3.279 layers: 11 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV GFX1103_R1) driver: mesa radv v: 24.0.7-arch1.3
    device-ID: 1002:15bf surfaces: xcb,xlib,wayland device: 1
    type: discrete-gpu name: NVIDIA GeForce RTX 4060 driver: nvidia v: 550.78
    device-ID: 10de:2882 surfaces: xcb,xlib,wayland device: 2 type: cpu
    name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
    v: 24.0.7-arch1.3 (LLVM 17.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 4 link-max: lanes: 8 bus-ID: 01:00.1
    chip-ID: 10de:22be class-ID: 0403
  Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: c5:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_ps
    v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_sof_amd_renoir,
    snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63 pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: c5:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-4: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: c5:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.8.9-lqx2-4-lqx status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak]
    vendor: Rivet Networks Killer driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:4 chip-ID: 8087:0032
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 953.87 GiB used: 908.93 GiB (95.3%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8PGP41024Q-A0
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: ELFK0S.6 temp: 32.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 848.35 GiB size: 848.35 GiB (100.00%)
    used: 453.3 GiB (53.4%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 38.5 MiB (7.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 848.35 GiB size: 848.35 GiB (100.00%)
    used: 453.3 GiB (53.4%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-4: /var/log raw-size: 848.35 GiB size: 848.35 GiB (100.00%)
    used: 453.3 GiB (53.4%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-5: /var/tmp raw-size: 848.35 GiB size: 848.35 GiB (100.00%)
    used: 453.3 GiB (53.4%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 60.55 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p6 maj-min: 259:6
Sensors:
  System Temperatures: cpu: 37.1 C mobo: N/A gpu: amdgpu temp: 33.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: N/A available: 60.55 GiB used: 4.84 GiB (8.0%)
  Processes: 431 Power: uptime: 3h 25m states: freeze,mem,disk
    suspend: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 24.18 GiB services: upowerd Init: systemd
    v: 255 default: graphical tool: systemctl
  Packages: 1911 pm: pacman pkgs: 1905 libs: 567 tools: pacseek,paru
    pm: flatpak pkgs: 6 Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi
    default: fish v: 3.7.1 running-in: foot inxi: 3.3.34
Garuda (2.6.26-1):
  System install date:     2024-05-05
  Last full system update: 2024-05-19
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

Update

Itā€™s an upstream Hyprland issue. idle_inhibitor stopped working Ā· Issue #3268 Ā· Alexays/Waybar Ā· GitHub

4 Likes
7

Done, I will reboot and give it a try.
Is there any way to make this work simply on or off, (activated or deactivated)?

8

Still no joy.
only change was that the eye icon disappeared from waybar.
swayidle is still not inhibited from kicking in after the timeout.

Thanks

9

:arrow_up:

3 Likes
10

Thanks, good to know.
Will there be some kind of notification when it is fixed, or will a future upgrade resolve the problem?

11

A good way to keep an eye on fixes and releases is to join the Hyprland discord. They list out fixes and releases quite often. Iā€™m in it if you decide you want an invite. I use armcord-git from the chaotic to avoid all the nasty Discord tracking.

1 Like
12

You can subscribe to a thread to get notifications when progress has been made on an issue if you want.

image
image1283Ɨ1200 176 KB

According to one of the comments in that thread, it sounds like when Hyprland 0.41 is released it will resolve the issue. You wonā€™t need to do anything in this case, except just update your system normally.

3 Likes
13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.