Just wanted to confirm that upgrading to libgupnp-1.6-0 from sid,
version 1.6.3-1, seems to have completely solved this problem. Rygel
used to crash constantly, and now seems rock solid on a server with a
WiFi link to the home network and exposing a NAT Ethernet connection
to a TV, with both bounci
Cool!
I had assumed, from the log messages etc, that this was likely a race
condition between the network configuration changing and rygel being
notified of, and adjusting to, said configuration.
On Mi, Dez 21 2022 at 13:34:15 +, Barak A. Pearlmutter
wrote:
Dec 21 09:00:20 sweat rygel[853]: Error sending SSDP packet to
FF0E::C: Error sending message: Network is unreachable
Dec 21 09:00:20 sweat rygel[853]: Error sending SSDP packet to
FF0E::C: Error sending message: Network is unreac
Okay, here's a manifestation of some network-change rygel-stops issue.
This is rygel 0.42.0-2.
Logs below.
After "systemctl --user restart rygel.service" it works fine.
$ last -1 reboot
reboot system boot 6.0.0-6-amd64Wed Dec 21 09:00 still running
$ systemctl --user status rygel.service
Hi Barak,
Rygel should be able to cope with this situation. If it does not not,
then this is a bug that needs looking into.
Please provide the output of journalctl -u rygel.service and also feel
free to take this upstream at
https://gitlab.gnome.org/GNOME/rygel/issues
Package: rygel
Version: 0.42.0-2
Dear Maintainer,
Thanks for maintaining Rygel. It's made our big TV useful! And tablets!
Everyone on the local network is happy!
To keep everyone happy, I turned on lingering for the involved user (me)
$ loginctl enable-linger $(whoami)
and enabled rygel. This
6 matches
Mail list logo
