Description of problem: I was testing for Ekiga's configuration. Just received an incoming call. Version-Release number of selected component: ekiga-4.0.1-1.fc17 Additional info: backtrace_rating: 4 cmdline: ekiga crash_function: std::__throw_logic_error executable: /usr/bin/ekiga kernel: 3.7.9-104.fc17.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 std::__throw_logic_error at ../../../../../libstdc++-v3/src/c++11/functexcept.cc:66 #7 std::string::_S_construct<char const*> at /usr/src/debug/gcc-4.7.2-20120921/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:135 #8 _S_construct_aux<char const*> at /usr/src/debug/gcc-4.7.2-20120921/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1722 #9 _S_construct<char const*> at /usr/src/debug/gcc-4.7.2-20120921/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1743 #10 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string at /usr/src/debug/gcc-4.7.2-20120921/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:217 #11 on_chat_unread_alert at gui/main_window.cpp:859 #12 _g_closure_invoke_va at gclosure.c:840 #15 on_message_notice_event at ../lib/engine/gui/gtk-frontend/chat-window.cpp:294 #16 _g_closure_invoke_va at gclosure.c:840 #22 chat_area_add_message at ../lib/engine/gui/gtk-frontend/chat-area.cpp:258
Created attachment 712362 [details] File: backtrace
Created attachment 712363 [details] File: cgroup
Created attachment 712364 [details] File: core_backtrace
Created attachment 712365 [details] File: dso_list
Created attachment 712366 [details] File: environ
Created attachment 712367 [details] File: gconf_subtree
Created attachment 712368 [details] File: limits
Created attachment 712369 [details] File: maps
Created attachment 712370 [details] File: open_fds
Created attachment 712371 [details] File: proc_pid_status
Created attachment 712372 [details] File: smolt_data
Created attachment 712373 [details] File: var_log_messages
Can you recreate it when running "ekiga -d 4" and attach the resulting log to the ticket please?
I will take a look and tell you if the -d 4 is needed in this case. It seems a problem with the audio file used when a chat message arrives.
José, what does gconftool -g /apps/ekiga/general/sound_events/new_message_sound show if you run it in a terminal? Have you modified that information (the file for new_message_sound)?
Any news, José?
Fixed with https://git.gnome.org/browse/ekiga/commit/?id=7d54888028e. I wanted to know how this could happen, but the reporter still have not yet answered...
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.