With the Raspbian image, you can re-run the initial start up script using:
$ sudo raspi-config
and entering your sudo password.
This will bring up the same menu options that you got after first boot.
You do not need to remake all your first boot choices, just use the arrow keys to move to the menu options you want to change.
In your case, selecting:
TL;DR or "Just scorch my pi"
sudo apt-get remove --auto-remove --purge 'libx11-.*'
sudo apt-get autoremove --purge
(Repeat apt-get autoremove --purge until no orphans remain)
If a package foo depends on another package libfoo and you remove the libfoo package, the dependent (foo) is also removed. Because Foo has a depends line ...
This is an X power-saving thing.
Firstly, you may need to install xset, a lightweight application that controls some X settings.
apt-get install x11-xserver-utils
Now open up your ~/.xinitrc file (if you don't have one then create it) and enter this:
xset s off # don't activate screensaver
xset -dpms # disable DPMS (Energy Star) features....
You can use the command-line fbi app ("framebuffer image viewing"). The framebuffer is also what oxmplayer uses. Fbi is available from the raspbian repos and should be in any other GNU/Linux distro as well; it is not specific to the pi.
It takes a filename or series of filenames, and you can use shell globbing for this, so e.g.:
Will show all ...
The other solutions here did not work for me (fresh Raspbian, boot to GUI). Instead, this worked:
Open up /etc/lightdm/lightdm.conf using your favorite text editor (I prefer nano).
Look for the line #xserver-command=X. Change it to xserver-command=X -s 0 dpms
It should be at line 87 if things don't change.
Save and reboot.
Linux uses a heterogeneous GUI stack, meaning it's arranged in layers but there's different layers you can arrange.
The bottom of the stack is relatively homogeneous, meaning it's almost always the same. This is the Xorg server joan has indicated.
However, while X all by itself does provide you with a graphical desktop, it doesn't look like much -- plain ...
Simple! :) Buy TWO Raspberry Pies and hook them up with ethernet cable. Then use synergy to hook up the two systems in a virtual multihead config. See http://synergy-foss.org/ for more details.
Apart from that - there's not much you can do now as hdmi & composite cannot be used simultaneously.
This may change once we find out more about how to use the ...
According to the official Raspberry_Pi twitter feed, GPU accelerated X.org is not yet available.
26 June 2012: @Raspberry_Pi :
The Wheezy beta's worth a go http://www.raspberrypi.org/archives/1435 - but X isn't hardware
accelerated yet. (It will be soon.)
If you start Xming on your Windows computer, then you already have an X server running. You don't have to start the X server of your Raspberry Pi using startx. Your X applications will run on the Raspberry Pi but the application will draw onto Windows' Xming X server.
The documentation you linked, states that you have to start X server on Windows, and it ...
I think @Jivings answer may be better, but I have it in my notes to do this:
Install apt-get install x11-xserver-utils
Append these lines:
@xset s noblank
@xset s off
Possibly also comment out the line that says @xscreensaver -no-splash, so the complete file should look something like this:
Systemd users "service bunlde" named target, to achieve different system states while booting the system. You need to change the desired state of the system, from graphical to multi-user.
Will show you
You could change it with
sudo systemctl set-default multi-user.target
I could recommend this article to ...
The way I've done it is to remove all the packages under the Installed Packages --> x11 category in aptitude, then run sudo apt-get autoremove, which uninstalls any leftover packages that aren't needed anymore.
You can apply hildred's suggestion permanently by creating a ~/.xinitrc file:
exec chromium --kiosk
This will then be applied if you are using a graphical login, so that you do not have to boot to console. To test it from the console, try startx with no arguments.
One possible source of this problem can be file ownership. You could try running following command:
sudo chown -R pi:pi /home/pi
This should change ownership of all files in pi directory (and all directories inside of it) back to the user pi and group pi.
xauth application has a commandline option -b which is intended to clean stale locks if they exists ...
$ sudo apt-get --purge remove "x11-*"
This will remove all the packages that are under x11 which is the library with all the graphical packages. the option --purge allow you to delete all the config file related.
$ sudo apt-get --purge autoremove
autoremove removes all the unused packages. There are a lot of unused packages after the first command.
For the past month or so I've been working on basically the exact same thing, so I've researched how to do this a lot and know how to do it with the latest version of Raspbian (PIXEL).
nodm is a minimal display manager that bypasses loading LXDE, and openbox (which is already installed on the Pi) provides a minimal session manager and works with the X ...
Starting GDM At Boot
You need to edit /etc/inittab so that init knows that it should boot directly into runlevel 5 (default for X11) when it starts.
Beginners note: Lines that begin with a # represent comments. They will be ignored completely when the file is used.
This section controls the default runlevel:
## Only one of the following ...
You can use a great tool called x2x. This essentially treats the monitor connected to the remote device (the Raspberry Pi) as a second X screen to you existing session as if you had two monitors connected.
Install x2x on both devices:
sudo pacman -S x2x # Arch Linux
sudo apt-get install x2x # Debian/Raspbian
On the Raspberry Pi ...
Personal experience tells me it's pretty excellent. I have used X-forwarding over SSH and it performs well, as if executing natively. I've had multiple forwarded windows on the go at once, including Eclipse and Chromium.
I've also played with forwarding mouse and keyboard using from my desktop to the Pi using x2x which works by using the Pi X session as a ...
The problem is that the X session for the superuser doesn't know what the cookie is.
After logging into the Pi execute the following:
$ xauth list $DISPLAY
This prints the cookie, something like this:
pi:10 mit-magic-cookie-1 4d22408aga55sad1ccd165723g77923ae
Then switch the superuser with su and set the cookie:
# xauth add pi:10 mit-magic-cookie-1 ...