I am trying to run Firefox (or any other browser) through an X11 connection from Bash on Ubuntu on Windows.
I am using VcXsrv 1.20.6.0
My Firefox version I see through the bash terminal is:
(env) flx#pc:/etc/ssh$ firefox --version
Mozilla Firefox 74.0
When I try to start Firefox from the bash I get the following error:
(env) flx#pc:/etc/ssh$ firefox
Exiting due to channel error.
###!!! [Parent][MessageChannel] Error: (msgtype=0x1E0057,name=PBrowser::Msg_UpdateEffects) Channel error: cannot send/recv
(firefox:16625): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Error spawning command line 'dbus-launch --autolaunch=f6c6eb9e4e7543fa90e8fb64fbdd8983 --binary-syntax --close-stderr': Child process exited with code 1
[Parent 16625, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox-LE_x6q/firefox-74.0+build3/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 23
I am quite stuck here, do you have any ideas what I could try to get it to work?
Adding on to #Roudcore's answer
wget https://ftp.mozilla.org/pub/firefox/releases/52.0/firefox-52.0.linux-x86_64.sdk.tar.bz2
sudo tar xjf firefox-52.0.linux-x86_64.sdk.tar.bz2 -C /opt/
sudo ln -s /opt/firefox-sdk/bin/firefox /usr/local/bin/firefox
Try to service dbus start before starting firefox, after that dbus-launch should work properly
As alternative, i would recommend you to use firefox 52.
52 version works correctly.
Related
Installed tmux on my local machine via
brew install tmux
Trying to run it and getting this
error connecting to /private/tmp/tmux-501/default (Socket operation on non-socket)
Could someone to suggest something to do with it? Seems something wrong with socket but in all tutorials I have to install and just run it.
I tried:
To reinstall - nothing as a result. Any command such as tmux new, tmux attach gives the same error message.
I am trying to build Fuchsia OS and run it on the Fuchsia Emulator femu, but after waiting for the emulator to start the fx command exists and displays the error below.
failed to create Fuchsia device device health check failed. Unable to ssh due to error:
Error: Cannot start Fuchsia Emulator. Exit status is 1
I have followed the instructions provided by Google at fuchsia.dev, the build completes successfully and the commands used to build the OS were
fx set core.qemu-x64 --with //examples/hello_world
fx build
Subsequently, I tried running in headless mode with fx vdl start -N --headless which results in the same error as above, I also tried build the OS without the --with argument but received the same error.
The log file gives us more details, the second last line of the log file may be of interest and it reads:
emu-system-x86_64-headless: network script /etc/qemu-ifdown failed with status 256
I am using Ubuntu 21.04 on my machine.
It seems that the network configuration scripts /etc/qemu-ifup and /etc/qemu-ifdown are missing. You can work around it by installing the qemu package:
$ sudo apt install qemu
I created a service in macOS so I could open any file with emacs as I wanted. The service was created using Automator with the following shell script:
/usr/local/bin/../Cellar/emacs/25.3/bin/emacsclient -nc "$#"
While this service will always failed with the following message:
emacsclient: could not get terminal name
Anyone has some clues? Thanks forward.
Is it possible to get xvfb-run to work in the newest version of OS X? I've installed XQuartz and Xvfb runs the scripts with the following command:
Xvfb :4000 & export DISPLAY=:4000 & rspec
instead of this one:
xvfb-run rspec
This is however not without fault, either the temp file "x4000-lock" will not get removed after the script is finished and stop Xvfb to start up again or I'll recieve this error next time the script runs:
[2] 13220
[3] 13221
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
Run options: include {:focus=>true}
This error is also recieved on a linux system so i Suspect "xvfb-run" is doing something more in the background and thus wondering how to get that running in OS X
I have setup the xvfb server on my headless server and when I m running the
DISPLAY=:99 firefox
I am getting this exception missing RANDR extension
Many of them said to disable some xinerna from the xorg.conf file but this file is not getting created in my case.
So I am searching for how to add the missing RANDR extension.
I am seeing this error message when I run Firefox headless through selenium using xvfb. It turns out that the message was a red herring for me. The message is only a warning, not an error. It is not why Firefox was not starting correctly.
The reason that Firefox was not starting for me was that it had been updated to a version that was no longer compatible with the Selenium drivers that I was using. I upgraded the selenium drivers to the latest and Firefox starts up fine again (even with this warning message about RANDR).
New releases of Firefox are often only compatible with one or two versions of Selenium. Occasionally Firefox is released with NO compatible version of Selenium. When that happens, it may take a week or two for a new version of Selenium to get released. Because of this, I now keep a version of Firefox that is known to work with the version of Selenium that I have installed. In addition to the version of Firefox that is kept up to date by my package manager, I have a version installed in /opt/ (eg /opt/firefox31/). The Selenium Java API takes an argument for the location of the Firefox binary to be used. The downside is that older versions of Firefox have known security vulnerabilities and shouldn't be used with untrusted content.
First off, Xvfb doesn't read configuration from xorg.conf. Xvfb is a variant of the KDrive X servers and like all members of that family gets its configuration from the command line.
It is true that XRandR and Xinerama are mutually exclusive, but in the case of Xvfb there's no Xinerama in the first place. You can enable the XRandR extension by starting Xvfb using at least the following command line options
Xvfb +extension RANDR [further options]
I had the same problem with Firefox 30 + Selenium 2.49 + Ubuntu 15.04.
It worked fine with Ubuntu 14 but after upgrade to 15.04 I got same RANDR warning and problem at starting Firefox using Xfvb.
After adding +extension RANDR it worked again.
$ vim /etc/init/xvfb.conf
#!upstart
description "Xvfb Server as a daemon"
start on filesystem and started networking
stop on shutdown
respawn
env XVFB=/usr/bin/Xvfb
env XVFBARGS=":10 -screen 1 1024x768x24 -ac +extension GLX +extension RANDR +render -noreset"
env PIDFILE=/var/run/xvfb.pid
exec start-stop-daemon --start --quiet --make-pidfile --pidfile $PIDFILE --exec $XVFB -- $XVFBARGS >> /var/log/xvfb.log 2>&1