abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/pulseaudio --start component: pulseaudio executable: /usr/bin/pulseaudio global_uuid: c0182f44afc7aa4712986e3acc34aa75ba70e657 kernel: 2.6.33.2-47.fc13.x86_64 package: pulseaudio-0.9.21-6.fc13 rating: 4 reason: Process /usr/bin/pulseaudio was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) comment ----- What I did: 1)mplayer playing 2ch radio on terratec aureon mk2 (stereo duplex) 2)changed aureon to 4.1 3)unlock channels and tried to set front channel to 0 %, during slider movement it crashed
Created attachment 407165 [details] File: backtrace
Created attachment 407166 [details] var log messages
Package: pulseaudio-0.9.21-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.mplayer -ao pulse playing internet radio stream on usb soundcard 2.pavucontrol 3.system volume from 0 to 100 % 4.change volume of integrated soundcard Comment ----- I'll check if I can reproduce. Log does not seem to contain anything interesting: Apr 26 21:55:11 nbone pulseaudio[1984]: ratelimit.c: 481 events suppressed Apr 26 22:02:25 nbone pulseaudio[1984]: ratelimit.c: 1 events suppressed Apr 26 22:02:28 nbone pulseaudio[1984]: sink-input.c: Assertion 'tchunk.memblock' failed at pulsecore/sink-input.c:671, function pa_sink_input_peek(). Aborting.
I was not able to reproduce intentionally
Package: pulseaudio-0.9.21-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Not Sure this will reproduce the Problem 1.i opened an MP3 File using FC13 Movie Player the File worked briefly then i started some"hiss" from the Speakers 2.closed it then tried to reopen using gnome player which also failed to open the file 3.executed the command kill on the "PID" values resulted from "ps -A |grep player" , the values where for gnome-player and mplayer 4- tried to reopen the File again using movie player "i guess" and a crash notification of pulseaudio appeared 5-i followed the steps presented to me by abrt
(In reply to comment #5) > Package: pulseaudio-0.9.21-6.fc13 > Architecture: i686 > OS Release: Fedora release 13 (Goddard) > > > How to reproduce > ----- > Not Sure this will reproduce the Problem > 1.i opened an MP3 File using FC13 Movie Player the File worked briefly then i > started to hear some"hiss" from the Speakers > 2.closed it then tried to reopen using gnome player which also failed to open > the file > 3.executed the command kill on the "PID" values resulted from "ps -A |grep > player" , the values where for gnome-player and mplayer > 4- tried to reopen the File again using movie player "i guess" and a crash > notification of pulseaudio appeared > 5-i followed the steps presented to me by abrt
Package: pulseaudio-0.9.21-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Listen to Kraftwerk or other music in Spotify 2.Change the volume of the output device (Sennheiser USB headset in my case) in pavucontrol 3.pulseaudio crashes and pavucontrol gives an error message that it's unable to connect to pulseaudio Comment ----- This is all done in KDE
pa_context_set_sink_volume_by_index() failed: Bad state is the error message pavucontrol gives me.
Package: pulseaudio-0.9.21-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- I've opened video with 5.1 sound using smplayer and then changed volume using pavucontrol
Package: pulseaudio-0.9.21-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.start up computer, log in, wait for desktop environment (kde) to start padevchooser 2.trying for the first time to adjust a volume slider causes pulseaudio to crash and padevchooser to freeze 3.after manually killing padevchooser and restarting it, it works fine Comment ----- See above. This is 100% reproducible on that one machine, for quite some time now
*** Bug 618715 has been marked as a duplicate of this bug. ***
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
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.