Can not start sound-juicer

[Thomas Bechtold]

When I try to start sound-juicer (from unity launcher or from command line) I get a GtkMessageDialog with:

Could not start Sound Juicer

Reason: The plugin necessary for file access was not found.
Please consult the documentation for assistance.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: sound-juicer 3.4.0-3
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Fri Oct 5 16:24:17 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423.2)
SourcePackage: sound-juicer
UpgradeStatus: Upgraded to quantal on 2012-06-23 (103 days ago)

[Efrain Valles (effie-jayx)]

I can confirm this bug I have the same issue

It has no verbose mode to check more details on the problem

[ole.tange (n-launchpad-net-tange-dk)]

tracefile -n sound-juicer

gives this as the last non-existing file before the pop-up box:

/home/tange/.config/ibus/bus/94b41d05e427f639453109520000000f-unix-0

[ole.tange (n-launchpad-net-tange-dk)]

I think these are the issue:

/usr/local/lib/libavcodec.so.52
/usr/local/lib/libavformat.so.52
/usr/local/lib/libpostproc.so.51
/usr/local/lib/libswscale.so.0

They are all installed in newer version in Quantal.

[Meindert Frouws (m-j-frouws)]

Even a fresh install of ubuntu 12.10 did not solve the problem.
On my laptop I have no problems with sound juicer.

[Meindert Frouws (m-j-frouws)]

To make things more complicated to me:
I have two user accounts on my computer and sound juicer behaves normal at the other account.

[James Henstridge (jamesh)]

The error seems to come from this part of the code:

http://git.gnome.org/browse/sound-juicer/tree/libjuicer/sj-extractor.c#n686

It is trying to create a "giosink" GStreamer element.

This is a standard element, but it didn't seem to be showing up in the output of gst-inspect-0.10. The library implementing the element was present, so I guess something got confused along the way.

I was able to fix the problem by issuing the following two commands:

    rm ~/.gstreamer-0.10/registry.*.bin
    gst-inspect-0.10 > /dev/null

This should cause all the GStreamer plugins to be rescanned to find out what elements they implement, and was enough to make giosink available again.

I've got no idea what would have caused the problem though.

[Meindert Frouws (m-j-frouws)]

OK. I just deleted the .gstreame-0.10 map and that did the trick.

[Jan Groenewald (jan-aims)]

Confirmed on Ubuntu 12.04 64bit. This used to work fine before, some update must've done this.

[äxl (aexlf)]

James solution works.
Though I had this problem on Debian Squeeze (oldstable) with sound-juicer 2.28.2-3 ...
Happened after I accidentaly rm -fr in /home. So only hidden files were spared. I don't know if debugging with --brasero-media-debug is useful.
diff'ing broken and working registry.*.bin ... gives me a 1 MB file ...

[Florian W. (florian-will)]

In Ubuntu Trusty I did this to fix the issue (seems like the new version uses gstreamer 1.0 instead of 0.10):
 rm ~/.cache/gstreamer-1.0/registry.x86_64.bin

The file name might be a little different if you're not on x86_64.

[Peter Adolphs (futzilogik)]

Thanks, Florian W., rm ~/.cache/gstreamer-1.0/registry.x86_64.bin also fixed this for me on Ubuntu 14.04.

[Donk (donk)]

Thanks, Florian
Fix in comment 11 solve the bug on Ubuntu 14.4

[Daniel Stöckner (da567l)]

Comment 11 also fixed it for me on Trusty (updated from Precise)! Thanks Florian!

[bezolaam (vainio)]

Deleting ~/.cache/gstreamer-1.0/registry.*.bin fixes the problem