[PLUG] How to stop X

[Steve Dum]

Ubuntu decided that ctrl-alt-delete should be used to kill the x-server. 
which should also occur if you log out.

If logging out or ctrl-alt-delete doesn't work to clean up the problem, 
probably it means its a kernel issue, some corruption in the display driver

If you want ctrl-alt-bksp back just go to settings -> keyboard -> 
shortcuts system
and change the ctrl-alt-delete to ctrl-alt-bksp

steve
John Jason Jordan wrote:
> I am familiar with startx command, but I need the opposite. E.g., I use
> Ctrl-Alt-F2 to get to a console and, while in the console I want to
> restart X. I tried stopx and restartx, but both gave "command not
> found." Google told me to use /etc/init.d/gdm stop and then start to
> restart it, but that yielded "no such file or directory."
>
> This is a System76 computer with nVidia GeForce GTX 765M and Haswell
> core i7-4810MQ. When I installed Xubuntu I just let it install its
> default driver, which is xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
> (the latest available in the repos). I have not installed bumblebee or
> anything to take advantage of the advanced capabilities of the GTX
> 765M and Haswell chip, nor have I ever tried the proprietary driver.
>
> I suspect a problem with the nouveau driver but I cannot rule out a
> hardware fault. The symptoms are thousands of short, thin red lines all
> over the display, most visible on darker objects. For wallpaper I use a
> solid white color, and the lines do not appear there at all. The
> display continues to be usable after the lines appear, although some
> things are harder to read. The lines appear at random times and once
> they appear they stay. This first happened late in the afternoon at the
> July Clinic. Since then they have appeared four more times. In each
> case the cure is to reboot; logging out and back in again does not
> solve the problem. Note that the *buntus disable Ctrl-Alt-Backspace.
> (Why?)
>
> There are no hardware related issues that could explain this; e.g., it
> has happened early in the morning when the house is cool, and it
> happened a couple of times before the soda in the keyboard incident.
> And if the hardware was failing because of some condition, why does
> rebooting the computer always cure the problem immediately? But neither
> can I come up with a software trigger; in each case I was doing
> something completely different.
>
> I only wanted to try stopping and restarting X, although I suspect
> it will make no difference, as the lines appear in the console as
> well.
>
> Any other suggestions and observations welcome.
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>