Upstream replied that they fixed the warnings in totem, and that they "couldn't reproduce the problem, but I can see how the original warning might happen. Most likely, gnome-screensaver crashed, or was killed, and the gnome-session inhibition didn't notice. gnome-screensaver is supposed to proxy to
gnome-session, and it should be transparent to users."
Bastien finished by: "File a bug against gnome-screensaver if you still see the problem."
Now the question is whether we will still be affected now that a fix for the warnings has been committed in totem, or if gnome-screensaver is still problematic, or something.
Luis, could you help doing some additional testing on this? I'm not sure how to proceed myself.
Upstream replied that they fixed the warnings in totem, and that they "couldn't reproduce the problem, but I can see how the original warning might happen. Most likely, gnome-screensaver crashed, or was killed, and the gnome-session inhibition didn't notice. gnome-screensaver is supposed to proxy to
gnome-session, and it should be transparent to users."
Bastien finished by: "File a bug against gnome-screensaver if you still see the problem."
Now the question is whether we will still be affected now that a fix for the warnings has been committed in totem, or if gnome-screensaver is still problematic, or something.
Luis, could you help doing some additional testing on this? I'm not sure how to proceed myself.