Bug 923029

Summary: [abrt] ekiga-4.0.1-1.fc17: std::__throw_logic_error: Process /usr/bin/ekiga was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: José Serralde <contacto>
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: eugen.dedu, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:451520e8d9c2becccfc23886ab91783ef44f6b1f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 08:29:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: gconf_subtree
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description José Serralde 2013-03-19 03:36:01 UTC
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

Comment 1 José Serralde 2013-03-19 03:36:04 UTC
Created attachment 712362 [details]
File: backtrace

Comment 2 José Serralde 2013-03-19 03:36:06 UTC
Created attachment 712363 [details]
File: cgroup

Comment 3 José Serralde 2013-03-19 03:36:08 UTC
Created attachment 712364 [details]
File: core_backtrace

Comment 4 José Serralde 2013-03-19 03:36:10 UTC
Created attachment 712365 [details]
File: dso_list

Comment 5 José Serralde 2013-03-19 03:36:12 UTC
Created attachment 712366 [details]
File: environ

Comment 6 José Serralde 2013-03-19 03:36:14 UTC
Created attachment 712367 [details]
File: gconf_subtree

Comment 7 José Serralde 2013-03-19 03:36:16 UTC
Created attachment 712368 [details]
File: limits

Comment 8 José Serralde 2013-03-19 03:36:17 UTC
Created attachment 712369 [details]
File: maps

Comment 9 José Serralde 2013-03-19 03:36:19 UTC
Created attachment 712370 [details]
File: open_fds

Comment 10 José Serralde 2013-03-19 03:36:21 UTC
Created attachment 712371 [details]
File: proc_pid_status

Comment 11 José Serralde 2013-03-19 03:36:22 UTC
Created attachment 712372 [details]
File: smolt_data

Comment 12 José Serralde 2013-03-19 03:36:24 UTC
Created attachment 712373 [details]
File: var_log_messages

Comment 13 Peter Robinson 2013-03-19 06:51:27 UTC
Can you recreate it when running "ekiga -d 4" and attach the resulting log to the ticket please?

Comment 14 Eugen Dedu 2013-03-20 08:38:21 UTC
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.

Comment 15 Eugen Dedu 2013-03-22 15:52:52 UTC
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)?

Comment 16 Eugen Dedu 2013-03-25 10:42:21 UTC
Any news, José?

Comment 17 Eugen Dedu 2013-04-02 08:29:00 UTC
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...

Comment 18 Fedora End Of Life 2013-07-04 02:29:51 UTC
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.

Comment 19 Fedora End Of Life 2013-08-01 08:29:57 UTC
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.