After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 509856 - Unable to start visualization: Failed to link new visual effect into the GStreamer pipeline
Unable to start visualization: Failed to link new visual effect into the GStr...
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Plugins (other)
0.11.x
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-16 09:49 UTC by Joshua Henderson
Modified: 2018-05-24 13:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
attached crash data (3.97 KB, text/plain)
2010-08-29 22:49 UTC, Hussam Al-Tayeb
Details
crash on exit if I try to exit rhythmbox when ui is frozen (21.16 KB, text/plain)
2010-08-29 22:55 UTC, Hussam Al-Tayeb
Details
while switching visualizations (8.46 KB, text/plain)
2010-08-29 23:09 UTC, Hussam Al-Tayeb
Details
using thread apply all bt. (22.22 KB, text/plain)
2010-08-29 23:15 UTC, Hussam Al-Tayeb
Details

Description Joshua Henderson 2008-01-16 09:49:34 UTC
Please describe the problem:
The following error occurs when attempting to change from the GOOM visualization to the Monoscope visualization.

"Unable to start visualization
Failed to link new visual effect into the GStreamer pipeline"

Along with this, the music stops and Rhythmbox freezes after I click "Close".

Steps to reproduce:
1. Open up Rhythmbox and start playing some music.
2. Open up Visualizations from the View menu.
3. Check the current visualization is on GOOM, and change to Monoscope.


Actual results:
The music stops and a popup with the error:

"Unable to start visualization
Failed to link new visual effect into the GStreamer pipeline"

is displayed.

Expected results:
The visualization is changed to Monoscope.

Does this happen every time?
Yes, on the computer I am currently using (Running Ubuntu Gutsy). I have not tried this on other computers, though many times on this one.

Other information:
When Rhythmbox is restarted (it freezes after I click Close, so I have to use killall to close it), the Monoscope visualization is displayed when visualizations is opened, so it does change when the program is restarted.
Comment 1 Hussam Al-Tayeb 2008-04-30 03:16:17 UTC
confirmed here under rhythmbox svn trunk and gst 0.10.19
Comment 2 Hussam Al-Tayeb 2010-03-01 23:06:09 UTC
This bug still happens in 0.12.7 with latest gstreamer
In addition, I see this warning in the terminal 
(rhythmbox:8585): GLib-GObject-WARNING **: invalid cast from `GstAudioSinkRingBuffer' to `GstElement'
Comment 3 Hussam Al-Tayeb 2010-07-04 14:31:34 UTC
still happens in rhythmbox 0.13.

best way to reproduce it is start visualization with chosen visualization 'monoscope' then switch to 'synaesthesia' or the opposite.
switch from one of those to the other always triggers the erorr bug for me.

gstreamer 0.10.29
gstreamer-bad 0.10.19
gstreamer-base 0.10.29
gstreamer-ffmpeg 0.10.10
gstreamer-good 0.10.23
gstreamer-python 0.10.18
gstreamer-ugly 0.10.15
Comment 4 Hussam Al-Tayeb 2010-08-29 22:49:52 UTC
Created attachment 169023 [details]
attached crash data

attached crash data using gdb.
Comment 5 Hussam Al-Tayeb 2010-08-29 22:55:01 UTC
Created attachment 169024 [details]
crash on exit if I try to exit rhythmbox when ui is frozen

crash on exit if I try to exit rhythmbox when ui is frozen
Comment 6 Hussam Al-Tayeb 2010-08-29 23:09:24 UTC
Created attachment 169025 [details]
while switching visualizations
Comment 7 Hussam Al-Tayeb 2010-08-29 23:15:51 UTC
Created attachment 169026 [details]
using thread apply all bt.
Comment 8 GNOME Infrastructure Team 2018-05-24 13:06:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/496.