Is gnome-settings-daemon running?

ps -A | grep gnome-settings-daemon

Yup.  But not sure what is starting it.  The XFCE controls do not show it under Application Autostart or the Session tab.  I can't just nuke the package like I did with gnome-power-manager and gnome-screensaver because it wants to yank gdm out with it and I kinda need that.

Do you have have "Launch GNOME services on startup" under "Advanced" enabled? Also, what user is running gnome-settings-daemon?

gnome-settings-daemon was running as me.  Unchecking GNOME services solves the power problem but hoses ssh keys even though GNOME keyring is still checked in Autostart.  Should this instead be filed as a bug against gnome-settings-daemon?  If GNOME isn't the primary desktop environment it's parts shouldn't be taking over if one gets invoked as a side effect.

It's not the desired behavior, but not necessarily a bug I think. gnome-settings-daemon does what it's configured to.

This means you are left with the following options:
- Disable "Launch GNOME services on startup" and unlock your ssh keys manually with ssh-add.
- Fake gnome-session presence. I recall it had something to do with environment variables that are not getting set if gnome-session is not running.
- configure gnome-settings-daemon to do nothing with gnome-tweak-tool.

Please let me know if this works for you or if you need further assistance.

Hey John, can you please get back to me? I'd like to close or reassign this bug. TIA!

Sorry, got behind on email.  Anyway, disabled Launch GNOME Services and just started manually running ssh-add. Solves the problem of getting GNOME's broken behavior but there is still a bug.

If you are on AC and close the lid it won't suspend, which is correct.  What is wrong is that if you then yanlk the AC it stays awake until you open the lid and reclose it while running on battery.  Somebody is going to shake and bake their laptop when they fail to notice what is happeniong and stick a running laptop into a bag and toss it in the car.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.