Bug 399466 – crash in Ekiga Softphone:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 399466 - crash in Ekiga Softphone:


Summary:	crash in Ekiga Softphone:


Status:	RESOLVED DUPLICATE of bug 411438

Product:	ekiga
Classification:	Applications
Component:	general
Version:	2.0.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Ekiga maintainers
QA Contact:	Ekiga maintainers

URL:
Whiteboard:

Duplicates:	419454 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-22 17:52 UTC by federico_lox
Modified:	2007-03-17 18:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description federico_lox 2007-01-22 17:52:59 UTC

Version: 2.0.4

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 259346432 vsize: 259346432 resident: 40095744 share: 25608192 rss: 40095744 rss_rlim: -1
CPU usage: start_time: 1169487417 rtime: 1565 utime: 1410 stime: 155 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/ekiga'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46977654920992 (LWP 8299)]
[New Thread 1109707088 (LWP 8377)]
[New Thread 1109440848 (LWP 8376)]
[New Thread 1134352720 (LWP 8374)]
[New Thread 1099716944 (LWP 8312)]
[New Thread 1099450704 (LWP 8310)]
[New Thread 1074272592 (LWP 8303)]
0x00002ab9d2a28d78 in __lll_mutex_lock_wait () from /lib/libpthread.so.0

+ Trace 104340

Thread 4 (Thread 1134352720 (LWP 8374))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 SIPEndPoint::OnReceivedAuthenticationRequired
from /usr/lib64/libopal_linux_x86_64_r.so.2.2
#4 SIPEndPoint::OnReceivedResponse
from /usr/lib64/libopal_linux_x86_64_r.so.2.2
#5 SIPTransaction::OnReceivedResponse
from /usr/lib64/libopal_linux_x86_64_r.so.2.2
#6 SIPEndPoint::OnReceivedPDU
from /usr/lib64/libopal_linux_x86_64_r.so.2.2
#7 SIPEndPoint::HandlePDU
from /usr/lib64/libopal_linux_x86_64_r.so.2.2
#8 SIPEndPoint::TransportThreadMain
from /usr/lib64/libopal_linux_x86_64_r.so.2.2
#9 PThread::PX_ThreadStart
from /usr/lib64/libpt_linux_x86_64_r.so.1.10.3
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6
#12 ??

Comment 1 Damien Sandras 2007-01-22 18:53:30 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!

Comment 2 Bruno Boaventura 2007-02-25 14:56:44 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 3 Christian Kirbach 2007-03-17 18:35:04 UTC

duplicate, reopening

Comment 4 Christian Kirbach 2007-03-17 18:35:28 UTC

*** Bug 419454 has been marked as a duplicate of this bug. ***

Comment 5 Christian Kirbach 2007-03-17 18:35:47 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 6 Damien Sandras 2007-03-17 18:39:07 UTC

Should be a DUP of bug #411438.

*** This bug has been marked as a duplicate of 411438 ***