user-changed brightness settings do not survive re-boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Most of Ubuntu's System Settings survive re-boot, but changing the screen brightness does not.
This is annoying to me because every time I boot up I must lower the settings manually.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: compiz 1:0.9.9~
ProcVersionSign
Uname: Linux 3.8.0-13-generic x86_64
.tmp.unity.
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
Date: Mon Mar 18 15:40:27 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2203]
InstallationDate: Installed on 2013-01-04 (73 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130102)
MachineType: LENOVO 3434CTO
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET21WW (1.10 )
dmi.board.
dmi.board.name: 3434CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 3434CTO
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.9~
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.42-0ubuntu2
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Mon Mar 18 15:30:40 2013
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu2b1
xserver.
Status changed to 'Confirmed' because the bug affects multiple users.