[Gstreamer-bugs] [Bug 142850] - GST-Register didn't find any plugins

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=142850
GStreamer | gstreamer (core) | Ver: 0.8.1





------- Additional Comments From rbultje at ronald.bitfreak.net  2004-05-26 11:40 -------
I'll try to explain again.

I understand that you guys are having difficulties. I do not know what the
problem is (obviously - else I'd have fixed it already). However, it is not
absolutely sure that the problem is related to GStreamer. I *know* and *see*
that gst-register fails for you guys, but that's merely a *symptom*. I don't
know the *cause* yet.

Now, in order to find the cause, there will have to be some debugging,
trying-out-things, etc. It seems that this is reiser4-related, but it's also
reproduceable on loopback-ext2 devices (looped back to what base file system,
btw?). I see reports here from various distributions that have a variety of
packages/kernel versions installed, none of which is in any way reproduceable by
me, and *that* is why I am not directly able to provide any direct help here. In
order to fix it, I need to be able to reproduce it first.

Now, how can you guys help in fixing this. It requires some programming
knowledge. I want to ask you to add various g_print()s in places in
gstreamer/tools/gst-register.c to see what code is exactly being executed. A
"gst-register --gst-debug-level=5 &> log" would also help. Add g_print()s to the
dir_list for()-loop in main() and to the spawn_in_dir() function. If you don't
know what any of this means, then ask it on the Gentoo fora or on the Slackware
fora.

It would also help if you can reproduce this on a variety of kernel versions
(2.6.x, 2.4.x) or even base systems (preferrably something standard, like Suse
or Fedora). That helps in pinning down the problem and we might be able to help
in solving the problem then.

Hope this helps.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.