I'm going to assume this was fixed in 0.12.3 which means that this bug
has been fixed in all supported Ubuntu releases for a while now.
** Changed in: gupnp (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Is this still reproducible? Looks like something that could have been
fixed in this upstream commit:
http://gitorious.org/gupnp/gupnp/commit/3e528acd79d55fd9fe778a3ecdde50263da3ddce
--
nautilus-sendto crashed with SIGSEGV in gupnp_service_introspection_get_action()
gupnp 0.12.3 should be the first release to contain the above mentioned
commit.
--
nautilus-sendto crashed with SIGSEGV in gupnp_service_introspection_get_action()
https://bugs.launchpad.net/bugs/353816
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: nautilus-sendto (Ubuntu) = gupnp (Ubuntu)
--
nautilus-sendto crashed with SIGSEGV in gupnp_service_introspection_get_action()
https://bugs.launchpad.net/bugs/353816
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Visibility changed to: Public
--
nautilus-sendto crashed with SIGSEGV in gupnp_service_introspection_get_action()
https://bugs.launchpad.net/bugs/353816
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
