Description of problem: openvrml-player doesn't work on FC10 (cf. below) Version-Release number of selected component (if applicable): openvrml-player-0.17.10-1.0.fc10.x86_64 How reproducible: Almost always (cf. below) Steps to Reproduce: 1. run "openvrml-player" Actual results: After being started, nothing happens for several seconds, then an error message is being issued and openvrml-player come up with an empty window only displaying a text-entry. $ openvrml-player ** (openvrml-player:3389): CRITICAL **: Browser creation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. When selecting "Open" and pointing the file browser dialog to a *.wrl file, occasionally this happens aft: ** ERROR:openvrml-player/curlbrowserhost.cpp:345:void openvrml_player_curl_browser_host_load_url(OpenvrmlPlayerCurlBrowserHost*, const char*): assertion failed: (host->priv->browser) Expected results: function. Additional info: * This issue seems to start after launching openvrml-player for a second time after system bootup. * I would not want to exclude this issue being related to the current dbus mess up in Fedora 10.
Does one of these programs use a system service?
openvrml-player uses openvrml-xembed. openvrml-xembed is a system service.
After the dbus package has been reverted, this issue seems to have vanished. => IMO, a clear case of dbus mess-up. Any dbus tracker bug available? Reassign this BZ to dbus?
I also see this bug openvrml-gl-0.17.10-1.0.fc9.i386 openvrml-xembed-0.17.10-1.0.fc9.i386 openvrml-player-0.17.10-1.0.fc9.i386 openvrml-0.17.10-1.0.fc9.i386
Looks like this was probably D-Bus bustage. Anyone still observing these symptoms, please file a new bug.