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 452983 - crash in IP Telephony, VoIP and Video Conferencing: Running Ekiga
crash in IP Telephony, VoIP and Video Conferencing: Running Ekiga
Status: RESOLVED DUPLICATE of bug 416551
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-02 03:36 UTC by tarunmani
Modified: 2007-07-02 04:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description tarunmani 2007-07-02 03:36:46 UTC 
Version: 2.0.5

What were you doing when the application crashed?
Running Ekiga


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.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 133750784 vsize: 0 resident: 133750784 share: 0 rss: 41558016 rss_rlim: 0
CPU usage: start_time: 1183347380 rtime: 0 utime: 56 stime: 0 cutime:49 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

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 -1208301856 (LWP 28021)]
[New Thread -1306018928 (LWP 28036)]
[New Thread -1305752688 (LWP 28035)]
[New Thread -1305486448 (LWP 28033)]
[New Thread -1294996592 (LWP 28031)]
[New Thread -1210668144 (LWP 28024)]
[New Thread -1210401904 (LWP 28023)]
0x00e1c402 in __kernel_vsyscall ()

+ Trace 145161

Thread 1 (Thread -1208301856 (LWP 28021))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 gm_open_uri
  • #6 gm_open_uri
  • #7 avahi_service_browser_event
    from /usr/lib/libavahi-client.so.3
  • #8 avahi_client_new
    from /usr/lib/libavahi-client.so.3
  • #9 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #10 avahi_dbus_connection_glue
    from /usr/lib/libavahi-client.so.3
  • #11 avahi_glib_poll_new
    from /usr/lib/libavahi-glib.so.1
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 PList<PString>::~PList
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 PAbstractSortedList::GetAt
    at ../common/collect.cxx line 987
  • #0 __kernel_vsyscall 


----------- .xsession-errors (179153 sec old) ---------------------
CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz (Family: 15, Model: 4, Stepping: 1)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
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 0x3600019 (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 http://192.168.200.2/torus7.mpg.
Resolving 192.168.200.2 for AF_INET6...
Couldn't resolve name for AF_INET6: 192.168.200.2
Connecting to server 192.168.200.2[192.168.200.2]: 80...
Cache size set to 320 KBytes

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 Karsten Bräckelmann 2007-07-02 04:31:05 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 416551 ***