| Summary: | [abrt] pavucontrol-0.9.10-1.fc13: Process /usr/bin/pavucontrol was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Misha Shnurapet <shnurapet> | ||||||||||
| Component: | pavucontrol | Assignee: | Lennart Poettering <lpoetter> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | adrin.jalali, arikomagik, a.thanabalasingam, bdm, brian, davematel, dkovalsk, ld.daniel, lpoetter, mreuroguy, narf, ryan, tech, u5afe | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:99cae03c5f6ee38464a73a477c5cf4acff5fa76f | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-08-01 03:05:00 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Misha Shnurapet
2011-05-07 14:18:51 UTC
Created attachment 497535 [details]
File: backtrace
Package: pavucontrol-0.9.10-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Was using skype and changing skype's recording source Package: pavucontrol-0.9.10-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Clicked on the mute button for a remote pulseaudio sound source. Package: pavucontrol-0.9.10-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I canceled pavucontrol Package: pavucontrol-0.9.10-2.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- try to mute internal mic. Package: pavucontrol-0.9.10-1.fc13 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I put the sound up to 100% then it jumps back down to 21% 2. 3. I selected to mute the output audio of a SignaLink USB radio interface, the pavucontrol crashed. backtrace_rating: 4 Package: pavucontrol-0.9.10-2.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Created attachment 559287 [details]
File: backtrace
*** Bug 678953 has been marked as a duplicate of this bug. *** *** Bug 702829 has been marked as a duplicate of this bug. *** *** Bug 767821 has been marked as a duplicate of this bug. *** playing with the mic setting on skype backtrace_rating: 4 Package: pavucontrol-0.9.10-2.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Created attachment 579801 [details]
File: backtrace
Try to adjust the microfone volume when Skype is on with "auto volume" enabled. backtrace_rating: 4 Package: pavucontrol-0.9.10-2.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Created attachment 581434 [details]
File: backtrace
Still reproducible on F16, bumping release. And reproducible on both i686 (original reported) and x86_64 (me). On the Advanced tab in the audio menu, select vypvdvyuschem built-in microphone. Nearby there is a button that would drown out the sound immediately after pressing the program crashes. Error is easily repeated. Established this program when trying to understand why the built-in microphone is not working. And did not understand. backtrace_rating: 4 Package: pavucontrol-0.9.10-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) just clicked... backtrace_rating: 4 Package: pavucontrol-0.9.10-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) I was looking at the display of audio level in and pressed the button to mute the sound. The app crashed. backtrace_rating: 4 Package: pavucontrol-0.9.10-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Can we have the Version(s): of this bug updated since there are a number of reports on FC17? Done. Has this bug been fixed? Does it still exist in the lasted version? (In reply to comment #23) > Has this bug been fixed? Does it still exist in the lasted version? As I reported in comment #21, it was seen on FC17 and there has been no indication that it has been even looked at since, so I would guess it's still there. That's why I requested that the Version(s): field be updated to 17. If by 19-20 no new reports have been added, it can get closed out as EOL per usual. I agree. Anything to keep it alive until someone responsible solves his or her errors. 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. 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. |