Ekiga client crash in in std::_Rb_tree_increment

Bug #415001 reported by Marcus Paiva
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ekiga
Invalid
Medium
ekiga (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ekiga

When you are connect with someone and he/she closes Ekiga, your client crashes.

Revision history for this message
Yannick Defais (sevmek) wrote :

Hi,

What is the version of ekiga?

Is it reproducible?

Best regards,
Yannick

Changed in ekiga (Ubuntu):
status: New → Incomplete
Revision history for this message
Marcus Paiva (mpaivac) wrote : Re: [Bug 415001] Re: Ekiga client crash

Hi,
im using Ekiga 3.2.0 at Ubuntu 9.04 on a lan network.
When we use nighborhood users to connect each other and someone close his
client the other client crashs and close too.

2009/8/17 Yannick Defais <email address hidden>

> Hi,
>
> What is the version of ekiga?
>
> Is it reproducible?
>
> Best regards,
> Yannick
>
> ** Changed in: ekiga (Ubuntu)
> Status: New => Incomplete
>
> --
> Ekiga client crash
> https://bugs.launchpad.net/bugs/415001
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ekiga” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ekiga
>
> When you are connect with someone and he/she closes Ekiga, your client
> crashes.
>

Revision history for this message
Yannick Defais (sevmek) wrote : Re: Ekiga client crash

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

Revision history for this message
Marcus Paiva (mpaivac) wrote : Re: [Bug 415001] Re: Ekiga client crash
  • gdb-ekiga.txt Edit (160.2 KiB, text/plain; charset=ISO-8859-1; name="gdb-ekiga.txt")

2009/8/18 Yannick Defais <email address hidden>

> 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 direct subscriber
> of the bug.
>
> Status in “ekiga” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ekiga
>
> When you are connect with someone and he/she closes Ekiga, your client
> crashes.
>

Revision history for this message
Marcus Paiva (mpaivac) wrote : Re: Ekiga client crash
Yannick Defais (sevmek)
summary: - Ekiga client crash
+ Ekiga client crash in in std::_Rb_tree_increment
Changed in ekiga (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Yannick Defais (sevmek) wrote :

Thank you Marcus. I pushed upstream.

Best regards,
Yannick

Changed in ekiga (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in ekiga:
status: Unknown → New
Revision history for this message
Yannick Defais (sevmek) wrote :

Hi,

This should be fixed in Ekiga 3.2.5, which you can find in Ubuntu Karmic 9.10.

Best regards,
Yannick

Changed in ekiga:
status: New → Fix Committed
status: Fix Committed → Fix Released
Changed in ekiga (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Marcus Paiva (mpaivac) wrote : Re: [Bug 415001] Re: Ekiga client crash in in std::_Rb_tree_increment

Great job guys,

Ekiga and Ubuntu rock !

2009/8/19 Yannick Defais <email address hidden>

> Hi,
>
> This should be fixed in Ekiga 3.2.5, which you can find in Ubuntu Karmic
> 9.10.
>
> Best regards,
> Yannick
>
> ** Changed in: ekiga
> Status: New => Fix Committed
>
> ** Changed in: ekiga
> Status: Fix Committed => Fix Released
>
> ** Changed in: ekiga (Ubuntu)
> Status: Triaged => Fix Released
>
> --
> Ekiga client crash in in std::_Rb_tree_increment
> https://bugs.launchpad.net/bugs/415001
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ekiga Voice Over IP Suite: Fix Released
> Status in “ekiga” package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: ekiga
>
> When you are connect with someone and he/she closes Ekiga, your client
> crashes.
>

Changed in ekiga:
importance: Unknown → Medium
status: Fix Released → Unknown
Revision history for this message
Chrescht (sekateur) wrote :

I had the same problem just now when closing ekiga 3.2.7 on Ubuntu 10.10 when connected to an ekiga session on another pc running 3.2.6 on Ubuntu 10.4.
Both are on the same network.

I closed 3.2.7 and 3.2.6 crashed (then apport did his job).

Now since the status is unknown (from fix released), is this the wrong bug to report to?

cheers.

Changed in ekiga:
status: Unknown → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.