Version-Release number of selected component: jack-audio-connection-kit-example-clients-1.9.9.5-3.fc20 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: jack_server_control crash_function: Jack::JackServer::Start executable: /usr/bin/jack_server_control kernel: 3.11.0-0.rc7.git1.2.fc21.x86_64 runlevel: unknown uid: 1000 var_log_messages: Aug 28 23:53:26 fed19raw abrt[5607]: Saved core dump of pid 5603 (/usr/bin/jack_server_control) to /var/tmp/abrt/ccpp-2013-08-28-23:53:26-5603 (30437376 bytes) Truncated backtrace: Thread no. 1 (2 frames) #0 Jack::JackServer::Start at ../common/JackServer.cpp:183 #1 jackctl_server_start at ../common/JackControlAPI.cpp:1064 Potential duplicate: bug 770347
Created attachment 791616 [details] File: backtrace
Created attachment 791617 [details] File: cgroup
Created attachment 791618 [details] File: core_backtrace
Created attachment 791619 [details] File: dso_list
Created attachment 791620 [details] File: environ
Created attachment 791621 [details] File: exploitable
Created attachment 791622 [details] File: limits
Created attachment 791623 [details] File: maps
Created attachment 791624 [details] File: open_fds
Created attachment 791625 [details] File: proc_pid_status
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.