f.lux not working on 4.4.0-38

[rob]

f.lux does not change screen brightness

lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rob 1275 F.... pulseaudio
 /dev/snd/controlC0: rob 1275 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Sep 28 02:24:37 2016
HibernationDevice: RESUME=UUID=a8eba1de-75f8-4e4b-b7b2-4ee1e7e91229
InstallationDate: Installed on 2016-07-09 (81 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp2s0 no wireless extensions.

 lo no wireless extensions.
MachineType: ZOTAC ZBOX-MI520-X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=eaa5f618-d44d-44db-9359-617ce3b92a86 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic N/A
 linux-firmware 1.157.3
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B239P202
dmi.board.asset.tag: NA
dmi.board.name: ZBOX-MI520-X
dmi.board.vendor: ZOTAC
dmi.board.version: XX
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB239P202:bd08/13/2015:svnZOTAC:pnZBOX-MI520-X:pvrXX:rvnZOTAC:rnZBOX-MI520-X:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: ZBOX-MI520-X
dmi.product.version: XX
dmi.sys.vendor: ZOTAC

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 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'.

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.8

[rob (calvin8714)]

Joseph,

Yes, this started happening after an upgrade. Unfortunately, I don't remember the last kernel I had and it's since been removed where it was working. I stay on stable builds though, if that helps with identifying the previous Kernel. (If there's logs stored for upgrades, let me know where to look and I'll follow up.)

uname -a
Linux rob-media 4.8.0-040800-generic #201610022031 SMP Mon Oct 3 00:32:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Followed the instructions above with the mainline kernel builds linked above, and it seems that f.lux doesn't effect anything.

[rob (calvin8714)]

Just tried doing a 'sudo apt-get upgrade' command, and the entries contain:

linux-headers-4.4.0-36-generic
linux-image-4.4.0-36-generic
linux-image-extra-4.4.0-36-generic

The original log above has "linux-image-4.4.0-38-generic 4.4.0-38.57," so this must be the prior Kernel where f.lux was working, right?

[rob (calvin8714)]

One more, sorry. The comment above appeared when doing 'sudo apt-get upgrade,' and appeared below, "The following packages were automatically installed and are no longer required:"

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]