After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 120811 - Installation troubles
Installation troubles
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.6.3
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-27 06:41 UTC by Artur Flinta
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description Artur Flinta 2003-08-27 06:41:13 UTC 
Hi!

When installing gst-plugins via rpm in %postinstall gst-register is called,
but it is calle from root account. In this case gstreamer is working
incorrectly, ie: rhythmbox 0.5.2 with gst bckend:

(rhythmbox:25533): GStreamer-CRITICAL **: Factory for `mad' has no type
 
(rhythmbox:25533): GStreamer-CRITICAL **: file gstbin.c: line 459
(gst_bin_add): assertion `element != NULL' failed
 
(rhythmbox:25533): GStreamer-CRITICAL **: file gstelement.c: line 1429
(gst_element_link_filtered): assertion `dest != NULL' failed
 
(rhythmbox:25533): GStreamer-CRITICAL **: file gstbin.c: line 546
(gst_bin_remove): assertion `element != NULL' failed


Rerunnig gst-register from plain user account solves this problem.
But then it is hard to maintain it on larger systems, cause upgrading
packages forces You to rerun gst-register from each user.
Comment 1 Ronald Bultje 2003-08-27 20:08:05 UTC 
Why do you use user registries? If the root account runs gst-register,
then please remove the user registries (~/.gstreamer-0.6/*.xml). You
can do this scriptwise.