General :: Xset: Unable To Open Display
Oct 30, 2010I tried to log on to a remote computer using ssh, but I got an error:
xset: unable to open display
I tried to log on to a remote computer using ssh, but I got an error:
xset: unable to open display
I'm SSH'ed in to my Ubuntu 11.04 machine and trying to take a screen shot of a virtual display where I'm running (hopefully) Firefox. I get the error
Code:
selenium@selenium:~$ xwd -display localhost:15.0 -out ~/desk.xwd -root
xwd: unable to open display 'localhost:15.0'
I know that I have displayed the right display variable because in an earlier script that runs at system bootup I have
Code:
export DISPLAY=localhost:15.0
/usr/bin/Xvfb :15 -ac -screen 0 1024x768x16 &
I recently did a clean install of Fedora 11 (from Fedora 10). In Fedora 9 and 10 I used a remote font server so that I could launch HP OpenView over a VPN tunnel. The procedure would go something like this:
*connect to VPN
*xset +fp tcp/<hp_ux_server>:7000
*ssh -X user@hp_ux_server
*launch OpenView
OpenView requires the fonts that are installed on the HP-UX server, hence the need for the xset command. Now since the installation of Fedora 11, I cannot get the xset command to work.
xset fp+ tcp/<hp_ux_server>:7000
xset: bad font path element (#23), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
I have turned off the firewall to make sure it wasn't blocking the request. But to no avail. I have also had two other people with Fedora 11 machines try this, they get the same error. Were there major changes in the X server from Fedora 10 to 11+?
I have configured an instance in AWS EC2. I am trying to set the display back so I can run x apps. I login using ssh -xy -i...
export DISPLAY=XXX.XXX.X.XXX:0.0
echo $DISPLAY to verify
xhost +
xhost: unable to open display "XXX.XXX.X.XXX:0.0"
I have commented out nolisten tcp as suggested HERE I have modified /etc/gdm/custom.conf as suggested HERE Actually, the last suggested modifying /etc/gdm/gdm.conf, but that file didn't exist, so I added the line: DisallowTCP=false to /etc/gdm/custom.conf I rebooted, and still I get: xhost: unable to open display "XXX.XXX.X.XXX:0.0"
The title pretty much describes the issue. The timespan is sometimes some minutes instead of some seconds. I've tried unplugging every peripherials and disabling the touchpad, killing every non-critical processes, disabling and enabling Compiz, but nothing has helped so far.
I'm running Karmic on an Acer Aspire 8935G-874G100BN laptop with a Radeon graphics chipset.
I have the following scenario that doesn't seem to work normally. I have a windows 7 pc from which I am using putty to connect to my other linux servers (all running redhat 5 and 6). So here is the scenario that works and one that does not work. And I'm trying to figure out the one that does not work. Scenario that works:
From windows 7 (putty) I ssh into Linux_Server_1.
echo $DISPLAY
localhost:10.0
I run xclock and I see it pop up on my windows 7 pc. I am using xming on windows 7 to help me populate the display from linux to windows. One that does not work:
From windows 7 (putty) I ssh into Linux_Server_1. Then from Linux_Server_1 I ssh into Linux_Server_2.
echo $DISPLAY
<no output>
I try to setup $DISPLAY with localhost:10.0 or 0.0 or even my windows 7 pc ip address:0.0 ....etc Then when I try to run xclock I doesn't work.
I get these error messages: Error: Can't open display: <ip of display>
Also as a side note all our Linux servers are sitting on one subnet. My pc is sitting on another subnet. I use vpn to connect to the subnet where the servers sit from my pc.
I'm experimenting with old linux Distributions again, and while trying tostart an x server, I get the following error message:X: unable to open display ''That makes me think that the config file is incomplete, but I would have no idea how to make it. If there is an auto configuration utility that I do not know about for X, it would be great to hear about. Here are some other specifications that might help:*Host: VMWare Workstation on Windows XP Home*Distribution: Debian 2.2 (potato) (Yes, I know it's old.)*Connection: Local. I've heard of people having difficulties like this on remote connections, but I am on the physical computer
View 7 Replies View RelatedWell after messing with compiz Opacity I managed to make all panels and windows transparent. Only thing I see is desktop background and icons. Tried ctrl+although+f1 and running gconftool-2 --recursive-unset /apps/compiz
Then a reboot. Same issue. Next ran metacity --replace I get: Windows manager error: Unable to open X display
Ever since upgrading to Fedora 14, my system has been almost unusable. I can only have a few windows of anything open before I start getting messages about:
Maximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedxwininfo: unable to open display ':0.0'
I am unable to open any new windows then and lots of programs crash.
When things are still running correctly.
A few minutes later:
Well this is my first time using redhat 7, the install went fine and webserver, mysql, phpmyadmin are all working......great
The only problem i have is the remote desktop
I have set the password in preferences/remote desktop run command vncpasswd and set password
In services vncserver i get this message......... xsetroot: unable to open display '' Xvnc is stopped and vncserver failed. The error was: xsetroot: unable to open display '' Shutting down VNC server: 1:user1[FAILED]
Starting VNC server: 1:user1 [FAILED]
My vncservers file looks like this
I have tried restarting service using root login and user1
We rebooted the server an got the following error:
Quote:
RHEL xhost unable to open display ""
Can't login or do anything at the monitor or kb. How ever I can ssh to the server, not sure where to start looking. I have two servers that are the same and checked the xorg.conf on both servers and they looked the same.
i recently moved from Ubuntu to Debian(squeeze).. i am very pleased with squeeze except for this bug..I have this python script i wrote to change my wallpaper (through Gconf), the script would be called by cron from time to time.The problem i am facing in Debian is that this script stopped working.I am exporting the $DISPLAY=:0 in Cron, (this is how it worked in Ubuntu)..the cron job i used is below:
-----------
* * * * * export DISPLAY=:0 && /path/to/my/script.py
--------
so the above was not running...I redirected the output and this is what i got as error:
-------------
Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: /usr/bin/dbus-launch terminated abnormally with the following error: Invalid MIT-MAGIC-COOKIE-1 keyAutolaunch error: X11 initialization failed.)
-------------
[code].....
Im using the Redhat 5, when m trying to connect from X-start it showing error:
Can't open display: localhost:0.0
Where as /etc/ssh/sshd_config settings are correct
Also ssh is running
$DISPLAY is set to localhost
still it is not started any x-service
I'm trying to connect to my linux server but I'm having some major problems. The server had OEL 5 installed and my local pc is running Windows XP. I'm using PuTTy to connect to the server with Xming running on my loacl machine. I login as root and run the following command - export DISPLAY={ipaddress}:0.0I then run xclock and get the following error - Xlib: connection to "{ipaddress}:0.0" refused by serverXlib: No protocol specifiedError: Can't open display: {ipaddress}:0.0The strange thing is that on my bosses pc (who has got almost the exact same setup ie. PuTTy & Xming) is works perfectly.
View 2 Replies View RelatedI have installed RHEL 4.6. But X server is not running. Wen i executed xclock Error: Can't open display: hostnmae:0.0
View 4 Replies View Related/usr/bin/xterm Xt error: Can't open display: %s
I tried to connect to remote server ,which is installed Centos 5.4 x86, through Xmanager on windows 7, and got this error.
Quote:
/usr/bin/xterm Xt error: Can't open display: %s
At the remote server, I turned on firewall and after this I got the above-mentioned error message.
I do this accrding to instruction on remote server.
Quote:
2. Firewall (TCP/UDP Ports) Configuration
Open UDP port 177 from the PC to the remote host direction.
Open incoming TCP ports 6000~6010 from the remote host to your PC.
After adding these ports "/etc/sysconfig/iptable" as the enoder mentioned, /etc/init.d/iptables restart
3. Reboot the remote host and start Xmanager <- I could not restart remote server.
I try to change locale for a program to run my native language with root. I don't know what I made, but can't open gui programs from konsole with root account.
It appear this error:
Code:
When type locale, it appear:
Code:
Yesterday I make run level 4 to skip typing startx in console, and login directly to KDE.
I with one problem to open files on terminal. By example, I open the thunar on terminal, see the error:
gustavo@universe /media/montagem $ thunar
(process:7902): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Maximum number of clients reachedThunar: Cannot open display:
gustavo@universe /media/montagem $ ^C
I also had ever tried all methods they mentioned, but my problem is still there. I am using a MAC OS X 10.6 ssh a remote redhat server. I hope to see X of redhat on my own MAC. Below is what I've done: 'MAC_ip' stands for my mac; 'redhat_ip' stands for redhat server.
1) ssh to redhat server
2) change to root
3) type command: DISPLAY=MAC_ip:0.0
4) type command: export
5) Back to MAC
6) change to root
7) type command: xhost +Redhat_ip
8) vim /etc/ssh_config, add X11Forwarding yes
9) Back to redhat, type: xclock
I got below message: Error: Can't open display: MAC_ip:0.0 I also tried some methods to login as others suggested:
[Code]....
I installed Open Office 4 on Debian 8 but when I run the program I get this error message.
root@localhost:/home/paul# openoffice4
No protocol specified
No protocol specified
/opt/openoffice4/program/soffice.bin X11 error: Can't open display:
Set DISPLAY environment variable, use -display option
or check permissions of your X-Server
(See "man X" resp. "man xhost" for details)
Open Office works fine when I run the command "startx" in the Konsole but so far I haven't been able to configure it.
I'm using wmctrl on an Ubuntu machine to manage windows from a script, that I run inside a (gnu) screen.
If I start the screen session from the local machine, wmctrl works fine, including if I completely close the terminal window and issue the wmctrl commands when connecting to the screen remotely via ssh.
Conversely, if I connect remotely with ssh and start a screen, wmctrl doesn't work (returns "Cannot open display") even if I attach that screen session locally from the Ubuntu Terminal.
I guess there is some hidden screen parameter that doesn't get set in a way that allows accessing the display when it's launched remotely -- any ideas what it is and how to modify it from within a remote ssh-screen session so that that the script can access the windows?
We have a digital signage appliance built on SUSE 11.3 with a LAMP server that uses the flashplayer application to play a .swf file from localhost. It is a AOpen GP7A mini pc that has the nVidia drivers loaded. We have lots of customers that have been running the exact same system for over 6 months (we image the drive for each sale).
For some reason, my last customer is seeing the following problem shown below, and this linux configuration is way over my head. Everything else is working (local LAMP server is working, communicating with our production servers to get information works, etc). I have verified that it is screen 0 that is running (at least it shows with Ctrl-Alt-F7). I thought that it may have occurred because of updating the software with zypper up. I had the customer rebuild from the image being careful not to upgrade the software. The result was the same. The pc is a newer version compared to my bench pc, but there are multiple other customers running that same version just fine. So I am not sure if it is
The command is issued by a php script that is run in a root cron job. As I said, it works great on all other customer pc's including my bench system. I also tried to execute the command on a ssh terminal as the root user with the same result. I also upgraded my bench pc and it still worked properly.
The command being executed is sudo env DISPLAY=:0 XAUTHORITY=/home/svision/.Xauthority flashplayer http://localhost/flash/sign.swf &
the result (when run in terminal) is: No protocol specified (flashplayer:15077): Gtk-WARNING **: cannot open display: :0
I use kubuntu (8.04) which does not have a root account.
[sudo] password for ts:
However, starting xclock or gvim on root shell on konsole has the "Can't open display" error appears.
Error: Can't open display: localhost:0.0
Press ENTER or type command to continue
Just loaded Linux mint 9 but having problems with video display. When I open Mozilla it works ok for awhile but then goes crazy and i can't see anything.
View 1 Replies View RelatedMy script is not diaplying output as it contains awk while iterating over the array. My script is as follows:
shortcodes=( "56882" "58585" "58888" "57575" "57677" );
for shortcode in ${shortcodes[@]}
do
echo "`awk -F"|" '/ShortCode=tel:$shortcode/ { arr[substr($2,1,4)]++ } END { for( no in arr) { print no , arr[no] } }'
[code]....
Since reinstalling Ubu9.04 from disk, I'm unable to view many MP4 videos.
My laptop only has 3 settings for res.
Here's some lshw:
And some attempt at adding a higher value in xorg.conf:
I want to configure xmms music player in my linux, but it didn't run 'xmms &' command, gives output like 'unable to show display'.
View 8 Replies View RelatedI have 2 Fedora 12 installs with this problem. Before installing FC 12, xset led 3 worked fine.
The command:
SHOULD turn on the scroll lock LED.
With FC 12, it doesn't.
In Xorg.log, I see: (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(I believe before FC12, I was using driver "kbd".) The man page for kbd shows the options needed for program control of the LEDs.
The new driver appears to be "evdev". I've read some of the HAL documentation and I think this driver uses the file: /usr/share/hal/fdi/policy/10osvendor/10-leds.fdi
I see nothing about program control in this file.
Anyway, anyone have any idea why xset led stopped working and how to go about fixing it?
I use 'xset r 133' to set autorepeat for the 'Windows key'.
But somehow after a while autorepeat does not work any longer and I have to redo the 'xset r 133'. I don't log out or so.
Ubuntu 10.04, gnome, compiz
Debian Lenny on a Toshiba Portege 350000:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev 82)kernel version 2.6.26-2-686On my system, "xset dpms force off" blanks the screen, but does not turn off the backlight. This means that the automated screen off in X does not actually save any power when it blanks the screen.I can turn off the backlight manually using the BIOS tool "vbetool dpms off" (but then I have to turn it back on again manually too).Question 1: is this a problem with the graphics driver interface, or with X, or with the power management driver interface?Question 2: as a workaround, is there any way for me to hook into the dpms off/on that X is doing, and run a script to call vbetool? The best workaround hack I have come across so far is to have a screensaver that calls vbetool, but I was hoping to find something that doesn't require me to run a daemon all the time.
View 4 Replies View Related