GNOME Bugzilla – Bug 358296
crash in Ekiga Softphone: Video conference with ne...
Last modified: 2006-09-30 14:08:13 UTC
Version: 2.0.3 What were you doing when the application crashed? Video conference with netmeeting client Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 112898048 vsize: 0 resident: 112898048 share: 0 rss: 32092160 rss_rlim: 0 CPU usage: start_time: 1159535221 rtime: 0 utime: 268 stime: 0 cutime:222 cstime: 0 timeout: 46 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1247025488 (LWP 23059)] [New Thread -1265079392 (LWP 23226)] [New Thread -1266533472 (LWP 23201)] [New Thread -1266267232 (LWP 23200)] [New Thread -1264505952 (LWP 23198)] [New Thread -1263891552 (LWP 23197)] [New Thread -1265427552 (LWP 23188)] [New Thread -1265693792 (LWP 23185)] [New Thread -1307579488 (LWP 23174)] [New Thread -1310332000 (LWP 23092)] [New Thread -1310065760 (LWP 23087)] [New Thread -1309033568 (LWP 23081)] [New Thread -1308767328 (LWP 23080)] [New Thread -1297462368 (LWP 23076)] [New Thread -1299186784 (LWP 23074)] [New Thread -1249072224 (LWP 23065)] [New Thread -1248805984 (LWP 23064)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 73567
Thread 3 (Thread -1266533472 (LWP 23201))
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. Also, unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 358488 has been marked as a duplicate of this bug. ***
Yeah, sorry about that. BugBuddy doesn't seem to report the process id anywhere. At least I can't seem to find it. This seems to be camera related somehow, but I'm not really sure. I can't find any debug package for ekiga for edgy eft, and I failed miserably to build it myself :) Sorry I can't give any more info at this point. Now Ekiga crashes directly at startup, it's getting worse.
try this : gdb ekiga type 'run' when it crashes, type 'bt' There is a bug in GTK+ 2.10.4, affecting many GTK+ applications, including Ekiga. We have received several bug reports related to that.
"several" !? I call that "many", or even "too many"!!
Okay I've tried what Damien Sandras said, and here is the result: (Something about segfault int strcmp, odd but.. well) GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /usr/bin/ekiga (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1246902608 (LWP 7179)] GTK Accessibility Module initialized Bonobo accessibility support initialized [New Thread -1249510496 (LWP 7186)] [New Thread -1249776736 (LWP 7187)] [New Thread -1264563296 (LWP 7192)] [New Thread -1272956000 (LWP 7193)] [New Thread -1282409568 (LWP 7194)] [New Thread -1290802272 (LWP 7196)] [New Thread -1291404384 (LWP 7199)] [New Thread -1291670624 (LWP 7200)] [New Thread -1291936864 (LWP 7201)] [New Thread -1292203104 (LWP 7203)] [New Thread -1292973152 (LWP 7204)] [Thread -1272956000 (LWP 7193) exited] [Thread -1264563296 (LWP 7192) exited] [New Thread -1264563296 (LWP 7205)] [New Thread -1272956000 (LWP 7206)] [New Thread -1293632608 (LWP 7207)] Program received signal SIGSEGV, Segmentation fault.
+ Trace 73704
Thread NaN (LWP 7179)
OK, then it is a GTK+ 2.10.4 bug. We are getting dozens of that bug report each day. I guess that they will release GTK+ 2.10.5. Thanks for the report! *** This bug has been marked as a duplicate of 358405 ***