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 728198 - (Re-)creation of main context fails after suspend
(Re-)creation of main context fails after suspend
Status: RESOLVED OBSOLETE
Product: GUPnP
Classification: Other
Component: gupnp
0.20.x
Other Linux
: Normal normal
: ---
Assigned To: GUPnP Maintainers
GUPnP Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-14 17:20 UTC by Daniel Mack
Modified: 2021-05-17 16:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Mack 2014-04-14 17:20:01 UTC 
When the system resumes after suspend, applications report:

** (gupnp-universal-cp:30246): WARNING **: Error creating GUPnP context: Failed to find IP of interface wlp3s0

This happens with both gupnp-universal-cp as well as my own code. It appears to me as a race condition - the reconnect is tried before the network has come fully up again. The application needs to be restarted after that happens.

This is on Fedora 20, gupnp 0.20.10.
Comment 1 Jens Georg 2014-04-14 19:48:20 UTC 
Suspend to disk or ram?
Comment 2 Daniel Mack 2014-04-14 20:58:56 UTC 
Just ordinary suspend-to-RAM.
IOW, "echo mem >/sys/power/state".
Comment 3 Jens Georg 2014-05-10 16:42:08 UTC 
Works here :-/ Do you know which context manager GUPnP uses on Fedora?
Comment 4 Jens Georg 2015-01-04 11:23:58 UTC 
Network Manager.
Comment 5 GNOME Infrastructure Team 2021-05-17 16:30:07 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: https://gitlab.gnome.org/GNOME/gupnp/-/issues/38.