Bug 660001 - [abrt] pavucontrol-0.9.10-1.fc13: Process /usr/bin/pavucontrol was killed by signal 11 (SIGSEGV)
Summary: [abrt] pavucontrol-0.9.10-1.fc13: Process /usr/bin/pavucontrol was killed by ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pavucontrol
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:398cf4b024e10238df95f8312c0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-04 22:52 UTC by bill pemberton
Modified: 2011-06-28 10:10 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 10:10:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.55 KB, text/plain)
2010-12-04 22:52 UTC, bill pemberton
no flags Details

Description bill pemberton 2010-12-04 22:52:27 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: pavucontrol
component: pavucontrol
crash_function: StreamWidget::onMuteToggleButton
executable: /usr/bin/pavucontrol
kernel: 2.6.34.7-61.fc13.x86_64
package: pavucontrol-0.9.10-1.fc13
rating: 4
reason: Process /usr/bin/pavucontrol was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1291502800
uid: 500

How to reproduce
-----
1. tried to start something dealing with the pulse audio controller.
2.
3.

Comment 1 bill pemberton 2010-12-04 22:52:29 UTC
Created attachment 464781 [details]
File: backtrace

Comment 2 Bruce Barbour 2010-12-06 19:37:31 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
Playing around with sound system.  Changing volume control options in Kmix

Comment 3 fernando 2010-12-08 20:04:50 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Just start pavucontrol
2. I mutted on input channel
3. A few seconds later it crashed



Comment
-----
I crashes quite often, but I cannot tell a consistent set of steps to reproduce it.

Comment 4 Robert Lightfoot 2010-12-12 19:24:12 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Launch Chrome and Watch show from hulu
2. From ssh instance launch ffmpeg to do x11grab
3. launch pauvcontrol and try to mute sound

Comment 5 Stefan Hellermann 2010-12-15 00:07:23 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I tried to disable qemu from recording my microphone
2. I muted qemu in pavucontrol
3. boom :)

Comment 6 Mikkel L. Ellertson 2010-12-23 23:47:38 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Plug in the ADS InstantFM Music USB radio tuner.
2. Load the module-loopback module using "pactl load-module module-loopback source=alsa_input.usb-ADS_TECH_ADS_InstantFM_Music-00-Music.analog-stereo"
3. Try to use "pctrl unload-module module-loopback".
4. Remove the USB radio.
5. Later, install the USB radio again, and load module-loopback.
6. Get reverb effect.
7. Use PA Volume Control - discover multiput loopbacks and try and mute one of them.


Comment
-----
I was playing with my new USB radio. To get it to play under PA, I have to use the loopback module to feed the input from the radio back to the soundcard output. I was working on a script to do this, and launch Gnomeradio. It was supposed to remove the loopback module after I exited Gnomeradio. I was also building in error checking to exit if the module failed to load. I should probably used "pactl list | grep {device name}" instead, but this was a quick and dirty script - I could get fancy later.

I am not sure how, but I managed to get several loopbacks set up. When I tried to mute one of them, PA crashed. I had not checked to see if more then one copy of the module was loaded...

Comment 7 Mikkel L. Ellertson 2010-12-24 00:02:46 UTC
Well, I should have read the man page better - you have to use the module number, not the name. I had 10 copies of module-loopback loaded. I guess I can have more then one instance of the module so I can pipe more then one device to the output. Time to experiment some more...

Comment 8 Klemens Schragel 2011-03-08 22:29:53 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
I wish I'd know...
Pulseaudio goes for whatever reason at times mental when having Skype calls - Audio In- and Out don't work properly anymore.
When trying to change some configuration in PulseAudio Volumne Control the crash occures...

Comment 9 Antoine Martin 2011-04-18 19:13:44 UTC
Package: pavucontrol-0.9.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Clicked mute on a recording channel plugged to "Monitor of Analog ..."

Comment 10 Bug Zapper 2011-05-30 13:06:06 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 11 Bug Zapper 2011-06-28 10:10:38 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.


Note You need to log in before you can comment on or make changes to this bug.