Is this a Trinity problem or hardware? I have a Thinkpad T400. Adjusting the screen brightness works with the Fn-Home and Fn-End key combinations regardless of whether I'm using Trinity.

(In reply to comment #1)
> Is this a Trinity problem or hardware? I have a Thinkpad T400. Adjusting the
> screen brightness works with the Fn-Home and Fn-End key combinations regardless
> of whether I'm using Trinity.

It's just as I described it.

When I start up the machine after hibernation, sometimes the screen is at max brightness, sometimes it's how it was set before hibernation.

Starting "Configure KPowersave" from the power/battery status applet (KPowersave-trinity?) restores the brightness and the slider works.

But once I use fn-down to change the brightness the screen goes to max-brightness and the on-screen display indicates zero brightness.

Pressing fn-up shows the osd with its zero brightness indicator but otherwise does nothing.

Changing from NEEDINFO -> NEW as I believe I supplied the requested information.

Maybe this is related: I'm also having problems with the volume control.

I've got kmix runnimg and the <Fn-key>+left, <Fn-key>+right keys change the volume by one small jump, so I can change the master volume on Intel HDA PCH from 68 to 72, that's it.

The volume buttons don't change the pulseaudio mixer volume in kmix at all.

If I change the master volume then I get two different choices, e.g. 50 and 59.
To investigate some more I ran pavucontrol and noticed that the volume buttons do the two-value thing there too.

Maybe I've got some residual config - I'll try setting up another account.

Same behaviour with a new account :(

Hi Philip,
just for info, is this on 3.5.13.2 or on R14.0.x? Are you using Kpowersave or TDEPowersave?

I'm using R14.0.2 with TDEPowerSave.

Out of curiosity I tried KDE 4 and it has issues too - brightness isn't the whole range and it's sound system has no clue that I can't hear anything from my speakers, but when it works (earphones?) the "media" keys can adjust the volume like they should.

I was watching a movie recently and the power just died - I hadn't plugged in the charger.
No warning, no hibernate.

Just now as I wanted to try Ubuntu again I logged out, then realized I wanted to reboot so I shut down and, from the login screen, I was dropped to the command prompt.

Plenty of Ubuntu updates and I'm writing this.

Apparently there are xdg compliance tests and the X-window message boxes told me where to read about the errors (something failed with return code 3).

I selected the file location and typed Ctrl-C.
It didn't save the file location to the clipboard.

Now I'm in Ubuntu the volume control works fine with the Samsung/Laptop "Fn" meta-key and via the multimedia keys.

About 1 in 3 times the sound system starts off muted, with pulseaudio and "HDA Intel PCH" devices.

The screen brightness Fn-buttons don't work.

Now my touchpad features like circular scrolling don't work.

As that's much more inconvenient to deal with I'm going back to Debian...

I just rebooted in case the kernel flags I pass were a factor.

linux   /vmlinuz-3.19.0-47-generic root=/dev/mapper/Vg750-ubuntu resume=/dev/mapper/Vg750-swap ro quiet acpi_backlight=vendor samsung-laptop.force cryptopts=target=750,source=UUID=ace8c59d-c5f7-424a-a374-58d103c68788,key=none,rootdev,lvm=Vg750-ubuntu crashkernel=256M nmi_watchdog=1 b43.allhwsupport=1

As the update rewrote grub.cfg it didn't use these flags so I guess not a factor.

I noted the X-server message box text with a pen and paper this time (!)
r14-xdg-update - error code 3.

Check files for
   '/opt/trinity/share/applications/kde'
in
  /var/tmp/tdecache-contact/r14-xdg-update-validation-test3.txt

The file contains one line:
  /home/contact/.trinity/share/apps/kdesktop/IconPositions/backtrace.mod

I bought a new hard disk and installed everything from scratch.
I can now assign the media keys for volume up-down and they show that little on screen display.
I still don't know how to assign global shortcuts for the brightness keys so I created two
   "Regional & Accessibility" -> "Input actions"
for brightness up/down:

Brightness Up:
Action type: Keyboard shortcut -> DCOP Call(simple)
Keyboard shortcut: XF86KbdBrightnessUp
Remote application: tdepowersave
Remote object: tdepowersaveIface
Called function: do_brightnessUp
Arguments: 5

Brightness Down:
Action type: Keyboard shortcut -> DCOP Call(simple)
Keyboard shortcut: XF86KbdBrightnessDown
Remote application: tdepowersave
Remote object: tdepowersaveIface
Called function: do_brightnessDown
Arguments: 5

There must be a "Trinity" way to do this.

Notes:
1. When installing Debian onto the new hard disk I transferred the old hard disk to the secondary drive bay in my laptop.
Once the Debian installation was complete with "Guided, with encrypted LVM" the crypto-luks partition on the secondary hard disk is now reported as being a "lvm2 pv".
Did I accidentally hose my old crypto-luks partition by letting the Debian installer see it?
Anyone know of a way to set it back to crypto-luks so cryptsetup can open it?
I had a recent-ish backup to fall back on but I'd prefer not having to rewrite stuff.

2. Before, I had to sudo su; synaptic to run synaptic from the terminal.
   Now sudo synaptic works again as it used to.

Maybe the hard disk failed, but I ran a SMART scan and it reported no errors.

Hi Philip,
I am still not clear whether this is a TDE issue or a hardware/bios issue, since you mentioned it happened also with KDE.
What's the status of this bug?

Brightness change using keyboard shortcuts has been added in R14.0.9 using the generic monitor, see https://mirror.git.trinitydesktop.org/gitea/TDE/tdeutils/pulls/21. Unaware of comment 10, if does actually a similar thing, just within kmilo instead of using input actions.

If you still experience problems with R14.0.9, please reopen this bug and I will take a look.