Can't open display: 0:0

Hi board,
I got SGD EE 4.0 running on a debian sarge. Ok. ok.. I know that debian is
not supported - but with some assistance I maneged to get SGD 3.? working
on debian too.
As this assistance is no more available for me I hope to find some help
here.
Starting the SGD is no prob and also the login via browser from a client
is working fine. But neither array- nor objectmanager can be strated as
there's an error when opening Display 0.0
Unfortunatly my linux know how is quite poor so I've no idea what to
check. Has anybody some ideas where to loo and what to to to make it work?
cheers,

Hi,
you should check, whether the range of virtual
X display, used both by ssh and tarantells
intersects. By default, both are using the
range :10, :11, ...
Then you are using local (to the tta server) X
Apps via ssh (typical such apps. are object and
array manger), this can rise a confict.
The solution, in this case, is to change
the default range. For ssh: edit (e.g.)
/etc/shhd/sshd_config and set
X11DisplayOffset 200
Don't forget to send the master sshd daemon
a SIGHUP, that notic the sshd to reread it's
config file...
regards,
Tankred
Mat wrote:
Hi Carmelo,
nice idea - but it didn't work :-(
drwxrwxrwx 2 root root 4096 Aug 2 19:26 .
drwxrwxrwt 10 root root 4096 Aug 2 19:27 ..
srwxrwxrwx 1 ttasys ttaserv 0 Aug 2 19:26 X10
is my output - (the root line is missing... is that a/the prob?)
or any other idea... the logs I found are not very usefull :-(
cheers,
Carmelo wrote:
Mat,
Try the following
chang the permissions on the /tmp/.X11-unix directory from 775 to 777.
This allowed the ttasys user to create the unix socket in the directory.
~> ls -la /tmp/.X11-unix
total 48
drwxrwxrwx 2 root root 236 Jul 13 10:39 ./
drwxrwxrwt 25 root sys 9072 Jul 13 10:40 ../
srwxrwxrwx 1 root root 0 Jul 13 09:56 X0=
srwxrwxrwx 1 ttasys ttaserv 0 Jul 13 10:39 X10=
let me know if that works.
Thanks,
Mat wrote:
Rob wrote:
Mat wrote:
Hi board,
I got SGD EE 4.0 running on a debian sarge. Ok. ok.. I know that debian
is
not supported - but with some assistance I maneged to get SGD 3.?working
on debian too.
As this assistance is no more available for me I hope to find some help
here.
Starting the SGD is no prob and also the login via browser from a client
is working fine. But neither array- nor objectmanager can be strated as
there's an error when opening Display 0.0
Unfortunatly my linux know how is quite poor so I've no idea what to
check. Has anybody some ideas where to loo and what to to to make itwork?
>>>>>
cheers,
Are you in the position to tell us if the application you want to run is
accessed using either TELNET or SSH ?
What about character applications ? Do they work fine ?
If the problems are only noticeable for graph apps, please point your
browser at the following URL:
http://www.tarantella.com/support/documentation/sgd/ee/4.1/help/en-us/base/indepth/ssh.html
>>>
>>>
Best,
RobHi Rob,
the app I would start is the array manager :-( (or also the objectmanager)
>>>
I can ssh my machine and have also XForwarding on yes.
The output when starting an xapp is:
Starting...
Locating session...
..found session
Connecting to session...
Initialising ...
Logging in to the application server...
[email protected]'s password:
Last login: Mon Aug 1 20:17:17 2005 from sophie.xxx.de
sophie:~# exec /bin/sh
sophie:~# [ -f /bin/ksh ] && exec /bin/ksh
sophie:~# set o emacs ; set o gmacs ; set +o vi
sh: set: gmacs: invalid option name
sophie:~#
Configuring your environment...
LD_LIBRARY_PATH=/usr/lib; export LD_LIBRARY_PATH
sophie:~# ALTDISPLAY=sophie.xxx.de:11; export ALTDISPLAY
sophie:~# TTA_UID="`LANG=C LC_ALL=C id | sed
's/.*uid=\([0-9][0-9]*\).*/\1/'`"; export TTA_UID
sophie:~# find ${TMPDIR:-/tmp}/ -name "TTA_SESSION_TOKEN.$TTA_UID.*" -a !
-mtime 0 -exec rm -f {} ";" -o -type d -prune 2>/dev/null
sophie:~#
TTA_USERNAME='.../_ens/o=Tarantella System Objects/cn=Administrator';
export TTA_USERNAME
sophie:~#
TTA_SESSION_TOKEN="${TMPDIR:-/tmp}/TTA_SESSION_TOKEN.$TTA_UID.$$"; export
TTA_SESSION_TOKEN
sophie:~#
( umask 177; echo '.../_token/"vPchu2G3YtpCFALA+qSxFAO/XQk="' >
"$TTA_SESSION_TOKEN" )
sophie:~#
TTA_PRIMARY_DNSNAME='sophie.xxx.de'; export TTA_PRIMARY_DNSNAME
sophie:~#
TTA_PE_ID=''; export TTA_PE_ID
sophie:~# TTA_CLIENT_IPADDR='192.168.xxx.xx'; export TTA_CLIENT_IPADDR
sophie:~#
TERM=''; export TERM
sophie:~# TTA_PEERDNSNAME='sophie.xxx.de'; export TTA_PEERDNSNAME
sophie:~#
TTA_EXTDNSNAME='sophie.xxx.de'; export TTA_EXTDNSNAME
sophie:~# if [ -f /etc/ttaprinter.conf ]; then . /etc/ttaprinter.conf;
export LPDEST; fi
sophie:~#
Starting the application...
..connected
STATE_PROTOCOL_INIT
Connecting to server...
Connected
Initializing session...
Starting session...
Waiting for application...
Logging application output
./.././bin/bin/ttaxset: unable to open display ""
Exception in thread "main" java.lang.InternalError: Can't connect to X11
window server using ':0.0' as the value of the DISPLAY variable.
     at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
     at
sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:134)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:141)
     at
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
     at java.awt.Window.init(Window.java:231)
     at java.awt.Window.<init>(Window.java:275)
     at java.awt.Frame.<init>(Frame.java:401)
     at java.awt.Frame.<init>(Frame.java:366)
     at javax.swing.JFrame.<init>(JFrame.java:154)
     at
com.sco.tta.admin.gui.RunAdminGui$AdminFrame.<init>(RunAdminGui.java:260)
     at com.sco.tta.admin.gui.RunAdminGui.<clinit>(RunAdminGui.java:68)
Connection to sophie.xxx.de closed.
Some things I noticed:
ALTDISPLAY=sophie.xxx.de:11; export ALTDISPLAY
is set on :11 - but later the message is open :0.0 what does thatmean?
>>>
hope you can help me....
(PS: I also noticed that client IP is set on the IP from my proxy
server... I changed but that has no effect... as expected)

Similar Messages

  • Xclock Error: Can't open display: - after upgrading to openSSH 5.2p1

    I have got two servers apssvrX and apssvrZ on OEL. Both were built by the same team using their standard build scripts.
    Having received the servers I had installed Oracle (ODI) product on it successfully.
    Then as a part of requirement and as per Oracle support's advise, I had upgraded the ssh version on apssvrX server from OpenSSH_4.3p2 To OpenSSH_5.2p1, so that, I can implement the chroot jailing.
    As per Oracle advise, I had downloaded the 3 RPMs from "_http://layer1.rack911.com/openssh/rhel5/x86_64/" to run them on my first server i.e., apssvrX and then configured the sshd services following the below steps:
    a) Modify /etc/ssh/sshd_config to comment the below line:
    #Subsystem sftp /usr/libexec/openssh/sftp-server
    b) Add below lines:
    Subsystem sftp internal-sftp
    Match Group sftponly
    ChrootDirectory %h
    X11Forwarding no
    AllowTcpForwarding no
    ForceCommand internal-sftp
    Then lastly, Restart sshd services complete the configuration
    # /etc/init.d/sshd restart
    apssvrX server current details are as below:
    apssvrX$ uname -a
    Linux apssvrX 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
    apssvrX$ ssh -V
    OpenSSH_5.2p1, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
    My problems started from this point onwards. I want to install another Oracle product using OUI, but when I try to execute xclock using the Exceed HummingBird tool on apssvrX server then it fails with the error - (xclock) Error: Can't open display:
    I tried the DISPLAY variable setup as well but to no use.
    Whereas I can successfully execute the xclock on apssvrZ and OUI as well. Its config details are as below:
    apssvrZ$ uname -a
    Linux apssvrZ 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
    apssvrZ$ ssh -V
    OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
    Please advise the way forward.

    Tried but still same error.
    Affected servers's sshd_config is as below:
    [root@apssvrX]# cat /etc/ssh/sshd_config
    # $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $
    # This is the sshd server system-wide configuration file. See
    # sshd_config(5) for more information.
    # This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin
    # The strategy used for options in the default sshd_config shipped with
    # OpenSSH is to specify options with their default value where
    # possible, but leave them commented. Uncommented options change a
    # default value.
    #Port 22
    Protocol 2
    Protocol 2
    #AddressFamily any
    #ListenAddress 0.0.0.0
    #ListenAddress ::
    # HostKey for protocol version 1
    #HostKey /etc/ssh/ssh_host_key
    # HostKeys for protocol version 2
    #HostKey /etc/ssh/ssh_host_rsa_key
    #HostKey /etc/ssh/ssh_host_dsa_key
    # Lifetime and size of ephemeral version 1 server key
    #KeyRegenerationInterval 1h
    #ServerKeyBits 768
    # Logging
    # obsoletes QuietMode and FascistLogging
    #SyslogFacility AUTH
    SyslogFacility AUTHPRIV
    #LogLevel INFO
    # Authentication:
    #LoginGraceTime 2m
    PermitRootLogin without-password
    #StrictModes yes
    #MaxAuthTries 6
    #RSAAuthentication yes
    #PubkeyAuthentication yes
    #AuthorizedKeysFile .ssh/authorized_keys
    # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
    #RhostsRSAAuthentication no
    # similar for protocol version 2
    #HostbasedAuthentication no
    # Change to yes if you don't trust ~/.ssh/known_hosts for
    # RhostsRSAAuthentication and HostbasedAuthentication
    #IgnoreUserKnownHosts no
    # Don't read the user's ~/.rhosts and ~/.shosts files
    #IgnoreRhosts yes
    # To disable tunneled clear text passwords, change to no here!
    #PasswordAuthentication yes
    #PermitEmptyPasswords no
    PasswordAuthentication yes
    # Change to no to disable s/key passwords
    #ChallengeResponseAuthentication yes
    ChallengeResponseAuthentication no
    # Kerberos options
    #KerberosAuthentication no
    #KerberosOrLocalPasswd yes
    #KerberosTicketCleanup yes
    #KerberosGetAFSToken no
    # GSSAPI options
    #GSSAPIAuthentication no
    GSSAPIAuthentication yes
    #GSSAPICleanupCredentials yes
    GSSAPICleanupCredentials yes
    # Set this to 'yes' to enable PAM authentication, account processing,
    # and session processing. If this is enabled, PAM authentication will
    # be allowed through the ChallengeResponseAuthentication mechanism.
    # Depending on your PAM configuration, this may bypass the setting of
    # PasswordAuthentication, PermitEmptyPasswords, and
    # "PermitRootLogin without-password". If you just want the PAM account and
    # session checks to run without PAM authentication, then enable this but set
    # ChallengeResponseAuthentication=no
    #UsePAM no
    UsePAM yes
    # Accept locale-related environment variables
    AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
    AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
    AcceptEnv LC_IDENTIFICATION LC_ALL
    #AllowTcpForwarding yes
    #GatewayPorts no
    #X11Forwarding no
    X11Forwarding yes
    #X11DisplayOffset 10
    #X11UseLocalhost yes
    #PrintMotd yes
    #PrintLastLog yes
    #TCPKeepAlive yes
    #UseLogin no
    #UsePrivilegeSeparation yes
    #PermitUserEnvironment no
    #Compression delayed
    #ClientAliveInterval 0
    #ClientAliveCountMax 3
    #ShowPatchLevel no
    #UseDNS yes
    #PidFile /var/run/sshd.pid
    #MaxStartups 10
    #PermitTunnel no
    # no default banner path
    #Banner /some/path
    # override default of no subsystems
    Subsystem sftp /usr/libexec/openssh/sftp-server
    ## Commented the sftp jailing configuration
    ##Subsystem sftp internal-sftp
    ##Match Group sftponly
    ## ChrootDirectory %h
    ## X11Forwarding no
    ## AllowTcpForwarding no
    ## ForceCommand internal-sftp

  • X11 remote app and XQuartz and xterm Xt error: Can't open display: %s

    Hi
    I have Snow Leopard  (10.8.4) and XQuartz on it I need to run X11 remote app on redhat.
    On local host echo $DISPLAY shows /tmp/launch-d33HNb/org.macosforge.xquartz:0
    When i do ssh -X (or -Y) [email protected] and try to run xterm i got:
    xterm Xt error: Can't open display: %s
    xterm:  DISPLAY is not set
    the sshd_config on remote host has
    cat /etc/ssh/sshd_config | grep X11
    #X11Forwarding no
    X11Forwarding yes
    X11DisplayOffset 10
    #X11UseLocalhost yes
    Question is do i need to set up DISPLAY variable on remote host?
    If yes which display number do i choose?
    if i do export DISPLAY=<my mac ip>:10.0 or export DISPLAY=<my mac ip>:0.0
    i still have message xterm Xt error: Can't open display: %s
    Maybe this will help also
    ssh -v -v -Y [email protected]
    OpenSSH_5.9p1, OpenSSL 0.9.8x 10 May 2012
    debug1: Reading configuration data /etc/ssh_config
    debug1: /etc/ssh_config line 20: Applying options for *
    debug1: /etc/ssh_config line 53: Applying options for *
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to 172.20.0.12 [172.20.0.12] port 22.
    debug1: Connection established.
    debug1: permanently_set_uid: 0/0
    debug1: identity file /var/root/.ssh/id_rsa type -1
    debug1: identity file /var/root/.ssh/id_rsa-cert type -1
    debug1: identity file /var/root/.ssh/id_dsa type -1
    debug1: identity file /var/root/.ssh/id_dsa-cert type -1
    debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
    debug1: match: OpenSSH_4.3 pat OpenSSH_4*
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_5.9
    debug2: fd 3 setting O_NONBLOCK
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie- hellman-group14-sha1,diffie-hellman-group1-sha1
    debug2: kex_parse_kexinit: [email protected],[email protected],ssh-rsa,[email protected],[email protected],ssh-dss
    debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blow fish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]
    debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blow fish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]
    debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: none,[email protected],zlib
    debug2: kex_parse_kexinit: none,[email protected],zlib
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-g roup1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blow fish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]
    debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blow fish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]
    debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: none,[email protected]
    debug2: kex_parse_kexinit: none,[email protected]
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: mac_setup: found hmac-md5
    debug1: kex: server->client aes128-ctr hmac-md5 none
    debug2: mac_setup: found hmac-md5
    debug1: kex: client->server aes128-ctr hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug2: dh_gen_key: priv key bits set: 110/256
    debug2: bits set: 492/1024
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug1: Server host key: RSA 92:ac:c2:7b:1e:ba:6b:62:9b:32:3e:14:c6:87:a7:59
    debug1: Host '172.20.0.12' is known and matches the RSA host key.
    debug1: Found key in /var/root/.ssh/known_hosts:2
    debug2: bits set: 524/1024
    debug1: ssh_rsa_verify: signature correct
    debug2: kex_derive_keys
    debug2: set_newkeys: mode 1
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug2: set_newkeys: mode 0
    debug1: SSH2_MSG_NEWKEYS received
    debug1: Roaming not allowed by server
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug2: service_accept: ssh-userauth
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug2: key: /var/root/.ssh/id_rsa (0x0)
    debug2: key: /var/root/.ssh/id_dsa (0x0)
    debug1: Authentications that can continue: publickey,gssapi-with-mic,password
    debug1: Next authentication method: publickey
    debug1: Trying private key: /var/root/.ssh/id_rsa
    debug1: Trying private key: /var/root/.ssh/id_dsa
    debug2: we did not send a packet, disable method
    debug1: Next authentication method: password
    [email protected]'s password:
    debug2: we sent a password packet, wait for reply
    debug1: Authentication succeeded (password).
    Authenticated to 172.20.0.12 ([172.20.0.12]:22).
    debug1: channel 0: new [client-session]
    debug2: channel 0: send open
    debug1: Entering interactive session.
    debug2: callback start
    debug2: client_session2_setup: id 0
    debug2: fd 3 setting TCP_NODELAY
    debug2: channel 0: request pty-req confirm 1
    debug1: Sending environment.
    debug2: channel 0: request shell confirm 1
    debug2: callback done
    debug2: channel 0: open confirm rwindow 0 rmax 32768
    debug2: channel_input_status_confirm: type 99 id 0
    debug2: PTY allocation request accepted on channel 0
    debug2: channel 0: rcvd adjust 2097152
    debug2: channel_input_status_confirm: type 99 id 0
    debug2: shell request accepted on channel 0
    Last login: Thu Jun  6 09:12:43 2013 from 172.20.0.17
    [root@npecdp01 ~]#

    Jeffrey Jones2 wrote:
    I'm always looking for new tricks of the trade.
    I remember now why I originally changed the ssh config file. Here is another trick: In a text editor, type
    ssh://[email protected]
    making the obvious substitutions. Select the line and drag it to the Desktop. It will create an inetloc file that, when double-clicked, opens a Terminal window and connects to the ssh session. I have several of these in my Dock.
    That is a neat trick. However, with LaunchPad I'm not much of a Finder double-clicker anymore. What is interesting is that the OS knows how to handle the ssh protocol. You can also type "open ssh://[email protected]" for the same effect. That may not seem like much of a gain, but it reveals some interesting OS-level possibilities.
    With an RSA key, I don't even need a password
    You can use the newer DSA keys. There is another neat trick too. Pretty much every set of instructions I've seen online suggests using an empty private key password because running ssh-agent is such a hassle on Linux. It is built-in to OS X. So, on OS X, you can create more secure DSA private keys with pass phrases that are stored (and encrypted) in your keychain. You only have to supply the Then, even if someone gets your private keys, they get nothing.

  • Can't open display

    hi.
    I can't open xwindows with another user than root, under my solaris 10 x86.
    I checked the config, tried lots of things (set a display for my user, put /usr/openwin/bin in PATH,etc), but still the same:
    Xlib: connection to localhost: 0.0 refused by server
    Xlib: no protocol specified
    Error: can't open display
    Please help me :)

    That s ok I found.
    You just need to do as follows:
    root@localhost: xhost + localhost
    root@localhost: su - myUser
    myUser@localhost: export DISPLAY=localhost:0
    myUser@localhost: xclock &
    :)

  • Can't Open Display localhost:0.0

    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.0
    I then run xclock and get the following error -
    Xlib: connection to "{+ipaddress+}:0.0" refused by server
    Xlib: No protocol specified
    Error: Can't open display: {+ipaddress+}:0.0
    The strange thing is that on my bosses pc (who has got almost the exact same setup ie. PuTTy & Xming) is works perfectly.
    Please help.
    Thanx in advance.

    You normally enter the xhost command in a XTerm window, or you can start Xming with the -ac parameter which disables access control (not recommend). You don't need to use xhost if you make a SSH connection, but from the information you provided it is not possible to determine.
    Perhaps the following link will be useful for you: http://www.straightrunning.com/XmingNotes/trouble.php

  • Error can't open display after reboot

    Hi,
    I encounter this problem :
    I just install SSGD 4.2 on Solaris 10 01/06 T2000 server. After installation I can connect to the SSGD using browser from my notebook, and can try the various demo (dtterm, xclock etc)
    I reboot the Solaris 10 OS.
    After reboot I tried to login again via browser in my notebook and try to run the various demo.
    I can login, but almost all the demo failed to execute, the X applications give error "can't open display:" with no hostname following the error.
    The only demo still runs is the vt420 demo
    Anybody can help me to point out what causes the problem ? I am trying to demo this SSGD software to a customer.
    Regards
    Adrianus B. Kurnadi

    I've noticed this as well, under Solaris 10 FCS, Solaris 10 U1, and Solaris Express nv_39.
    However, I have tried it out under S8 02/04, and S9 09/04 and I do not have this problem after rebooting the host at all.
    For the hell of it, I (rather badly) converted the S89/S90 startup scripts to be SMF manifests with S90Tarantella having a dependancy on tS89TarantellaWebServer as I thought perhaps there was a strange issue with the tta process starting before the web service had fully started (beats me why it would matter, ends up it didn't) - as my test S10 host is a slow Netra T1.
    I'd be interested to know what the difference is between it being started up via an rc2.d script and the root user logging into the system console running /opt/tarantella/bin/tarantella start. I haven't even bothered starting to try to observe the environment differences between startup via SMF in S10 and init.d in S8.
    </2.2c>
    Andrew

  • Error can't open display while installation

    Hi,
    While installting oracle, i am unable to launch the oracle universal installer. I have already set the DISPLAY value to IPAddress.
    I am installing it from ora<sid>, it asking about xlock. When i am running it from root, i am able to open up xclock. But i am unable to open up xclock from ora<sid>. It is giving error as error: can't open display.
    Please suggest the solution.
    Regards
    Karunakar

    Hello,
    It already solved!
    What I did was:
    Open a new Term. session.
    Under root user I ran
    #xhost + *
    (this enables the X window for all users)
    Then I don´t needed to set the Display variable with the value  user within that Term. session.
    #echo $DISPLAY
    #:0.0
    ... then I test xclock to validate the display functionality and then I start oracle wizard installation with command
    #./RUNINSTALLER
    The oracle installation finish without problems! 
    Best regards,
    João Dimas - Portugal

  • Error: Can't open display: localhost:0.0

    Hi all,
    Please help to solve the problem of x display, thanks a lot!
    $DISPLAY=localhost:0.0; export DISPLAY
    $xhost +sky
    xhost: unable to open display "localhost:0.0"
    $xclock
    Error: Can't open display: localhost:0.0
    Vivia/en

    reboot
    or
    using xmanager tool

  • Xterm: Xt error: Can't open display: xterm: DISPLAY is not set

    Hello, I am completely new to networking/systems. I have been asked to complete an open flow tutorial ( http://www.openflow.org/wk/index.php/OpenFlow_Tutorial ) I have fininshed a part of the tutorial and when i used "ssh -X [email protected]**.*", I was able to log in successfully but when i type in Xterm, it says "xterm: Xt error: Can't open display: xterm: DISPLAY is not set". I have downloaded virtual box, XQuartz and an ovf file as given in teh tutorial. I don't know what the problem is. Can someone please guide me through this? Thank you so much!

    I didn't quite understand what you were saying but when i typed "ssh -Y ..." this is what happened:
    mobile-172-16-103-167:~ mininet$ ssh -Y [email protected]
    Password:
    Last login: Sat May 18 20:25:50 2013 from 192.168.56.1
    mobile-172-16-103-167:~ mininet$
    ssh -X and ssh -Y do essentially the same thing. -Y is just less restrictive on X11 return traffic authority (basically it tells the local X11 display server that you trust the remote system sending X11 traffic to it).
    Now what you are display seems strange.  You prompt implies that your current system's IP address is 172.16.103.167 and you are ssh'ing to 192.168.56.1.  You get a password prompt as expected, but then the "Last Login" messages says you are coming from 192.168.56.1, which is should be where you are coming, but that it the address you are trying to ssh to.  And then to top it off, you command line prompt has not changed.
    So I'm wondering if 192.168.56.1 is the same system you are currently using, but just a different account on that system?
    Is this true?
    Also your prompt implies you were logged into the 'mininet' account when you issued the ssh -Y command to login to the 'mininet' account on 192.168.56.1.
    Or is it possible that you are loosing track of which system and account you are current remotely logged into?

  • Exceed : Error: Can't open display

    Trying to install SAP with sapinst on AIX 6.1 , after launching exceed , and exporting the display variable , when try xclock , get the following error
    ladksapdk33:/root # export DISPLAY=XXX.XX.XXX.XXX:2.0
    adksapdk33:/root # xclock
    Error: Can't open display: XXX.XX.XXX.XXX:2.0
    Any one has any clue ? Please help

    Abu Al MAmun wrote:
    > ladksapdk33:/root # export DISPLAY=XXX.XX.XXX.XXX:2.0
    > adksapdk33:/root # xclock
    > Error: Can't open display: XXX.XX.XXX.XXX:2.0
    Verify this IP
    Thanks

  • [Solved] [Macbook 9,2] xrandr - "Can't open display"

    Hi,
    after a long time Arch Linux runs on my Macbook!
    Now I need an X-Server. After a while it runs too.
    But I can't load i3.
    When I starting it with:
    xinit i3
    i3 display: "ERROR: No outputs found via RandR, disabling"
    When I use xrandr in commandline, it show's:
    "Can't open display"
    How can I fix it?
    Last edited by DasLampe (2012-09-25 19:29:51)

    When you say you get that error in commandline, do you mean a tty without X running?  If so, that is the expected result.
    Not that this is part of a solution, but it may refocus on the problem: X/i3 is failing to start properly, this may not actually be related to xrandr.
    As a test, have you / can you try starting the twm session described in the beginners guide?  Does that work?
    Then please post your ~/.xinitrc.

  • VERY annoying thing with XServer "Can't open display" after a while

    This issue is *very* annoying I would love if someone could help.
    I had this issue for a long time, thinking I'll fix it. I googled, but everybody seems to have the same problem, but no fix (only temporary ones).
    So here's the problem : I installed archlinux on my (very old) laptop, everything works great, now I even installed the XServer, which however is causing this problem:
    everything works good for a while, but after a while, I can't launch any new programs, but existing ones work good... If I try to start any X-App in an already running terminal, it gives me:
    No protocol specified
    xterm Xt error: Can't open display: :0.0
    However, all already running apps run fine, they even can create new windows!
    The only fix I found for this is to kill & restart the xserver with ctrl+alt+backspace.
    Here's my xorg.conf:
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "ServerFlags"
    Option "AutoAddDevices" "False"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "extmod"
    Load "xtrap"
    Load "glx"
    Load "dbe"
    Load "dri"
    Load "freetype"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "probe_sparse" # [<bool>]
    #Option "accel" # [<bool>]
    #Option "crt_display" # [<bool>]
    #Option "composite_sync" # [<bool>]
    #Option "hw_cursor" # [<bool>]
    #Option "force_pci_mode" # [<bool>]
    #Option "dma_mode" # <str>
    #Option "agp_mode" # <i>
    #Option "agp_size" # <i>
    #Option "local_textures" # [<bool>]
    #Option "buffer_size" # <i>
    #Option "tv_out" # [<bool>]
    #Option "tv_standard" # <str>
    #Option "mmio_cache" # [<bool>]
    #Option "test_mmio_cache" # [<bool>]
    #Option "panel_display" # [<bool>]
    #Option "reference_clock" # <freq>
    #Option "shadow_fb" # [<bool>]
    #Option "sw_cursor" # [<bool>]
    #Option "AccelMethod" # <str>
    #Option "RenderAccel" # [<bool>]
    Identifier "Card0"
    Driver "mach64"
    VendorName "ATI Technologies Inc"
    BoardName "3D Rage LT Pro"
    BusID "PCI:0:5:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Here's lspci of my VGA controller (this is probably irrelevant, because people will all sorts of hw have this problem, but here it is anyway):
    [x@y ~]$ lspci | grep VGA
    00:05.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro (rev dc)
    XServ version:
    X.Org X Server 1.5.3
    Release Date: 5 November 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.27-ARCH i686
    Current Operating System: Linux 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8 10:13:45 UTC 2009 i686
    Build Date: 17 December 2008 08:20:05PM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    I would be grateful if somebody could help me.

    Just to let you know, I updated X to the latest version right now.
    Here's the new output of X -version:
    X.Org X Server 1.6.1
    Release Date: 2009-4-14
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.29-ARCH i686
    Current Operating System: Linux 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8 10:13:45 UTC 2009 i686
    Build Date: 15 April 2009 11:09:10AM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.

  • [fvwm][main]: ERROR can't open display :1

    I can start a second xfce (session?) in a tty while I have a normal xfce session running in tty10, by logging into the tty and designating an alternative display.  example:
    $ startxfce4 -- :1
    Now I'm playing around with fvwm and trying to start it in a tty with xfce running in tty10, per the command and error below:
    $ fvwm -d :1
    [fvwm][main]: <<ERROR>> can't open display :1
    I've tried find a solution with no luck. How would I start fvwm in a tty?

    You have to start another X session.  Perhaps xfce hides this fact from you by bundling all that in the startxfce4 script, but any other window manager requires X to already be running.
    Use startx/xinit -- :1
    You can create conditional entries in your xinitrc so you could do `xinit fvwm -- :1`
    Edit: As I don't use fvwm you can test and confirm what I am suggesting by trying to start fvwm from a tty even in the default display before any other x session is running.  Calling just `fvwm` from a terminal should fail.
    Last edited by Trilby (2012-09-17 01:31:28)

  • "xrdb: Can't open display" error

    After the text from the bootup process I get error:
    xrdb: Can't open display ''
    img=error message.   
    After this startx and autologin works fine. 
    I can ignore this message, but still want to solve this, how can I do this?
    moderator edit (ewaller) converted image tags to over sized image to a url link in accorance with our policy.
    Last edited by pgiback (2014-07-28 17:03:22)

    I connected as root, from the tty tried to "xrdb /home/user/.Xresources" and got same "xrdb: Can't open display" message. 
    My .Xresources:
    ! Removes gap around terminal -- this one is a must!!!
    xterm*internalBorder: 6
    xterm*loginShell: true
    xterm*saveLines: 2000
    ! Revome boarder
    xterm*borderWidth: 0
    ! Double click to select a word
    xterm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48
    ! Clipboard -- thus one is a must
    xterm*VT100.translations: #override <Btn1Up>: select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0)
    ! Font
    xterm*faceName: Vera Mono
    xterm*faceSize: 10
    ! Can remove these - dont know what changes
    xterm*vt100*geometry: 80x60
    xterm*termName: xterm-color
    xterm*eightBitInput: false
    ! DOS-box colours...
    xterm*background: rgb:08/0c/11
    xterm*foreground: rgb:b9/84/00
    xterm*color0: rgb:00/00/00
    xterm*color1: rgb:d3/62/65
    xterm*color2: rgb:ae/ce/91
    xterm*color3: rgb:e7/e1/8c
    xterm*color4: rgb:7a/7a/b0
    xterm*color5: rgb:96/3c/59
    xterm*color6: rgb:41/81/79
    xterm*color7: rgb:20/24/28
    xterm*color8: rgb:66/66/66
    xterm*color9: rgb:ef/81/71
    xterm*color10: rgb:e5/f7/79
    xterm*color11: rgb:ff/f7/99
    xterm*color12: rgb:41/86/be
    xterm*color13: rgb:ef/9e/be
    xterm*color14: rgb:20/24/28
    xterm*color15: rgb:ff/ff/ff
    ! replaze bold
    xterm*boldMode: false
    xterm*colorBDMode: true
    xterm*colorBD: rgb:82/a4/d3
    ! Do not underscore text, underlined text is white.
    xterm*colorULMode: true
    xterm*colorUL: rgb:e4/e4/e4
    Edit: I am adding my dwm config.h as I started to get these errors same day as I tried to modify my config.h
    /* appearance */
    static const char font[] = "-*-terminus-medium-r-*-*-16-*-*-*-*-*-*-*";
    static const char normbordercolor[] = "#444444";
    static const char normbgcolor[] = "#222222";
    static const char normfgcolor[] = "#bbbbbb";
    static const char selbordercolor[] = "#111111";
    static const char selbgcolor[] = "#005577";
    static const char selfgcolor[] = "#eeeeee";
    static const unsigned int borderpx = 1; /* border pixel of windows */
    static const unsigned int snap = 32; /* snap pixel */
    static const Bool showbar = True; /* False means no bar */
    static const Bool topbar = True; /* False means bottom bar */
    /* tagging */
    static const char *tags[] = { "term", "vim", "work", "web", "misc"};
    static const Rule rules[] = {
    /* class instance title tags mask isfloating monitor */
    { "Firefox", NULL, NULL, 1 << 3, True, -1 },
    /* layout(s) */
    static const float mfact = 0.55; /* factor of master area size [0.05..0.95] */
    static const int nmaster = 1; /* number of clients in master area */
    static const Bool resizehints = True; /* True means respect size hints in tiled resizals */
    static const Layout layouts[] = {
    /* symbol arrange function */
    { "[]=", tile }, /* first entry is default */
    { "><>", NULL }, /* no layout function means floating behavior */
    { "[M]", monocle },
    /* key definitions */
    #define MODKEY Mod4Mask
    #define TAGKEYS(KEY,TAG) \
    { MODKEY, KEY, view, {.ui = 1 << TAG} }, \
    { MODKEY|ControlMask, KEY, toggleview, {.ui = 1 << TAG} }, \
    { MODKEY|ShiftMask, KEY, tag, {.ui = 1 << TAG} }, \
    { MODKEY|ControlMask|ShiftMask, KEY, toggletag, {.ui = 1 << TAG} },
    /* helper for spawning shell commands in the pre dwm-5.0 fashion */
    #define SHCMD(cmd) { .v = (const char*[]){ "/bin/sh", "-c", cmd, NULL } }
    /* commands */
    static const char *dmenucmd[] = { "dmenu_run", "-fn", font, "-nb", normbgcolor, "-nf", normfgcolor, "-sb", selbgcolor, "-sf", selfgcolor, NULL };
    static const char *terminal[] = { "xterm", NULL };
    static const char *browser[] = { "firefox-nightly", NULL};
    static const char *vim[] = { "xterm", "-title", "vim", "-e", "vim", NULL };
    static const char *news[] = { "xterm", "-title", "newsbeuter", "-e", "newsbeuter", NULL };
    static const char *music[] = { "xterm", "-title", "mocp", "-e", "mocp", NULL };
    static Key keys[] = {
    /* modifier key function argument */
    { MODKEY, XK_p, spawn, {.v = dmenucmd } },
    { MODKEY, XK_space, spawn, {.v = terminal } },
    { MODKEY, XK_a, spawn, {.v = browser } },
    { MODKEY, XK_q, spawn, {.v = vim } },
    { MODKEY, XK_s, spawn, {.v = news } },
    { MODKEY, XK_x, spawn, {.v = music } },
    { MODKEY, XK_b, togglebar, {0} },
    { MODKEY, XK_j, focusstack, {.i = +1 } },
    { MODKEY, XK_k, focusstack, {.i = -1 } },
    { MODKEY, XK_i, incnmaster, {.i = +1 } },
    { MODKEY, XK_d, incnmaster, {.i = -1 } },
    { MODKEY, XK_h, setmfact, {.f = -0.05} },
    { MODKEY, XK_l, setmfact, {.f = +0.05} },
    { MODKEY, XK_Return, zoom, {0} },
    { MODKEY, XK_Tab, view, {0} },
    { MODKEY|ShiftMask, XK_c, killclient, {0} },
    { MODKEY, XK_t, setlayout, {.v = &layouts[0]} },
    { MODKEY, XK_f, setlayout, {.v = &layouts[1]} },
    { MODKEY, XK_m, setlayout, {.v = &layouts[2]} },
    { MODKEY|ShiftMask, XK_space, setlayout, {0} },
    { MODKEY, XK_0, view, {.ui = ~0 } },
    { MODKEY|ShiftMask, XK_0, tag, {.ui = ~0 } },
    { MODKEY, XK_comma, focusmon, {.i = -1 } },
    { MODKEY, XK_period, focusmon, {.i = +1 } },
    { MODKEY|ShiftMask, XK_comma, tagmon, {.i = -1 } },
    { MODKEY|ShiftMask, XK_period, tagmon, {.i = +1 } },
    TAGKEYS( XK_1, 0)
    TAGKEYS( XK_2, 1)
    TAGKEYS( XK_3, 2)
    TAGKEYS( XK_4, 3)
    TAGKEYS( XK_5, 4)
    { MODKEY|ShiftMask, XK_q, quit, {0} },
    /* button definitions */
    /* click can be ClkLtSymbol, ClkStatusText, ClkWinTitle, ClkClientWin, or ClkRootWin */
    static Button buttons[] = {
    /* click event mask button function argument */
    { ClkLtSymbol, 0, Button1, setlayout, {0} },
    { ClkLtSymbol, 0, Button3, setlayout, {.v = &layouts[2]} },
    { ClkWinTitle, 0, Button2, zoom, {0} },
    { ClkStatusText, 0, Button2, spawn, {.v = terminal } },
    { ClkClientWin, MODKEY, Button1, movemouse, {0} },
    { ClkClientWin, MODKEY, Button2, togglefloating, {0} },
    { ClkClientWin, MODKEY, Button3, resizemouse, {0} },
    { ClkTagBar, 0, Button1, view, {0} },
    { ClkTagBar, 0, Button3, toggleview, {0} },
    { ClkTagBar, MODKEY, Button1, tag, {0} },
    { ClkTagBar, MODKEY, Button3, toggletag, {0} },
    Last edited by pgiback (2014-07-28 18:16:39)

  • [fixed] can not open display :0?

    I don't know which part cause this error, I'm using KDE and intel's driver, everty time I boot the system, run an application, it will fail with "cannot open display". Then I need to log out and log in, then every thing will fine.
        And sometime the system will freeze when wake up from sleep state, lock screen's background is displayed but no password input dialog.
    These issues is quite similar, but I just don't know where they are from. But at least this is a system issue, not a single application.
    Last edited by ThomasKing0529 (2014-10-07 03:49:35)

    Sorry to reply so late
    Yeah, it's now definitely a problem, every time I start system, then every application won't open with this error. And just as I explained, they all tell me they can't open display or just with another message: "No protocol specified". The first time I see this error message is when I install VMware Player.
    And now the details of this problem: it will appear after entering KDE desktop, and cause everything with GUI(Qt or Gtk) failed to run. This is not a problem raised immediately: Cause I can run Konsole at first, but then everything including Konsole will not run.
    As root privilege cause this problem, and I use sudo to connect to network, maybe this is a bug of Konsole?
    Seems not, cause I can get out of this by re-login, this must be a bug of KDE anyway. 
    That's all I can supply. In fact, I'm really confused by this problem. And horribly, I'm being used to this problem, I'm being used to log out and log in to get out of this problem.
    Maybe this is why I forgot to reply this post, sorry again for this.

  • Putty xming Can't open display

    Yes I have googled and went through all Xming trouble? pages. Thanks for asking.
    I have a arch box called janus and a xp workstation japetus
    on janus /etc/ssh/sshd_config have
    X11Forwarding yes
    X11DisplayOffset 10
    X11UseLocalhost yes
    on japetus installed: Putty 0.60, under Connection|SSH|X11|Enable X11 forwarding is switched on the X display location is: localhost:0, with MIT-Magic-Cookie-1 protocol
    on japetus installed: Xming 6.9.0.31
    there is no firewall running on japetus
    on japetus started Xlaunch and left Display number: 0
    on japetus fired up putty and connected to janus. Contrary to recommend the DISPLAY var is not set, so:
    on janus:
    export DISPLAY=localhost:0
    echo $DISPLAY returns localhost:0 so that is in order
    on janus: xlock &
    result
    Error: Can't open display: localhost:0
    I've been over these settings over and over and am not able to get it working. It must be a small simple oversight

    Logs as attached.
    debug1: sshd version OpenSSH_5.8p1
    debug1: read PEM private key done: type RSA
    debug1: private host key: #0 type 1 RSA
    debug1: read PEM private key done: type DSA
    debug1: private host key: #1 type 2 DSA
    debug1: read PEM private key done: type ECDSA
    debug1: private host key: #2 type 3 ECDSA
    debug1: rexec_argv[0]='/usr/sbin/sshd'
    debug1: rexec_argv[1]='-d'
    Set /proc/self/oom_score_adj from 0 to -1000
    debug1: Bind to port 22 on 0.0.0.0.
    Server listening on 0.0.0.0 port 22.
    debug1: Bind to port 22 on ::.
    Server listening on :: port 22.
    debug1: Server will not fork when running in debugging mode.
    debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
    debug1: inetd sockets after dupping: 3, 3
    Connection from 192.168.2.1 port 4556
    debug1: Client protocol version 2.0; client software version PuTTY_Release_0.60
    debug1: no match: PuTTY_Release_0.60
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_5.8
    debug1: permanently_set_uid: 99/99
    debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: client->server aes256-ctr hmac-sha1 none
    debug1: kex: server->client aes256-ctr hmac-sha1 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received
    debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
    debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: KEX done
    debug1: userauth-request for user root service ssh-connection method none
    debug1: attempt 0 failures 0
    debug1: PAM: initializing for "root"
    debug1: PAM: setting PAM_RHOST to "192.168.2.1"
    debug1: PAM: setting PAM_TTY to "ssh"
    debug1: userauth-request for user root service ssh-connection method password
    debug1: attempt 1 failures 0
    debug1: PAM: password authentication accepted for root
    debug1: do_pam_account: called
    Accepted password for root from 192.168.2.1 port 4556 ssh2
    debug1: monitor_child_preauth: root has been authenticated by privileged process
    debug1: PAM: establishing credentials
    debug1: Entering interactive session for SSH2.
    debug1: server_init_dispatch_20
    debug1: server_input_channel_open: ctype session rchan 256 win 16384 max 16384
    debug1: input_session_request
    debug1: channel 0: new [server-session]
    debug1: session_new: session 0
    debug1: session_open: channel 0
    debug1: session_open: session 0: link with channel 0
    debug1: server_input_channel_open: confirm session
    debug1: server_input_channel_req: channel 0 request x11-req reply 1
    debug1: session_by_channel: session 0 channel 0
    debug1: session_input_channel_req: session 0 req x11-req
    debug1: server_input_channel_req: channel 0 request pty-req reply 1
    debug1: session_by_channel: session 0 channel 0
    debug1: session_input_channel_req: session 0 req pty-req
    debug1: Allocating pty.
    debug1: session_pty_req: session 0 alloc /dev/pts/0
    debug1: server_input_channel_req: channel 0 request shell reply 1
    debug1: session_by_channel: session 0 channel 0
    debug1: session_input_channel_req: session 0 req shell
    debug1: Setting controlling tty using TIOCSCTTY.
    debug1: Received SIGCHLD.
    debug1: session_by_pid: pid 5077
    debug1: session_exit_message: session 0 channel 0 pid 5077
    debug1: session_exit_message: release channel 0
    debug1: session_pty_cleanup: session 0 release /dev/pts/0
    debug1: session_by_channel: session 0 channel 0
    debug1: session_close_by_channel: channel 0 child 0
    debug1: session_close: session 0 pid 0
    debug1: channel 0: free: server-session, nchannels 1
    Connection closed by 192.168.2.1
    debug1: do_cleanup
    debug1: PAM: cleanup
    debug1: PAM: closing session
    debug1: PAM: deleting credentials
    Transferred: sent 3664, received 2008 bytes
    Closing connection to 192.168.2.1 port 4556

Maybe you are looking for

  • Sneak Preview Installation issue

    Hi, I'm trying to install the NW sneak preview 04 and it hangs on step 22 of 33. I have java 1.4.2_10 installed and it's running at 97 - 100% cpu capacity. There are no errors or warnings in the logs. Any help is appreciated! - Rao

  • Internal table with header line

    Hi All,      I want to declare a internal table with headerline as page attribute.      i am having to fields in the internal table ( firstname and lastname ). how to do that? helpful answers will be rewarded. Regards, Azaz Ali.

  • Slideshow file sequence number

    Most of my slideshows use a text box displaying file # and total # of files. Used to work fine with 1.0, shows only blanks with LR 1.1. Whath used to display text like : "Photo 1 of 25", now comes up as "Photo of " Do I need to change something ? I t

  • Telnettin' Java-Style

    Hello! Ok, here's a question, perhaps a dooozee for U ... ;-) I'd like to telnet a server, in the terminal, that's easy, enter "telnet my.server.org 1400" and you're in, type user and pass and rummage around. However, you are INTO the telnet session,

  • My charger won't go in all the way

    So, I got my iPad 2 months ago, but I just notice know that it is not going in all the way, buy comparing it from my brothers iPad 2. When I charge my iPad 2  I can like take on side press on it and the other side pops up and does not charge, but it