-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run brightness-controller after installing. Python error with index out of range. #248
Comments
See I2C Device Permissions section in https://www.ddcutil.com/config_steps/ |
I'm experiencing a similar problem and I think it might be a bug 🤔 So, I suspect that during the init of the app, Brightness/brightness-controller-linux/brightness_controller_linux/init.py Lines 50 to 52 in dab46e3
Finally, when it reaches the following line, an error is thrown since the Brightness/brightness-controller-linux/brightness_controller_linux/init.py Lines 281 to 284 in dab46e3
This is the error that I see on the logs. If needed I can create a separate issue for this. |
@thardev Thanks for the bug report! Can you also try my fork? https://github.com/Soggy-Pancake/Brightness-Direct-Control The problem was that in CDisplay.match_ddc_order it was failing to add the laptop display and it was still counted so it then tried to load the reordered names missing the laptop display. I also added several other patches since my last pull request that improves the ddcutil mode. |
Thank you for your answer 🙂 I did try your fork but I don't seem to be able to make it work properly, I've followed the instructions of this README https://github.com/Soggy-Pancake/Brightness-Direct-Control/blob/master/brightness-controller-linux/README.md but the app crashes when I try to adjust the brightness. Probably I need to install it system wide properly? Or what else could it be? |
What is the traceback when it crashes? DDCutil needs to be installed if you are using direct backlight control but you should be able to run the brightness controller from any location. |
@thardev Can you please provide the traceback for the crash when attempting to change brightness? |
Hey @Soggy-Pancake - I just wanted to drop by and thank you for looking at this issue! |
@thardev I looks like you might be using wayland. Wayland is not currently supported. I have experimental support for wayland in my fork but it is direct backlight control only. Edit: Nvm they tried to set the laptop display brightness with ddcutil which is not supported. Laptop displays don't use ddc and use an entirely different system for brightness control. You can see the warning your |
Added message box popups for wayland users as well as an exit condition if they are using wayland and don't have ddcutils since the program would be useless. It shouldn't be able to crash anymore if xrandr is called in wayland since I've wrapped it in a try block as well as the ddcutil set command. Since xrandr is x11 only I've also force enabled ddc mode on wayland. |
@thardev is there any chance we could get in a discord call? Currently working on adding a lot of logging so commands don't need to be copied into reports anymore as well as showing the exact input everything is getting. I also changed the command that raised an exception to getOutput so it ignores the process return value. discord is Soggy_Pancake |
I think yes, we could, sorry for the late response but I'm a bit busy recently. |
Nice, my time zone is mountain standard time. Discord is @ soggy_pancake. Lmk what ur handle is through here when you send the friend request so I know its you :) |
I installed it, installed ddcutil using
sudo apt install ddcutil
, but the application crashes at start. Is there some permissions I need to set?Version
brightness-controller-linux==2.4
To Reproduce
Steps to reproduce the behavior:
starting app with
brightness-controller
in terminalExpected behavior
Not a index out of range?
Desktop (please complete the following information):
Running on a Dell Inc. Precision 5560
Additional context
Am I missing any instructions?
The text was updated successfully, but these errors were encountered: