cannot find projectm in rhythmbox visualisations

[Kyle Martin]

Binary package hint: libvisual-projectm

OS: Ubuntu 8.10 amd64
libvisual-projectm:1.0-1+nmu1

this might be due to a compatability problem between the libvisual plugin and libprojectm, seeing as libprojectm is at version 1.2.0-1 and libvisual-projectm is at an older version, 1.0-1+nmu1

at any rate, when I open the visualizations tab in rhythmbox or amarok projectm is not available under visualization options. All the other options are there but not projectm. kind of sucks

[Kyle Martin (martikj2-deactivatedaccount)]

tried in amarok again and it shows up, now it just crashes out instead :-\

[Crosshair (will-e-carlson)]

Confirmed.

[Bálint Magyar (balintm)]

Confirmed on Intrepid beta upgraded from 8.04.1.

[Tim Besard (maleadt)]

Confirmed on latest Intrepid. I hope this gets libvisual-projectm an update, so this feature works!

[Dan Quade (danquade)]

Confirmed on 8.10 Intrepid.
Are there any known workarounds for this?

[aquatix (h-launchpad-aquariusoft-org)]

Confirmed here too on 8.10 Intrepid in Rhythmbox. Any news on workarounds or plain fixes? It'd be really nice to have it functioning :)

[Jonas Ådahl (jadahl)]

This issue still exists in 9.04. It's installed, but doesn't show up in Rhythmbox among the other libvisual plugins.

[Martyn Ranyard (ranyardm)]

Rhythmbox uses gstreamer for visualisation and therefore can't use any openGL-based visualisations :(

This is an upstream problem, gstreamer needs fixing, and/or libvisual using directly in rhythmbox, as amarok does, and/or projectm-pulse packaging, so we can at least fire up projectm standalone!

[Martyn Ranyard (ranyardm)]

This is nothing like a duplicate of the other bug! This is an intrepid and a Jaunty bug, the other bug report is about hardy, the bug is upstream (gstreamer needs openGL support) and a packaging bug (projectm-pulse is not packaged)

[Daniel Hahler (blueyed)]

Martyn, it does not matter if the bug is in Hardy, Intrepid or Jaunty, as long as it's the same bug.

Apart from that, if it's a different issue, then please unduplicate it (you can do this yourself) - I have not investigated myself.
You may create a need-packaging bug for the new package (and maybe assign it to the source package libprojectm?!).

Sorry for being ignorant, just trying to help a bit.. ;)