Bug 1049267

Summary: [abrt] qmmp: qmmp killed by SIGSEGV
Product: [Fedora] Fedora Reporter: klaus
Component: qmmpAssignee: Karel Volný <kvolny>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: kvolny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2c59ac849aa43f373f50647f8be7aa76a8bb31d2
Whiteboard: abrt_hash:540372366ddba1f85650395624bd24bfe72d23d2
Fixed In Version: qmmp-0.7.4-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-31 04:23:32 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description klaus 2014-01-07 10:10:40 UTC 
Version-Release number of selected component:
qmmp-0.7.2-1.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        /usr/bin/qmmp
executable:     /usr/bin/qmmp
kernel:         3.12.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 ??
 #1 StateHandler::dispatch at /usr/src/debug/qmmp-0.7.2/src/qmmp/statehandler.cpp:65
 #2 OutputWriter::dispatch at /usr/src/debug/qmmp-0.7.2/src/qmmp/outputwriter.cpp:256
 #3 OutputWriter::status at /usr/src/debug/qmmp-0.7.2/src/qmmp/outputwriter.cpp:404
 #4 OutputWriter::run at /usr/src/debug/qmmp-0.7.2/src/qmmp/outputwriter.cpp:312
 #5 QThreadPrivate::start at thread/qthread_unix.cpp:338
Comment 1 klaus 2014-01-07 10:10:44 UTC 
Created attachment 846549 [details]
File: backtrace
Comment 2 klaus 2014-01-07 10:10:46 UTC 
Created attachment 846550 [details]
File: cgroup
Comment 3 klaus 2014-01-07 10:10:48 UTC 
Created attachment 846551 [details]
File: core_backtrace
Comment 4 klaus 2014-01-07 10:10:54 UTC 
Created attachment 846552 [details]
File: dso_list
Comment 5 klaus 2014-01-07 10:10:57 UTC 
Created attachment 846553 [details]
File: environ
Comment 6 klaus 2014-01-07 10:11:00 UTC 
Created attachment 846554 [details]
File: exploitable
Comment 7 klaus 2014-01-07 10:11:01 UTC 
Created attachment 846555 [details]
File: limits
Comment 8 klaus 2014-01-07 10:11:05 UTC 
Created attachment 846556 [details]
File: maps
Comment 9 klaus 2014-01-07 10:11:07 UTC 
Created attachment 846557 [details]
File: open_fds
Comment 10 klaus 2014-01-07 10:11:09 UTC 
Created attachment 846558 [details]
File: proc_pid_status
Comment 11 klaus 2014-01-07 10:11:11 UTC 
Created attachment 846559 [details]
File: var_log_messages
Comment 12 Fedora Update System 2014-01-17 14:21:40 UTC 
qmmp-0.7.4-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/qmmp-0.7.4-1.fc20
Comment 13 Karel Volný 2014-01-17 14:25:59 UTC 
the output code got refactored, I believe this bug shouldn't appear in the new version I've just submitted - please test, see the link in comment #12
Comment 14 Fedora Update System 2014-01-18 04:22:33 UTC 
Package qmmp-0.7.4-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing qmmp-0.7.4-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1043/qmmp-0.7.4-1.fc20
then log in and leave karma (feedback).
Comment 15 Karel Volný 2014-01-30 11:27:31 UTC 
*** Bug 1058937 has been marked as a duplicate of this bug. ***
Comment 16 Fedora Update System 2014-01-31 04:23:32 UTC 
qmmp-0.7.4-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.