GNOME Bugzilla – Bug 424544
crash in IP Telephony, VoIP and Video Conferencing: Opening Ekiga.
Last modified: 2007-03-30 17:05:10 UTC
Version: 2.0.5 What were you doing when the application crashed? Opening Ekiga. 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.2933.fc6 #1 SMP Mon Mar 19 10:42:48 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 150618112 vsize: 0 resident: 150618112 share: 0 rss: 23691264 rss_rlim: 0 CPU usage: start_time: 1175273401 rtime: 0 utime: 67 stime: 0 cutime:61 cstime: 0 timeout: 6 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 -1208396064 (LWP 10152)] [New Thread -1334416496 (LWP 10169)] [New Thread -1334150256 (LWP 10168)] [New Thread -1333564528 (LWP 10166)] [New Thread -1333298288 (LWP 10165)] [New Thread -1333032048 (LWP 10163)] [New Thread -1322542192 (LWP 10161)] [New Thread -1210762352 (LWP 10155)] [New Thread -1210496112 (LWP 10154)] 0x00254402 in __kernel_vsyscall ()
+ Trace 123557
Thread 1 (Thread -1208396064 (LWP 10152))
----------- .xsession-errors (14662 sec old) --------------------- QFile::open: No file name specified QFile::open: No file name specified QFile::open: No file name specified X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1401ede X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 154 Minor opcode: 6 Resource id: 0x1401ede QFile::open: No file name specified QFile::open: No file name specified ...Too much output, ignoring rest... --------------------------------------------------
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 ***