Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 199584
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Colin Macdonald <cbm@m.fsf.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 199584 depends on: Show dependency tree
Bug 199584 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-11-18 20:13 0000
The configure call in the ebuild for gnome-power-manager-2.20-r1 passes
parameter  --enable-keyring.  This is no longer present in the source.  AFAICT,
--enable-actions-menu doesn't do anything either:

cbm@aconite ~/src/gnome-power-manager-2.20.0 $ ./configure --help | grep action
cbm@aconite ~/src/gnome-power-manager-2.20.0 $ ./configure --help | grep key   
cbm@aconite ~/src/gnome-power-manager-2.20.0 $ 


In previous versions (at least 2.18), --enable-keyring actually did something
which I didn't want (namely locking my keyring on hibernate).  However, it
seems in 2.20 this is controlled by gconf keys rather than at configure time:
/apps/gnome-power-manager/lock/gnome_keyring_hibernate
/apps/gnome-power-manager/lock/gnome_keyring_suspend

------- Comment #1 From Rémi Cardona 2007-11-19 09:28:19 0000 -------
Done. Thanks for the report :)

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug