Sponsored Content
Operating Systems Linux SuSE HELP for Newbie: Unable to run GUI installer (Ubuntu client connected to SLES server) Post 302661117 by kartrait on Sunday 24th of June 2012 11:17:26 PM
Old 06-25-2012
HELP for Newbie: Unable to run GUI installer (Ubuntu client connected to SLES server)

Hello All,

I'm using my Ubuntu 10.04 client connected via SSH to a SuSE Linux server (SuSE Linux Enterprise Server 11 (x86_64) version 11 patchlevel=1).
I'm trying to run an install of WebSphere Portal but can't seem to be able to run the GUI installer.

Running xclock as root returns this error:
Error: Can't open display:
Running xhost returns this:
xhost: unable to open display ""

As far as my very limited knowledge of Linux goes, I don't have to export display while connecting from an Ubuntu client (never had to do that connecting to AIX and some others). So I think it's something on the server side that needs to be configured or run... Your help would be very appreciated!

Thanks in advance!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

If a is windows gui ( client), b is a unix gui ( Server for a) and c is a shell scrip

Hello all, 1) I want to have a GUI application that will call Unix shell scripts, 2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix. That is for example. If a is windows gui (... (1 Reply)
Discussion started by: hchivukula
1 Replies

2. Virtualization and Cloud Computing

Unable to install ubuntu on vmware server

Hi I have downloaded vmware server 1.0.10 and ubuntu 9.10. Installed vmware server on my windows xp and created the disk space for Ubuntu. Now when i am running the virtual machine using the above downloaded iso image, I get the installation window. I selected 'Install Ubuntu' option and... (2 Replies)
Discussion started by: kushal154
2 Replies

3. UNIX for Dummies Questions & Answers

I'm unable to run Keyed List commands(in ubuntu's terminal and Evolane Tcl Engine)

I'm trying to run these commands (keylset,keylget) but i keep getting a error message "invalid command name "keylset"". I've tried running it on both ubuntu's terminal and also Evolane Tcl Engine. Any idea what could be the problem? (1 Reply)
Discussion started by: abe171
1 Replies

4. Shell Programming and Scripting

Shell Installer GUI

Hey guys, I just can't seem to find any hints on this topic (or maybe I just don't find the correct search terms to use :rolleyes: ). My company developed an application which requires harsh configuration to run it on a server. So I wrote a LOT of shell scripts which take care of the... (2 Replies)
Discussion started by: fatfingerjoe
2 Replies

5. AIX

GUI Installer Error

Hey I'm getting the below error when trying to launch the GUI installer. I contacted the application owner and they asked me to remove JAVA_HOME env variable, I removed it but still get this error. As the error message said, tried with -console and it didnt work too. nothing happened, it... (3 Replies)
Discussion started by: rocker_me2002
3 Replies

6. Red Hat

Unable to access NFS share on Solaris Server from Linux client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. share -F nfs -o rw /var/share & then ran the following svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies

7. Shell Programming and Scripting

unable to configure NIS client server

Dear all, I am using solaris 10 OS. I configured NIS server and i also configured NIS client server but when i use the command ypinit -s sunserv1 in NIS client it is showing me the below error. Enumerates maps from sunserv1. please check that it is running. (2 Replies)
Discussion started by: bhargav90
2 Replies

8. SuSE

Linux SLES Gui Not coming up

I had sles 11 sp2 installed on my system some days back and it was running fine. Today after I restarted my system the gui is not coming up and system starts in command terminal. sax2 command returns error: sax: gui is missing, starting command line interface sax: no x-server... (4 Replies)
Discussion started by: rupeshkp728
4 Replies

9. IP Networking

Unable to SSH from Windows client to Ubuntu Server

I'm trying to setup a small home network environment as a pet project. These are physical machines nothing virtual. Any help or ideas is greatly appreciated. I can ping between both machines and I have Samba established and can read/write different shares. When I try to SSH from Windows 8.1... (10 Replies)
Discussion started by: lombardi4851
10 Replies

10. Ubuntu

Unable to boot Ubuntu server 15.10

Hi; I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation. After installation, Ubuntu server not booting I guess there is boot problem conflicting with my old Windows Server. This is my pastebin: http://paste.ubuntu.com/13851828/ Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies
SYNERGYC(1)						      General Commands Manual						       SYNERGYC(1)

NAME
synergyc -- synergy client SYNOPSIS
synergyc [-d level | --debug level ] [--display display ] [--daemon | { --no-daemon | -f } ] [-n name | --name name ] [--restart | { --no-restart | -1 } ] address synergyc { --help | -h } synergyc --version DESCRIPTION
Starts the synergyc mouse/keyboard sharing client. This manual page was written for the Debian distribution because the original program does not have a manual page. Slightly old documenta- tion exists in /usr/share/doc/synergy/obsolete/index.html; it is the most up-to-date information available, despite the pathname. OPTIONS
-d level --debug level use debugging level level. Debug levels are from highest to lowest: FATAL, ERROR, WARNING, NOTE, INFO, DEBUG, DEBUG1, and DEBUG2. Only messages at or above the given level are logged. Messages are logged to a terminal window when running in the foreground, and to syslog when running as a daemon. --display display connect to the X server at display --daemon run the client as a daemon. -f --no-daemon run in client the foreground. -n screen-name --name screen-name use screen-name instead of the hostname. This option lets the client use a name other than its hostname for its screen. This name is used when checking the configuration. --restart restart the client automatically if it fails. -1 --no-restart do not try to restart the client if it fails for some reason. -h --help display help and exit. --version display version information and exit. address address of server. address has one of the following forms: o hostname o hostname:port hostname is a hostname or address of a network interface on the server system. port is a port number from 1 to 65535. port defaults to 24800. RUNNING THE CLIENT
Run the client on all computers that aren't the server using the following command line: synergyc -f server-hostname Replace server-hostname with the hostname or address of the server system. The `-f' option causes synergy to run in the foreground. This option is recommended until you've verified that the configuration works. If you didn't include the system's hostname in the configuration file (either as a screen name or an alias) then you'll have to add `--name screen-name' to the command line, where screen-name is a name in the configuration file. The client should quickly report `connected to server'. If it does not but doesn't print an error and exit immediately then it's trying to connect to the server but cannot. It will time out in 30 seconds and exit (use ctrl+c to exit earlier). You should check that the server is running and is reachable over the network and try again. If the client fails and exits it should print an error describing the problem. Here are typical problems and possible solutions: o failed to open screen: check permission to open the X display check that the DISPLAY environment variable is set o already connected: check that the synergy client isn't already running o refused client: add client to the server's configuration file o connection failed: check server-hostname the server cannot open the desired port, stop the program using that port (24800) and restart the server Once all the clients are running, try moving the mouse to each screen. Be sure to check all the configured links. STARTING AUTOMATICALLY
Synergy requires an X server. That means a server must be running and synergy must be authorized to connect to that server. I recommend to start the synergy client from a start script of your desktop environment or window manager. The commands should look something like this: pkill synergyc synergyc [options] server-hostname If you are using GNOME, you can add the synergy client to the list of the non-session-managed startup programs. For doing this, start the control center, choose `Session Properties & Startup' and then `Startup Programs'. Add a new entry with `/usr/bin/synergyc server-hostname' as the startup command. options must not include `-f' or `--no-daemon'. It's important to make sure no old copies of synergy are running so they can't interfere with the new one. SEE ALSO
synergys(1) AUTHOR
This manual page was written by Daniel Lutz <danlutz@debian.org> for the Debian system. Edited by Titus Barik <barik@ieee.org>. SYNERGYC(1)
All times are GMT -4. The time now is 03:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy