----- Original Message -----
On Thu, Jan 31, 2013 at 08:44:39AM -0500, Kamil Paral wrote:
> >
> > 1) can anyone else verify?
> > 2) is this a bug? Or a feature?
>
> It's this:
>
https://bugzilla.gnome.org/show_bug.cgi?id=690713
"You are not authorized to access bug #690713."
Well, that does not help very much unless you happen to be
"authorized".
>
https://bugs.freedesktop.org/show_bug.cgi?id=58950
That is better but it reads like "we are sorry but this will remain
broken until _other_ applications will get fixed" if I understand
responses correctly.
If there is anything to fix here, it is that we need a suitable signal from the kernel -
until then, there will be various user-space mechanisms that all have their own
about-to-suspend and resume signals:
* pm-utils scripts get called if you use pm-suspend
* upowers NotifySleep signal is emitted if you use upower to suspend
* loginds PrepareForSleep signal is emitted if you use logind
What has changed in f18 is that GNOME components (gnome-settings-daemon, gnome-shell) are
now using logind, because it offers features that we want (inhibitors and delay
inhibitors). upower has also been changed to use logind, and NetworkManager is listening
for PrepareForSleep.
Matthias