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 361765 - crash in Ekiga Softphone: listening music with lis...
crash in Ekiga Softphone: listening music with lis...
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: OPAL
2.0.x
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
: 371845 372772 374351 374917 376739 377381 378026 378350 384939 387600 387954 389807 390014 393120 397252 398098 407951 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-12 18:01 UTC by fandonov
Modified: 2007-02-15 18:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description fandonov 2006-10-12 18:01:01 UTC
Version: 2.0.3

What were you doing when the application crashed?
listening music with listen player and there was error message from Ekiga, that other program is using the sound card


Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.0 2006-10-03 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 107954176 vsize: 0 resident: 107954176 share: 0 rss: 30244864 rss_rlim: 0
CPU usage: start_time: 1160686829 rtime: 0 utime: 589 stime: 0 cutime:543 cstime: 0 timeout: 46 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1245768000 (LWP 3302)]
[New Thread -1259856976 (LWP 3339)]
[New Thread -1259025488 (LWP 3337)]
[New Thread -1259287632 (LWP 3331)]
[New Thread -1315554384 (LWP 3327)]
[New Thread -1258316880 (LWP 3324)]
[New Thread -1315816528 (LWP 3321)]
[New Thread -1315132496 (LWP 3318)]
[New Thread -1314870352 (LWP 3317)]
[New Thread -1314608208 (LWP 3315)]
[New Thread -1306219600 (LWP 3313)]
[New Thread -1247478864 (LWP 3305)]
[New Thread -1247216720 (LWP 3304)]
0xb6323d57 in ___newselect_nocancel () from /lib/tls/libc.so.6

Thread 4 (Thread -1259287632 (LWP 3331))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 H323_RTPChannel::OnReceivedAckPDU
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #5 H323_RealTimeChannel::OnReceivedAckPDU
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #6 H245NegLogicalChannel::HandleOpenAck
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #7 H245NegLogicalChannels::HandleOpenAck
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #8 H323Connection::OnH245Response
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #9 H323Connection::HandleControlPDU
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #10 H323Connection::HandleControlData
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #11 H323Connection::HandleControlChannel
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #12 H323Connection::NewIncomingControlChannel
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #13 H323Connection::NewIncomingControlChannel_PNotifier::Call
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #14 OpalListener::ListenForConnections
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #15 OpalListener::ListenForConnections_PNotifier::Call
    from /usr/lib/libopal_linux_x86_r.so.2.2
  • #16 PSimpleThread::Main
    from /usr/lib/libpt.so.1
  • #17 PThread::PX_ThreadStart
    from /usr/lib/libpt.so.1
  • #18 start_thread
    from /lib/tls/libpthread.so.0
  • #19 clone
    from /lib/tls/libc.so.6

Comment 1 Snark 2006-10-12 18:06:28 UTC
There is a backtrace, and it isn't edgy... this is news !

Are you using gtk+ 2.10 ?
Comment 2 Damien Sandras 2006-10-12 18:15:51 UTC
No, the backtrace indicates a crash in OPAL during an H.323 call.

We should report that bug upstream on sourceforge, but the backtrace doesn't have debug symbols, so it is hardly useful.
Comment 3 Damien Sandras 2006-10-28 16:53:01 UTC
A bug was introduced by myself when fixing SIP reinvite between 2.0.2 and 2.0.3. It is now fixed.
Comment 4 Damien Sandras 2006-11-07 08:51:06 UTC
*** Bug 371845 has been marked as a duplicate of this bug. ***
Comment 5 Damien Sandras 2006-11-10 08:53:36 UTC
*** Bug 372772 has been marked as a duplicate of this bug. ***
Comment 6 Damien Sandras 2006-11-12 17:30:14 UTC
*** Bug 374351 has been marked as a duplicate of this bug. ***
Comment 7 Damien Sandras 2006-11-14 09:00:56 UTC
*** Bug 374917 has been marked as a duplicate of this bug. ***
Comment 8 Damien Sandras 2006-11-19 10:36:58 UTC
*** Bug 376739 has been marked as a duplicate of this bug. ***
Comment 9 Damien Sandras 2006-11-20 14:36:24 UTC
*** Bug 377381 has been marked as a duplicate of this bug. ***
Comment 10 Damien Sandras 2006-11-22 15:15:17 UTC
*** Bug 378026 has been marked as a duplicate of this bug. ***
Comment 11 Damien Sandras 2006-11-23 09:48:33 UTC
*** Bug 378350 has been marked as a duplicate of this bug. ***
Comment 12 Damien Sandras 2006-12-12 08:34:32 UTC
*** Bug 384939 has been marked as a duplicate of this bug. ***
Comment 13 Damien Sandras 2006-12-19 19:09:28 UTC
*** Bug 387600 has been marked as a duplicate of this bug. ***
Comment 14 Damien Sandras 2006-12-20 17:09:03 UTC
*** Bug 387954 has been marked as a duplicate of this bug. ***
Comment 15 Damien Sandras 2006-12-29 11:20:45 UTC
*** Bug 389807 has been marked as a duplicate of this bug. ***
Comment 16 Damien Sandras 2006-12-29 11:21:10 UTC
*** Bug 390014 has been marked as a duplicate of this bug. ***
Comment 17 Damien Sandras 2007-01-05 16:59:33 UTC
*** Bug 393120 has been marked as a duplicate of this bug. ***
Comment 18 Damien Sandras 2007-02-15 18:49:21 UTC
*** Bug 407951 has been marked as a duplicate of this bug. ***
Comment 19 Damien Sandras 2007-02-15 18:49:35 UTC
*** Bug 398098 has been marked as a duplicate of this bug. ***
Comment 20 Damien Sandras 2007-02-15 18:49:58 UTC
*** Bug 397252 has been marked as a duplicate of this bug. ***