GNOME Bugzilla – Bug 437276
crash in IP Telephony, VoIP and Video Conferencing: video call, just switche...
Last modified: 2007-05-10 05:54:13 UTC
Version: 2.0.5 What were you doing when the application crashed? video call, just switched to LPC and then reconnected and 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.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:41:13 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 122540032 vsize: 0 resident: 122540032 share: 0 rss: 29884416 rss_rlim: 0 CPU usage: start_time: 1178742327 rtime: 0 utime: 174 stime: 0 cutime:166 cstime: 0 timeout: 8 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 26458)] [New Thread -1281786992 (LWP 26528)] [New Thread -1280300144 (LWP 26527)] [New Thread -1280033904 (LWP 26526)] [New Thread -1279767664 (LWP 26525)] [New Thread -1282344048 (LWP 26524)] [New Thread -1267221616 (LWP 26512)] [New Thread -1279493232 (LWP 26511)] [New Thread -1278780528 (LWP 26502)] [New Thread -1267909744 (LWP 26501)] [New Thread -1266955376 (LWP 26487)] [New Thread -1266689136 (LWP 26486)] [New Thread -1266422896 (LWP 26485)] [New Thread -1265636464 (LWP 26467)] [New Thread -1255146608 (LWP 26465)] [New Thread -1211237488 (LWP 26462)] [New Thread -1210971248 (LWP 26461)] 0x00b2f402 in __kernel_vsyscall ()
+ Trace 133348
Thread 6 (Thread -1282344048 (LWP 26524))
----------- .xsession-errors (2858 sec old) --------------------- localuser:ahuxley being added to access control list warning: /etc/X11/xinit/xinitrc.d/xmbind does not end in .sh extension, ignoring /home/ahuxley/.xsession: line 6: osid: command not found --------------------------------------------------
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 398549 ***