Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1867 - sound-juicer cannot find any encoder

Attached to Project: Arch Linux
Opened by Nikos Kouremenos (zeppelin) - Wednesday, 01 December 2004, 22:15 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 01 December 2004, 22:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I used to work with OGGs in my box.
$whereis oggenc
oggenc: /usr/bin/oggenc /usr/man/man1/oggenc.1.gz
$sound-juicer
will inform me that it cannot find the encodings. I see prefrences and I can select only WAVE. I did that to test wtf was going on

$ sound-juicer

(sound-juicer:4003): GStreamer-CRITICAL **: file gstpad.c: line 3660 (gst_pad_template_new): assertion `caps != NULL' failed

(sound-juicer:4003): GStreamer-CRITICAL **: file gstelementfactory.c: line 368 (__gst_element_factory_add_pad_template): assertion `templ != NULL' failed

** (sound-juicer:4003): CRITICAL **: how to remove plugins?

(sound-juicer:4003): GStreamer-CRITICAL **: Factory for `vorbisenc' has no type. This probably means the plugin wasn't found because the registry is broken. The plugin GStreamer was looking for is named 'vorbis' and is expected in file '/opt/gnome/lib/gstreamer-0.8/libgstvorbis.so'. The registry for this plugin is located at '/home/nk/.gstreamer-0.8/registry.xml'

** (sound-juicer:4003): CRITICAL **: how to remove plugins?

(sound-juicer:4003): GStreamer-CRITICAL **: Factory for `lame' has no type. This probably means the plugin wasn't found because the registry is broken. The plugin GStreamer was looking for is named 'lame' and is expected in file '/opt/gnome/lib/gstreamer-0.8/libgstlame.so'. The registry for this plugin is located at '/home/nk/.gstreamer-0.8/registry.xml'

** (sound-juicer:4003): CRITICAL **: how to remove plugins?

(sound-juicer:4003): GStreamer-CRITICAL **: Factory for `flacenc' has no type. This probably means the plugin wasn't found because the registry is broken. The plugin GStreamer was looking for is named 'flac' and is expected in file '/opt/gnome/lib/gstreamer-0.8/libgstflac.so'. The registry for this plugin is located at '/home/nk/.gstreamer-0.8/registry.xml'

** (sound-juicer:4003): CRITICAL **: how to remove plugins?

(sound-juicer:4003): GStreamer-CRITICAL **: Factory for `cdparanoia' has no type. This probably means the plugin wasn't found because the registry is broken. The plugin GStreamer was looking for is named 'cdparanoia' and is expected in file '/opt/gnome/lib/gstreamer-0.8/libgstcdparanoia.so'. The registry for this plugin is located at '/home/nk/.gstreamer-0.8/registry.xml'
This CD was not found.

eventhough I get the tracks listed I get this and it shut downs. I have the latest gst-plugins, maybe that is the case here.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 02 March 2005, 07:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems all profiles work again now flac has been fixed.
Comment by Jan de Groot (JGC) - Wednesday, 01 December 2004, 22:49 GMT
What gst-plugins version and what sound-juicer version?

It seems like you upgraded to the new gst-plugins version in testing, but didn't take sound-juicer from it. It's sufficient to install the required gst-plugins packages (sound-juicer in testing depends on them).
Comment by Nikos Kouremenos (zeppelin) - Friday, 03 December 2004, 09:37 GMT
sudo pacman -Sy sound-juicer
(I have testing)
sound-juicer-0.5.14-2: is up to date. Upgrade anyway? [Y/n] n

sudo pacman -S gst-plugins
:: gst-plugins-0.8.6-1: is up to date. Upgrade anyway? [Y/n]

I still get:
Could not start Sound Juicer

Reason: The plugin necessary for CD access was not found.
Please consult the documentation for assistance.
Comment by Jan de Groot (JGC) - Friday, 03 December 2004, 15:06 GMT
Removing your user's .gstreamer-0.8 directory should be fine.
You're the first one that I see who has a local gstreamer register with entries in it.

gst-plugins get registered now on the system itself somehow using postinstall scripts.
The "how to remove plugins" stuff is from gstreamer which thinks it loaded a plugin available in its registry and then thinks it unloads the plugin because it couldn't load it (gstreamer doesn't support plugin unloading yet)

Comment by Nikos Kouremenos (zeppelin) - Saturday, 04 December 2004, 11:23 GMT
ok I dont get the problems now in the console. I get the dialog that inform me

Could not start Sound Juicer

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

note that in the main window I can see the duration of the tracks and it is correct. still I have to click OK and it exits
Comment by Jan de Groot (JGC) - Sunday, 05 December 2004, 13:56 GMT
Could you show me the output of
"pacman -Q | grep -e gst -e sound-juicer"

I don't think you have all required plugins somehow.
Comment by Nikos Kouremenos (zeppelin) - Sunday, 05 December 2004, 15:37 GMT
hmm, so gstreamer-plugins is a missing dep (ok this is group) for sound-juicer?

previously I had
pacman -Q | grep -e gst -e sound-juicer
gst-plugins 0.8.6-1
gst-plugins-cdparanoia 0.8.6-1
gst-plugins-faad 0.8.6-1
gst-plugins-flac 0.8.6-1
gst-plugins-gnomevfs 0.8.6-1
gst-plugins-lame 0.8.6-1
gst-plugins-mad 0.8.6-1
gst-plugins-ogg 0.8.6-1
gst-plugins-vorbis 0.8.6-1
gstreamer 0.8.7-2
sound-juicer 0.5.14-2

btw, i also had this issue:

installing gst-plugins-xine... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
--
i rm it , pacman -R gst-plugin-xine then pacman -S it

I know have them ALL BUT STILL DOESNOT WORK

run sound-juicer, get a dialog about non valid encoders. I press OK it closes. Then re-run it and again a new dialog that CD plugins are not there. (note that the CD tracks are even read by freedb!)
Comment by Nikos Kouremenos (zeppelin) - Sunday, 05 December 2004, 15:39 GMT
I also get the segfaul on the loading plugin file when pacman -S gst-plugins-xine, eventhough I rm the file

[i have gxine, and xine] this is another bug I guess :)
Comment by Jan de Groot (JGC) - Sunday, 05 December 2004, 16:13 GMT
I just uploaded a new version to testing, it fixes a problem where external libraries are not linked into the various plugins. Please test them and see if it fixes your problem.
Comment by Nikos Kouremenos (zeppelin) - Sunday, 05 December 2004, 20:44 GMT
upgrading gst-plugins-1394... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-a52dec... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-aalib... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-arts... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-audiofile... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-cdaudio... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-cdparanoia... done.


ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-dv... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-dvd... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-esd... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-faac... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-faad... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-flac... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-gdkpixbuf... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-gnomevfs... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-hermes... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-jack... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-ladspa... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-lame... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-mad... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
upgrading gst-plugins-mikmod... done.

ERROR: Caught a segmentation fault while loading plugin file:
/opt/gnome/lib/gstreamer-0.8/libgstxine.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.

and can't w8 for all hte plugins to tell me the same message
Comment by Jan de Groot (JGC) - Sunday, 05 December 2004, 21:04 GMT
maybe you should upgrade the xine plugin first before upgrading the others. Every postinstall script of every plugin will run gst-register and will segfault on your b0rken gst-plugins-xine that's about to be upgraded as last.
When the xine plugin is upgraded as last everything should be fine though, since the postinstall script of every plugin is in fact the same.
Comment by Nikos Kouremenos (zeppelin) - Sunday, 05 December 2004, 23:59 GMT
in the first setence you say first. in the last you say last
I tried the last. I removed it and then re-install, I still get the segfault, so I shouldn't try sound-juicer.

then removed all the group (gstreamer-plugins)
then tried to add gst-plugins-xine
but got the same segfault
Comment by Jan de Groot (JGC) - Monday, 06 December 2004, 07:10 GMT
Somehow the xine plugin is broken. I think I'll remove it since it was not in gst-plugins before. The gstreamer developers don't recommend it too, so it's not very useful to have if it's segfaulting.

Try to remove all your gstreamer plugins, then remove your ~/.gstreamer-0.8 and reinstall sound-juicer and its required dependencies.
Comment by Nikos Kouremenos (zeppelin) - Monday, 06 December 2004, 15:23 GMT
ok, now it works ok.
I'm glad I prevented such problems for day2day al users :)
thank you
Comment by Judd Vinet (judd) - Tuesday, 22 February 2005, 18:26 GMT
Re-opened by request from Nikos Kouremenos
Comment by Nikos Kouremenos (zeppelin) - Wednesday, 23 February 2005, 17:18 GMT
I hope Jan will find the solution once again..
it asks me to quit or change profile
and I can't have any encoders [i Love ogg]
Comment by Jan de Groot (JGC) - Wednesday, 23 February 2005, 17:50 GMT
What happens when you run gnome-audio-profiles-properties? There should be 3 profiles: CD Quality Lossless, CD Quality Lossy, Voice.
If these 3 aren't there, please reinstall gnome-media.

One problem I know of is that gst-plugins-flac is broken because the flac library is broken too. I will rebuild gst-plugins-flac once dorphell fixes the flac library.
Comment by Jan de Groot (JGC) - Wednesday, 23 February 2005, 17:53 GMT
Yes, found the problem: gst-plugins-flac needs a rebuild. When you start sound-juicer, it tells the current selected profile (which uses flac) is not available and forces you to load another one (which can be lossy: OGG).
Comment by Nikos Kouremenos (zeppelin) - Wednesday, 23 February 2005, 18:35 GMT
I have 3 profiles btw
Comment by Nikos Kouremenos (zeppelin) - Wednesday, 23 February 2005, 18:44 GMT
and yes you're right :)

Loading...