Bug 459657 – crash in Ekiga Softphone: Hanging up from sip:500@...

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 459657 - crash in Ekiga Softphone: Hanging up from sip:500@...


Summary:	crash in Ekiga Softphone: Hanging up from sip:500@...


Status:	RESOLVED DUPLICATE of bug 413552

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:

Depends on:
Blocks:

Reported:	2007-07-23 18:00 UTC by adam.wilson.ie
Modified:	2007-07-23 18:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description adam.wilson.ie 2007-07-23 18:00:59 UTC

Version: 2.0.9

What were you doing when the application crashed?
Hanging up from sip:500@ekiga.net


Distribution: Unknown
Gnome Release: 2.18.3 2007-07-07 (Archlinux)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-ARCH #1 SMP PREEMPT Sat Jul 7 09:57:11 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 93196288 vsize: 93196288 resident: 27086848 share: 20193280 rss: 27086848 rss_rlim: 4294967295
CPU usage: start_time: 1185213728 rtime: 393 utime: 360 stime: 33 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 -1244461360 (LWP 4343)]
[New Thread -1285244016 (LWP 4391)]
[New Thread -1283339376 (LWP 4380)]
[New Thread -1308456048 (LWP 4376)]
[New Thread -1307915376 (LWP 4375)]
[New Thread -1273549936 (LWP 4364)]
[New Thread -1273283696 (LWP 4363)]
[New Thread -1273017456 (LWP 4360)]
[New Thread -1264624752 (LWP 4354)]
[New Thread -1245729904 (LWP 4350)]
[New Thread -1245463664 (LWP 4349)]
(no debugging symbols found)
0xb7f4c410 in __kernel_vsyscall ()

+ Trace 150045

Thread 2 (Thread -1285244016 (LWP 4391))

#0 __kernel_vsyscall
#1 ??
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 __assert_fail
from /lib/libc.so.6
#8 sndrv_pcm_hw_params
from /usr/lib/libasound.so.2
#9 snd_pcm_plug_hw_params
from /usr/lib/libasound.so.2
#10 sndrv_pcm_hw_params
from /usr/lib/libasound.so.2
#11 snd_pcm_hw_params
from /usr/lib/libasound.so.2
#12 PSoundChannelALSA::Setup
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
#13 PSoundChannelALSA::Open
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
#14 PSoundChannel::CreateOpenedChannel
from /usr/lib/libpt_linux_x86_r.so.1.10.7
#15 GMSoundEvent::Main
#16 GMSoundEvent::GMSoundEvent
#17 GMPCSSEndpoint::PlaySoundEvent
#18 GMManager::OnClearedCall
#19 OpalCall::OnCleared
from /usr/lib/libopal_linux_x86_r.so.2.2
#20 OpalCall::OnReleased
from /usr/lib/libopal_linux_x86_r.so.2.2
#21 OpalManager::OnReleased
from /usr/lib/libopal_linux_x86_r.so.2.2
#22 GMManager::OnReleased
#23 OpalEndPoint::OnReleased
from /usr/lib/libopal_linux_x86_r.so.2.2
#24 OpalConnection::OnReleased
from /usr/lib/libopal_linux_x86_r.so.2.2
#25 SIPConnection::OnReleased
from /usr/lib/libopal_linux_x86_r.so.2.2
#26 OpalConnection::OnReleaseThreadMain
from /usr/lib/libopal_linux_x86_r.so.2.2
#27 OpalConnection::OnReleaseThreadMain_PNotifier::Call
from /usr/lib/libopal_linux_x86_r.so.2.2
#28 PSimpleThread::Main
from /usr/lib/libpt_linux_x86_r.so.1.10.7
#29 PThread::PX_ThreadStart
from /usr/lib/libpt_linux_x86_r.so.1.10.7
#30 start_thread
from /lib/libpthread.so.0
#31 clone
from /lib/libc.so.6

Comment 1 Snark 2007-07-23 18:36:23 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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