| chax | |
| Aug 26 2019, 8:52 PM |
| F5091495: Screenshot from 2019-08-26 23-04-38.png | |
| Aug 26 2019, 9:06 PM |
| F5091473: Screenshot from 2019-08-26 22:31:43.png | |
| Aug 26 2019, 8:52 PM |
Added new plugin to my panel, and got polkit dialog asking me to authenticate as superuser.
Tried to pull slider for brightness and got bunch of new polkit dialogs (i guess one for each slider step)
I'm tagging @algent because he packaged this budgie-extras R4783
Providing screenshot so you can see what is happening
This might be something that is happening only on my setup but i'm filing this issue anyway because someone else could be facing the same issue.
| R4783 budgie-extras | |||
| D7043 | R4783:b5295bfcdf8a Resolve T8287. | ||
Opening Settings->Power and changing Screen brightness slider value from there works normally but changes it only for my laptop screen.
Unfortunally i don't have a laptop to try it, and in my PC there are only two options. I don't have issues with it.
Those two Dim options work for me no problem, they dim my external display, and i don't get asked for superuser authentication.
Actually i just realized that this Dim label is actually a button and you can select different output. This way i can dim my laptop screen also.
But using this "Light" slider is what asks me for superuser authentication. Clicking on Light label gives me only one option "nvidia_0".
Same thing happens on my laptop; one authentication window shows up when trying to add the applet to a panel, and multiple windows show up when moving the "Light" slider.
They're running it with pkexec, that's what is causing the prompts. https://github.com/UbuntuBudgie/budgie-extras/blob/master/budgie-brightness-controller/src/helpers/LightHelper.vala#L142
I would suggest talking to upstream about it and that we remove the applet until it's resolved by them. Ideally they should be settings brightness via the dbus interface org.gnome.SettingsDaemon.Power.Screen + key Brightness instead.
A patch was submitted to fix this issue upstream. I packaged this again but need help by someone who had this issue.
You can find the eopkg files here shared with google drive.
Please test.
@algent, i just saw your comment on this upstream patch. I had the issue myself, so i can test it and report back. Hopefully this patch fixes it now for us.