When I tried to downgrade my totem from 2.16 to 1.4.2-r1 the emerge stopped at an error. I required gconfaudiosink and ask the user to reemerge gst-plugins-good, but after reemerging that one and later several other packages relating to gconf and gstreamer I finally found the right package I think, gst-plugins-base. After that the emerge went through, but I'm still missing the gconfaudiosink file, maby it only was a coincidence it worked. If it was, someone would probably change the package to refer to gst-plugins-base instead of pst-plugins-good, don't know if it is a gentoo specific problem or gnome in general.
Downgrading is expected to require recompiling. The package is gst-plugins-gconf, which is a Gentoo specific split. The dependency is listed, I guess some other package had been recompiled and gst-plugins-gconf needed one as well.
*** Bug 155356 has been marked as a duplicate of this bug. ***
*** Bug 155657 has been marked as a duplicate of this bug. ***
Created attachment 252139 [details] error.log
Hi I have the same issue with all releases of totem , in portage tree... And I can't resolve the problem... Thanks.
Hello. How can I resolve this bug, because now anyone release of totem compil, always with the same error... And I have need it... I unmerge gst-plugins-good ,re-compile gst-plugins-good , recompile totem but this is always the same problem and error... I'm very disappointed for that :(. Thanks.
If the issue still persists, try rebuilding gstreamer first. Fixed it for me.
I've found out what the problem is. To shed some light on this issue: when doing this as normal user: tom@note ~ $ gst-inspect-0.10 gconfaudiosink blahblahblah ... works. But doing the same as root: root@note tom # gst-inspect-0.10 gconfaudiosink ** GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL) This is the reason the check in configure fails. workaround: start a gnome session as root (from gdm), then the emerge works.
In fact, the only way to solve this was to start a gnome session as root. that's nasty. I guess the status of this in OPEN? there is a chance of a work around more elegant?
(In reply to comment #9) > In fact, the only way to solve this was to start a gnome session as root. > that's nasty. > I guess the status of this in OPEN? there is a chance of a work around more > elegant? If you have app-admin/sudo installed and your user is in /etc/sudoers then you can simply run $ sudo emerge -v1 media-video/totem Kind regards, der Max
I don't understand why this was marked resolved: this is still not working. maxb's suggestion is only a workaround and not a solution to the problem.
This is the same as bug 332139, marking it as a dupe of that because it has more information.
*** This bug has been marked as a duplicate of bug 332139 ***