[karmic] gnome-power-preferences not storing settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power |
Fix Released
|
Critical
|
|||
gnome-power-manager (Ubuntu) |
Fix Released
|
Critical
|
Canonical Desktop Team | ||
Karmic |
Fix Released
|
Critical
|
Canonical Desktop Team |
Bug Description
Binary package hint: gnome-power-manager
Actions:
Open gnome-power-
Change settings
Close gnome-power-
Result:
Power management does not follow the set options. Opening the preference window again, shows the settings according to some default and do not reflect the choices I made earlier.
Expected result:
The settings should have been stored in the configuration.
The attached log shows the output of:
gnome-power-
gnome-power-
It seems like the settings are not properly stored and/or reset on opening the application.
ProblemType: Bug
Architecture: amd64
Date: Fri Jul 31 22:29:36 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.27.2+
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSign
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-4-generic x86_64
Related branches
Changed in gnome-power: | |
status: | Unknown → New |
Changed in gnome-power-manager (Ubuntu Karmic): | |
assignee: | nobody → Canonical Desktop Team (canonical-desktop-team) |
Changed in gnome-power: | |
importance: | Unknown → Critical |
status: | New → Fix Released |
Thanks for your report and helping make Ubuntu better. Since you have attached all the relevant logs, I'm marking as confirmed. Since this will affect a large population of users, the status is high (especially since there is potential data loss from unwanted shutdowns, suspends, etc.)
There is another release of GPM coming out next week. Let's test that version (2.27.3-0ubuntu1) and see if the bug still exists. If it does, we should report this bug upstream. Forwarding instructions please have a look to http:// wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you forward the bug, please post a link to the upstream bug report here.