Ubuntu
gnome-session package

indicator-applet-session must be running for session idle to happen

Bug #543932 reported by Kees Cook
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Triaged
Medium
Unassigned
Lucid
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: gnome-session

The gnome-session idle does not happen unless indicator-applet-session is running. Having this applet running to gain idle timers is a regression.

Reproducer:
- set screensaver idle timeout to 1 minute
- kill (or never start) indicator-applet-session
- dbus-monitor --session "type='signal',interface='org.gnome.SessionManager.Presence',member='StatusChanged'"
- observe lack of presence change

I would expect gnome-session to send dbus signals regardless of the state of the session applet, as it used to do in earlier Lucid:
signal sender=:1.0 -> dest=(null destination) serial=671 path=/org/gnome/SessionManager/Presence; interface=org.gnome.SessionManager.Presence; member=StatusChanged
   uint32 3

Tags: lucid
Kees Cook (kees)
tags: added: regression-potential
Changed in gnome-session (Ubuntu Lucid):
milestone: none → ubuntu-10.04-beta-2
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I'm not confirming this. gnome-session does it's own tracking for idle time, so that's a bit strange

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Kees - are there any idle inhibitors registered when you see this happen? (For getting a list of inhibitors, there is some example code in the gnome-power-manager apport hook). I've tried this and can't reproduce it

Revision history for this message
Kees Cook (kees) wrote :

no, there were no inhibitors:

dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitors

gave me an empty array.

dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:-1

was false

Leaving this running:

dbus-monitor --session "type='signal',interface='org.gnome.SessionManager.Presence',member='StatusChanged'"

resulted in no status changes. As soon as I added indicator-applet-session to my panel, it started working. Try starting a session without indicator-applet-session in your panel.

Pedro Villavicencio (pedro)
Changed in gnome-session (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Sebastien Bacher (seb128) wrote :

I can't confirm the issue on a fresh lucid beta1 installation there, screensaver starts after one minute as it should

Revision history for this message
Sebastien Bacher (seb128) wrote :

I'm not sure the bug settings are adapted btw, screensaver not starting for one user doesn't seem a beta2 blocker

Revision history for this message
Kees Cook (kees) wrote :

fresh installs include the applet, though, yes? I'm removed the milestone since no one else seems to be seeing it.

Changed in gnome-session (Ubuntu Lucid):
milestone: ubuntu-10.04-beta-2 → none
Revision history for this message
Sebastien Bacher (seb128) wrote :

right, what I meant is an install without too many change, it's basically a fresh beta1 install I've upgraded and used for bug testing. to test this one I've changed the screensaver setting, removed the session applet, restarted the session, checked that the indicator-session-service was not running and waited for a minute to see that the screensaver was kicking in as configured

Revision history for this message
Robert Siemer (robert-siemer-launchpad-net) wrote :

The dbus SessionManager.Presence StatusChanged signal has nothing to do with idle timers. It is related to the ‘What are you doin?’ status on facebook, etc.

I can confirm, though, that the gnome-screensaver and gnome-power-manager situation is a disaster.

Right now, on my Lucid system, the screensaver doesn’t kick in. Yesterday noon it still did.
gnome-power-manager never seems to activate DPMS (hard to tell, though). And it’s dbus interface is crippled completely.

The UI side of the problem will never be bug-free until Screendimming, User-Idle, Screensaver and DPMS are configured together.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Kees, do you still have that issue?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Unassigning from the Canonical Desktop Team, nobody else seems to get the issue and the submitter is not responsive

Changed in gnome-session (Ubuntu Lucid):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Changed in gnome-session (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Revision history for this message
C de-Avillez (hggdh2) wrote :

Taking out the regression-* tag.

Jean-Baptiste Lallement (jibel)
tags: added: lucid regression-release
removed: regression-potential
tags: removed: regression-release
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in gnome-session (Ubuntu Lucid):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.