Adding the Battery Monitor widget to my plasma desktop causes the screen brightness to drop to 0 when first logging in; this is a huge problem because this particular laptop turns off the screen at 0. It would be helpful if it kept the last setting, used the value specified in the power management settings, or set it a non-zero value (such as 1). Reproducible: Always Steps to Reproduce: 1. Add widget to desktop 2. Log out 3. Log back in Actual Results: The screen was blank (literally turned off); work around is to guess at where the slider to adjust brightness is, or to plug and unplug the charger. Expected Results: The battery monitor should have kept the brightness it was at the last time KDE was quit. Laptop: ASUS ZENBOOK UX303LN
Created attachment 95829 [details] Set a defalt value for slider; not tested I'm having trouble compiling the widget for testing; please test this, but I believe this solution will work based on the documentation here (http://api.kde.org/4.x-api/kde-runtime-apidocs/plasma/declarativeimports/plasmacomponents/html/classSlider.html)
That patch doesn't make a lot of sense. but the user of BrightnessItem (PopupDialog.qml) *also* sets a value: BrightnessItem { id: brightnessSlider value: batterymonitor.screenBrightness ... } so you'd set the value of 1, then this would override it before you've started doing anything. Currently we set it to undefined which isn't very good code tbh, but it won't do anything as we only connect the valueChanged signal on the slider after everything is loaded. We then call updateBrightness in Logic.js that updates the slider's initial value. That initial value comes from powerdevil, I think you want to be looking there and this slider is a red herring. I think you're looking very much in the wrong place; the slider won't do
Did you try it without the widget, what happens? if you (from a terminal) kquitapp5 plasmashell plasmashell does it reset?
I'll try that as soon as I can David, thanks (left the laptop with the issue at home, I'll be back and have time Thursday night).
This was not fun debugging, jumping from kdeinit5/powerdevil via dbus to plasmashell to a widget. Question: have you expanded the battery monitor widget? That seems to trigger the bad condition in plasma-workspace 5.6.4. Can you try this patch: https://git.reviewboard.kde.org/r/128098/ (and check also if the analysis is sane)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!