Bug#705425: asterisk: segmentation fault on start after upgrade from 1:1.8.13.1~dfsg-1 to 1:1.8.13.1~dfsg-3 (wheezy amd64)
Christian Lauinger
christian at lauinger-clan.de
Wed Apr 17 16:10:21 UTC 2013
Am Mittwoch, den 17.04.2013, 10:33 +0200 schrieb Christian Staake:
> On 2013-04-14 21:10, Christian Lauinger wrote:
> > dpkg -l asterisk*
> > ii asterisk 1:1.8.13.1~dfsg-3 amd64 Open Source Private Branch Exchange (PBX)
> > ii asterisk-chan-capi 1.1.6-1 amd64 Common ISDN API 2.0 implementation for Asterisk
>
> Hi Christian,
>
> It seems you are using asterisk-chan-capi which is not even in wheezy...
>
> I had the same problem as you: Because I am still running squeeze, I had
> to use the asterisk version available from squeeze-backports (still at
> 1:1.8.13.1~dfsg-1~bpo60+1).
> In order to use chan_capi with it, I backported asterisk-chan-capi from
> unstable (1.1.6-1) in my private repository.
> Then asterisk 1:1.8.13.1~dfsg-2 became available and I backported that
> too and after installation: boom, segfault when loading chan_capi. :(
>
> The problem now is that the fix in asterisk for CVE-2012-5977 introduced
> an incompatible change in the module API. All stock asterisk modules
> were of course updated, but the out-of-tree modules like chan_capi were not.
> Because of bug #694793 (or, more precisely, #694805) the package
> management system doesn't know about this incompatibility.
>
> What you need is a new (yet unreleased) version of chan_capi with a
> (rather simple) fix taken from the chan_capi svn repository (see
> attached patch).
> If you're really desperate, you can try to build the package yourself
> from my backported source package at
> http://www.bbg.xssoft.de/debian/pool/main/asterisk/asterisk-chan-capi_1.1.6-1~bpo60+2.dsc
>
> This is just my private repository, so it only has binary builds for
> squeeze on i386.
>
Hi Christian,
thanks for your answer.
I currently "solved" my problem by installing the 1.8.13.1~dfsg-1
package from snapshot repo. But this is only temporary.
The asterisk_chan_capi package is architecture independent (any). Can't
I just use the one you build ?
Thx and greets
Chris
More information about the Pkg-voip-maintainers
mailing list