I have been the same problems :
- can't unlock any gnome settings
- when i want to suspend , hibernate or stop, i get a polkit prompt and gnome freeze
It's why i have think it was the same problem.
]]>EDIT: Which kernel are you using? I've sticked with 3.5.6-1 because of serious power regressions ( https://bbs.archlinux.org/viewtopic.php?pid=1176627 ).
]]>I don't use rhythmbox and I am not experiencing your polkit errors. I don't have to logout/in for suspend or hibernate and I am able to unlock User Accounts in gnome settings.
]]>systemd-inhibit --list
My Gnome does not, for some reason, handle the lid close event, but it doesn't inhibit systemd from doing it, either. Therefore, if you restore logind.conf to its defaults, the system should get suspended on the lid event (by systemd) regardless of the Gnome setting.
Do you experience the other two issues I mentioned above (polkit, rhythmbox)?
]]>systemctl suspend
but my machine no longer suspends on lid close events since I updated to Gnome 3.6 this morning. I disabled the acpid.service in systemd and altered the logind.conf file as directed in the wiki:
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
I believe that my gnome settings are correct:
>> gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action
'suspend'
>> gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action
'suspend'
I have rebooted and still don't suspend on lid close. Any ideas?
]]>loginctl show-session $XDG_SESSION_ID | grep Active
Active=no
You just have to disable gdm-plymouth :
sudo systemctl disable gdm-plymouth.service
and enable gdm :
sudo systemctl enable gdm.service
reboot
after :
loginctl show-session $XDG_SESSION_ID | grep Active
Active=yes
Well, I get
Active=yes
Damn...
]]>