GNOME Bugzilla – Bug 464603
crash in Ekiga Softphone: startade
Last modified: 2007-08-08 07:55:30 UTC
Version: 2.0.7 What were you doing when the application crashed? startade Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.16.3 2007-06-02 (Gentoo) BugBuddy Version: 2.16.1 System: Linux 2.6.20-gentoo-r8 #7 SMP Mon May 14 23:55:25 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled Memory status: size: 241917952 vsize: 241917952 resident: 31154176 share: 23789568 rss: 31154176 rss_rlim: -1 CPU usage: start_time: 1186558360 rtime: 92 utime: 84 stime: 8 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47449205684400 (LWP 19130)] [New Thread 1141680448 (LWP 19149)] [New Thread 1141414208 (LWP 19147)] [New Thread 1074272576 (LWP 19135)] [New Thread 1074006336 (LWP 19134)] 0x00002b279b74ab0f in waitpid () from /lib/libpthread.so.0
+ Trace 153651
Thread 1 (Thread 47449205684400 (LWP 19130))
----------- .xsession-errors (6 sec old) --------------------- ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Öppna mapp ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Väderrapport ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Volymkontroll ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Diskmonterare ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Systemövervakare ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Visa skrivbord ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Papperskorg ** (bug-buddy:19152): WARNING **: Kunde inte läsa in ikon för Batteriövervakare --------------------------------------------------
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. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 416532 ***