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?
Gnome Forum have told me that changing the appearance of gdm I run: sudo -u gdm dbus-launch gnome-appearance-properties but I get this error: (Gnome-properties-Appearance: 18 047): Gtk-WARNING **: can not open display:
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 recently installed opensuse 11.4 on a remote server. It has GNOME installed as a desktop. The problem I am experiencing is that when logged in through VNC, most of the GUI apps are not functioning, especially ones that require root privs. Example: The Add/Create users context does not function. After you supply root pw, nothing happens. If you launch it from a terminal, you see this:
jjmuw@g01:~> xdg-su -c /sbin/yast2 users Xlib: extension "RANDR" missing on display "::1:1.0". No protocol specified No protocol specified
(y2base:4872): Gtk-WARNING **: cannot open display: ::1:1.0
Followed by a hang. This is also affecting things like the Xen configuration contexts (creating/managing VMs).
After following a tutorial to install a pxe server for debian network install I can't log in my user session on gnome anymore
I got an error saying : /$home/.dmrc was ignored, can't save session and language the file must belong to the user and has persmission 644
I remember on my last session i got some icons on my home folder with a little lock icon on them i tried to remove them successfully using the command line but i still can't login. however i can successfully login with another user.
I tried to connect to remote server ,which is installed Centos 5.4 x86, through Xmanager on windows 7, and got this error.
/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.
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 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:
I have a fresh install of OpenSUSE 11.4 64bit and I have installed the AMD Display drivers for my Radeon HD 5970. Everything seems to be working quite well. I have a multiple monitor setup (1280x1024 monitor and a 1920x1080 monitor).
I have my primary display set to 1920x1080, however when I try to enable the second display, I get a CRTC error that the display is over the maximum (1920x1920). If I enable both monitors at lower resolutions, there is no problem.
I have done a fair bit of reading and have been unable to determine where this maximum is set, or how to change it. I'd like to be able to run both monitors at their native resolutions.
The following message comes up when I boot up: Logging in user Warning: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0. When I press OK, the system completes the start up and everything looks normal. But when I try to connect to internet, I get the following message:
KNetworkManager cannot start because the installation is misconfigured. System DBUS policy does not allow it to provide user settings; contact your system administrator or distribution. KNetworkManager will not start automatically in future. If I reboot the system, I logg in successfully. So far the problem has appeared approximately upon every second time I boot up. Rebooting the system seems to take care of it.
Don't know what info is of interest. I'm using
Opensuse 11.2 KDE 4.4.2 (Factory) After upgrade from 4.4.1 to 4.4.2 it worked fine for a week or so.
I do a clean install of slackware64 13.1 beta1 with KDE and switch default runlevel to 4 in /etc/inittab.
I try to login in kdm, I always come back to the login....
I try this with default runlevel 3 and an .xinitrc with "ck-launch-session startkde" .. works without problems, so I switch back to default runlevel 4, now i can login and only get the error "Cannot open ConsoleKit session: Unable to open session..."
My server (CentOS 5.5) is a ldap client authenticate to LDAP server (Successfully authenticate) I use pam for ssh. I can ssh successfully with any users on system. But I cannot su - from ssh. It display the error: Could not open session. I look to log file and it shows: # tail -f /var/log/secure
I have Ubuntu 11.04 and whenever I install gnome3, I will get an error during the install. Following are the details. "sudo apt-get dist-upgrade". I will always get an error pop-up and a error message in terminal saying "errors were encountered while processing: /var/cache/apt/archives/gnome-session_3.0.1-0ubuntu~build1_all.deb" & "E:sub-process /usr/bin/dpkg returned an error code (1)" And when I reboot, I will get stuck at the ubuntu splash page and ubuntu will not load.
After finally getting libptp2 to compile I find that ptpcam does not work. This has worked perfectly fine before with the same camera using Slackware 12.0, I am now using Slackware 13.1 and ptpcam will simply not work. The error is as follows:
x86_1# ptpcam -l Listing devices... bus/dev vendorID/prodID device model ERROR: Could not open session! Try to reset the camera.
I have tried to reset with "ptpcam -r", I have also tried to disconnect and reconnect the camera to the USB system, I have tried to reboot the computer, I have tried to use different versions of libptp2 -- all to no avail. The strace shows the issue is apparently a failed ioctl(), although I have no idea why it fails:
I have verified that the camera is working in Windows 7 on the same physical computer and I can see the camera from lsusb and dmesg output when I connect it to the USB system. This system is Slackware 13.1, Linux x86_1 184.108.40.206-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux.
When i try to create a virtual machine using the Windows 7 Enterprise Evaluation iso file, everything goes as planned untill i click on the start button. when i click on it i get two error messages. the first: Failed to open a session for the virtual machine Windows 7. The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1. Kernel driver not installed (rc=-1908). The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. reinstall the kernel module by executing
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. i have installed the DKMS package, but when i try to run the command stated in the error message, i get another error message in the terminal:
i have to install the driver that is specified (vboxdrv) but i do not know where to find it.
I have logged as e.g. user1 via ssh into my machine. Then I perform `su -` to switch to root user and I don't see debug messages which are normally displayed when I log as root via system console.How to display console messages in ssh session ?
I was trying to remotely log in to my desktop which uses 11.3 from my laptop via ssh. For some reason I get an empty field for the command echo $DISPLAY. and as a result an xclock command results in error: can't open display. I tried to set it to localhost:10.0 and I get: Error: Can't open display: localhost:10.0
I've tried :0.0 and I get: Invalid MIT-MAGIC-COOKIE-1 keyError: Can't open display: :0.0 ssh used to work about a week ago before I performed various security updates. I was wondering what' the solution to this. I checked the /etc/ssh/sshd_config file and ssh_config file both have X11 forwarding on. Can anyone with more experience out there give me any ideas?
When I attempt to use Putty for xterm (to run DBCA for Oracle) I check x11 and put my IP Address in the Display field of putty. However, when I then try to execute ./dbca I receive the following:
Xlib: connection to "localhost:10.0" refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted Error: Can't open display: localhost:10.0
I notice the following when logging in to the server as well.
Last login: Fri Mar 19 13:51:19 2010 from 10.47.48.33 /usr/X11R6/bin/xauth: error in locking authority file /home/oracle/.Xauthority. These are the same steps I take successfully on all the servers. The above file exists on the servers I can initiate the GUI, but not on <server1>.
In the past, when I open a gvim session on a remote machine, the title bar of gvim would show the machine name in brackets. I am not sure if this was done by the remote gvim itself, or the local window manager. In the past I have used gnome2, although I am currently using unity (and finding it rather frustrating). Is there some setting I can change to always force remote windows to display the source machine?
So I just installed 32-bit Squeeze. I've done exactly two things since booting into the first install: pt-get install gtk+2.0, and ./firefox, so unless gtk did something, this might be an easily fixable problem with Debian itself. After installing gtk and trying to run firefox via command line, it tells me
Code: Error: cannot open display: :0 I googled a bit and couldn't come up with a solid solution, but the problem seems to be around other places. Any idea how to fix this?