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:
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.
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%20corrupti on%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.