Xrandr gamma and brightness problem on 4.4.0-34 kernel

Bug #1613359 reported by Roberto D.
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Situation

Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34.

If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness
xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25

In eDP1 already 60 hertz and already 1368x768

Nothing is happening.

The change in brightness occurs if you change the resolution:
xrandr --output eDP1 --mode 1024x768

The screen is considerably brighter.

After the command:

xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1

Nothing happens, but the change of brightness occurs to the resolution change.

for example

xrandr --output eDP1 --mode 1360x768
or
xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1

Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately.

Is my first report, I hope it is clear. Thank you.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: robby 3691 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a
InstallationDate: Installed on 2016-07-01 (44 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: HP HP ENVY Notebook
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic N/A
 linux-firmware 1.157.3
Tags: xenial
Uname: Linux 4.4.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/19/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80E5
dmi.board.vendor: HP
dmi.board.version: 87.57
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

Colin Watson (cjwatson)
affects: launchpad → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1613359

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Roberto D. (lucius1202) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Roberto D. (lucius1202) wrote : CRDA.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : IwConfig.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : JournalErrors.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : Lspci.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : Lsusb.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : ProcEnviron.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : ProcModules.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : PulseList.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : RfKill.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : UdevDb.txt

apport information

Revision history for this message
Roberto D. (lucius1202) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.17

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key regression-update
Revision history for this message
Roberto D. (lucius1202) wrote :

kernel-unable-to-test-upstream

I have installed the package that you have shown me, as explained in the wiki but with errors, missing dependency. I am unable to boot the mainline kernel. Sorry.

Revision history for this message
Ondrej Mosnáček (omosnacek) wrote :

I tested the current latest version (4.4.19) and it appears the bug is fixed there.

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The proposed Xenial kernel now has the 4.4.19 updates and is in the -proposed repository. Would it be possible for you to test this latest kernel and post back if it resolves this bug?

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Revision history for this message
Roberto D. (lucius1202) wrote :

Sorry but I'm a low-level user and the distribution I am using is that of daily productivity. I risk to mix packages that I can not recover. I am sorry not to be able to deepen my report.

Revision history for this message
Roberto D. (lucius1202) wrote :

I have an update, after my post above, I checked manually if there were any updates.

sudo apt update
apt list --upgradable

I noticed that there was a new version of the kernel to be updated.

4.4.0-36-generic

I have updated:

sudo apt upgrade

Restarted the computer the problem with brightness and gamma has disappeared.

This behavior is normal.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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.