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 452066 - crash in IP Telephony, VoIP and Video Conferencing: Starting ekiga causes th...
crash in IP Telephony, VoIP and Video Conferencing: Starting ekiga causes th...
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-06-28 22:15 UTC by stevepaquin
Modified: 2007-06-28 23:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description stevepaquin 2007-06-28 22:15:13 UTC 
Version: 2.0.5

What were you doing when the application crashed?
Starting ekiga causes this crash every time.  I just did a yum update to my system.  It was working fine before that.


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.2962.fc6 #1 SMP Tue Jun 19 18:24:12 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 140353536 vsize: 0 resident: 140353536 share: 0 rss: 46096384 rss_rlim: 0
CPU usage: start_time: 1183068801 rtime: 0 utime: 71 stime: 0 cutime:64 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 -1208387872 (LWP 3319)]
[New Thread -1302774896 (LWP 3336)]
[New Thread -1302086768 (LWP 3335)]
[New Thread -1301820528 (LWP 3334)]
[New Thread -1301554288 (LWP 3333)]
[New Thread -1301288048 (LWP 3331)]
[New Thread -1290798192 (LWP 3329)]
[New Thread -1210754160 (LWP 3326)]
[New Thread -1210487920 (LWP 3325)]
0x00ee1402 in __kernel_vsyscall ()

+ Trace 144463

Thread 1 (Thread -1208387872 (LWP 3319))

  • #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 ---------------------
  Resource id:  0x1400b65
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1400b66
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  155
  Minor opcode:  6
  Resource id:  0x1400b66
Could not find the frame base for "PSyncPoint::Wait(PTimeInterval const&)".
Could not find the frame base for "PHouseKeepingThread::Main()".
Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)".
Could not find the frame base for "PSocket::Select(PSocket::SelectList&, PSocket::SelectList&, PSocket::SelectList&, PTimeInterval const&)".
Could not find the frame base for "PThread::PX_ThreadStart(void*)".
Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)".
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-28 23:58:39 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 ***