Normally, when ekiga crash aport should start automatically to report a backtrace. It seems it does not work in your case.
As we need a backtrace to see where Ekiga crash, here is a manual approach: Install needed packages for a good backtrace: $ sudo aptitude install gdb ekiga-dbg libopal3.6.1-dbg libpt2.6.1-dbg avahi-dbg libglib2.0-0-dbg libgtk2.0-0-dbg Getting the stack backtrace, in a terminal, type: $ gdb --args ekiga -d 4 2>&1 | tee gdb-ekiga.txt (gdb) run Now Ekiga should run normally. Perform the action you did to make it crash, then go back to the terminal window and you should see something like SIGSEGV at... At this stage type: (gdb) thread apply all bt (gdb) quit The file gdb-ekiga.txt has the backtrace you need to attach here; go to this URL: https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/415001 , there is a form to attach a file at the bottom. The file gdb-ekiga.txt should be in your home directory. Now you can safely remove the packages you installed in order to get the backtrace: $ sudo aptitude remove gdb ekiga-dbg libopal3.6.1-dbg libpt2.6.1-dbg avahi-dbg libglib2.0-0-dbg libgtk2.0-0-dbg Best regards, Yannick -- Ekiga client crash https://bugs.launchpad.net/bugs/415001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
