Summary: | segfault in tp_debug_sender_add_message_vprintf() | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Sebastien Bacher <seb128> |
Component: | mission-control | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | backport to stable serie |
Description
Sebastien Bacher
2013-11-12 17:00:32 UTC
I think you might need commit cc2af09f60851 (or part of) from Bug #69542. If my guess is right, then this is probably reproducible by installing MC 5.12 (e.g. Ubuntu precise), setting up Telepathy accounts for a disposable user account, and upgrading. As a short cut: install precise, set up the accounts, save the user's home directory in a tarball or something, discard the rest of the OS, install 13.10, replace the 13.10 user's home directory with the one you saved. The version of MC in raring appears to be from the middle of a development branch, so I'm not going to support that version: you're on your own with that one. Depending when the faulty debug message was introduced, it might need a similar patch, or not. We do not recommend using development versions in a stable OS release. If you need features from a development branch, please ask for a stable branch sometime around your freeze time. > I think you might need commit cc2af09f60851 (or part of) from Bug #69542. Thanks Simon, that seems likely indeed > The version of MC in raring appears to be from the middle of a development > branch, so I'm not going to support that version: you're on your own with that > one. https://launchpad.net/ubuntu/+source/telepathy-mission-control-5 ... you mean quantal I guess? Don't worry about that one, in practice most users stick to the current stable or current LTS, quantal is current_stable-2 which probably has a very limited set of users I'm going to upload that fix and comment again in a few days to let you know what impact it has on reports! (In reply to comment #3) > > The version of MC in raring appears to be from the middle of a development > > branch > > you mean quantal I guess? Sorry, yes, I meant MC 5.13 (or any future x.odd.z version). We got no report on the package version which has cc2af09f60851 backport, I think you can consider that to be indeed the fix for that issue, thanks! Probably worth backporting to 5.12, could you attach the exact patch you applied please? Created attachment 89405 [details] [review] backport to stable serie > Probably worth backporting to 5.12, could you attach the exact patch you applied please? Sure, I guess you meant 5.14 there? That's the patch we have been using (basically the git commit, refreshed, without the hunk which applied to code not present in that serie) (In reply to comment #7) > Sure, I guess you meant 5.14 there? Yes. Pushed to telepathy-mission-control-5.14 branch for the benefit of anyone else still on that version. Thanks! Regression somewhere in the 5.13/5.14 cycle, fixed in 5.14.2 in the unlikely event that that version is ever released. Also fixed in 5.15.1 and all subsequent versions. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.