screensaver starts when movie plays

Can you reproduce this when totem is running on fullscreen mode? When windowed, totem doesn't keep gnome-screensaver from kicking in, but seems to work when on fullscreen.

I cannot reproduce this on current up-to-date Edgy.

Yeah it happens even if the movie is on FS.

I watched another movie yesterday tho, and the screensaver did not appear. I'll play the one that I was watching while the problem happened today, to see if it happens again.

Thanks for your bug. Do you use totem-gstreamer or totem-xine? Do you have a xinerama setup or a standard one screen setup?

I'm on gstreamer and standard setup.

I'm thinking that I had CTRL+ALT+BACKed before watching the movie, got some error messages when logging back in, and the interface was all weird, like GTK1. So maybe something was just not working right.

I'll play the same movie today, and if I can't reproduce it I guess you can disregard this bug.

Your previous description looks like gnome-settings-daemon was not running, maybe the dbus session bus was not correctly configured too. Let we know if you can get the issue on a normally working desktop

David, can you reproduce this anymore?

Sorry, I had totally forgotten about this!

I didn't get the error again, please close the bug.

And thanks a lot :)

closing since it works now, feel free to reopen if you get the issue again

Curiously, it's happening again and now gnome-settings-daemon IS running. Watching movies in fullscreen mode just doesn't keep gnome-screensaver from starting anymore in Feisty.

the feisty bug is known and fixed upstream

(This is mentioned upstream in http://bugzilla.gnome.org/show_bug.cgi?id=344577 )

Hi,

This bug is appearing in Ibex for me. Whilst watching movies the screensaver will come on.

matthew@matthew-desktop:~$ apt-cache policy totem
totem:
  Installed: 2.24.2-0ubuntu2
  Candidate: 2.24.2-0ubuntu2
  Version table:
 *** 2.24.2-0ubuntu2 0
        500 http://nz.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

matthew@matthew-desktop:~$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

mmnz: Yes, here in Intrepid too. It gets on my nerves. Just wanted to report this bug. Am I allowed to set it to "confirmed" or "new"? "Invalid" is wrong in my opinion.
Thanks.

Set to confirmed.

could somebody having the issue send the bug to bugzilla.gnome.org?

done.
Is there a way to help?

this is fixed on jaunty.

I've updated ubuntu form interpid to jaunty and the bug is still here.

don't reopen a closed bug but rather open a new one

don't reopen a closed bug but rather open a new one if you have a similar issue