Brightness set to maximum after DPMS standby

Bug #1490229 reported by Czikus
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

After configuring screen energy saving in KDE, I noticed that after DPMS standby, my screen brightness is set to maximum. This is confirmed by `cat /sys/class/backlight/intel_backlight/brightness`. The problem can be easily reproduce by switching to standby manually using `xset dpms force standby`.

Steps to reproduce:
1) echo "300" | sudo tee /sys/class/backlight/intel_backlight/brightness
2) cat /sys/class/backlight/intel_backlight/brightness
This will report: 300
3) xset dpms force standby
4) Move mouse/press key
5) cat /sys/class/backlight/intel_backlight/brightness
This will report 937

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Aug 29 21:26:27 2015
InstallationDate: Installed on 2015-08-10 (20 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150809)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
BootLog: enabled, not active
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: wily
DistroRelease: Ubuntu 15.10
DistroVariant: kubuntu
DkmsStatus:
 virtualbox, 5.0.4, 4.2.0-10-generic, x86_64: installed
 virtualbox, 5.0.4, 4.2.0-7-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:13bd]
InstallationDate: Installed on 2015-08-10 (40 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150809)
Lsusb:
 Bus 001 Device 005: ID 03eb:8a0c Atmel Corp.
 Bus 001 Device 004: ID 1bcf:2987 Sunplus Innovation Technology Inc.
 Bus 001 Device 003: ID 8087:07dc Intel Corp.
 Bus 001 Device 002: ID 8087:8000 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX301LAA
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic.efi.signed root=UUID=103e34fc-23b4-497c-ac6b-791d423bee52 ro quiet splash acpi_osi= i915.powersave=1 i915.semaphores=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 drm.vblankoffdelay=1 vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
Tags: wily kubuntu single-occurrence reproducible has-workaround has-fix
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgConf:
 Section "Extensions"
     Option "Composite" "Disabled"
 EndSection
_MarkForUpload: True
dmi.bios.date: 05/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX301LAA.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX301LAA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX301LAA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Sep 19 18:26:05 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5126
 vendor SHP
xserver.version: 2:1.17.2-1ubuntu7

Revision history for this message
Czikus (czikus-gmail) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Czikus, could you please run the following command from a terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg 1490229

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Czikus (czikus-gmail) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected has-fix has-workaround kubuntu reproducible single-occurrence
description: updated
Revision history for this message
Czikus (czikus-gmail) wrote : Dependencies.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : DpkgLog.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : JournalErrors.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : Lspci.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : ProcModules.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : UdevDb.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : XorgLog.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : XorgLogOld.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : Xrandr.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : xdpyinfo.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote : xserver.devices.txt

apport information

Revision history for this message
Czikus (czikus-gmail) wrote :

Done. Please note that the following errors:

[drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)
[ 254.128904] ------------[ cut here ]------------
[ 254.128960] WARNING: CPU: 0 PID: 2279 at /build/linux-i3y0fS/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
[ 254.128963] pipe state doesn't match!

that are polluting the logs are a new regression due to bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492764

The problems reported in this bug appeared before the bug 1492764 occurred.

penalvch (penalvch)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in xorg (Ubuntu):
status: New → Won't Fix
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.