GNOME Bugzilla – Bug 664907
ekiga crash after upgrade to oneiric (kubuntu)
Last modified: 2012-10-17 19:32:19 UTC
full details of this bug are previously reported at : https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/896838
I don't see any stacktrace in downstream bug. Please paste stacktrace in upstream (GNOME bugzilla) when you are reporting bug here from launchpad.
Created attachment 202282 [details] crash dump, generated by apport crash dump, generated by apport
gdb stacktrace is probably more welcome than a coredump, but I'll let the Ekiga developers decide...
Nadav, you must use the instructions at http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze
Here is a debug output from gdb: GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>... Reading symbols from /usr/bin/ekiga...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/ekiga [Thread debugging using libthread_db enabled] [New Thread 0x7ffff7fa5700 (LWP 7544)] [New Thread 0x7ffff7f64700 (LWP 7545)] [New Thread 0x7ffff7f23700 (LWP 7546)] [New Thread 0x7ffff7ee2700 (LWP 7547)] [New Thread 0x7ffff7ea1700 (LWP 7548)] [New Thread 0x7ffff7e60700 (LWP 7549)] [New Thread 0x7fffe399c700 (LWP 7550)] [New Thread 0x7fffe395b700 (LWP 7551)] [New Thread 0x7fffe391a700 (LWP 7552)] [New Thread 0x7fffe34a7700 (LWP 7553)] [New Thread 0x7fffe3466700 (LWP 7554)] [Thread 0x7fffe391a700 (LWP 7552) exited] [New Thread 0x7fffe391a700 (LWP 7555)] [New Thread 0x7fffe3425700 (LWP 7556)] [Thread 0x7fffe3466700 (LWP 7554) exited] [New Thread 0x7fffe3466700 (LWP 7557)] [New Thread 0x7fffe33e4700 (LWP 7558)] [Thread 0x7fffe33e4700 (LWP 7558) exited] [New Thread 0x7fffe33e4700 (LWP 7559)] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff3181ccb in gconf_engine_get_fuller () from /usr/lib/libgconf-2.so.4 (gdb) quit A debugging session is active. Inferior 1 [process 7539] will be killed.
Please enter "thread apply all bt" before "quit", plus make sure that debug packages are installed.
Created attachment 202286 [details] gdb output for ekiga I have installed ekiga-debug and got a full debug output Attached as gdb-ekiga.txt
Comment on attachment 202286 [details] gdb output for ekiga Can you also install debug packages for libgconf?
I just installed a debug packages of libgconf-dev but it seems they are not used. I am not even sure there are debug libs in dev How can i force it? or make sure i am using debug libs? Here is what i get:
+ Trace 229155
Thread 1 (Thread 0x7ffff7fad980 (LWP 10095))
It is not -dev, it is -dbg or -debug. Please install and get another trace. The problem comes when reading a gconf key.
Nadav: Can you provide a new trace as asked for in comment 10, please?
Andre: sorry, i am unable to find debug packages to libgconf :-(
Well, I have just had it once when run under gdb. And indeed, there is no libgconf2-dbg package in debian (unstable). Maybe it is because the gconf entry involved (call_history) is very big (125kB)? Anyway, I cannot reproduce anymore.
This could be bug #667167. Let's wait until it appears in our distributions.
*** This bug has been marked as a duplicate of bug 667167 ***