I am using a very complex setup to test various non-public webpages. I use jenkins
to run the python-selenium
tests within a docker
ima
For me the solution was to install dbus-x11
apt install dbus-x11
The error you are seeing is :
(firefox:55): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
So it is clear Firefox attempts to connect to D-BUS daemon and fails as dbus-launch gets terminated abnormally.
dbus-launch is basically the utility to start a message bus by firefox through a shell script. It would normally be called from a user's login scripts. dbus-launch launches a session bus instance and print the address and pid
of that instance to standard output.
You can read more about dbus-launch from the Linux man page
This error can arise if you use su
(root), sudo
, suedit
, gksu
. The main reason is DBUS_SESSION_BUS_ADDRESS
retains its value when you su
instead of picking up the value in /root/.dbus/session-bus
.
Here you will find a detailed discussion on GConf Error: No D-BUS daemon running?! How to reinstall or fix?.
Another possible reason may be the base Firefox
Browser version may be an older version on which updates were taken to reach the current version.
There are a couple of solutions available to address this ubuntu related issue as follows :
export $(dbus-launch)
NSS_USE_SHARED_DB
. So you have to use export NSS_USE_SHARED_DB=ENABLED
as well.The most convenient way would be to put all the configuration with in .bashrc
file :
export $(dbus-launch)
export NSS_USE_SHARED_DB=ENABLED
firefox &
This discussion speaks about the solution in details.
dbus-launch
is not installed on your system you have to install dbus-x11
package which contains the dbus-launch program.The issue with dbus-launch was addressed properly by both Ubuntu and Mozila. To overcome this error you need to follow the below mentioned steps :
What does this message mean?
DBus is a message bus system for interprocess commutation. There is an open geckodriver
issue on a similar if not the same subject:
Could that be an indication of the reason why sometimes the tests are failing?
The warning should not really affect the tests but it's difficult to speculate about your intermittent test failures without seeing what is actually happening in your tests.
If so, how to fix it?
Here are some things to try:
geckodriver
to the latest stable version (currently 0.19.1)