[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 Jakob Petsovits changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #10 from Jakob Petsovits --- Actually no, let me un-duplicate this again because Bug 482278 is about brightness being dimmed after *unlocking*, whereas this bug is about brightness being dimmed immediately after wake-up (i.e. brightness would be wrong even on the lock screen). Sorry about that. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 Jakob Petsovits changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482278 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 Jakob Petsovits changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #9 from Jakob Petsovits --- This looks close enough to Bug 482278 to call both reports duplicates of each other. Let's continue at the other bug, as it has been around for longer with more participants (although this one has more useful info so far). *** This bug has been marked as a duplicate of bug 482278 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #8 from Jakob Petsovits --- (In reply to Mitja from comment #4) > Here are the logs. I would like to note, that the reduction is higher than > 30%, because > the brightness setting is reduced from 75% to 23%. This makes a reduction of > a 70%. Sorry, yes. I should have been clear to say that the dimming action reduces brightness *to* 30% of the original value, not *by* 30%. So a reduction by 70% is expected (we just need to raise it back up after standby). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #7 from Jakob Petsovits --- Thanks. These are only regular logs, not verbose - did I make a mistake in the README instructions for setting the QT_LOGGING_RULES environment variable? Please double-check that this was set and powerdevil was restarted. The main thing we can learn from these logs is this line: > org.kde.powerdevil: [DDCutilDisplay]: ddca_set_non_table_vcp_value -3023 Which basically tells us that setting the brightness via DDC/CI failed. According to the libddcutil source code, this result is DDCRC_VERIFY, described as "read after VCP write failed or wrong value". I.e. the monitor was present to communicate with the system and accepted the command, but ignored it so the brightness was still unchanged. I think the theory is still the same. I'd still be interested in more detailed powerdevil logs. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #6 from Mitja --- These are logs related only to powerdevil events (journalctl --boot | grep -i "powerdevil"). The logs were collected the following way: 1. At 10:10 I turned on the computer and login to desktop 2. Left the computer inactive to make it enter in standby. 3. Recovery from standby and collection of logs started at around 10:34:50 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #5 from Mitja --- Created attachment 169177 --> https://bugs.kde.org/attachment.cgi?id=169177&action=edit powerdevil logs -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #4 from Mitja --- Here are the logs. I would like to note, that the reduction is higher than 30%, because the brightness setting is reduced from 75% to 23%. This makes a reduction of a 70%. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #3 from Mitja --- Created attachment 169176 --> https://bugs.kde.org/attachment.cgi?id=169176&action=edit Journalctl logs -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 --- Comment #2 from Jakob Petsovits --- (In reply to Nate Graham from comment #1) > Natalie or Jakob, is this one of those things that was fixed recently? I > cannot reproduce it. 6.0.4 is the very latest in brightness-related bugfixes at this time. I would assume that the reported issue is still present and reproduction circumstances are simply different. Let's see. Rounded up, a 23% brightness value is 30% of 75%. The dimming action uses 30%. So what we're looking at here is that the display was dimmed (likely before suspending) and doesn't get reset to its original value after waking up. I would be interested in the sequence of DPMS (screen turn-on) and brightness change operations. Mitja, could you follow the instructions of the PowerDevil README [1] to turn on verbose logs and then post the logs here? [1] https://invent.kde.org/plasma/powerdevil/-/blob/master/README.md My first guess would be that the DimDisplay and DPMS actions are both reacting to the system waking up, but they aren't coordinating and in this case the DimDisplay action goes first by setting the brightness. But the screen is still off and rejects the brightness change command. I don't know if this is actually what's happening, but it would seem plausible. If my theory is correct, a fix would involve coordinating both actions to make DPMS react to suspend events last and react to wake-up events first, so that DimDisplay can generally count on the screen being turned on when it sets the brightness. On a tangential note, I have some more patches in the works that should soon make it possible for us to remember brightness information across display remove+connect events, which might provide an indirect fix for the same issue but without action reordering. I need some more work to actually implement this, and it's also going to take a fair bit of reviewing effort by other developers to get there. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486500] Reduced brightness after standby
https://bugs.kde.org/show_bug.cgi?id=486500 Nate Graham changed: What|Removed |Added CC||jpe...@petsovits.com, ||m...@ratijas.tk, ||natalie_clar...@yahoo.de, ||n...@kde.org Version|unspecified |6.0.4 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Product|kde |Powerdevil Component|general |general --- Comment #1 from Nate Graham --- Natalie or Jakob, is this one of those things that was fixed recently? I cannot reproduce it. -- You are receiving this mail because: You are watching all bug changes.
