Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Rdesktop failed to open keymap common#015 Post 302372435 by lokeshsingla on Wednesday 18th of November 2009 02:43:34 AM
Old 11-18-2009
Can you explain this in bit more detail...
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Failed to open output file Error

Hi guys, I Have written a script,In that it will call another file which contains the sql quaries. while wxecuting that I am getting the below exception 01/16|06:28:06:16800: Operating System Error|Failed to open output file Can anybody help me about this,,Its urgent (0 Replies)
Discussion started by: Anji
0 Replies

2. Solaris

libCstd.so.1: open failed

Morning all, I have a problem with a Sun workstation which is running Solaris 8. When I attempt to open an application, the executable fails with this message : "fatal: libcstd.so.1: open failed: No such file or directory" It was suggested to me that I need to add these patches to fix the... (4 Replies)
Discussion started by: AndyD
4 Replies

3. Solaris

Error:: libm.so.2:open failed

Hi, I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command ./p4v after that it is giving the error--- ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory Killed I am not... (3 Replies)
Discussion started by: smartgupta
3 Replies

4. Solaris

Solaris10..Open boot diagnostic failed

Hi all, when am rebooting the server (SF v890) we are facing "open boot diagnostic failed". Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies

5. Solaris

libucb.s0.1: open failed...

Hi all. I try to start an application, but libucb.so1 is missing. # appl23 # appl23ld.so.1: appl23: fatal: libucb.so1: open failed: No such file or directory killed # # ldd appl23 libXm.so.3 => /usr/lib/libXm.so.3 libMrm.so.3 => /usr/lib/libMrm.so.3 ... (14 Replies)
Discussion started by: wolfgang
14 Replies

6. Ubuntu

Failed to install Common Array Manager in Ubuntu

Dear All, I have a problem installing SUN CAM on my laptop running Ubuntu 9.04 The error message is : Failed when detecting Sun StorageTek(TM) Common Array Manager Core Components : Could not convert Pkg version : For input string: "" Any idea why? Best regards (0 Replies)
Discussion started by: frankoko
0 Replies

7. UNIX for Dummies Questions & Answers

NDM: Source file open failed. Error= 2

Hi, I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder? Source file open failed. Error= 2 Regards, Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies

8. Red Hat

rpmdb open failed

Hi, # yum --skip-broken -y update rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies

9. Solaris

Sendmai l: libssl.so.0.9.7: open failed

Hey for some reason I think I deleted a critical file for sendmail. I was looking the log file on /var/log/cron for cron, and the file isn't there and I found out the reason why is because I'm missing libssl.so.0.9.7. Im running Solaris 11. I checked smtp and got the following: #svcs -xv... (3 Replies)
Discussion started by: picolin
3 Replies

10. UNIX for Beginners Questions & Answers

Rdesktop - ERROR: Failed to open keymap en-us

I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working. I see this on the console: ERROR: Failed to open keymap en-us The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
Discussion started by: agentrnge
1 Replies
rdesktop(1)						      General Commands Manual						       rdesktop(1)

NAME
rdesktop - Remote Desktop Protocol client SYNOPSIS
rdesktop [options] server[:port] DESCRIPTION
rdesktop is a client for Remote Desktop Protocol (RDP), used in a number of Microsoft products including Windows NT Terminal Server, Win- dows 2000 Server, Windows XP and Windows 2003 Server. OPTIONS
-u <username> Username for authentication on the server. -d <domain> Domain for authentication. -s <shell> Startup shell for the user - starts a specific application instead of Explorer. -c <directory> The initial working directory for the user. Often used in combination with -s to set up a fixed login environment. -p <password> The password to authenticate with. Note that this may have no effect if "Always prompt for password" is enabled on the server. WARNING: if you specify a password on the command line it may be visible to other users when they use tools like ps. Use -p - to make rdesktop request a password at startup (from standard input). -n <hostname> Client hostname. Normally rdesktop automatically obtains the hostname of the client. -k <keyboard-map> Keyboard layout to emulate. This requires a corresponding keymap file to be installed. The standard keymaps provided with rdesktop follow the RFC1766 naming scheme: a language code followed by a country code if necessary - e.g. en-us, en-gb, de, fr, sv, etc. The default keyboard map depends on the current locale (LC_* and LANG environment variables). If the current locale is unknown, the default keyboard map is en-us (a US English keyboard). The keyboard maps are file names, which means that they are case sensitive. The standard keymaps are all in lowercase. The keyboard maps are searched relative to the directories $HOME/.rdesktop/keymaps, KEYMAP_PATH (specified at build time), and $CWD/keymaps, in this order. The keyboard-map argument can also be an absolute filename. The special value `none' can be used instead of a keyboard map. In this case, rdesktop will guess the scancodes from the X11 event key codes using an internal mapping method. This method only supports the basic alphanumeric keys and may not work properly on all platforms so its use is discouraged. -g <geometry> Desktop geometry (WxH). If geometry is the special word "workarea", the geometry will be fetched from the extended window manager hints property _NET_WORKAREA, from the root window. The geometry can also be specified as a percentage of the whole screen, e.g. "-g 80%". If the specified geometry depends on the screen size, and the screen size is changed, rdesktop will automatically reconnect using the new screen size. This requires that rdesktop has been compiled with RandR support. -f Enable fullscreen mode. This overrides the window manager and causes the rdesktop window to fully cover the current screen. Fullscreen mode can be toggled at any time using Ctrl-Alt-Enter. -b Force the server to send screen updates as bitmaps rather than using higher-level drawing operations. -A Enable SeamlessRDP. In this mode, rdesktop creates a X11 window for each window on the server side. This mode requires the Seamless- RDP server side component, which is available from http://www.cendio.com/seamlessrdp/. When using this option, you should specify a startup shell which launches the desired application through SeamlessRDP. Example: rdesktop -A -s 'seamlessrdpshell notepad'. -B Use the BackingStore of the Xserver instead of the integrated one in rdesktop. -e Disable encryption. This option is only needed (and will only work) if you have a French version of NT TSE. -E Disable encryption from client to server. This sends an encrypted login packet, but everything after this is unencrypted (including interactive logins). -m Do not send mouse motion events. This saves bandwidth, although some Windows applications may rely on receiving mouse motion. -C Use private colourmap. This will improve colour accuracy on an 8-bit display, but rdesktop will appear in false colour when not focused. -D Hide window manager decorations, by using MWM hints. -K Do not override window manager key bindings. By default rdesktop attempts to grab all keyboard input when it is in focus. -S <button size> Enable single application mode. This option can be used when running a single, maximized application (via -s). When the minimize button of the windows application is pressed, the rdesktop window is minimized instead of the remote application. The maxi- mize/restore button is disabled. For this to work, you must specify the correct button size, in pixels. The special word "standard" means 18 pixels. -T <title> Sets the window title. The title must be specified using an UTF-8 string. -N Enable numlock syncronization between the Xserver and the remote RDP session. This is useful with applications that looks at the numlock state, but might cause problems with some Xservers like Xvnc. -X <windowid> Embed rdesktop-window in another window. The windowid is expected to be decimal or hexadecimal (prefixed by 0x). -a <bpp> Sets the colour depth for the connection (8, 15, 16, 24 or 32). More than 8 bpp are only supported when connecting to Windows XP (up to 16 bpp) or newer. Note that the colour depth may also be limited by the server configuration. The default value is the depth of the root window. -z Enable compression of the RDP datastream. -x <experience> Changes default bandwidth performance behaviour for RDP5. By default only theming is enabled, and all other options are disabled (corresponding to modem (56 Kbps)). Setting experience to b[roadband] enables menu animations and full window dragging. Setting experience to l[an] will also enable the desktop wallpaper. Setting experience to m[odem] disables all (including themes). Experi- ence can also be a hexidecimal number containing the flags. -P Enable caching of bitmaps to disk (persistent bitmap caching). This generally improves performance (especially on low bandwidth con- nections) and reduces network traffic at the cost of slightly longer startup and some disk space. (10MB for 8-bit colour, 20MB for 15/16-bit colour, 30MB for 24-bit colour and 40MB for 32-bit colour sessions) -r <device> Enable redirection of the specified device on the client, such that it appears on the server. Note that the allowed redirections may be restricted by the server configuration. Following devices are currently supported: -r comport:<comport>=<device>,... Redirects serial devices on your client to the server. Note that if you need to change any settings on the serial device(s), do so with an appropriate tool before starting rdesktop. In most OSes you would use stty. Bidirectional/Read support requires Windows XP or newer. In Windows 2000 it will create a port, but it's not seamless, most shell programs will not work with it. -r disk:<sharename>=<path>,... Redirects a path to the share \tsclient<sharename> on the server (requires Windows XP or newer). The share name is limited to 8 characters. -r lptport:<lptport>=<device>,... Redirects parallel devices on your client to the server. Bidirectional/Read support requires Windows XP or newer. In Windows 2000 it will create a port, but it's not seamless, most shell programs will not work with it. -r printer:<printername>[=<driver>],... Redirects a printer queue on the client to the server. The <printername> is the name of the queue in your local system. <driver> defaults to a simple PS-driver unless you specify one. Keep in mind that you need a 100% match in the server environment, or the driver will fail. The first printer on the command line will be set as your default printer. -r sound:[local|off|remote] Redirects sound generated on the server to the client. "remote" only has any effect when you connect to the console with the -0 option. (Requires Windows XP or newer). -r lspci Activates the lspci channel, which allows the server to enumerate the clients PCI devices. See the file lspci-channel.txt in the documentation for more information. -r scard[:<Scard Name>=<Alias Name>[;<Vendor Name>][,...]] Enables redirection of one or more smart-cards. You can provide static name binding between linux and windows. To do this you can use optional parameters as described: <Scard Name> - device name in Linux/Unix enviroment, <Alias Name> - device name shown in Win- dows enviroment <Vendor Name> - optional device vendor name. For list of examples run rdesktop without parameters. -r clipboard:[off|PRIMARYCLIPBOARD|CLIPBOARD] Enable clipboard redirection. 'PRIMARYCLIPBOARD' looks at both PRIMARY and CLIPBOARD when sending data to server. 'CLIPBOARD' looks at only CLIPBOARD. -0 Attach to the console of the server (requires Windows Server 2003 or newer). -4 Use RDP version 4. -5 Use RDP version 5 (default). EXIT VALUES
0 RDP session terminated normally 1 Server initiated disconnect (also returned for logoff by XP joined to a domain) 2 Server initiated logoff 3 Server idle timeout reached 4 Server logon timeout reached 5 The session was replaced 6 The server is out of memory 7 The server denied the connection 8 The server denied the connection for security reason 16 Internal licensing error 17 No license server available 18 No valid license available 19 Invalid licensing message 20 Hardware id doesn't match software license 21 Client license error 22 Network error during licensing protocol 23 Licensing protocol was not completed 24 Incorrect client license enryption 25 Can't upgrade license 26 The server is not licensed to accept remote connections 62 The local client window was closed 63 Some other, unknown error occured 64 Command line usage error 69 A service or resource (such as memory) is unavailable 70 An internal software error has been detected 71 Operating system error 76 Protocol error or unable to connect to remote host. LINKS
Main website of rdesktop http://www.rdesktop.org/ November 2005 rdesktop(1)
All times are GMT -4. The time now is 10:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy