asterisk 1.4.11~dfsg-1 segfaults on startup

[Tim Groeneveld]

Binary package hint: asterisk

On Ubuntu Gutsy, after typing apt-get install asterisk, asterisk fails to start up with the command " asterisk -vvvvvvvvvvvvc "

[Lionel Porcheron (lionel.porcheron)]

Hi Tim,

Two question to begin:
- asterisk 1.4.11 does not build in Ubuntu, so are you sure you have 1.4.11 on your gutsy?
- does it works if you launch with the init script? If you launch asterisk by hand, it will be launched with the user account, and it should work with asterisk account.

[Alex (gralex)]

Hi,

I also face the problem with the latest Gutsy package 1:1.4.10~dfsg-1:

# asterisk -f -U asterisk
[Oct 10 16:16:48] NOTICE[11256]: cdr.c:1359 do_reload: CDR simple logging enabled.
[Oct 10 16:16:48] NOTICE[11256]: loader.c:831 load_modules: 156 modules will be loaded.
[Oct 10 16:16:48] NOTICE[11256]: config.c:1178 ast_config_engine_register: Registered Config Engine odbc
Segmentation fault
#

[Alex (gralex)]

Hi,

After tracing the problem a little bit, it seems that it comes from the asterisk-h323 package.

When asterisk is installed alone, it starts just fine. But as soon as you install asterisk-h323, it crashes with a segfault. Disabling chan_h323 in /etc/asterisk/modules.conf also resolves the segfault problem.

Hope it helps locate the problem. This is rather critical for users of Asterisk PBX software. In it's current state, the Asterisk package released for Gutsy is unusable.

Alex

[Grzegorz "McCartney" Oledzki (grzegon)]

It behaves the same (segfault) with asterisk and asterisk-h323 taken from Hardy, i.e. 1.4.17~dfsg-2.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
Gutsy task.

[Paul Belanger (pabelanger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance.