Ubuntu Zesty: Problem With Screen Brightness Settings

Bug #1681493 reported by aljosa
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
NVIDIA Drivers Ubuntu
Invalid
Undecided
Unassigned
nvidia-graphics-drivers-375 (Ubuntu)
Invalid
Undecided
Unassigned
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Non-Optimus laptop ASUS G752VS (Nvidia GTX1070)
Ubuntu 17.04
Xorg-Server-1.19.3
Nvidia driver 375.39

Situation on 2017-04-05:
Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum.

Situation on 2017-04-08:
Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA).
Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed)

Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1"

~$ systemctl status systemd-backlight@backlight:acpi_video0.service
● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo
   Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago
     Docs: man:systemd-backlight@.service(8)
 Main PID: 683 (code=exited, status=0/SUCCESS)

~$ systemctl status systemd-backlight@backlight:acpi_video1.service
● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo
   Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago
     Docs: man:systemd-backlight@.service(8)
 Main PID: 684 (code=exited, status=0/SUCCESS)

Situation on 2017-04-10:
I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers.
Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum.
---
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-01-02 (98 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc.
 Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. G752VS
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: systemd 232-21ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Tags: zesty
Uname: Linux 4.10.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 10/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VS.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G752VS
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
aljosa (aljosa-p) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
aljosa (aljosa-p) wrote : Dependencies.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : JournalErrors.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : Lspci.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : ProcEnviron.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : ProcInterrupts.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : ProcModules.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : SystemdDelta.txt

apport information

Revision history for this message
aljosa (aljosa-p) wrote : UdevDb.txt

apport information

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-375 (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Maxim (makseq) wrote :

I have very similar problem, details are here: https://askubuntu.com/q/935585/698509

Revision history for this message
Maxim (makseq) wrote :

I think this bug may be connected with display matrices: asus g752vs and my laptop have b172han01. I made a display replacement and this problem appeared after this.

Revision history for this message
dino99 (9d9) wrote :
Changed in systemd (Ubuntu):
status: Confirmed → Invalid
Changed in nvidia-graphics-drivers-375 (Ubuntu):
status: Confirmed → Invalid
Changed in nvidia-drivers-ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.