Bug 537422

Summary: [abrt] crash detected in pulseaudio-0.9.19-2.fc12
Product: [Fedora] Fedora Reporter: AkhaBorz <postVictor>
Component: pulseaudioAssignee: Lennart Poettering <lpoetter>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: lkundrak, lpoetter, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:93b3f9e729610e2dd9edd804c07a57137688230c
Fixed In Version: 0.9.21-4.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-08 22:48:20 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

Description AkhaBorz 2009-11-13 15:28:30 UTC
abrt detected a crash.

Attached file: backtrace
cmdline: /usr/bin/pulseaudio --start --log-target=syslog
component: pulseaudio
executable: /usr/bin/pulseaudio
kernel: 2.6.31.5-127.fc12.i686.PAE
package: pulseaudio-0.9.19-2.fc12
rating: 4
reason: Process was terminated by signal 6

Comment 1 AkhaBorz 2009-11-13 15:28:33 UTC
Created attachment 369446 [details]
File: backtrace

Comment 2 Lennart Poettering 2010-01-08 22:48:20 UTC
Fixed now upstream. Will update F12 packages soon.

http://git.0pointer.de/?p=pulseaudio.git;a=patch;h=e7d9f891e2a8e6b670098b80315ca1f0010c35ca

Comment 3 Fedora Update System 2010-01-15 01:46:43 UTC
pulseaudio-0.9.21-3.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/pulseaudio-0.9.21-3.fc12

Comment 4 Fedora Update System 2010-01-18 01:24:17 UTC
pulseaudio-0.9.21-4.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/pulseaudio-0.9.21-4.fc12

Comment 5 Fedora Update System 2010-01-26 01:04:16 UTC
pulseaudio-0.9.21-4.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.