gstreamer can't be started

[Ralph]

Whenever I try to start an application depending on gstreamer, I get the following error:
Could not initialize GStreamer: Error re-scanning registry , child terminated by signal

This means that for example gnome-sound-properties, gnome-settings-daemon don't work.

I'm running feisty on a G3 ibook.

Running strace gnome-sound-properties I get:
(gnome-sound-properties:15408): libgnomevfs-WARNING **: Cannot load module `/usr/lib/gnome-vfs-2.0/modules/libmapping.so' (/usr/lib/gnome-vfs-2.0/modules/libmapping.so: cannot open shared object file: No such file or directory)
child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x3003cc68) = 15408
close(4) = 0
read(3, "", 1) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
close(3) = 0
waitpid(15408, NULL, 0) = 15408
open("/usr/share/locale-langpack/en/LC_MESSAGES/gstreamer-0.10.mo", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=17144, ...}) = 0
mmap(NULL, 17144, PROT_READ, MAP_PRIVATE, 3, 0) = 0x30193000
close(3) = 0
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x30198000
write(1, "Could not initialize GStreamer: "..., 88Could not initialize GStreamer: Error re-scanning registry , child terminated by signal
) = 88
exit_group(1) = ?
Process 15407 detached

[peter76 (pf-moll)]

Having same problem here on iBook g3 900...

At login I get an error about gnome-settings-daemon not being able to load, when I run it from the CL I get:

peter@ibook:~$ gnome-settings-daemon
0:00:02.768864000 7344 0x1003d110 ERROR GST_INIT gst.c:832:ensure_current_registry_forking: child did not exit normally, terminated by signal
[1171107637,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationCould not initialize GStreamer: Error re-scanning registry , child terminated by signal

Also get an error like this when I start try to run Totem from the CL. Don't get these errors on a pentium 111, so is probably ppc specific

[Sebastien Bacher (seb128)]

That looks like similar to bug #72814, marking duplicate, feel free to reopen if you disagree