GNOME Bugzilla – Bug 436923
crash in IP Telephony, VoIP and Video Conferencing:
Last modified: 2007-05-08 15:51:46 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.20-1.2948.fc6 #1 SMP Fri Apr 27 18:53:15 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 107634688 vsize: 0 resident: 107634688 share: 0 rss: 24170496 rss_rlim: 0 CPU usage: start_time: 1178639193 rtime: 0 utime: 63 stime: 0 cutime:59 cstime: 0 timeout: 4 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 -1208559904 (LWP 3107)] [New Thread -1268782192 (LWP 3124)] [New Thread -1256801392 (LWP 3123)] [New Thread -1256535152 (LWP 3121)] [New Thread -1258292336 (LWP 3114)] [New Thread -1210926192 (LWP 3111)] [New Thread -1210659952 (LWP 3110)] 0x007c0402 in __kernel_vsyscall ()
+ Trace 133096
Thread 1 (Thread -1208559904 (LWP 3107))
----------- .xsession-errors (165 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/group3d.netlab.eecs.ku.edu:/tmp/.ICE-unix/2813 ** (eggcups:2917): WARNING **: IPP request failed with status 1030 ** (eggcups:2917): WARNING **: IPP request failed with status 1030 You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. --------------------------------------------------
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 ***