Tag Info

New answers tagged

0

I do not believe these warnings are usually significant. As I understand it they are verbose complaints made by GTK for varied reasons --- I don't think they are application-specific warnings. A sample from my end if I launch Nautilus from my terminal: (nautilus:26464): Gtk-WARNING **: Failed to register client: ...


0

If you use the -vte argument to cat, it will escape the terminal codes. e.g. cat -vte myfile


0

Using Jander's rule, I was able to access my USB serial adapter... but only if running PuTTY as root. Modifying the rule to specify different permissions allowed me to access it by any user. I.E. SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", MODE="0666", SYMLINK+="serial"


0

@ Archemar : Since the ultimate goal was to install DB2 on remote AIX server, I was hoping that if my method was wrong, someone would show me a way other than X11, so the title is correct. Here is how I solved the problem: I went to the place where Xming was installed, i.e. C:\Program Files (x86)\Xming in my case I edited the X0.hosts file. It originally ...


0

After rereading and editing your post, I believe you are confusing your Local Machine with your Remote Connection. XMing does not install an XServer on AIX as AIX has it's own XServer. The Instructions below will give you a command line interface that will work, but you'll get no wizard. Remove Putty Remove Xming Remove Cygwin Install Cygwin Use SSH ...


0

when you run xming, you have to specify a local display number e.g. 1234 (first screen) no access control (before last screen) when you run putty in connexion -> ssh -> X11, enable X11 forawding set X display location to localhost:1234.0 (this tell putty to forward X11 to Xming) It is best not to set DISPLAY. By the way, this looks rather an ...


5

It is not possible. You will have to end this login session by Ctrl-D and start all over with a new ssh session. For your use (putty) it might be noteworthy that - if you insist on autheticiation by username/password and not using keyfiles - it still saves a little time to save a session profile for easy later use. The host name (or IP address) can be ...


0

From the debug server log you shared it looks like the key you specified on the client side just does not match any of available in /testuser/.ssh/authorized_keys if /testuser/.ssh/authorized_keys is the expected location you should check that there is a public key line there that matches your private key used on client side - that is if you use say, id_rsa ...



Top 50 recent answers are included