Ubuntu
gnome-settings-daemon package

Screen brightness does not persist over reboots

Bug #974260 reported by Ivan Katanović on 2012-04-05

This bug affects 12 people

	Status	Importance	Assigned to
Unity Greeter	Invalid	Undecided	Unassigned
ubuntu-nexus7	Incomplete	Medium	Unassigned
gnome-settings-daemon (Ubuntu)	Invalid	Medium	Unassigned
ubuntu-defaults-nexus7 (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

The brightness of laptop panel is set to minimum instead to maximum when system starts. In Natty and older Ubuntu versions it was set to minimum during boot, and wold go to maximum just before login screen. In Onerick and Precise it just stays at minimum until changed manually to higher values. Laptop is connected to power.
I have Nvidia G105M GPU. On laptop with Intel graphics and Onerick I can't reproduce this.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-22-generic 3.2.0-22.35
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mile 1998 F.... pulseaudio
CheckboxSubmission: 9448ae01985a062cb9f7d6705930e25a
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
Date: Thu Apr 5 15:31:51 2012
HibernationDevice: RESUME=UUID=4dfa8c64-5b19-422d-be25-6053b9b44eab
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111004)
MachineType: Acer Extensa 5635G
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=67f9c537-e53e-444a-98d0-12afd884e79e ro quiet splash pcie_aspm=force vt.handoff=7
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-01-07 (88 days ago)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.3311
dmi.board.name: BA50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5635G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
---
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 12.10
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
NonfreeKernelModules: nvidia
Package: gnome-settings-daemon 3.4.2-0ubuntu14
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Tags: quantal running-unity
Uname: Linux 3.5.0-17-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-08-28 (40 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

See original description

Tags:

Related branches

lp:ubuntu/raring-proposed/ubuntu-defaults-nexus7

Revision history for this message

Ivan Katanović (igadmile-deactivatedaccount) wrote on 2012-04-05:

AcpiTables.txt Edit (198.9 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (437 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (281 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (160 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (59.3 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.info.txt Edit (184 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (7.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (511 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (13.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (670 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (609 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (329 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.8 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (17.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (138 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (190 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (121.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (267.4 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (222.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-04-05:

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

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Ivan Katanović (igadmile-deactivatedaccount) wrote on 2012-04-05:

I've just installed Kubuntu Precise and can't reproduce this bug (brightness sets to maximum while Kde is loading).
Maybe it's lightdm since it's introducet in Onerick?

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-04-05:

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc1-precise/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
tags:	added: needs-upstream-testing
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Ivan Katanović (igadmile-deactivatedaccount) wrote on 2012-04-05:

I've tested with 3.4rc1 and the bug isn't fixed (although nvidia proprietary driver did't work). But as I said, with Kubuntu Precise I don't have this bug so maybe this isn't kernel bug?

tags:	added: kernel-bug-exists-upstream removed: needs-upstream-testing
Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Joseph Salisbury (jsalisbury) on 2012-04-05

Changed in linux (Ubuntu):
status:	Confirmed → Triaged

Revision history for this message

Seth Forshee (sforshee) wrote on 2012-04-06:

This probably isn't a kernel issue. Backlight drivers generally only change the brightness when told to do so by userspace, although sometimes system firmware plays a role as well.

But based on the described behavior, I suspect that it was userspace setting the brightness value when the login screen appeared. gnome-settings-daemon is what will actually be applying the brightness settings, so I'm going to reassign the Linux task to that.

affects:	linux (Ubuntu) → gnome-settings-daemon (Ubuntu)
Changed in gnome-settings-daemon (Ubuntu):
status:	Triaged → Confirmed

Robert Ancell (robert-ancell) on 2012-05-02

affects:

lightdm → unity-greeter

Revision history for this message

Ivan Katanović (igadmile-deactivatedaccount) wrote on 2012-09-06:

still happens in quantal

Revision history for this message

Ivan Katanović (igadmile-deactivatedaccount) wrote on 2012-10-08: Dependencies.txt

Dependencies.txt Edit (7.0 KiB, text/plain)

apport information

tags:	added: apport-collected quantal running-unity
description:	updated

Revision history for this message

Ivan Katanović (igadmile-deactivatedaccount) wrote on 2012-10-08: ProcEnviron.txt

ProcEnviron.txt Edit (301 bytes, text/plain)

apport information

Daniel van Vugt (vanvugt) on 2012-11-07

tags:

added: mobile nexus7

Revision history for this message

Chris Wayne (cwayne) wrote on 2012-11-09: Re: Brightnes of laptop panel is set to minimum when system starts

#10

So this bug is more about the brightness level not being saved upon a reboot, therefore marking as confirmed for nexus7 as I have reproduced this.

Changed in ubuntu-nexus7:
status:	New → Confirmed

Chris Wayne (cwayne) on 2012-11-09

summary:

- Brightnes of laptop panel is set to minimum when system starts
+ Brightness of laptop panel is set to minimum when system starts

Chris Wayne (cwayne) on 2012-11-13

summary:	- Brightness of laptop panel is set to minimum when system starts + Screen brightness does not persist over reboots
Changed in ubuntu-nexus7:
importance:	Undecided → Medium

Revision history for this message

Matt Fischer (mfisch) wrote on 2012-11-13:

#11

There's a Gnome bug about this filed against gnome-applets in 2009 with no activity:

https://bugzilla.gnome.org/show_bug.cgi?id=577978

Revision history for this message

Sean Feole (sfeole) wrote on 2012-12-10:

#12

Still an issue in 13.04 , raring.

Alex Chiang (achiang) on 2013-01-28

tags:

added: sensors

Revision history for this message

Srdjan Grubor (srdjan-grubor) wrote on 2013-02-06:

#13

On ubuntu-nexus7, I don't think this bug applies as the user reports are caused by /usr/bin/luxd dynamically setting the brightness based on the light sensor input. I'm adding more info to Nexus 7 bug report (https://bugs.launchpad.net/ubuntu-nexus7/+bug/1075473)

Revision history for this message

Oliver Grawert (ogra) wrote on 2013-02-06:

#14

this bug pre-dates the inclusion of luxd, luxd is just an interim solution while the function is added to gnome-settings-daemon properly (with a checkbox to allow manual vs auto-setting of the backlight)

fixes to luxd are indeed welcome in the interim ...

Sasa Paporovic (melchiaros) on 2013-02-16

tags:

added: raring

Revision history for this message

Felipe van Schaik Willig (felipevsw) wrote on 2013-02-17:

#15

I have a laptop Asus K45A. Just installed Ubuntu 13.04 daily 2013-02-16. And after every reboot, the screen brightness is set to maximum instead of keep the way I'd configured it before the reboot. Really annoying.

Revision history for this message

Oliver Grawert (ogra) wrote on 2013-03-14:

#16

a new ubuntu-defaults-nexus7 with luxd removed was uploaded ... please check if the issue still persists on the recent nexus7 images

Changed in gnome-settings-daemon (Ubuntu):
status:	Confirmed → Invalid
Changed in unity-greeter:
status:	New → Invalid
Changed in ubuntu-defaults-nexus7 (Ubuntu):
status:	New → Incomplete
Changed in ubuntu-nexus7:
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-03-14:

#17

This bug was fixed in the package ubuntu-defaults-nexus7 - 0.54

---------------
ubuntu-defaults-nexus7 (0.54) raring; urgency=low

* drop luxd (LP: #974260 ), (LP: #1077096) (LP: #1126836)
-- Oliver Grawert <email address hidden> Thu, 14 Mar 2013 10:12:10 +0100

Changed in ubuntu-defaults-nexus7 (Ubuntu):
status:	Incomplete → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #942756

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

gnome-bugs #577978
[UNCONFIRMED] Edit

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

Ubuntugnome-settings-daemon package

Screen brightness does not persist over reboots

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-settings-daemon package