[Bug 883107] Re: Rygel fails to listen on eth0

2018-12-03 Thread Sebastien Bacher
** Changed in: rygel (Ubuntu) Status: Confirmed => Fix Released ** Changed in: rygel (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883107 Title: Ryge

[Bug 883107] Re: Rygel fails to listen on eth0

2013-04-30 Thread Jens Georg
This should be fixed since quantal with gupnp using the linux context manager, I suppose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883107 Title: Rygel fails to listen on eth0 To manage notific

[Bug 883107] Re: Rygel fails to listen on eth0

2012-07-06 Thread Andreas Henriksson
Recent versions of gupnp switched from using NM "context manager" to using a new Linux context manager. This will listen to network interface events directly from the kernel, so should include interfaces that NM considers "unmanaged". Beware, that in the future NM context manager might be used aga

[Bug 883107] Re: Rygel fails to listen on eth0

2012-03-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rygel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883107 Title: Rygel

[Bug 883107] Re: Rygel fails to listen on eth0

2011-12-12 Thread Andreas Henriksson
If you don't use NM you should make sure NM is stopped! gupnp will then fall back on the unix connection manager. No need to recompile anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883107 Ti

[Bug 883107] Re: Rygel fails to listen on eth0

2011-12-12 Thread Marc Pignat
Hello! Same problem here. Rygel or (gupnp) uses NetworkManager only!, and I don't use NetworkManager because it does not support bridged connections. Please have a look at http://live.gnome.org/Rygel/FAQ. I fixed the problem by recompiling gupnp. This bug is really annoying an should be fixed,

[Bug 883107] Re: Rygel fails to listen on eth0

2011-10-29 Thread Mikael Ståldal
Possibly, but shouldn't rygel listen on eth0 if I explicitly tell it to do so, regardless of what NetworkManager says? But perhaps we have a bug in NetworkManager. How can I check which interfaces NetworkManager thinks is available (without using rygel)? -- You received this bug notification bec

[Bug 883107] Re: Rygel fails to listen on eth0

2011-10-28 Thread Andreas Henriksson
I guess this might be because NetworkManager on your system says no interfaces are available.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883107 Title: Rygel fails to listen on eth0 To manag

[Bug 883107] Re: Rygel fails to listen on eth0

2011-10-28 Thread Mikael Ståldal
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883107 Title: Rygel fails to listen on eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/883107/+s