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 694178 - using old idle api
using old idle api
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: gnome-session
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-02-19 15:14 UTC by William Jon McCann
Modified: 2013-02-19 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
presence: Don't connect to 'became-active' signal (1.03 KB, patch)
2013-02-19 15:15 UTC, Florian Müllner 		committed Details | Review

Description William Jon McCann 2013-02-19 15:14:11 UTC 
gnome-session[21701]: GLib-GObject-WARNING: gsignal.c:2471: signal `became-active' is invalid for instance `0xe26140'
Comment 1 Florian Müllner 2013-02-19 15:15:52 UTC 
Created attachment 236772 [details] [review]
presence: Don't connect to 'became-active' signal

The signal was removed from GnomeIdleMonitor a while ago. Commit
377e02494ab0e9 updated to the new API, but left the outdated
signal connection in place.
Comment 2 Ray Strode [halfline] 2013-02-19 15:32:06 UTC 
Review of attachment 236772 [details] [review]:

do it!
Comment 3 Florian Müllner 2013-02-19 15:40:30 UTC 
Attachment 236772 [details] pushed as 796e1a8 - presence: Don't connect to 'became-active' signal