[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #48 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/powerdevil/-/merge_requests/480

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-13 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC||mokaz...@disroot.org

--- Comment #47 from Nate Graham  ---
*** Bug 496890 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #46 from matterhorn...@proton.me ---
I never got round to responding to report the result of the fix in 6.2.1 for
me, sorry!

In contrast to the other recent reports I can add some positivity to say that
every time I have checked recently everything the brightness slider works
correctly :) I believe it was fixed with 6.2.1 and has remained fixed for me
since then.

Current state of system:

Operating System: openSUSE Tumbleweed 20241211
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD Ryzen 3 3200G with Radeon Vega Graphics
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450 I AORUS PRO WIFI

i.e. I am still on kernel 6.11. I'll pay special attention to what happens when
the kernel upgrade lands.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC||aron...@gmail.com

--- Comment #45 from Nate Graham  ---
*** Bug 497382 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC||thiago.girol...@hotmail.com

--- Comment #44 from Nate Graham  ---
*** Bug 496952 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

m.k...@irregular.at changed:

   What|Removed |Added

 CC||m.k...@irregular.at

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=486067

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC||saipavanchitta1...@gmail.co
   ||m

--- Comment #43 from Nate Graham  ---
*** Bug 497287 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

kde@grau.net changed:

   What|Removed |Added

 CC||kde@grau.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

kde@grau.net changed:

   What|Removed |Added

 CC||husband.of.de...@gmail.com

--- Comment #42 from kde@grau.net ---
*** Bug 496295 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #41 from kde@grau.net ---
*** Bug 497146 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-06 Thread Jordan JD Peterson
https://bugs.kde.org/show_bug.cgi?id=482713

Jordan JD Peterson  changed:

   What|Removed |Added

 CC||common.disturbances@gmail.c
   ||om

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-06 Thread d3vilguard
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #40 from d3vilguard  ---
won't be reopening my https://bugs.kde.org/show_bug.cgi?id=494233 report but on
Arch with kernel 6.12 the issue seems to be back. Now I lose control over both
monitors if they were off for some time. Restarting powerdevil services helps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

mira...@mirandastreeter.com changed:

   What|Removed |Added

 CC||mira...@mirandastreeter.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #39 from zvova7...@gmail.com ---
With the 6.12 kernel, I encountered a regression again. Something has changed
with the connect-disconnect event, causing ddcutils to try to get info from the
monitor while it is in DPMS. I reverted back to the 6.11 kernel. I haven't had
time to gather more details yet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-05 Thread Andrea Ippolito
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #38 from Andrea Ippolito  ---
Sharing what seems to be a workaround:

systemctl --user restart plasma-powerdevil.service

I had also tried turning the external display off and on again before that, but
that wasn't effective. Restarting powerdevil instead is (or seems to be, for
the moment)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-05 Thread Andrea Ippolito
https://bugs.kde.org/show_bug.cgi?id=482713

Andrea Ippolito  changed:

   What|Removed |Added

Version|6.0.0   |6.2.4

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-12-05 Thread Andrea Ippolito
https://bugs.kde.org/show_bug.cgi?id=482713

Andrea Ippolito  changed:

   What|Removed |Added

 CC||andrea.i...@gmail.com

--- Comment #37 from Andrea Ippolito  ---
Can also confirm this is still an issue.

Sometimes my external display appears in Plasma's OSD/powerdevil, sometimes
there's the laptop display only.

But even when the external display is not "visible", I can still query it and
change values (brightness, contrast) via dccutil, and it just works.

This has to mean that the bug is somewhere "higher up" in the stack, i.e. (I
guess) Plasma or some other KDE component.

Operating System: openSUSE Tumbleweed 20241202
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

Some logs from my current session (notice however that the last timestamp,
13:02, is a few hours ago, much before my attempts to change brightness via
plasma - might it be that the "connection" broke at that point and wasn't
recovered since then?):

```
❯  journalctl -b | grep org_kde_powerdevil | grep ddc
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
Dec 05 09:05:06 andromeda org_kde_powerdevil[2412]: Initializing libddcutil. 
ddcutil version: 2.1.4, shared library: /usr/lib64/libddcutil.so.5.1.2
Dec 05 09:05:07 andromeda org_kde_powerdevil[2412]: busno=14, Feature 0xdd
should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00
ml=0x64 sh=0x00 sl=0x64
Dec 05 09:05:07 andromeda org_kde_powerdevil[2412]: busno=14, Feature 0x41
should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00
ml=0x64 sh=0x00 sl=0x64
Dec 05 09:05:07 andromeda org_kde_powerdevil[2412]: busno=14, Feature 0x00
should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00
ml=0x64 sh=0x00 sl=0x64
Dec 05 13:02:39 andromeda org_kde_powerdevil[2412]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_open_display2 -3030
Dec 05 13:02:40 andromeda org_kde_powerdevil[2412]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_open_display2 -3030
Dec 05 13:02:42 andromeda org_kde_powerdevil[2412]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_open_display2 -3030
Dec 05 13:02:45 andromeda org_kde_powerdevil[2412]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_open_display2 -3030
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-11-29 Thread Jelle De Loecker
https://bugs.kde.org/show_bug.cgi?id=482713

Jelle De Loecker  changed:

   What|Removed |Added

 CC||skerit_...@kipdola.com

--- Comment #36 from Jelle De Loecker  ---
On 6.2.3, I'm getting a very similar problem, though my setup is more
complicated. (But I think that doesn't matter in this case)

I have a Framework 16 laptop
- Integrated GPU
- Dedicated GPU extension
- AMD eGPU

After the initial boot, all the monitors are visible in the brightness applet.
I can modify them all.
After a screen lock + screen standby, all of them have disappeared from the
widget AND they're all at 30% brightness again.
Then I have to use another tool (like the GTK ddccontrol GUI) to actually
change the brightness.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-11-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #35 from kyle_day...@msn.com ---
*** Bug 496676 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-11-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

kyle_day...@msn.com changed:

   What|Removed |Added

 CC||kyle_day...@msn.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-11-14 Thread Marcus Johansson
https://bugs.kde.org/show_bug.cgi?id=482713

Marcus Johansson  changed:

   What|Removed |Added

 CC||marcus.typ.johansson@gmail.
   ||com

--- Comment #34 from Marcus Johansson  ---
Some kind of regression has been implemented.
This bug was fixed for me, but it came back again a week or so ago.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=494233

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-17 Thread d3vilguard
https://bugs.kde.org/show_bug.cgi?id=482713

d3vilguard  changed:

   What|Removed |Added

 CC||g.igna...@outlook.com

--- Comment #33 from d3vilguard  ---
This seems very similar to my findings  -
https://bugs.kde.org/show_bug.cgi?id=494233

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-16 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #31 from Jakob Petsovits  ---
(In reply to Julien Delquié from comment #30)
> Didn’t see anything strange, but patch doesn’t apply anymore against
> powerdevil v6.2.1.

PowerDevil in 6.2.1 already includes it (and a minor fix-up that also always
uses repeated tries after monitor wake-up).

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-16 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #30 from Julien Delquié  ---
(In reply to Julien Delquié from comment #29)
> Patch applied. I will test it.

Didn’t see anything strange, but patch doesn’t apply anymore against powerdevil
v6.2.1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-16 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #32 from Julien Delquié  ---
(In reply to Jakob Petsovits from comment #31)
> (In reply to Julien Delquié from comment #30)
> > Didn’t see anything strange, but patch doesn’t apply anymore against
> > powerdevil v6.2.1.
> 
> PowerDevil in 6.2.1 already includes it (and a minor fix-up that also always
> uses repeated tries after monitor wake-up).

Oh I remember you already told this in a previous comment, sorry!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-14 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #29 from Julien Delquié  ---
Patch applied. I will test it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-14 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #28 from Jakob Petsovits  ---
Hey guys, the commit above is introducing repeated retries for PowerDevil's
DDC/CI support. This applies to both initialization and setting brightness.
Plasma 6.2.1 will have the change, please test if this fixes any issues for you
and leave a comment in case something still isn't working.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-14 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

Jakob Petsovits  changed:

   What|Removed |Added

  Latest Commit||48453745b1cfb0fce66e16ec9ef
   ||8caf961e79677

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-14 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #27 from Jakob Petsovits  ---
Git commit 48453745b1cfb0fce66e16ec9ef8caf961e79677 by Jakob Petsovits.
Committed on 14/10/2024 at 23:04.
Pushed by jpetso into branch 'Plasma/6.2'.

daemon: Retry failed DDC/CI reads and writes repeatedly

DDC/CI communication with monitors can be unreliable,
especially when the monitor is still in the process of
fully waking up. The moment that we receive a connection
or DPMS awake event may not be the moment that brightness
commands start working.

Prior to this commit, `DDCutilDisplay` protected itself against
this case with a drastic measure: if a read or write command
failed, the object would claim brightness controls as
unsupported. This error condition meant that we won't end up
with inconsistent state, but it also makes the monitor's
brightness slider go away (or fall back to software
brightness controls if KWin wants those instead).

This commit still uses the same failure mode, but will try
harder before we give up on the monitor altogether.
Both initialization (reading the initial brightness value)
and `setBrightness()` will now retry a few times if the
first attempt didn't work out. Subsequent retries will be
spaced out further, until we finally give up on that monitor.

To avoid exposing uninitialized `DDCutilDisplay` objects,
a list of pending displays now holds these objects while
they're waiting for another initialization attempt.

`setBrightness()` will only be performed once initialization
has succeeded, so the two operations are mutually exclusive.
We can reuse DDCutilDisplay's existing brightness delay timer
for both kinds of retry operations.
Related: bug 493329


(cherry picked from commit 44e6922ae9f06a3e2fa3e7640be7eb32591cd579)

Co-authored-by: Jakob Petsovits 

M  +23   -11   daemon/controllers/ddcutildetector.cpp
M  +69   -15   daemon/controllers/ddcutildisplay.cpp
M  +8-2daemon/controllers/ddcutildisplay.h

https://invent.kde.org/plasma/powerdevil/-/commit/48453745b1cfb0fce66e16ec9ef8caf961e79677

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-10-14 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #26 from Jakob Petsovits  ---
Git commit 44e6922ae9f06a3e2fa3e7640be7eb32591cd579 by Jakob Petsovits.
Committed on 14/10/2024 at 22:36.
Pushed by jpetso into branch 'master'.

daemon: Retry failed DDC/CI reads and writes repeatedly

DDC/CI communication with monitors can be unreliable,
especially when the monitor is still in the process of
fully waking up. The moment that we receive a connection
or DPMS awake event may not be the moment that brightness
commands start working.

Prior to this commit, `DDCutilDisplay` protected itself against
this case with a drastic measure: if a read or write command
failed, the object would claim brightness controls as
unsupported. This error condition meant that we won't end up
with inconsistent state, but it also makes the monitor's
brightness slider go away (or fall back to software
brightness controls if KWin wants those instead).

This commit still uses the same failure mode, but will try
harder before we give up on the monitor altogether.
Both initialization (reading the initial brightness value)
and `setBrightness()` will now retry a few times if the
first attempt didn't work out. Subsequent retries will be
spaced out further, until we finally give up on that monitor.

To avoid exposing uninitialized `DDCutilDisplay` objects,
a list of pending displays now holds these objects while
they're waiting for another initialization attempt.

`setBrightness()` will only be performed once initialization
has succeeded, so the two operations are mutually exclusive.
We can reuse DDCutilDisplay's existing brightness delay timer
for both kinds of retry operations.
Related: bug 493329

M  +23   -11   daemon/controllers/ddcutildetector.cpp
M  +69   -15   daemon/controllers/ddcutildisplay.cpp
M  +8-2daemon/controllers/ddcutildisplay.h

https://invent.kde.org/plasma/powerdevil/-/commit/44e6922ae9f06a3e2fa3e7640be7eb32591cd579

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-09-19 Thread Dmitrii Chermnykh
https://bugs.kde.org/show_bug.cgi?id=482713

Dmitrii Chermnykh  changed:

   What|Removed |Added

 CC||chermnykh2...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #25 from matterhorn...@proton.me ---
I've also had similar odd behaviour so thought I'd record it here. For more
than three years using KDE on Tumbleweed I had my monitor (HP M24f 1080p)
plugged into my PC via the bundled HDMI cable, and was blissfully unaware that
changing the brightness of a monitor from software was even possible. Suddenly
– and I forget when exactly this was, but earlier this year – I noticed that a
brightness slider had appeared next to the Night Control toggle. And it worked!
I assumed that a Plasma update had added either the functionality or the
compatibility with my monitor.

I don't remember it being only sporadically available, though I didn't use it
all that much.

A short while ago, maybe a month or so but no idea really, I noticed that the
option was gone. And it stayed gone, so I assumed it was a regression. I didn't
think to report it at the time.

Now I got to wondering why it didn't work any more, did some googling, found
this bug report. I yesterday switched to using a DP to HDMI cable rather than
the old HDMI cable, and over the course of several reboots and logout/login
cycles it doesn't seem to ever work with this cable.

Weirdly, when I now switch back to the old cable, or another HDMI-HDMI cable,
the brightness control seems to consistently appear. Which would imply that
maybe the new DP-HDMI cable can't carry the DCC signal, something that would be
entirely unsurprising – but the thing is, it is only now when I'm fiddling
around with it and swapping back and forth that the brightness control appears
with the HDMI-HDMI cable, whereas at least for the past few weeks I am
absolutely 100% certain that it wasn't. But now I can't reproduce that.

Another point is that if I swap from one cable to another during a session
(i.e. the monitor is disconnected then reconnected via a different cable and
port on the GPU) there are no new entries printed to the log, and the
brightness slider either remains hidden or remains shown, but if I boot with
HDMI-HDMI, get shown the slider, then switch to DP-HDMI, the slider is still
shown but no longer has any effect (indeed, if I try to change the brightness
the widget gets stuck and freezes).

Should it be relevant, the cable in question is this one:
https://www.amazon.de/UGREEN-DisplayPort-Uni-Direktional-Multi-Screen-Kompatibel/dp/B07V3RYBVY
. It's advertised specifically as being one-way only, but at least some
information must flow from the monitor to the PC as it still picks up the model
name for instance.

I've attached the log output of both the successful and failed cases. If I ever
replicate the brightness slider failing to show with the HDMI-HDMI connection
then I'll post a log of that, too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #24 from matterhorn...@proton.me ---
Created attachment 173581
  --> https://bugs.kde.org/attachment.cgi?id=173581&action=edit
Log after connection with DP-HDMI and brightness slider was missing

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

matterhorn...@proton.me changed:

   What|Removed |Added

 CC||matterhorn...@proton.me

--- Comment #23 from matterhorn...@proton.me ---
Created attachment 173580
  --> https://bugs.kde.org/attachment.cgi?id=173580&action=edit
Log after connection with HDMI-HDMI and brightness slider was shown

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-09-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC|m...@ratijas.tk   |

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-08-23 Thread postix
https://bugs.kde.org/show_bug.cgi?id=482713

postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-08-18 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=482713

Julien Delquié  changed:

   What|Removed |Added

 CC||julien@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-08-16 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=482713

TraceyC  changed:

   What|Removed |Added

 CC||kde...@tlcnet.info

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=491605

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

   Priority|NOR |HI

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-27 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC||n...@d3sox.me

--- Comment #22 from Nate Graham  ---
*** Bug 487959 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #21 from zvova7...@gmail.com ---
It is probably due to a race condition between KWin mode setting up and
Powerdevil DDC/CI work. DDC detection should probably also be delayed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #20 from rjawiygv...@gmail.com ---
and this transition is also happening when it goes from sddm to plasma

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #19 from rjawiygv...@gmail.com ---
(In reply to rjawiygvozd from comment #18)
> (In reply to rjawiygvozd from comment #17)
> > Created attachment 171302 [details]
> > powerdevil.log
> 
> I had to restart the session multiple times before I replicated it but the
> last one has the problem.
> This is Plasma 6.1.1

Also I don't know if this is relevant but this monitor actually has a horrible
startup time and whenever it goes from bios graphics mode or whatever it's
called to a proper screen resolution it also spends at least a few seconds in
the black screen, to the point that pc boots way before I can actually see
anything

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #18 from rjawiygv...@gmail.com ---
(In reply to rjawiygvozd from comment #17)
> Created attachment 171302 [details]
> powerdevil.log

I had to restart the session multiple times before I replicated it but the last
one has the problem.
This is Plasma 6.1.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #17 from rjawiygv...@gmail.com ---
Created attachment 171302
  --> https://bugs.kde.org/attachment.cgi?id=171302&action=edit
powerdevil.log

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

 CC||k...@malplena.net

--- Comment #16 from Nate Graham  ---
*** Bug 489563 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #15 from zvova7...@gmail.com ---
rjawiygv...@gmail.com,

Could you please put this into /etc/environment and catch the situation when
you have unavailable brightness controls?
QT_LOGGING_RULES="*powerdevil*.debug=true"

Then save the logs: journalctl -b -t org_kde_powerdevil > /tmp/powerdevil.log
... and attach here. 

Just wan't to understand what is going on.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-07-02 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #14 from Jakob Petsovits  ---
Git commit 220b6b9531b21bb3d2cc790c6a3718af3df7aa7b by Volodymyr Zolotopupov.
Committed on 02/07/2024 at 08:35 CET.
Pushed by jpetso into branch 'master'.

ddcutildisplay: give some time before changing brightness after the monitor
resumes

M  +4-1daemon/controllers/ddcutildisplay.cpp

https://invent.kde.org/plasma/powerdevil/-/commit/220b6b9531b21bb3d2cc790c6a3718af3df7aa7b

And also cherry-picked into Plasma/6.1 (will be released with 6.1.2):
https://invent.kde.org/plasma/powerdevil/-/commit/0c084dcb444173273b60934af7bdb321d39dbf13

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-28 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #13 from Zamundaaa  ---
Git commit d91bc62fa6ff93ac62ded148fee3722deab41442 by Xaver Hugl.
Committed on 28/06/2024 at 15:00.
Pushed by zamundaaa into branch 'Plasma/6.1'.

core: reload actions on brightness controller changes

Whether or not the brightness control action is supported depends on the
currently
connected list of screens, which is dynamic and can't just be checked on
startup.
To fix this, reload actions when devices get added or removed

(cherry picked from commit 584cfdf0256bc7034be0b3fadf94f7b486597aa6)

Co-authored-by: Xaver Hugl 

M  +4-0daemon/controllers/screenbrightnesscontroller.cpp
M  +1-0daemon/controllers/screenbrightnesscontroller.h
M  +23   -27   daemon/powerdevilcore.cpp
M  +2-2daemon/powerdevilcore.h

https://invent.kde.org/plasma/powerdevil/-/commit/d91bc62fa6ff93ac62ded148fee3722deab41442

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-28 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #12 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/powerdevil/-/merge_requests/395

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-28 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #11 from Zamundaaa  ---
Git commit 584cfdf0256bc7034be0b3fadf94f7b486597aa6 by Xaver Hugl.
Committed on 28/06/2024 at 13:17.
Pushed by zamundaaa into branch 'master'.

core: reload actions on brightness controller changes

Whether or not the brightness control action is supported depends on the
currently
connected list of screens, which is dynamic and can't just be checked on
startup.
To fix this, reload actions when devices get added or removed

M  +24   -27   daemon/powerdevilcore.cpp
M  +2-2daemon/powerdevilcore.h

https://invent.kde.org/plasma/powerdevil/-/commit/584cfdf0256bc7034be0b3fadf94f7b486597aa6

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-27 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #10 from zvova7...@gmail.com ---
I'm getting -3029 error.

Created MR: https://invent.kde.org/plasma/powerdevil/-/merge_requests/393

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-26 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #9 from Jakob Petsovits  ---
(In reply to zvova7890 from comment #6)
> I don't think it is my case, but with 6.1 I have issues when the monitor
> goes to sleep (DPMS). Probably, when it wakes up, Powerdevil tries to work
> with HDMI/DP i2c too early, and the monitor sometimes isn't yet ready to
> respond.

Thanks for running this experiment. Might be related to Bug 476540, which is
also seemingly related to DPMS. (My theory is that we should disable any
brightness commands while DPMS has the monitor turned off, and then apply the
last requested brightness after the monitor comes back.)

Could you check what the value of `status` is when ddca_open_display2() fails?
ddcutil_status_codes.h doesn't have a "wait and try again" status code like
EAGAIN, but I wonder if perhaps DDCRC_DPMS_ASLEEP (value -3030) serves a
similar purpose in this case.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #8 from zvova7...@gmail.com ---
Yes, sure. When I am certain it is working, I will make an MR. Today, I
encountered the issue again with this patch, so the place I am fixing is
probably wrong. Now, I have enabled more logs and am testing another fix.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #7 from Nate Graham  ---
Nice, would you like to submit that upstream so the developers can take a look.
Generally patches in Bugzilla tickets get overlooked.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

zvova7...@gmail.com changed:

   What|Removed |Added

 CC||zvova7...@gmail.com

--- Comment #6 from zvova7...@gmail.com ---
I don't think it is my case, but with 6.1 I have issues when the monitor goes
to sleep (DPMS). Probably, when it wakes up, Powerdevil tries to work with
HDMI/DP i2c too early, and the monitor sometimes isn't yet ready to respond.

I have fixed(seem, still testing) it with this patch:
diff --git a/daemon/controllers/ddcutildisplay.cpp
b/daemon/controllers/ddcutildisplay.cpp
index 1e1a274..09a5c93 100644
--- a/daemon/controllers/ddcutildisplay.cpp
+++ b/daemon/controllers/ddcutildisplay.cpp
@@ -49,7 +49,15 @@ DDCutilDisplay::DDCutilDisplay(DDCA_Display_Ref displayRef)
 // backed by libddcutil (like the ddcutil CLI itself) from functioning.

 DDCA_Display_Handle displayHandle = nullptr;
-if (status = ddca_open_display2(m_displayRef, true, &displayHandle);
status != DDCRC_OK) {
+status = ~status;
+for (int i = 0; i < 2 && status != DDCRC_OK; ++i) {
+if (status = ddca_open_display2(m_displayRef, true, &displayHandle);
status != DDCRC_OK) {
+QThread::msleep(200);
+continue;
+}
+}
+
+if (status != DDCRC_OK) {
 qCWarning(POWERDEVIL) << "[DDCutilDisplay]: ddca_open_display2" <<
status;
 return;
 }

Just a quick fix, but it can potentially confirm my theory. So, maybe it is
required to add some mechanism to handle this situations.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #5 from rjawiygv...@gmail.com ---
(In reply to rjawiygvozd from comment #4)
> This problem doesn't seem to be present on Plasma 6.0.5 that comes with
> Manjaro

Actually no, it still exists

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #4 from rjawiygv...@gmail.com ---
This problem doesn't seem to be present on Plasma 6.0.5 that comes with Manjaro

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-03-08 Thread Sdar
https://bugs.kde.org/show_bug.cgi?id=482713

Sdar  changed:

   What|Removed |Added

 CC||s...@vivaldi.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-03-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #3 from rjawiygv...@gmail.com ---
In the meantime now that I know DDC is a thing I've learned there is something
called "ddcci-driver-linux" which provides a kernel module that apparently
exposes DDC brightness control as typical brightness control so it just works
everywhere

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-03-07 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=482713

--- Comment #2 from Jakob Petsovits  ---
We don't really have control over the list of monitors that ddcutil tells us
about. It's unclear to me why your monitor would sometimes be detected and
sometimes not. Maybe ddcutil would always detect it after a while, but it
doesn't wait long enough before reporting back the list of displays to Plasma's
power management service. Not sure.

Chances are, once we react better to changes in detected monitors, this might
get fixed in practice. For Plasma 6.1, we've already merged a patch that
recognizes added or removed DDC monitors. More work is needed to hook this up
to the Brightness and Color applet so the slider gets added and removed on the
fly, without having to log in again to restart Plasma.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 482713] DDC-based Screen brightness control randomly unavailable in some sessions

2024-03-07 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482713

Nate Graham  changed:

   What|Removed |Added

   Severity|minor   |normal
 CC||jpe...@petsovits.com,
   ||n...@kde.org
   Keywords|qt6 |
Summary|Screen brightness control   |DDC-based Screen brightness
   |randomly unavailable in |control randomly
   |some sessions   |unavailable in some
   ||sessions

--- Comment #1 from Nate Graham  ---
Bugs in DDC support, I suppose.

-- 
You are receiving this mail because:
You are watching all bug changes.