By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2020

Summary:	Your hardware does not currently support changing the brightness of your display
Product:	TDE	Reporter:	Philip Ashmore <contact>
Component:	other (any)	Assignee:	Timothy Pearson <kb9vqf>
Status:	NEW ---
Severity:	normal	CC:	bugwatch, contact, michele.calgaro
Priority:	P5
Version:	3.5.13.x [Trinity]
Hardware:	amd64
OS:	Debian Wheezy
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2968

Description Philip Ashmore 2014-03-23 19:52:55 CDT

I just upgraded to kernel linux-image-3.13-0.bpo.1-amd64 from wheezy-backports.

When I open the KPowersave dialog and choose brightness it says that "Your Hardware currently not support changing the brightness of your display."

I can, however adjust the brightness by echoing any number from 0 to 7 to /sys/class/backlight/samsung/brightness

- as root.

Comment 1 Michele Calgaro 2018-08-02 02:17:51 CDT

Does this happen with TDEPowersave as well? What is the status of the bug?

Comment 2 Philip Ashmore 2018-08-02 05:19:02 CDT

I added to Regional&Accessibility->InputActions->MediaKeys:
brightness up: shortcut XF86KbdBrightnessUp
  DCOP Call Settings:
    tdepowersave->tdepowersafeIface->do_brightnessUp(5)
brightness down: shortcut XF86KbdBrightnessDown
  DCOP Call Settings:
    tdepowersave->tdepowersafeIface->do_brightnessDown(5)

There is no on-screen indication like with volume control.

Comment 3 Michele Calgaro 2018-08-02 07:59:59 CDT

ok, let's keep the bug open. Thanks for the feedback

Comment 4 Michele Calgaro 2023-09-06 01:04:22 CDT

There has been several changes in the code related to brightness controls and OSD feebdack. Things should now be working fine and this bug could be closed IMO.
Is that ok?

Comment 5 Philip Ashmore 2023-09-13 13:52:18 CDT

I'm still getting

Your hardware does not currently support changing the brightness of your display.

Honestly, I'm not surprised.

I've got a janky display setup on my laptop:
Console -> laptop display
GUI -> nvidia micro-displayport

I had a janky fix before I left my PC in for repair, which was to send brightness commands directly to the monitor using ddccontrol, but even that doesn't work if I'm watching a movie through Google Chromecast.

I had to hard code the i2c port to use, just trial and error.

gddccontrol fares better but there's no general way that I know of to identify the "active" display.

Although gddccontrol does identify the active display it takes a second, plus there's no way to bind global shortcuts through gddccontrol to the active display - it probably involves some digging.

I believe DDC (Display Data Channel) only works if the graphics adapter output is the active input for the monitor.

I can still pause and seek using the keyboard as it's going through ChromeCast.

I honestly can't remember if I could change the display brightness through ChromeCast when the Trinity keyboard shortcuts for display brightness worked.

So, yeah, keep the bug open or close it, either is fine with me.

Maybe this bug can serve as a jotter for those of us with more obscure display setups :)

Comment 6 Michele Calgaro 2023-09-14 20:12:19 CDT

Hi Philip,
good to see you are still around :-)
I was inaccurate in my last comment, because I forgot to specify that part of the changes have been done recently and will be part of R14.1.1 release.

What version of TDE are you using? If you are on R14.1.0 or R14.0.x, then definitely things could be broken.

Comment 7 Philip Ashmore 2023-09-20 11:47:55 CDT

I'm on R14.1.1~DEVELOPMENT

Comment 8 Michele Calgaro 2023-09-20 21:19:04 CDT

Ok, will leave the bug open, just so it does not get forgotten.