Description of problem: I cannot run ekiga. When it registers at my sip provider, it segfaults. Up until today it segfaulted only after a few calls, but now it segfault simply by launching it. It takes a few seconds, and it crashes in the same second as when I notice in the asterisk log that it attempts to register. ===== sudo grep segfault /var/log/syslog Mar 8 17:09:48 solbu-1 kernel: [898038.568498] ekiga[6375]: segfault at f0 ip 00007ff6ce3f7c48 sp 00007ff6ba1de370 error 4 in libopal.so.3.10.2[7ff6cdad4000+b5f000] Mar 8 17:10:30 solbu-1 kernel: [898080.253749] ekiga[6415]: segfault at f0 ip 00007fd79d398c48 sp 00007fd78917f370 error 4 in libopal.so.3.10.2[7fd79ca75000+b5f000] Mar 8 17:10:42 solbu-1 kernel: [898091.872113] ekiga[6441]: segfault at f0 ip 00007fe1b8f62c48 sp 00007fe1a4d49370 error 4 in libopal.so.3.10.2[7fe1b863f000+b5f000] Mar 8 17:21:42 solbu-1 kernel: [898750.712745] ekiga[7013]: segfault at f0 ip 00007f2ea1b57c48 sp 00007f2e8d93e370 error 4 in libopal.so.3.10.2[7f2ea1234000+b5f000] Mar 8 17:33:55 solbu-1 kernel: [899480.762168] ekiga[24655]: segfault at f0 ip 00007fb41a420c48 sp 00007fb405fe9370 error 4 in libopal.so.3.10.2[7fb419afd000+b5f000] Mar 8 17:45:30 solbu-1 kernel: [900173.785913] ekiga[26840]: segfault at f0 ip 00007f549652ac48 sp 00007f5482311370 error 4 in libopal.so.3.10.2[7f5495c07000+b5f000] ===== GDB trace: ===== Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe1d7b700 (LWP 27067)] 0x00007ffff5f91c48 in SIPMIMEInfo::SetContact(PString const&) () from /usr/lib64/libopal.so.3.10.2 ===== Version-Release number of selected component (if applicable): 3.3.2-4 How reproducible: Always. Reproducible: Steps to Reproduce:
Oh, and in case it's not obvious, this is mga2.
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (to packagers: please assign the bug to yourself if working on it)
Keywords: (none) => TriagedCC: (none) => ennael1, fundawang, nicolas.lecureuil, stormi
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD