This is probably the same as bug #984475 (i386) and bug #984450 (amd64). errors.ubuntu.com reports no instances of either of these bugs with the SRU version:
https://errors.ubuntu.com/bucket/?id=/usr/lib/telepathy/mission- control-5:***%20glibc%20detected%20***%20/usr/lib/telepathy/mission- control-5:%20double%20free%20or%20corruption%20%28out%29:%20ADDR%20*** https://errors.ubuntu.com/bucket/?id=/usr/lib/telepathy/mission- control-5:***%20glibc%20detected%20***%20/usr/lib/telepathy/mission- control-5:%20munmap_chunk():%20invalid%20pointer:%20ADDR%20*** This is moderate evidence that the bug may be fixed, however the bug is not so common that the lack of reports from precise-proposed makes this a certainty. It would be helpful if users who have seen this bug would install the version of the telepathy-mission-control-5 packages from precise- proposed, and confirm whether it solves the problem for them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024848 Title: mission-control-5 assert failure: *** glibc detected *** /usr/lib/telepathy/mission-control-5: double free or corruption (out): 0x0000000001756790 *** To manage notifications about this bug go to: https://bugs.launchpad.net/mission-control-5/+bug/1024848/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
