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 682159 - screenShield: Without systemd this._consoleKitProxy.ckSession is undefined
screenShield: Without systemd this._consoleKitProxy.ckSession is undefined
Status: RESOLVED DUPLICATE of bug 682096
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-08-18 15:19 UTC by Owen Taylor
Modified: 2012-08-18 15:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Owen Taylor 2012-08-18 15:19:35 UTC
The code in screenShield.js does:

            this._consoleKitProxy = new ConsoleKit.ConsoleKitManager();
            this._consoleKitProxy.ckSession.connectSignal('Lock', Lang.bind(this, function() { this.lock(false); }));
            this._consoleKitProxy.ckSession.connectSignal('Unlock', Lang.bind(this, function() { this.unlock(); }));

But ConsoleKitManager.ckSession is asynchronously initialized so it doesn't exist yet at this point. The solution might to be add gjs signals to the ConsoleKitManager object for Lock/Unlock.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-08-18 15:30:22 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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