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 455209 - crash in IP Telephony, VoIP and Video Conferencing:
crash in IP Telephony, VoIP and Video Conferencing:
Status: RESOLVED DUPLICATE of bug 417801
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-09 16:28 UTC by dpicard
Modified: 2007-07-09 16:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dpicard 2007-07-09 16:28:55 UTC 
Version: 2.0.5

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.21.5 #1 SMP Wed Jul 4 18:47:56 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 495996928 vsize: 495996928 resident: 40980480 share: 33714176 rss: 40980480 rss_rlim: -1
CPU usage: start_time: 1183998450 rtime: 16 utime: 13 stime: 3 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46966502112784 (LWP 7241)]
[New Thread 1133287744 (LWP 7258)]
[New Thread 1133021504 (LWP 7252)]
[New Thread 1074272576 (LWP 7245)]
[New Thread 1074006336 (LWP 7244)]
0x0000003d1b20d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 146766

Thread 1 (Thread 46966502112784 (LWP 7241))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strlen
    from /lib64/libc.so.6
  • #4 vfprintf
    from /lib64/libc.so.6
  • #5 __vsnprintf_chk
    from /lib64/libc.so.6
  • #6 e_vcard_new
  • #7 PPluginServiceDescriptor::~PPluginServiceDescriptor
  • #8 PPluginServiceDescriptor::~PPluginServiceDescriptor
  • #9 PList<PIPSocket::InterfaceEntry>::~PList\$delete
  • #10 PList<PIPSocket::InterfaceEntry>::~PList$delete
  • #11 PList<PIPSocket::InterfaceEntry>::~PList$delete
  • #12 PList<PString>::~PList
  • #13 __libc_start_main
    from /lib64/libc.so.6
  • #14 PAbstractSortedList::GetAt
    at ../common/collect.cxx line 987
  • #15 ??
  • #16 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (241 sec old) ---------------------
MPlayer 1.0rc1-4.1.1 (C) 2000-2006 MPlayer Team
CPU: Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz (Family: 6, Model: 15, Stepping: 6)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2
xscreensaver_disable: Could not find XScreenSaver window.
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Window manager warning: Window 0x2c00019 (MPlayer) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 440 x 120; this doesn't make much sense.
Playing /dev/video1.

Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache f
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Snark 2007-07-09 16:33:06 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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