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 684522 - No signal GDBusConnection::closed() but mistaken sync() and async() alternatives
No signal GDBusConnection::closed() but mistaken sync() and async() alternatives
Status: RESOLVED DUPLICATE of bug 684358
Product: vala
Classification: Core
Component: Bindings: GLib
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-21 06:08 UTC by Chandni Verma
Modified: 2012-09-21 09:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chandni Verma 2012-09-21 06:08:05 UTC 
This doesn't allow one to connect a handler to the close signal which is important to keep your networked application dealing with many connections crash-proof of connection damages.
Comment 1 Chandni Verma 2012-09-21 06:11:10 UTC 
I can connect to notify::close but that doesn't provide me causes of closing like remote_peer_vanished and is less helpful.
Comment 2 Evan Nemerson 2012-09-21 09:03:38 UTC 

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