Here are the problems I've found:
gpg-agent isn't loaded correctly
Gnome3's session does load gpg-agent, but it does not export the settings to gnome-terminal. Hence gnome-terminal does not use gpg-agent when you run, for example gpg --decrypt and -- if it's setup -- ssh
The fix is fairly simple: find the saved settings file (usually $HOME/.gnupg/gpg-agent-info-hostname), and export it in $HOME/.bashrc. For example:
if [ -r /home/berend.deschouwer/.gnupg/gpg-agent-hostname ]; then . .gnupg/gpg-agent-info-hostname export GPG_AGENT_INFO SSH_AUTH_SOCK SSH_AGENT_PID fi
Upgrading requires rebooting
Upgrading can require rebooting. If a Gnome2 gnome-settings-daemon is running when it's upgraded to a Gnome3 gnome-settings-daemon, gnome-settings-daemon can use 100% CPU utilisation until you reboot.
gnome-shell does not always start
I haven't found a permanent solution for this yet. The process gnome-shell doesn't always start, or maybe crashes.
The workaround is to open a terminal, and run
export DISPLAY=:0.0 gnome-shell --replace &
It usually starts fine the second time.
