GNOME Bugzilla – Bug 666980
Audio/Video stops working GStreamer problem: "Element bin1 already has parent" also qjackctl issue
Last modified: 2012-02-03 12:33:07 UTC
I am using Fedora12 (with the ccrma kernel for those familiar) for general purposes, including listening to music and watching video (mpg, mp3, ogg, wav) and also for music recording, using qjackctl, envy24control, ardour etc. I play mpg/mp3/ogg etc. thru the motherboard sound, but do the jack/ardour stuff thru an m-audio Delta 1010 8-channel interface which connects with a pci card. For years, it all worked fine. I had a recent crash, seemingly caused by forgetting to close jack before trying other video, altho that goof usually only freezes media, but doesn't crash the system. I recovered from the crash (using fsck as directed) and at first everything seemed fine, at least mpg/mp3/ogg playback. But then that stopped and jack doesn't work either. I'll describe the problems in 2 groups: 1) mpg/mp3/ogg/wav problems video plays back accelerated, not smoothly. no sound. this happens with Movie Player, audacity and rhythmbox, and also while streaming using Rhapsody.com. In rhythmbox, I also get this error: GStreamer-WARNING **: Element bin1 already has parent not sure if gstreamer itself is the culprit, or if it is caused by alsa or something else. To be clear: i get these problems even when jack is NOT running. I have rebooted and shut down many times, etc. Can't find solution by searches online (yet). 2) jack/ardour/m-audio Delta 1010 interface. Envy24Control sees the m-audio interface, but the light doesn't come on the unit. Not sure if this is related to a communication problem or independent hardware failure. It sounds like the latter, but I have read online that the light only comes on for this unit when it is communicating properly. Since I am having the other problems and it all started from a crash while using jack, I hope that this bug and the other bug are related. but i have no idea. THANK YOU VERY MUCH. Any help appreciated.
Fedora 12 is ancient, can you reproduce these issues with the latest Fedora release?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!