| Summary: | Change of display brightness by scroll not working after resume from sleep | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Murali Krishna <husband.of.deepu> |
| Component: | Brightness and Color widget | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | husband.of.deepu, kde.org, natalie_clarius, nate |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | edid info of my monitor | ||
|
Description
Murali Krishna
2024-11-15 08:00:29 UTC
Which Samsung monitor specifically? An Odyssey Neo G5 or G9? Samsung Essentials S3 LED Monitor (LS24C330GAWXXL) (In reply to Nate Graham from comment #1) > Which Samsung monitor specifically? An Odyssey Neo G5 or G9? Samsung Essentials S3 LED Monitor (LS24C330GAWXXL) Ok, so not the bug I was thinking of, then... maybe. Curious that it's also a Samsung monitor. Maybe a whole bunch of Samsung monitors are faulty. Does the slider in the widget work? Do the brightness up/down keys on your keyboard (if they exist) work? (In reply to Nate Graham from comment #4) >Slider for changing brightness exists and works on system boot. strangely, the brightness slider dissappears once the screen goes to sleep on inactivity and resumes after a key press on keyboard. On restarting the PC, the brightness slider appears again. Slider for changing brightness exists and works on system boot. strangely, the brightness slider dissappears once the screen goes to sleep on inactivity and resumes after a key press on keyboard. On restarting the PC, the brightness slider appears again. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Slider for changing brightness exists and works on system boot. strangely, the brightness slider dissappears once the screen goes to sleep on inactivity and resumes after a key press on keyboard. On restarting the PC, the brightness slider appears again. Its has been observed that the issue exists while using PC in X11 whereas the problem doesn't exist in the wayland session. The same has been happening to me as well on 6.1 and now on 6.2.4. When I use the scroll wheel over the brightness icon, the following message appears in journalctl -f
org_kde_powerdevil[23079]: org.kde.powerdevil: Adjust screen brightness step failed: no displays available to adjust
I can fix/work around the issue with
systemctl --user restart plasma-powerdevil.service
until the system wakes up from the next sleep. FWIW, I am on Manjaro stable. My display is quite old (as is my whole machine :-). I am using a 4k DP connection
$ inxi -G
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: i915 v: kernel
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: intel dri: i965 gpu: i915
resolution: 3840x2160
API: EGL v: 1.5 drivers: crocus,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-arch1.1
renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
API: Vulkan v: 1.3.295 drivers: intel surfaces: xcb,xlib,wayland
Created attachment 176411 [details]
edid info of my monitor
There are also several manjaro users reporting the same issue. Hence I'm changing the status to confirmed. Let me know if there is anything I can try to investigate the issue. Searching the bug database I found other reported issues similar to this one. There this bug if probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=482713 *** This bug has been marked as a duplicate of bug 482713 *** |