New answers tagged xorg
$HOME/.vnc/xstartup is for the X desktop running in the server, not for the server itself. You need to create a $HOME/.vncrc file with: $geometry = "1400x850"; in it. You have some documentation in: /usr/share/doc/vnc4server/examples/vnc.conf.gz
It was a kernel bug. For this version of the kernel, a line in the radeon KMS drivers needs to be tweaked and the kernel rebuilt. Most of this is moot, though, because it is fixed in newer kernel versions.
I've found the following commands to be useful in finding the model/vendor for use with the xorg.conf configuration. From https://bbs.archlinux.org/viewtopic.php?pid=753773: (where /dev/sdx is replaced with the target device's device path i.e. /dev/input/mouse1) udevadm info --query=all --path=$(udevadm info --query=path --name=/dev/sdx) According to ...
I found this: https://aur.archlinux.org/packages/xf86-input-evdev-debounce/ after googling for "linux xinput mouse debounce" I'm not gonna test it. It's been a long time since you asked, but maybe someone has the same problem with a favorite mouse, so here it is. Also, I'm not an Arch user; but they really rock!
Try Xvfb, is a X11 server that runs without screen and works with a framebuffer. All X11 programs and utilities work with Xvfb.
The following should switch of mdm startup at boot for upstart: echo manual | sudo tee /etc/init/mdm.override Just remove the .override file if you want the service to start normal. You can start the service from the console with sudo service mdm start
Note that, unless you tell it not to via "--no-convert", localectl will set the X settings to be equivalent to the console settings if you are setting console keymap via set-keymap and will set console equivalent to the X settings if you are setting the X keymap via set-x11-keymap. See man localectl.
Client-server models are a popular design for all sorts of applications, even when there's only one server and only one client. They allow a clean, well-defined interface between domains of responsibility. While there are many ways a server and client could communicate, the choice made by X (regardless of the advantages mentioned by others) is not ...
X was originally, developed and maintained by M.I.T. And, it was with an open source M.I.T license, not that, that really, matters. While seen as uncoventional, consider for a moment; how you would explain a choice to use a client-server paradigm in a piece of software? And, perhaps I should say to a C.E.O... Here's how I learned to appreciate the ...
A windowing system means that several independent programs share a common resource, the screen and input devices. Shared resources can only safely be implemented in two ways: The resource may be controlled by the kernel, and applications make kernel calls to access it. The resource may be controlled by a dedicated process (server), and applications contact ...
A window system does not have to have a server, but you can decide to implement window system based on a client-server model. Doing so has several advantages as you clearly separate the activities in the client and the server, they don't need to run on the same machine and it is more easy to service multiple clients. That is currently still very handy (e.g. ...
I think you've already noticed that some sort of "server" is needed. Each client (desktop environment, window manager, or windowed program) needs to share the display with all of the others, and they need to be able to display things without knowing the details of the hardware, or knowing who else is using the display. So the X11 server provides the layer ...
I think the issue you encounter is the overriding of your configuration by the GNOME environment. I suggest you to install dconf-editor if it is not already installed sudo apt-get install dconf-editor Then run it in your terminal with you own user (without using sudo), a gui should open. Go to org.gnome.settings-daemon.plugins.mouse and deactivate the ...
Execute these commands in a terminal, in this order. Step 4 adds the Xorg Developers PPA. Once completed, tell me if step 7 installs the same version you downloaded. Step 3 removes the offending module that is still loaded. Step 5 removes the need for nomodeset on your kernel command line, so please remove whatever edit you made to /etc/default/grub ...
You can see in your dmesg the order of discovery of the graphics chips. If they vary with the time, you could perhaps fix this compiling your stuff in your kernel not as a module. Or trying a workaround putting a rule that indicate the order of loading for the modules concerned...
Use showkey to know your key scancode: $ sudo showkey -s 0xe0 0xXX Kernel will add 8 to you code, use 112 instead 120: $ sudo setkeycodes e0XX 112 Use xmodmap to make your key report XF86AudioMute keysym: $ xmodmap -e "keycode 120 = XF86AudioMute" Optional. Press you key when creating shortcut to what you want in the settings of your DE.
Top 50 recent answers are included