Hide Forgot
Description of problem: Starting up freetalk, it prompts me for my JID and password. It then attempts to connect and promptly segfaults. Version-Release number of selected component (if applicable): freetalk-3.2-7.fc18.x86_64 How reproducible: 100%, at least on my system. Here is a dump from GDB: [pizza@stuffed ~]$ gdb freetalk GNU gdb (GDB) Fedora 7.5.1-42.fc18 Copyright (C) 2012 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-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/freetalk...Reading symbols from /usr/bin/freetalk...(no debugging symbols found)...done. (no debugging symbols found)...done. Missing separate debuginfos, use: debuginfo-install freetalk-3.2-7.fc18.x86_64 (gdb) run Starting program: /usr/bin/freetalk [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Detaching after fork from child process 1756. Detaching after fork from child process 1757. Detaching after fork from child process 1759. Detaching after fork from child process 1761. Loading dictionary [/usr/share/dict/words]... [479828] words Jabber ID: pizza Password: Connecting ... Detaching after fork from child process 1780. ~\/~ Program received signal SIGSEGV, Segmentation fault. 0x0000003ee3846005 in g_source_destroy () from /lib64/libglib-2.0.so.0 (gdb) bt #0 0x0000003ee3846005 in g_source_destroy () from /lib64/libglib-2.0.so.0 #1 0x0000003201e0e708 in _lm_socket_failed_with_error () from /lib64/libloudmouth-1.so.0 #2 0x0000003201e0ead1 in socket_connect_cb () from /lib64/libloudmouth-1.so.0 #3 0x0000003ee3847a55 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #4 0x0000003ee3847d88 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0 #5 0x0000003ee3848182 in g_main_loop_run () from /lib64/libglib-2.0.so.0 #6 0x0000000000404803 in inner_main(void*, int, char**) () #7 0x0000003ee28673df in invoke_main_func () from /lib64/libguile.so.17 #8 0x0000003ee283dcca in c_body () from /lib64/libguile.so.17 #9 0x0000003ee28a4b22 in scm_c_catch () from /lib64/libguile.so.17 #10 0x0000003ee283e257 in scm_i_with_continuation_barrier () from /lib64/libguile.so.17 #11 0x0000003ee283e2f0 in scm_c_with_continuation_barrier () from /lib64/libguile.so.17 #12 0x0000003ee28a2fe4 in scm_i_with_guile_and_parent () from /lib64/libguile.so.17 #13 0x0000003ee2867485 in scm_boot_guile () from /lib64/libguile.so.17 #14 0x0000000000404281 in main () I don't know why it's failing to connect (maybe IPv6 related?) but in any case freetalk shouldn't segfault when the connection fails.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.