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 711334 - Unclear semantics when using white-list and managed devices in CM
Unclear semantics when using white-list and managed devices in CM
Product: GUPnP
Classification: Other
Component: gupnp
Other Linux
: Normal normal
: ---
Assigned To: GUPnP Maintainers
GUPnP Maintainers
Depends on:
Blocks: 706120
Reported: 2013-11-03 15:06 UTC by Jens Georg
Modified: 2021-05-17 16:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Jens Georg 2013-11-03 15:06:27 UTC
The question is:

If the last context that is associated with a managed device in a CM is not available anymore, what should happen? Should the device be unreffed just as it would when the context "disappeared" normally?
Comment 1 Jussi Kukkonen 2013-11-26 13:19:20 UTC
Doing everything as if the context just disappeared sounds sensible to me.

Ludo, please chime in if you have an opinion.
Comment 2 Ludovic Ferrandis 2013-11-27 10:53:29 UTC
I don't have to much time to dig into UPnP these days. If you can be more precise that would help me. Any function/piece of code to look at?
Comment 3 Jens Georg 2013-12-17 11:22:17 UTC
ludovic: The question was what the intended semantic was:

What should happen with control points that are managed by the context manager if the context disappears due to white-listing?

Should the cm behave as if the context disappeared in the non-whitelist case or should it just be deactivated but kept in case the whitelist changes?...
Comment 4 GNOME Infrastructure Team 2021-05-17 16:30:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: