Bug 643296
Summary: | racy crashes across all applications | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Kratochvil <jan.kratochvil> | ||||
Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 13 | CC: | lkundrak, lpoetter, mcepl, mcepl, mschmidt, pablomg+fedora | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | pulseaudio-0.9.21-6.fc12 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-11-21 22:01:24 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
Jan Kratochvil
2010-10-15 08:11:33 UTC
According to: * http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers * Is PulseAudio dead? http://lists.fedoraproject.org/pipermail/devel/2010-August/140095.html * http://pulseaudio.org/ticket/859 filed on 2010-09-29 (2+ weeks now) * pending commit request since 2010-10-15 (two days ago) https://admin.fedoraproject.org/pkgdb/acls/name/pulseaudio starting the nonresponsive package maintainer process - the Outline item 1. Requesting application of the fix, first retry attempt according to: Policy for nonresponsive package maintainers Requesting application of the fix, second retry attempt according to: Policy for nonresponsive package maintainers Policy for nonresponsive package maintainers process has been completed after the 3 weeks. Going to verify the status with Lennart Poettering and make a post to fedora-devel. I can't reproduce the bug with either Firefox 3.6, Chromium or Firefox4. Versions used : pulseaudio-0.9.21-6.fc13.x86_64 firefox-3.6.12-1.fc14.x86_64 firefox4-4.0-0.12.beta7.fc14.remi.x86_64 chromium-8.0.560.0-2.fc14.x86_64 Reproducible also on: pulseaudio-0.9.21-6.fc13.x86_64 firefox-3.6.12-1.fc13.x86_64 But I do not have F14 box with audio ready now. It may be related to the number of CPU cores (reproducible on my i7-920=8x but even on my T7200=2x). And reproducible also on single-core AMD XP 2600+ (F13 i686). pulseaudio-0.9.21-7.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/pulseaudio-0.9.21-7.fc13 pulseaudio-0.9.21-7.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/pulseaudio-0.9.21-7.fc14 pulseaudio-0.9.21-6.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/pulseaudio-0.9.21-6.fc12 pulseaudio-0.9.21-7.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. Matěj, did you make sure the patch gets applied upstream? Also, we might as well just configure with "--disable-legacy-runtime-dir", because the last pulseaudio version using the legacy path was 0.9.11 which was in the Fedora 9 timeframe. (In reply to comment #12) > did you make sure the patch gets applied upstream? I have been assured by the maintainer that he is going to make upstream release incorporating what's appropriate from Fedora patches. > Also, we might as well just configure with "--disable-legacy-runtime-dir", > because the last pulseaudio version using the legacy path was 0.9.11 which was > in the Fedora 9 timeframe. I don't know, I will rather leave it to the upstream maintainer to decide. I was here just fixing this stupid bug. pulseaudio-0.9.21-7.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. pulseaudio-0.9.21-6.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |