Comment 32 for bug 365770

> Well, gnome-screensaver inhibition (through gnome-screensaver-command -i)
> works as expected, so the odds are more likely in kaffeine's field.

Hmm, interesting. I had a quick poke around in the source for Kaffeine and Gwenview, which shows:

1) Gwenview uses completely different methods to disable the screensaver. Gobnuts, could you check whether Gwenview triggers the screensaver when the screensaver is disabled? If not, this is probably an unrelated bug, which should be filed against Gwenview

2) I also can't see any changes to the way Kaffeine handles the screensaver between 0.8.6 (in Intrepid) and 0.8.7 (in Jaunty).
   Search (case-insensitively) for 'xtest' in 'kaffeine/src/kaffeine.cpp' to see the screensaver-related bits

3) I can't work out how to get any better debugging information out of Kaffeine without recompiling it

4) If someone can work out how to make Kaffeine print kdDebug messages (perhaps with kdebugdialog?), or is willing to do some experimental recompilation, there are some possible causes we could investigate

5) Even if Kaffeine is the direct cause, it's not doing anything that should break Peter's gconftool-2 workaround, so I still think the gnome-screensaver guys should look into this