Summary: | multiple issues on hotlugging a monitor over usbc/HDMI | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Wren Turkal <wt> |
Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jpetso, nate |
Priority: | NOR | ||
Version First Reported In: | git-stable-Plasma/6.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Wren Turkal
2025-01-28 00:55:12 UTC
> it usually shows up with 100% brightness instead of what it was set to when I last connected it This is Bug 494408, which is fixed in Plasma 6.3. > The monitor also has speakers in it, and the volume is always set to 100% when it connects as well, > which can be quite terrifying This is unfortunately an upstream PipeWire bug: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/744. Feel free to leave a comment there. > Sometimes, it just won't show the brightness control for external monitor after sleeping This is Bug 482713, which isn't fixed yet. Marking as a duplicate of that one. In the future, please open multiple bug reports to report multiple issues. Thanks! *** This bug has been marked as a duplicate of bug 482713 *** (In reply to Wren Turkal from comment #0) > 3. Be sad now that I need to reset my brightness/volume settings. When you reset your brightness/volume settings, do you use Plasma's brightness slider, accessible in the Brightness and Color applet and in the Display Configuration settings page? Or do you use your monitor's OSD menu? For Plasma 6.3, KWin will not remember external monitor brightness changes. I'm assuming you've set the value in Plasma as you mention the brightness control no longer showing up sometimes. But please confirm. Enabling verbose logging for the plasma-powerdevil service could provide insight as to what's happening: https://invent.kde.org/plasma/powerdevil/-/blob/master/README.md#troubleshooting--reporting-bugs (note that this doesn't include KWin verbose logging, so we may still miss some context) I only use the Plasma brightness slider (either from the systray or in the display settings). I think you are saying that Plasma doesn't remember brightness ever for a plugged in monitor. Is that correct? That seems kinda awful. Is that intentional or is this some kind of bug? Kinda weird that it remembers my screen layout and settings other than brightness. Just to give you a little more about my use case. I plug in this monitor whenever I am in my office. This isn't a once every so often monitor. I use it most days and must reset the brightness (if the slider doesn't disappear) pretty much every time I resume from sleep or boot the machine with the monitor connected. (In reply to Wren Turkal from comment #4) > I think you are saying that Plasma doesn't remember brightness ever for a > plugged in monitor. Is that correct? Sorry, I phrased this poorly. Plasma will of course remember brightness for an external monitor. What it will not do (for the time being) is realize when the monitor itself has initiated the brightness change through its own hardware buttons. We can read the monitor's brightness values but we won't get notified when a change happens, so for now we left "read brightness again" heuristics for a later time. As of Plasma 6.3, we only read brightness when the monitor is first detected to initialize settings for a monitor that KWin has not seen before. > Just to give you a little more about my use case. I plug in this monitor > whenever I am in my office. This isn't a once every so often monitor. I use > it most days and must reset the brightness (if the slider doesn't disappear) > pretty much every time I resume from sleep or boot the machine with the > monitor connected. Thanks. What I'm reading is that you're indeed using Plasma's brightness slider to re-adjust the brightness, you're not using your monitor's hardware buttons to do this. By using Plasma's brightness slider, the brightness would get stored and should indeed be restored next time your monitor gets connected again. The fact that this does not happen (reliably, at least) is indeed a bug. If you can collect some logs as described earlier, we may find an indication of what's going wrong. |