wluma: [Bug]: permission denied erros if ran without sudo, no config found if ran with sudo
Steps for reproducing the issue
- download the releases
- create a config file in
~/.config/wluma/config.toml
- try to launch the built artifact without sudo and then with sudo.
What is the buggy behavior?
behavior when ran without sudo:
vega@dart ~/s/w/t/release [1]> ./wluma
[2022-01-27T19:56:04Z WARN wluma] Skipping 'eDP-1' as it might be disconnected: Permission denied (os error 13)
[2022-01-27T19:56:04Z INFO wluma] Continue adjusting brightness and wluma will learn your preference over time.
behavior when ran with sudo:
vega@dart ~/s/w/t/release [SIGINT]> sudo ./wluma
[2022-01-27T19:53:16Z WARN wluma] Skipping 'keyboard-dell' as it might be disconnected: No such file or directory (os error 2)
[2022-01-27T19:53:16Z INFO wluma] Continue adjusting brightness and wluma will learn your preference over time.
thread 'als' panicked at 'Unable to initialize ALS IIO sensor: "No iio device found"', src/main.rs:116:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
here’s a link to a file with RUST_BACKTRACE=full
when running with sudo:
https://paste.centos.org/view/33b45dcf
What is the expected behavior?
I think the issue there is that when it’s ran with sudo it thinks the user is root and looks for config file in /root/.config/wluma/config.toml
Logs
https://paste.centos.org/view/2df8ad43
Version
version 4.1.0, from the built artifact in releases folder
Environment
default command doesn't work, so here's information from neofetch, I guess.
.',;::::;,'. vega@dart
.';:cccccccccccc:;,. ---------
.;cccccccccccccccccccccc;. OS: Fedora Linux 35.20220125.0 (Silverblue) x86_64
.:cccccccccccccccccccccccccc:. Host: Notebook NS50MU
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 5.15.16-200.fc35.x86_64
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 1 day, 7 hours, 3 mins
.:ccccccccccccc;KMMc;cc;xMMc;ccccccc:. Packages: 1432 (rpm), 101 (flatpak)
,cccccccccccccc;MMM.;cc;;WW:;cccccccc, Shell: fish 3.3.1
:cccccccccccccc;MMM.;cccccccccccccccc: Resolution: 1920x1080
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: DE: GNOME 41.3 (Wayland)
cccccc;0MMKxdd:;MMMkddc.;cccccccccccc; Theme: Adwaita-dark [GTK2/3]
ccccc;XM0';cccc;MMM.;cccccccccccccccc' Icons: Adwaita [GTK2/3]
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Terminal: gnome-terminal
ccccc;0MNc.ccc.xMMd;ccccccccccccccc; CPU: 11th Gen Intel i7-1165G7 (8) @ 4.700GHz
cccccc;dNMWXXXWM0:;cccccccccccccc:, GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics]
cccccccc;.:odl:.;cccccccccccccc:,. Memory: 6620MiB / 31889MiB
:cccccccccccccccccccccccccccc:'.
.:cccccccccccccccccccccc:;,..
'::cccccccccccccc::;,.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 15 (8 by maintainers)
Could you please create a separate ticket for this? Let’s see what we can improve with regards to webcam…
Also please include whether you can consistently reproduce (and if yes, some repro steps would be welcome), whether stopping wluma turns off the webcam light or it keeps shining even after exiting the app, whether running wluma without
als.webcam
turns the light off, whether you have some other apps running that might be using webcam.If it worked but then stopped, I imagine it’s some sort of conflict with another app, webcam is a single shared resource that can only be used by one app, so if you e.g. have a video call, wluma will not be able to use webcam.
hmm yes, it appears to work now. I’m going to add it as a user systemd service and let it run for a couple of days, will check in back later to report how well it turned out
Great!
This is because you are using Gnome, you must change
capturer
tonone
in the config; screen contents capturing is currently only implemented for wlroots-based compositors, #5 is tracking support for more.