GNOME Bugzilla – Bug 448215
crash in IP Telephony, VoIP and Video Conferencing: update on FC6 to ekiga 2...
Last modified: 2007-06-16 14:48:25 UTC
Version: 2.0.9 What were you doing when the application crashed? update on FC6 to ekiga 2.0.9 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 18:18:22 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 141336576 vsize: 141336576 resident: 44933120 share: 39149568 rss: 44933120 rss_rlim: -1 CPU usage: start_time: 1182004851 rtime: 140 utime: 30 stime: 110 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 4141647584 (LWP 9411)] [New Thread 4044352400 (LWP 9555)] [New Thread 4054842256 (LWP 9546)] [New Thread 4138396560 (LWP 9499)] [New Thread 4138662800 (LWP 9498)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 141447
Thread 1 (Thread 4141647584 (LWP 9411))
----------- .xsession-errors (19 sec old) --------------------- Invalid byte sequence during conversion from UTF-8 to ISO-8859-1 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from UTF-8 to ISO-8859-1 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from UTF-8 to ISO-8859-1 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from UTF-8 to ISO-8859-1 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from UTF-8 to ISO-8859-1 ** (bug-buddy:9283): WARNING **: Não foi possível carregar ícone para Abrir Pasta ** (bug-buddy:9283): WARNING **: Não foi possível carregar ícone para Zapping TV Viewer warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4 --------------------------------------------------
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 434223 ***