Ubuntu
sound-juicer package

Can not start sound-juicer

Bug #1062332 reported by Thomas Bechtold
80
This bug affects 18 people
Affects Status Importance Assigned to Milestone
sound-juicer (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

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)

Revision history for this message
Thomas Bechtold (toabctl) wrote :
Revision history for this message
Efrain Valles (effie-jayx) wrote :

I can confirm this bug I have the same issue

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

Thomas Bechtold (toabctl)
Changed in sound-juicer (Ubuntu):
status: New → Confirmed
Revision history for this message
ole.tange (n-launchpad-net-tange-dk) wrote :

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

Revision history for this message
ole.tange (n-launchpad-net-tange-dk) wrote :

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.

Revision history for this message
Meindert Frouws (m-j-frouws) wrote :

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

Revision history for this message
Meindert Frouws (m-j-frouws) wrote :

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

Revision history for this message
James Henstridge (jamesh) wrote :

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.

Revision history for this message
Meindert Frouws (m-j-frouws) wrote :

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

Revision history for this message
Jan Groenewald (jan-aims) wrote :

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

Revision history for this message
äxl (aexlf) wrote :

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 ...

Revision history for this message
Florian W. (florian-will) wrote :

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.

Revision history for this message
Peter Adolphs (futzilogik) wrote :

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

Revision history for this message
Donk (donk) wrote :

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

Revision history for this message
Daniel Stöckner (da567l) wrote :

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

Revision history for this message
bezolaam (vainio) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.