[Bug]: Default config even after changing config

[MCHAMSTERYT2]

Steps for reproducing the issue

Start wluma with modified config with webcam set as als source

What is the buggy behavior?

wluma gives error about als iio no device found and states intel backlight and dell keyboard are being used while in fact they were removed from the config

What is the expected behavior?

wluma should have launched fine and gave minimal errors if any and should use the modified config

Logs

RUST_LOG=debug wluma

[2025-06-08T23:38:10Z DEBUG wluma] == wluma v4.9.0 ==
[2025-06-08T23:38:10Z DEBUG wluma] Using Config {
als: Iio {
path: "/sys/bus/iio/devices",
thresholds: {
80: "dim",
20: "dark",
500: "bright",
800: "outdoors",
250: "normal",
0: "night",
},
},
output: [
Backlight(
BacklightOutput {
name: "eDP-1",
path: "/sys/class/backlight/intel_backlight",
capturer: Wayland(
Any,
),
min_brightness: 1,
predictor: Adaptive,
},
),
Backlight(
BacklightOutput {
name: "keyboard-dell",
path: "/sys/bus/platform/devices/dell-laptop/leds/dell::kbd_backlight",
capturer: None,
min_brightness: 0,
predictor: Adaptive,
},
),
],
}
[2025-06-08T23:38:10Z WARN  wluma] Skipping 'eDP-1' as it might be disconnected: No such file or directory (oserror 2)
[2025-06-08T23:38:10Z WARN  wluma] Skipping 'keyboard-dell' as it might be disconnected: No such file or directory (os error 2)
[2025-06-08T23:38:10Z INFO  wluma] Continue adjusting brightness and wluma will learn your preference over time.

thread 'als' panicked at src/main.rs:137:26:
Unable to initialize ALS IIO sensor: "No iio device found"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Version

4.9.0 installed via octopi on garuda with chaotic-aur repository

Environment

lsb_release -a; uname -a; pgrep -l sway; pacman -Q | egrep "(wlroots|vulkan|sway|hyprland|clang|rust)"; dpkg -l | egrep "(wlroots|vulkan|sway|hyprland|clang|rust)"; echo "WLR_DRM_NO_MODIFIERS=$WLR_DRM_NO_MODIFIERS"

LSB Version:    n/a
Distributor ID: Garuda
Description:    Garuda Linux Broadwing
Release:        Soaring
Codename:       Broadwing
Linux max-hpelitedesk800g1twr 6.14.6-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 09 May 2025 17:35:59 +0000 x86_64 GNU/Linux
clang 19.1.7-2
lib32-vulkan-icd-loader 1.4.313.0-1
lib32-vulkan-intel 1:25.1.3-2
lib32-vulkan-mesa-layers 1:25.1.3-2
lib32-vulkan-radeon 1:25.1.3-2
vulkan-headers 1:1.4.313.0-1
vulkan-icd-loader 1.4.313.0-1
vulkan-intel 1:25.1.3-2
vulkan-mesa-layers 1:25.1.3-2
vulkan-radeon 1:25.1.3-2
vulkan-swrast 1:25.1.3-2
vulkan-tools 1.4.313.0-1
WLR_DRM_NO_MODIFIERS=

[MCHAMSTERYT2]

Ok so i got it working but it's using the wrong webcam and won't use my monitor

[MCHAMSTERYT2]

Ok so got it using the right webcam now which was pretty easy but it still doesn't utilize my monitor yet

[max-baz]

I'm glad you are making progress! If you want a second pair of eyes on configuring your monitor, please share as much details as possible, like what you are putting in config, what steps you performed to conclude that this is indeed the correct configuration value to match your monitor, and wluma logs with RUST_LOG=trace.

This should be of some help too: https://github.com/maximbaz/wluma/blob/main/README.md#displays

[MCHAMSTERYT2]

I got the displays working now but it now keeps giving me the following errors libv4l2: error setting pixformat: Device or resource busy
ERROR wluma::brightness::controller] Unable to get brightness value: DDC/CI error: invalid DDC/CI length
Second one i listed happens only once at the start and when i adjust the brightness

[max-baz]

I think that's more or less expected, the ddc stuff is very unreliable - did you get lucky and does wluma actually work, despite writing those errors, or it isn't changing brightness at all? Regardless, I thiiiink some people have more luck with the ddcci-driver-linux mentioned in the README.

[MCHAMSTERYT2]

I think it isn't setting the brightness currently so i might have to try setting up the ddcci driver that i just installed yesterday

[MCHAMSTERYT2]

Alright i just seem to need to set up the ddcci driver using modprobe or something (which i tried but it says the driver doesn't exist in my kernel)

[MCHAMSTERYT2]

Got the driver working but there's still nothing in the /sys/class/backlight folder

[max-baz]

I believe a test for whether the driver working could be that you are able to change monitor brightness using "normal" backlight tools like brightnessctl, try to see if you can get to this point, and hopefully wluma would also be working at that moment.

[MCHAMSTERYT2]

Well i tried that and the driver is loaded but it only lists the scroll lock led in brightnessctl

[max-baz]

I would not be surprised if ddcci driver struggles with your particular monitor for the exact same reason as wluma did using ddc method, unfortunately it might just be the case that your monitor has a bad ddc implementation and linux cannot talk to it 😞

[MCHAMSTERYT2]

It's not a problem of the monitor it's the problem of the driver because it detected the brightness adjustment fine it's just i can't find where the monitor is able to be controlled

[MCHAMSTERYT2]

I got one of my monitors set up with it but the other currently doesn't want to get detected

[MCHAMSTERYT2]

For some reason when i rebooted now there's no devices set up with it anymore

[MCHAMSTERYT2]

Also wayland capturer doesn't work for some reason