+ self->priv- >replacing_ plymouth = TRUE + g_debug ("X server %s will replace Plymouth", xserver_get_address (XSERVER (self))) + g_debug ("Plymouth now seems to be running on VT %d, which is already used by another X server", active_vt) self->priv- >replacing_ plymouth = TRUE g_debug ("X server %s will replace Plymouth", xserver_get_address (XSERVER (self))) DEBUG: Registering seat with bus path /org/freedeskto p/DisplayManage r/Seat2ĭiff -rupN lightdm- 1.2.2.org/ src/vt. DEBUG: Registering seat with bus path /org/freedeskto p/DisplayManage r/Seat1 DEBUG: Registering seat with bus path /org/freedeskto p/DisplayManage r/Seat0 DEBUG: Acquired bus name org.freedesktop. DEBUG: Starting XDMCP server on UDP/IP port 177 DEBUG: Waiting for ready signal from X server :12 DEBUG: Launching process 1373: /usr/bin/X :12 -auth /var/run/ lightdm/ root/:12 -nolisten tcp vt11 -novtswitch DEBUG: Writing X server authority to /var/run/ lightdm/ root/:12 DEBUG: Logging to /var/log/ lightdm/ x-12.log DEBUG: Waiting for ready signal from X server :11 DEBUG: Launching process 1369: /usr/bin/X :11 -auth /var/run/ lightdm/ root/:11 -nolisten tcp vt10 -novtswitch -background none DEBUG: Writing X server authority to /var/run/ lightdm/ root/:11 DEBUG: Logging to /var/log/ lightdm/ x-11.log DEBUG: X server :11 will replace Plymouth DEBUG: Waiting for ready signal from X server :10 DEBUG: Launching process 1301: /usr/bin/X :10 -auth /var/run/ lightdm/ root/:10 -nolisten tcp vt10 -novtswitch DEBUG: Writing X server authority to /var/run/ lightdm/ root/:10 DEBUG: Logging to /var/log/ lightdm/ x-10.log DEBUG: Plymouth is running on VT 7, but this is less than the configured minimum of 10 so not replacing it DEBUG: Using D-Bus name org.freedesktop. DEBUG: Loaded configuration from /etc/lightdm/ lightdm. DEBUG: Starting Light Display Manager 1.2.1, UID=0 PID=1270 DEBUG: Logging to /var/log/ lightdm/ lightdm. One time in Oneiric, when trying to log into the graphical session I even had a CLEAR TEXT PASSWORD dialog residue on the screen after the X server was crashing.Īt the end of this report I suggest a patch which fits all 3 versions. The console switching (Alt Fn respectively Alt+Ctrl Fn) starts behaving funny.Ī TEXT console login on vt 2 followed by a "sudo su -" initiates a mouseless (i.e. The intention of the following nf is having an X login screen on vt 10, vt 11 and vt 12.īecause lightdm has an internal error "allocating" vt 10 TWICE on boot (i.e. Nowadays, you have to update /etc/gdm/nf as follows.Booting Oneiric or Precise with the following nf "screws up" console vt switching. This was easily done in Ubuntu before 10.04. To use XMing, XDMCP must be enabled on your Ubuntu machine. XMing is basically an X server to run on windows. If you would be running windows and want to start an X session on a remote Ubuntu machine, you can use XMing. This will leave you with a console, but when you start any application that uses X from that console, it will be shown in your current X session. So suppose you are running an Ubuntu machine and want to connect to another Ubuntu machine, you can type "ssh -X ipaddress" in the console. The first and easiest option would certainly be "ssh -X", but this will only work when the system you connect from is already running an X server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |