GNOME Bugzilla – Bug 588068
Empathy showing myself idle even if I am just idle for 2-3 minutes
Last modified: 2021-06-10 20:58:17 UTC
Please describe the problem: May be this is related to Gnome but because I am not too sure and also because this problem is happening on Empathy I chose to book the ticket on Empathy. So please help me if this is not correct. In Empathy I am noticing that the Empathy icon on gnome-panel goes into idle mode automatically even if there are no activity for only 2-3 minutes. The problem is I can't find any settings to control this time gap. I would prefer it to be at least 5 minutes. But the user should have control on changing the time period. Steps to reproduce: 1. Start Empathy 2. Do not do any thing on computer for few minutes 3. The Empathy icon goes idle. Problem : Can I control this idle time? Actual results: Empathy icon goes into idle mode. Expected results: I want to mange this time gap so that it goes idle in let's say 5 minutes. That means somewhere (in gnome/ empathy) there should be an option to control this time gap. Does this happen every time? Yes Other information: I hope this is not duplicate and if I have done any mistake while booking this bug then please advise me the correct way.
You can control it from gnome-screensaver 2.27 (maybe also 2.26 but I don't know)
I have tried that too, but it didn't work for me. I really thought that may be changing the screensave timing will help but now after I changed that to 30 minutes even then this is happening.
Strange, this does not happen to me
Thanks for your quick comments. I am sure this can be solved quickly because of late this is really creating some issues for me. Yes, it is really strange. I hope I am doing everything correct at my end. In Pidgin this issue never happens because they have a different idle setup system. May be attaching a screenshot will help. I am attaching it here. Here are the steps I did : a) Click on Gnome Menu b) System --> Preference --> Screensaver. c) It shows "Regard the computer idle after 30 minutes. Please suggest if I am missing something here.
Created attachment 138035 [details] Screenshot for the Screen Saver Screenshot for the Screen Saver setting at my end.
Empathy master (2.27.4) uses gnome-session instead of gnome-screensaver to detect when sesion is becoming idle. The reason is gnome-screensaver secretly removed their dbus API in >=2.26 versions. I don't know if gnome-session's idle time is configurable... But it's not empathy's problem. I reassign to gnome-session to see what they think about that.
gnome-session version is obviously not 1.5, stupid bugzilla!
Thanks Xavier for looking into this problem. Earlier in telepathy IRC, I also got the same view that this is Gnome's problem. As an user it will be great to get this configurable in gnome, because I should be able to configure the idle time (much like pidgin). I would also add here that not all the time this happens. Sometime the idle icon appear after much longer duration (>5 minutes). I am not sure whether there are any internal activities go on in those cases or not.
Are you using Empathy 2.27.4 (not yet released)? Why did you assign back to Empathy? As empathy now uses gnome-session for the idle time, it's session's responsability to let to user define the timeout.
Hello Xavier. Yes I am using Empathy 2.27.4 from git. Actually when I added my last comment bugzilla asked me the version of the product number, and I was surprised to find that it was only showing Empathy. I have read your earlier comments and I thought it will show gnome but it was showing Empathy only. I am on FF3 (if that matters). Extremely sorry for the trouble. Can you guide me on how to refer it back to Gnome?
ok, no problem. I can move it back.
Well, I've just tested this and I can say that gnome session works well with gnome screensaver idle time. I'm running ubuntu karmic, and I have gnome screensaver 2.27.0, but gnome session 2.26.1 (this might be the difference). Maybe when they will upload 2.27 I will also have this bug
I remember, this is also happening since the past few days only. I doubt since after upgrading to the Git version I have started noticing it.