Xorg
X11R7 X server
see also :
X - xinit - xvidtune
Synopsis
Xorg
[:display] [option ...]
add an example, a script, a trick and tips
examples
source
NumLock is completely useless, and I want to disable it completely on Linux
Well for your first question, you can remap it to nothing with
xmodmap
:
xmodmap -e "keycode # = """
where # is the scan code of NumLock. You can find the scan code
using xev
. Instead of nothing you can remap it to
any key you'd like.
source
Browser instead of window manager?
Try just put this in your .xinitrc file in your home directory.
exec konqueror
Then restart X. If this doesn't work or if you are using gdm, kdm
or xdm as a display manager, you can either shut that off and run
startx from the command line or you can create an alternate user
and configure their .xinitrc to do the same. Then you can try
running startx as that user from a virtual console (Ctrl-Alt +
F2). It should open another X session. I noticed when I tried
this with Firefox that Firefox wasn't filling the screen even if
I used a --geometry option. It seems that Firefox may store its
geometry preferences in a session. You may have to deal with this
on other programs like Chrome.
Keep in mind that a lot of things that these programs might be
expecting things that you'd have in a modern desktop like proxy
management, drag and drop or special paste buffer handling.
This is all old hat stuff. I'm sure you have a good purpose for
it, but a lot of people probably haven't done this type of stuff
since the early 2000s. You used to have to mess with it all the
time during the FVWM days (before display managers became
popular)
I'd also like to clarify something in your question. The program
that you exec like this is not a "window manager". A window
manager is a specific program that also gets run by X in this
fashion or through a desktop manager and allows you an easy way
to run (exec) additional programs, usually decorating them so
that you have an interface for closing them. In the early days of
X, it would just start an xterm and you would run the command for
your window manager from there with an &. So we are making
progress. ;-)
Some programs can be run outside of a window manager and still
allow you to control their window size or bits of their display.
For instance, Google Chrome pseudo decorates its windows.
However, I tested Google Chrome and it doesn't have or honor
enough standard X options to be a good solution here. For
instance, it doesn't seem to handle the --geometry= option (shame
on you Google). This is another good reason to use Konqueror or
Firefox instead.
Sorry for rambling.
source
How to stop the 'd' key from minimizing all windows in Ubuntu 10.10 when connected with Nomachine?
By default Ubuntu maps the "show desktop" command to the
Super
+D
key combination. The
Super
key is also sometimes known as the
Windows
key. While I've never used Nomachine, my
assumption would be that it is having an issue with the
Super
key as it does not exist on your Mac. I would
try changing that key binding on the Ubuntu side.
Go to System > Preferences > Keyboard
Shortcuts
Find the entry titled "Hide all normal windows and set focus to
the desktop" and try a new keyboard combination.
source
How do you start a program after X has started?
Try placing a script named .xinitrc
in your home
directory. KDE and Gnome also have the ability to run
scripts/applications on login if you're using one of those. I
believe .Xstartup
or .xstartup
might
also do what you want if .xinitrc
doesn't. My linux
is getting a bit rusty it seems. >.>
source
Updating screen session environment variables to reflect new graphical login?
You cannot start a shell script from the screen
session since it would inherit the old environment. You can
however us a fifo to get the new environment variables into the
old screen session. You can fill that fifo when you start your
graphical session.
#!/bin/bash
FIFO=/tmp/your_variables
[ -e $FIFO ] && cat $FIFO > /dev/null || mkfifo $FIFO
# save number of variables that follow
NVARS=2
echo $NVARS > $FIFO
echo ENV1=sth1 > $FIFO
echo ENV2=sth2 > $FIFO
Start that script in the background on login (it will only
terminate when all variables are read from it).
Now you can read from the fifo, e.g. add this function to your
.bashrc
update_session() {
FIFO=/tmp/your_variables
NVAR=$(cat $FIFO)
for i in $(seq $NVAR); do
export $(cat $FIFO)
done
#delete the pipe, or it will not work next time
rm $FIFO
}
so that you can in your old screen
session
update_session
source
Faking monitor EDID information
You might try
Option "IgnoreEDID" "TRUE"
and then specify your monitor's information manually. If
IgnoreEDID doesn't work for you, try
Option "UseEDIDFreqs" "FALSE"
Option "UseEDIDDpi" "FALSE"
source
"Detach" and "Reattach" xterms across X sessions?
Not quite what you've asked for, but screen may do what you want.
This shares at the shell level rather than the X-window level, so
you could have two xterms (on different Xservers, so long as they
were on the same box), running screen -x
, which
would show the same sh sessions.
This wouldn't work for non-terminal things.
source
X equivalent of 'screen' utility
Why not just use VNC?
So long as you don't log out (thus closing all your running
applications etc) your system will stay in the exact same state
no matter how many times you disconnect/reconnect.
source
using a second computer as a mere screen/monitor in X (VNC?)
That's what DMX: Distributed Multi-head X is designed to do,
unfortunately it's been broken in several X.Org releases, so you
may have to work a bit to get it working.
source
Firefox, two Linux machines, one X-server
Ok...don't know if this will work, but it's the first thing I'd
try:
How about if you create a second script on each machine, which
doesn't try to create the new tab, just a new instance. If you
don't have FF currently running on that machine, you use this new
script, but if it's already running, you use the old script that
creates the new tab.
If this works, you might be able to do some regex parsing of ps
output in a single script to see if FF is already running on the
machine, and either use the -new-tab switch or -no-remote,
depending on what it finds; but you probably want to wait until
this method is tested, as it's a fair amount of coding for
something that might not work....
source
How to make Elo touchscreen working for Linux?
Seems like you are going a smidgen bit too far into this. Would
it not be possible to put Wine on your computer and use that to
install the drivers for your touch screen with it? I have done
this with a few different pieces of hardware (including a Bamboo
Fun graphics tablet) and it works fine.
...EVEN BETTER...
Just get a straight up Linux driver! They can be acquired here;
http://www.elotouch.com/Support/Downloads/dnld.asp
If this is obvious, if you have tried this and its not the
solution, or if in some way my answer is not intelligent, please
notify me and i will remove this.
source
"Detach" and "Reattach" xterms across X sessions?
Not quite what you've asked for, but screen may do what you want.
This shares at the shell level rather than the X-window level, so
you could have two xterms (on different Xservers, so long as they
were on the same box), running screen -x
, which
would show the same sh sessions.
This wouldn't work for non-terminal things.
EDIT: xpra is probably what you want.
source
Detecting currently active window
There is, but no short answer or solution.
wmctrl -lp | grep `xprop -root | grep _NET_ACTIVE_WINDOW |
head -1 | awk '{print $5}' | sed 's/,//' | sed
's/^0x/0x0/'`
result:
0x03800004 0 16459 xxxxxxxxxx /bin/bash
In use:
for x in `seq 1 10`; do sleep 5; wmctrl -lp | grep `xprop
-root | grep _NET_ACTIVE_WINDOW | head -1 | awk '{print $5}' |
sed 's/,//' | sed 's/^0x/0x0/'`; done
0x03800004 0 16459 xxxxxxxxxx /bin/bash
0x020000a4 0 13524 xxxxxxxxxx linux - Detecting currently active
window - Super User - Mozilla Firefox (Build
20120129142219)
description
Xorg is
a full featured X server that was originally designed for
UNIX and UNIX-like operating systems running on Intel x86
hardware. It now runs on a wider range of hardware and OS
platforms.
This work was
derived by the X.Org Foundation from the XFree86
Project’s XFree86 4.4rc2 release. The
XFree86 release was originally derived from
X386 1.2 by Thomas Roell which was contributed
to X11R5 by Snitily Graphics Consulting Service.
options
Xorg
supports several mechanisms for supplying/obtaining
configuration and run-time parameters: command line options,
environment variables, the xorg.conf(5) configuration files,
auto-detection, and fallback defaults. When the same
information is supplied in more than one way, the highest
precedence mechanism is used. The list of mechanisms is
ordered from highest precedence to lowest. Note that not all
parameters can be supplied via all methods. The available
command line options and environment variables (and some
defaults) are described here and in the Xserver(1) manual
page. Most configuration file parameters, with their
defaults, are described in the xorg.conf(5) manual page.
Driver and module specific configuration parameters are
described in the relevant driver or module manual page.
In addition to
the normal server options described in the Xserver(1) manual
page, Xorg accepts the following command line
switches:
vtXX
XX specifies the Virtual Terminal device number
which Xorg will use. Without this option, Xorg
will pick the first available Virtual Terminal that it can
locate. This option applies only to platforms that have
virtual terminal support, such as Linux, BSD, OpenSolaris,
SVR3, and SVR4.
-allowMouseOpenFail
Allow the server to start up
even if the mouse device can’t be opened or
initialised. This is equivalent to the
AllowMouseOpenFail xorg.conf(5) file option.
-allowNonLocalXvidtune
Make the VidMode extension
available to remote clients. This allows the xvidtune client
to connect from another host. This is equivalent to the
AllowNonLocalXvidtune xorg.conf(5) file option. By
default non-local connections are not allowed.
-bgamma
value
Set the blue gamma correction.
value must be between 0.1 and 10. The default is 1.0.
Not all drivers support this. See also the
-gamma, -rgamma, and
-ggamma options.
-bpp n
No longer supported. Use -depth to set the
color depth, and use -fbbpp if you really need
to force a non-default framebuffer (hardware) pixel
format.
-config
file
Read the server configuration
from file. This option will work for any file when
the server is run as root (i.e, with real-uid 0), or for
files relative to a directory in the config search path for
all other users.
-configdir
directory
Read the server configuration
files from directory. This option will work for any
directory when the server is run as root (i.e, with real-uid
0), or for directories relative to a directory in the config
directory search path for all other users.
-configure
When this option is specified,
the Xorg server loads all video driver modules,
probes for available hardware, and writes out an initial
xorg.conf(5) file based on what was detected. This option
currently has some problems on some platforms, but in most
cases it is a good way to bootstrap the configuration
process. This option is only available when the server is
run as root (i.e, with real-uid 0).
-crt
/dev/ttyXX
SCO only. This is the same as
the vt option, and is provided for compatibility with
the native SCO X server.
-depth
n
Sets the default color depth.
Legal values are 1, 4, 8, 15, 16, and 24. Not all drivers
support all values.
-disableVidMode
Disable the parts of the
VidMode extension (used by the xvidtune client) that can be
used to change the video modes. This is equivalent to the
DisableVidModeExtension xorg.conf(5) file option.
-fbbpp
n
Sets the number of framebuffer
bits per pixel. You should only set this if you’re
sure it’s necessary; normally the server can deduce
the correct value from -depth above. Useful if
you want to run a depth 24 configuration with a 24 bpp
framebuffer rather than the (possibly default) 32 bpp
framebuffer (or vice versa). Legal values are 1, 8, 16, 24,
32. Not all drivers support all values.
-flipPixels
Swap the default values for the
black and white pixels.
-gamma
value
Set the gamma correction.
value must be between 0.1 and 10. The default is 1.0.
This value is applied equally to the R, G and B values.
Those values can be set independently with the
-rgamma, -bgamma, and
-ggamma options. Not all drivers support
this.
-ggamma
value
Set the green gamma correction.
value must be between 0.1 and 10. The default is 1.0.
Not all drivers support this. See also the
-gamma, -rgamma, and
-bgamma options.
-ignoreABI
The Xorg server checks
the ABI revision levels of each module that it loads. It
will normally refuse to load modules with ABI revisions that
are newer than the server’s. This is because such
modules might use interfaces that the server does not have.
When this option is specified, mismatches like this are
downgraded from fatal errors to warnings. This option should
be used with care.
-isolateDevice
bus-id
Restrict device resets to the
device at bus-id. The bus-id
string has the form
bustype:bus:device:function
(e.g., ’PCI:1:0:0’). At present, only isolation
of PCI devices is supported; i.e., this option is ignored if
bustype is anything other than ’PCI’.
-keeptty
Prevent the server from
detaching its initial controlling terminal. This option is
only useful when debugging the server. Not all platforms
support (or can use) this option.
-keyboard
keyboard-name
Use the xorg.conf(5) file
InputDevice section called keyboard-name as
the core keyboard. This option is ignored when the
Layout section specifies a core keyboard. In the
absence of both a Layout section and this option, the first
relevant InputDevice section is used for the core
keyboard.
-layout
layout-name
Use the xorg.conf(5) file
Layout section called layout-name. By default
the first Layout section is used.
-logfile
filename
Use the file called
filename as the Xorg server log file. The
default log file is /var/log/Xorg.n.log
on most platforms, where n is the display number of
the Xorg server. The default may be in a different
directory on some platforms. This option is only available
when the server is run as root (i.e, with real-uid 0).
-logverbose
[n]
Sets the verbosity level for
information printed to the Xorg server log file. If
the n value isn’t supplied, each occurrence of
this option increments the log file verbosity level. When
the n value is supplied, the log file verbosity level
is set to that value. The default log file verbosity level
is 3.
-modulepath
searchpath
Set the module search path to
searchpath. searchpath is a comma separated
list of directories to search for Xorg server
modules. This option is only available when the server is
run as root (i.e, with real-uid 0).
-nosilk
Disable Silken Mouse support.
-novtswitch
Disable the automatic switching
on X server reset and shutdown to the VT that was active
when the server started, if supported by the OS.
-pixmap24
Set the internal pixmap format
for depth 24 pixmaps to 24 bits per pixel. The default is
usually 32 bits per pixel. There is normally little reason
to use this option. Some client applications don’t
like this pixmap format, even though it is a perfectly legal
format. This is equivalent to the Pixmap xorg.conf(5)
file option.
-pixmap32
Set the internal pixmap format
for depth 24 pixmaps to 32 bits per pixel. This is usually
the default. This is equivalent to the Pixmap
xorg.conf(5) file option.
-pointer
pointer-name
Use the xorg.conf(5) file
InputDevice section called pointer-name as the
core pointer. This option is ignored when the Layout
section specifies a core pointer. In the absence of both a
Layout section and this option, the first relevant
InputDevice section is used for the core pointer.
-quiet
Suppress most informational messages at startup. The
verbosity level is set to zero.
-rgamma
value
Set the red gamma correction.
value must be between 0.1 and 10. The default is 1.0.
Not all drivers support this. See also the
-gamma, -bgamma, and
-ggamma options.
-sharevts
Share virtual terminals with
another X server, if supported by the OS.
-screen
screen-name
Use the xorg.conf(5) file
Screen section called screen-name. By default
the screens referenced by the default Layout section
are used, or the first Screen section when there are
no Layout sections.
-showconfig
This is the same as the
-version option, and is included for
compatibility reasons. It may be removed in a future
release, so the -version option should be used
instead.
-showDefaultModulePath
Print out the default module
path the server was compiled with.
-showDefaultLibPath
Print out the path libraries
should be installed to.
-showopts
For each driver module
installed, print out the list of options and their argument
types.
-weight
nnn
Set RGB weighting at 16 bpp.
The default is 565. This applies only to those drivers which
support 16 bpp.
-verbose
[n]
Sets the verbosity level for
information printed on stderr. If the n value
isn’t supplied, each occurrence of this option
increments the verbosity level. When the n value is
supplied, the verbosity level is set to that value. The
default verbosity level is 0.
-version
Print out the server version,
patchlevel, release date, the operating system/platform it
was built on, and whether it includes module loader
support.
configuration
Xorg typically uses a configuration file called
xorg.conf and configuration files with the suffix
.conf in a directory called xorg.conf.d for its
initial setup. Refer to the xorg.conf(5) manual page for
information about the format of this file.
Xorg has a mechanism for automatically generating a
built-in configuration at run-time when no xorg.conf file
or xorg.conf.d files are present. The current version of
this automatic configuration mechanism works in two ways.
The first is via enhancements that have made many components of
the xorg.conf file optional. This means that information
that can be probed or reasonably deduced doesn’t need to be
specified explicitly, greatly reducing the amount of built-in
configuration information that needs to be generated at run-time.
The second is to have "safe" fallbacks for most configuration
information. This maximises the likelihood that the Xorg
server will start up in some usable configuration even when
information about the specific hardware is not available.
The automatic configuration support for Xorg is work in progress.
It is currently aimed at the most popular hardware and software
platforms supported by Xorg. Enhancements are planned for future
releases.
environment variables
For operating systems that support local connections other than
Unix Domain sockets (SVR3 and SVR4), there is a compiled-in list
specifying the order in which local connections should be
attempted. This list can be overridden by the XLOCAL
environment variable described below. If the display name
indicates a best-choice connection should be made (e.g.
:0.0), each connection mechanism is tried until a
connection succeeds or no more mechanisms are available. Note:
for these OSs, the Unix Domain socket connection is treated
differently from the other local connection types. To use it the
connection must be made to unix:0.0.
The XLOCAL environment variable should contain a list of
one more more of the following:
NAMED
PTS
SCO
ISC
which represent SVR4 Named Streams pipe, Old-style USL Streams
pipe, SCO XSight Streams pipe, and ISC Streams pipe,
respectively. You can select a single mechanism (e.g.
XLOCAL=NAMED), or an ordered list (e.g.
XLOCAL="NAMED:PTS:SCO"). his variable overrides the
compiled-in defaults. For SVR4 it is recommended that
NAMED be the first preference connection. The default
setting is PTS:NAMED:ISC:SCO.
To globally override the compiled-in defaults, you should define
(and export if using sh or ksh) XLOCAL
globally. If you use startx(1) or xinit(1), the definition should
be at the top of your .xinitrc file. If you use xdm(1),
the definitions should be early on in the
/usr/lib/X11/xdm/Xsession script.
files
The Xorg server config files can be found in a range of
locations. These are documented fully in the xorg.conf(5) manual
page. The most commonly used locations are shown here.
/etc/X11/xorg.conf
Server configuration file.
/etc/X11/xorg.conf-4
Server configuration file.
/etc/xorg.conf
Server configuration file.
/usr/etc/xorg.conf
Server configuration file.
/usr/lib/X11/xorg.conf
Server configuration file.
/etc/X11/xorg.conf.d
Server configuration directory.
/etc/X11/xorg.conf.d-4
Server configuration directory.
/etc/xorg.conf.d
Server configuration directory.
/usr/etc/xorg.conf.d
Server configuration directory.
/usr/lib/X11/xorg.conf.d
Server configuration directory.
/var/log/Xorg.n.log
Server log file for display n.
/usr/bin/∗
Client binaries.
/usr/include/∗
Header files.
/usr/lib/∗
Libraries.
/usr/share/fonts/X11/∗
Fonts.
/usr/share/X11/XErrorDB
Client error message database.
/usr/lib/X11/app-defaults/∗
Client resource specifications.
/usr/share/man/man?/∗
Manual pages.
/etc/Xn.hosts
Initial access control list for display n.
keyboard
The Xorg server is normally configured to recognize
various special combinations of key presses that instruct the
server to perform some action, rather than just sending the key
press event to a client application. These actions depend on the
XKB keymap loaded by a particular keyboard device and may or may
not be available on a given configuration.
The following key combinations are commonly part of the default
XKEYBOARD keymap.
Ctrl+Alt+Backspace
Immediately kills the server -- no questions asked. It can be
disabled by setting the DontZap xorg.conf(5) file option
to a TRUE value.
It should be noted that zapping is triggered by the
Terminate_Server action in the keyboard map. This action
is not part of the default keymaps but can be enabled with the
XKB option "terminate:ctrl_alt_bksp".
Ctrl+Alt+Keypad-Plus
Change video mode to next one specified in the configuration
file. This can be disabled with the DontZoom xorg.conf(5)
file option.
Ctrl+Alt+Keypad-Minus
Change video mode to previous one specified in the configuration
file. This can be disabled with the DontZoom xorg.conf(5)
file option.
Ctrl+Alt+F1...F12
For systems with virtual terminal support, these keystroke
combinations are used to switch to virtual terminals 1 through
12, respectively. This can be disabled with the
DontVTSwitch xorg.conf(5) file option.
legal
Xorg is copyright software, provided under licenses that
permit modification and redistribution in source and binary form
without fee. Xorg is copyright by numerous authors and
contributors from around the world. Licensing information can be
found at <http://www.x.org>. Refer to the source
code for specific copyright notices.
XFree86(TM) is a trademark of The XFree86 Project, Inc.
X11(TM) and X Window System(TM) are trademarks of
The Open Group.
network connections
Xorg supports connections made using the following
reliable byte-streams:
Local
On most platforms, the "Local" connection type is a UNIX-domain
socket. On some System V platforms, the "local" connection types
also include STREAMS pipes, named pipes, and some other
mechanisms.
TCPIP
Xorg listens on port 6000+n, where n is the
display number. This connection type can be disabled with the
-nolisten option (see the Xserver(1) man page for
details).
platforms
Xorg operates under a wide range of operating systems and
hardware platforms. The Intel x86 (IA32) architecture is the most
widely supported hardware platform. Other hardware platforms
include Compaq Alpha, Intel IA64, AMD64, SPARC and PowerPC. The
most widely supported operating systems are the free/OpenSource
UNIX-like systems such as Linux, FreeBSD, NetBSD, OpenBSD, and
Solaris. Commercial UNIX operating systems such as UnixWare are
also supported. Other supported operating systems include GNU
Hurd. Mac OS X is supported with the Xquartz(1) X server.
Win32/Cygwin is supported with the XWin(1) X server.
see also
X ,
Xserver, xdm, xinit , xorg.conf, xvidtune ,
xkeyboard-config , apm, ati, chips, cirrus,
cyrix, fbdev, glide, glint, i128, i740,
imstt, intel, mga, neomagic, nsc, nv,
openchrome , r128, rendition, s3virge,
siliconmotion, sis, sunbw2, suncg14, suncg3,
suncg6, sunffb, sunleo, suntcx, tdfx, tga,
trident, tseng, v4l, vesa, vmware,
Web site <http://www.x.org>.
authors
Xorg has many
contributors world wide. The names of most of them can be
found in the documentation, ChangeLog files in the source
tree, and in the actual source code.
Xorg was
originally based on XFree86 4.4rc2. That was originally
based on X386 1.2 by Thomas Roell, which was
contributed to the then X Consortium’s X11R5
distribution by SGCS.
Xorg is
released by the X.Org Foundation.
The project
that became XFree86 was originally founded in 1992 by David
Dawes, Glenn Lai, Jim Tsillas and David Wexelblat.
XFree86 was
later integrated in the then X Consortium’s X11R6
release by a group of dedicated XFree86 developers,
including the following:
Stuart Anderson
anderson[:at:]metrolink[:dot:]com
Doug Anson danson[:at:]lgc[:dot:]com
Gertjan Akkerman akkerman[:at:]dutiba.twi.tudelft[:dot:]nl
Mike Bernson mike[:at:]mbsun.mlb[:dot:]org
Robin Cutshaw robin[:at:]XFree86[:dot:]org
David Dawes dawes[:at:]XFree86[:dot:]org
Marc Evans marc[:at:]XFree86[:dot:]org
Pascal Haible haible[:at:]izfm[:dot:]uni-stuttgart.de
Matthieu Herrb Matthieu.Herrb[:at:]laas[:dot:]fr
Dirk Hohndel hohndel[:at:]XFree86[:dot:]org
David Holland davidh[:at:]use[:dot:]com
Alan Hourihane alanh[:at:]fairlite.demon.co[:dot:]uk
Jeffrey Hsu hsu[:at:]soda.berkeley[:dot:]edu
Glenn Lai glenn[:at:]cs.utexas[:dot:]edu
Ted Lemon mellon[:at:]ncd[:dot:]com
Rich Murphey rich[:at:]XFree86[:dot:]org
Hans Nasten nasten[:at:]everyware[:dot:]se
Mark Snitily mark[:at:]sgcs[:dot:]com
Randy Terbush randyt[:at:]cse.unl[:dot:]edu
Jon Tombs tombs[:at:]XFree86[:dot:]org
Kees Verstoep versto[:at:]cs.vu[:dot:]nl
Paul Vixie paul[:at:]vix[:dot:]com
Mark Weaver Mark_Weaver[:at:]brown[:dot:]edu
David Wexelblat dwex[:at:]XFree86[:dot:]org
Philip Wheatley Philip.Wheatley[:at:]ColumbiaSC.NCR[:dot:]COM
Thomas Wolfram wolf[:at:]prz[:dot:]tu-berlin.de
Orest Zborowski orestz[:at:]eskimo[:dot:]com
Xorg source is
available from the FTP server
<ftp://ftp.x.org/>, and from the X.Org server
<http://gitweb.freedesktop.org/>. Documentation
and other information can be found from the X.Org web site
<http://www.x.org/>.