Ubuntu
casper package

Gnome-power-manager postinst not run

Bug #45654 reported by Matthew Garrett
8
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Fix Released
Medium
Tollef Fog Heen

Bug Description

Binary package hint: ubiquity

The postinst for gnome-power-manager doesn't appear to be run on a ubiquity install, which means it doesn't set default gconf values appropriately.

Revision history for this message
Colin Watson (cjwatson) wrote :

Well, er, yeah. No postinsts are ever run by Ubiquity, by design; it merely copies the live filesystem to the hard disk, and then does some extra tweaks.

Is this something that needs to be configured properly on the running live CD too? If so, casper needs to do it, and there's a facility for casper to install hooks to get stuff to happen just after Ubiquity copies the live filesystem. If not, please let me know ASAP and I can install a workaround.

Revision history for this message
Matthew Garrett (mjg59) wrote :

gnome-power-manager sets default gconf keys depending on the machine that it's installed on - that's knowledge that's only available if the postinst is run on the appropriate machine. It's only related to whether or not suspend to RAM is enabled by default, so it's probably not important for it to happen on the live CDs.

Tollef Fog Heen (tfheen)
Changed in ubiquity:
assignee: nobody → tfheen
status: Unconfirmed → Confirmed
Revision history for this message
Tollef Fog Heen (tfheen) wrote :

casper (1.55) dapper; urgency=low

  * Reconfigure gnome-power-manager when doing live installations.
    Malone #45654

 -- Tollef Fog Heen <email address hidden> Mon, 22 May 2006 11:16:46 +0200

Changed in casper:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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