(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.
Probably worth backporting to 5.12, could you attach the exact patch you
applied please?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1217086
Title:
Created attachment 89405
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
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!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
** Changed in: mission-control-5
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1217086
Title:
mission-control-5 segfaults
The verification of the Stable Release Update for telepathy-mission-
control-5 has completed successfully and the package has now been
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
This bug was fixed in the package telepathy-mission-control-5 -
1:5.14.1-1ubuntu6.1
---
telepathy-mission-control-5 (1:5.14.1-1ubuntu6.1) saucy; urgency=low
* debian/patches/git_migration_debug_segfault.patch:
- backport fix for a segfault in the config migration code (lp:
There has been no report with the new version, considering the issue as
resolved
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in
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.
(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).
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1217086
Title:
mission-control-5 crashed with SIGSEGV in
** Changed in: telepathy-mission-control-5 (Ubuntu)
Importance: Medium = High
** Changed in: telepathy-mission-control-5 (Ubuntu)
Status: Confirmed = Triaged
** Bug watch added: freedesktop.org Bugzilla #71539
https://bugs.freedesktop.org/show_bug.cgi?id=71539
** Also affects:
Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=71539.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: telepathy-mission-control-5 (Ubuntu)
Status: Triaged = Fix Committed
** Summary changed:
- mission-control-5 crashed with SIGSEGV in _IO_vfprintf_internal()
+ mission-control-5 segfaults intp_debug_sender_add_message_vprintf()
** Summary changed:
- mission-control-5
** Branch linked: lp:ubuntu/trusty-proposed/telepathy-mission-control-5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1217086
Title:
mission-control-5 segfaults
Hello Peter, or anyone else affected,
Accepted telepathy-mission-control-5 into saucy-proposed. The package
will build now and be available at http://launchpad.net/ubuntu/+source
/telepathy-mission-control-5/1:5.14.1-1ubuntu6.1 in a few hours, and
then in the -proposed repository.
Please help us
This bug was fixed in the package telepathy-mission-control-5 -
1:5.14.1-1ubuntu7
---
telepathy-mission-control-5 (1:5.14.1-1ubuntu7) trusty; urgency=low
* debian/patches/git_migration_debug_segfault.patch:
- backport fix for a segfault in the config migration code (lp:
** Branch linked: lp:ubuntu/saucy-proposed/telepathy-mission-control-5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1217086
Title:
mission-control-5 segfaults
18 matches
Mail list logo
