After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 330237 - should detect ekiga (voip) activity as activity and not lock screen
should detect ekiga (voip) activity as activity and not lock screen
Status: RESOLVED DUPLICATE of bug 353077
Product: ekiga
Classification: Applications
Component: general
GIT master
Other Linux
: Low enhancement
: ---
Assigned To: Snark
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-07 09:29 UTC by Sebastien Bacher
Modified: 2006-08-27 09:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2006-02-07 09:29:18 UTC 
The bug has been described on https://launchpad.net/distros/ubuntu/+source/gnome-screensaver/+bug/30659

"Currently, it seems like gnome-screensaver is only looking at keyboard and mouse activity to decide whether a session is idle or not. It should also look at other sources, such as active phone conversations and not activate the screensaver and lock the screen if there is a call in progress."
Comment 1 William Jon McCann 2006-02-07 14:10:55 UTC 
I'm not sure about this.  I think the better approach might be for ekiga to use the InhibitActivation DBUS method.
Comment 2 Sebastien Bacher 2006-02-07 14:38:42 UTC 
Reassigning that bug to ekiga so
Comment 3 Snark 2006-02-08 08:44:06 UTC 
It should be possible to do something with the dbus component. Assigning to myself to keep track of it.
Comment 4 Snark 2006-04-14 13:46:33 UTC 
The poster of Bug 338450 quite rightly noticed that if the call is audio-only, then the screensaver shouldn't be inhibited.
Comment 5 William Jon McCann 2006-04-14 14:10:48 UTC 
It is up to the ekiga folks but it seems really strange to allow the screen to blank when on a call (even an audio only one).  The fact is that the computer isn't idle - you are using it.  Having the screensaver activate have no positive effect, only a negative one - stealing CPU cycles from ekiga.

If you inhibit the screensaver you don't need to inhibit the power manager too.
Comment 6 lists 2006-06-11 03:22:55 UTC 
> Having the screensaver activate have no positive effect, 
> only a negative one - stealing CPU cycles from ekiga.

I don't necessarily agree with this. I have my screen turn off instead of a screensaver and this doesn't take any CPU. The positive is obvious; a huge cut in power consumption and longer that I can talk before my battery cuts out. There is also the screen burn that screensavers were designed to prevent.

The point is that when one is in a voice call, they are not using the screen. If they don't see any benefit in having a screensaver on the occassions when they are not using their screen, they should turn their screensaver off.
Comment 7 lists 2006-06-11 03:26:05 UTC 
BTW - William is correct that if you inhibit the screensaver you don't need to inhibit the power manager too. GPM takes its idle state from the screensaver, so if that is inhibited it also inhibits GPM.
Comment 8 lists 2006-06-16 13:47:52 UTC 
I have put together some information here:
https://wiki.ubuntu.com/InhibitingGnomeScreensaver
Comment 9 Snark 2006-08-27 09:14:13 UTC 

*** This bug has been marked as a duplicate of 353077 ***