Summary: | media-video/totem-2.32.0 aborts looking for gconfaudiosink plugin: "unset DBUS_SESSION_BUS_ADDRESS" needed at configure time | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Keith Harrison <KeithBHarrison> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | chrsclmn, cornicx, ghepeu, graaff, teidakankan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch for totem-2.32.0.ebuild |
Description
Keith Harrison
2010-12-07 23:59:41 UTC
I'm experiencing the same problem. The configure script calls `gst-inspect-0.10 gconfaudiosink` and this happens: $ gst-inspect-0.10 gconfaudiosink ** GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL) Aborted *** This bug has been marked as a duplicate of bug 253890 *** *** This bug has been marked as a duplicate of bug 253890 *** This certainly looks like a duplicate of bug 253890, however this does not help me because as far as I can tell the other bug was never resolved in a meaningful manner. Should the other bug be reopened then or am I missing an obvious solution? Thanks Got the same issue yesterday after mass-emerging -avDuN world. The problem was solved after revdep-rebuilding the system. Thanks for the info. I just tried it out but unfortunately revdep-rebuild -p && emerge -pv @preserved-rebuild both show nothing needing to be rebuilt. *** Bug 348155 has been marked as a duplicate of this bug. *** *** Bug 348209 has been marked as a duplicate of this bug. *** I worked around the issue by renaming gst-inspect-0.10 to gst-inspect-0.10.tmp and creating a bash script gst-inspect-0.10 who calls 'dbus-launch gst-inspect-0.10.tmp $1'. Then I had to emerge totem with FEATURES=-sandbox because otherwise it failed with an attempted access to /etc/mtab. It's not a solution anyway, and it just points to dbus issues (the current dbus process doesn't accept the commands launched by root?). I'm reopening this bug because it is not resolved for me or anyone else as far as I can tell with totem 2.32.0 and I cannot find any working solution or even a proposed solution in any of the bugs that are duplicates of this one, or the bug that this has been marked as a duplicate of. This happens on all of my computers, single-core, multi-core, ~x86, and ~amd64. If anyone needs any more information just ask. Downgrading to gconf-2.28.1 would work around this bug. A change was made between 2.28.1 and 2.32.0 that turned a non-fatal error into a fatal one. With gconf 2.28.1, running `gst-inspect-0.10 gconfaudiosink' prints an error message (can't contact dbus) but then continues to confirm the presence of the gconfaudiosink element. With gconf 2.32.0, running the same command aborts when it fails to contact dbus. Then the configure script sees the non-zero exit status and concludes wrongly that the gconfaudiosink element is not present. One way to fix this would be to modify configure.in to run gst-inspect-0.10 without arguments and grep the output for each element name. Created attachment 256944 [details, diff]
patch for totem-2.32.0.ebuild
Another, possibly better, way to fix this would be to unset DBUS_SESSION_BUS_ADDRESS before running configure.
(In reply to comment #11) > Another, possibly better, way to fix this would be to unset > DBUS_SESSION_BUS_ADDRESS before running configure. To add a bit more info: If DBUS_SESSION_BUS_ADDRESS is set, which it probably will be if an X session is running, then gconf, which is invoked indirectly when running `gst-inspect-0.10` with any of the gconfelements, will attempt to contact the per session message bus rather than the system message bus. And because the configure script will be running as root or portage and not the user that started the per-session dbus daemon, it won't be allowed to talk. (In reply to comment #12) > (In reply to comment #11) > > Another, possibly better, way to fix this would be to unset > > DBUS_SESSION_BUS_ADDRESS before running configure. Victim of the same bug I can confirm that disabling DBUS_SESSION_BUS_ADDRESS before running configure ("unset DBUS_SESSION_BUS_ADDRESS" as root...) solved the problem Confirmed that unsetting DBUS_SESSION_BUS_ADDRESS will make configure pass the gconfaudiosink check. applied patch to ebuild; pkgname.ebuild digest; package builds successfully. still hitting * QA Notice: command not found: * * /bin/sh: line 6: --variable: command not found as mentioned in bug #348403 That is weird. I'll have to double check. Compiles fine for me from portage now. Thanks everyone. Also, I am seeing: /bin/sh: line 6: --variable: command not found as well. Thanks again. Not sure if I should mark this as fixed now or not. (In reply to comment #18) > /bin/sh: line 6: --variable: command not found That bug is unrelated to this one. It's bug #348403. > Not sure if I should mark this as fixed now or not. Not until this bug has been fixed in the ebuild or upstream. Manually unsetting DBUS_SESSION_BUS_ADDRESS is just a workaround. bug 332139 was reopened by Arun *** This bug has been marked as a duplicate of bug 332139 *** emerged media-video/totem-2.32.0 successfully from the tty console after trying numerous times in a gnome-terminal window. (In reply to comment #21) > emerged media-video/totem-2.32.0 successfully from the tty console after trying > numerous times in a gnome-terminal window. Thanks, worked for me too :-) |