GNOME Bugzilla – Bug 533629
Segmentation fault when account information are set
Last modified: 2008-05-18 09:43:46 UTC
Steps to reproduce: - When already set some account information, then just start ekiga. The application immediately crashes. - When no account information are set, e.g. after deleting the gconf-keys manually from ~/.gconf/apps/, there are two possibilitys to reproduce: 1. Start ekiga, follow the configuration wizard with inserting account information for your ekiga.net-account. after finishing the wizard ekiga crashes. 2. Start ekiga, cancel the configuration-wizard and enter your account-information - e.g. for ekiga.net manually. When closing the account-configuration-dialog with [OK]-Button, ekiga crashes. Stack trace: [?1034hGNU gdb Fedora (6.8-5.fc9) Copyright (C) 2008 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 "i386-redhat-linux-gnu"... (gdb) start Breakpoint 1 at 0x8098c4b: file gui/main.cpp, line 4537. Starting program: /usr/bin/ekiga [Thread debugging using libthread_db enabled] [New Thread 0xb8069730 (LWP 24419)] main (argc=1, argv=0xbfdac0c4, envp=0xbfdac0cc) at gui/main.cpp:4537 4537 PProcess::PreInitialise (argc, argv, envp); Missing separate debuginfos, use: debuginfo-install keyutils.i386 (gdb) start[K[K[K[K[Kcontinue Continuing. [New Thread 0xb7d24b90 (LWP 25152)] [New Thread 0xb7ce3b90 (LWP 25153)] [Thread 0xb7d24b90 (LWP 25152) exited] [New Thread 0xb1ef1b90 (LWP 25158)] [New Thread 0xb14f0b90 (LWP 25159)] [New Thread 0xb0ae5b90 (LWP 25161)] [New Thread 0xb00e4b90 (LWP 25162)] [New Thread 0xaf6e3b90 (LWP 25163)] [New Thread 0xaece2b90 (LWP 25164)] [New Thread 0xae2e1b90 (LWP 25165)] [New Thread 0xad8e0b90 (LWP 25166)] [New Thread 0xb7d24b90 (LWP 25168)] [Thread 0xb0ae5b90 (LWP 25161) exited] [Thread 0xb00e4b90 (LWP 25162) exited] [Thread 0xaece2b90 (LWP 25164) exited] [Thread 0xaf6e3b90 (LWP 25163) exited] [Thread 0xb1ef1b90 (LWP 25158) exited] [Thread 0xb14f0b90 (LWP 25159) exited] [Thread 0xae2e1b90 (LWP 25165) exited] [New Thread 0xb0ae2b90 (LWP 25173)] [New Thread 0xb0aa1b90 (LWP 25174)] [New Thread 0xb0a60b90 (LWP 25176)] [Thread 0xb0a60b90 (LWP 25176) exited] [New Thread 0xae2e1b90 (LWP 25178)] [New Thread 0xb14f0b90 (LWP 25182)] [Thread 0xb14f0b90 (LWP 25182) exited] [Thread 0xae2e1b90 (LWP 25178) exited] Program received signal SIGSEGV, Segmentation fault. 0x00f06e74 in PContainer (this=0xbfdaaad4, cont=@0x8935a00) at ../common/contain.cxx:692 692 PAssert2(cont.reference != NULL, cont.GetClass(), "Copy of deleted container"); Missing separate debuginfos, use: debuginfo-install acl.i386 attr.i386 bug-buddy.i386 elfutils.i386 gamin.i386 gtk2-engines.i386 libavc1394.i386 libdv.i386 libraw1394.i386 tracker.i386 (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault. 0x0000004e in ?? () (gdb) quit The program is running. Exit anyway? (y or n) Not confirmed. (gdb) continue Continuing. [Thread 0xb0aa1b90 (LWP 25174) exited] [Thread 0xb0ae2b90 (LWP 25173) exited] [Thread 0xb7d24b90 (LWP 25168) exited] [Thread 0xad8e0b90 (LWP 25166) exited] [Thread 0xb7ce3b90 (LWP 25153) exited] Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) Other information: The stack trace is produced following the instructions from http://wiki.ekiga.org/index.php/Debugging_Ekiga (Before typing 'continue' i certainly installed the needed debug-information. Unfortunately the keyutils.i386 could not be found.). This errors seem to occur since i have upgraded my system from Fedora 8 to Fedora 9 this week.
I was quite certain our instructions didn't ask for "continue", but for "thread apply all bt"... Could you please try to get us a backtrace?
Created attachment 111087 [details] backtrace with thread-apply all-bt I'm sorry i forgot to get the backtrace..
It's a fedora packaging bug, see bug #532525 *** This bug has been marked as a duplicate of 532525 ***