I confirm that this issue has nothing to do with libavg, I'm experiencing it with gst-inspect too. The sigsegv happens in fini_contex_translations function (setrans_client.c) because it free a couple of uninitialized contexts. Mike's patch doesn't seem to solve the issue here (current intrepid) though, it makes it crash on init function.. Removing __thread keywords from contexts initialization seems to do the trick but I doubt it's the right fix. Is there an upstream tracker to report the issue?
-- SETRANS + libavg = SIGSEGV on Hardy https://bugs.launchpad.net/bugs/237156 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
