GNOME Bugzilla – Bug 437278
crash in IP Telephony, VoIP and Video Conferencing:
Last modified: 2007-05-10 05:55:17 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.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: 122298368 vsize: 0 resident: 122298368 share: 0 rss: 30023680 rss_rlim: 0 CPU usage: start_time: 1178742389 rtime: 0 utime: 523 stime: 0 cutime:513 cstime: 0 timeout: 10 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 -1209084192 (LWP 26579)] [New Thread -1283064944 (LWP 27475)] [New Thread -1282188400 (LWP 27474)] [New Thread -1281311856 (LWP 27473)] [New Thread -1281045616 (LWP 27472)] [New Thread -1280779376 (LWP 27471)] [New Thread -1268003952 (LWP 27460)] [New Thread -1280222320 (LWP 27459)] [New Thread -1279562864 (LWP 26621)] [New Thread -1268692080 (LWP 26620)] [New Thread -1267737712 (LWP 26606)] [New Thread -1267471472 (LWP 26605)] [New Thread -1267205232 (LWP 26604)] [New Thread -1254839408 (LWP 26588)] [New Thread -1256195184 (LWP 26586)] [New Thread -1212019824 (LWP 26583)] [New Thread -1211753584 (LWP 26582)] 0x00b1c402 in __kernel_vsyscall ()
+ Trace 133350
Thread 6 (Thread -1280779376 (LWP 27471))
----------- .xsession-errors (2973 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. By the way, you already reported the very same bug *one* minute ago. *** This bug has been marked as a duplicate of 398549 ***