Hi there,

After having done a world update, neither sddm nor lightdm do start an Xserver anymore. The X server itself runs fine, I can start it from the console and I after setting DISPLAY properly can even start programs using it, but the login managers do not start X for some reason.

No hint so far in the logs, and no ideas where I should looking.

The system is running inside a virtualbox VM, with Win10 as host operating system.

Any ideas?

Thanks
Alex

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Saturday, 11 March 2023 12:03:41 GMT Alexander Puchmayr wrote:

Hi there,

After having done a world update, neither sddm nor lightdm do start an Xserver anymore. The X server itself runs fine, I can start it from the console and I after setting DISPLAY properly can even start programs using it, but the login managers do not start X for some reason.

No hint so far in the logs, and no ideas where I should looking.

The system is running inside a virtualbox VM, with Win10 as host operating system.

Any ideas?

Thanks
Alex

Asking the obvious, but is display-manager service running?
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmQMcUgACgkQseqq9sKV ZxmE9A/+KmhjPm6B337sgqdyHEpYOXO4I/YPKP6XHT2G23H9RHT2UhmdJ5LD/TCU reGcUfuQcnKIRLsdc6Jg3xdqm17/uqL/wIJnSsU7IgyQjpis8/SwDmofFStNZ4rd PXbPsUUhnkugpTWTCfwwZIFWszQxnXnXgIkVqh9XYe2WdmI9R7TDXpocCuosR1Xs k6NYczsKs+7MIykqtOUjWCelXkuch4EkvoByfrAwKpVZKZahdfqcfEEwKLnD+9p2 nmq1lik4LmqZMRPjS6UY7DOS/wV+H9erxnLSZKQW2qPN6/DP7T4696Q1+3sGaKdZ dOWdn4Za4IBxfYknVnnZ0wiYpWnt8H922TwUPdhEib9/S3CMsiNgiv0t6wR8ENiw KE6NdalM/HkoKJkHeh8vbsIfLPbMXXbGgx+h2rvl5vxRX/PeMbQrrKHI5OGp9ScT yYdt6lXqjhtrMNlDwQCauMPBChiPCKrraebozA/FcSwFbREBZJ4dED90AuJ0HMcC gPIhK1E/twA1mxQpF/2L5xagmxXBfT8wszgVJM3vmzksCc6chDHvcKfW8JY3SpPG ct+fANaWSuoqMIYl9kZQ6UmL9zdlRYDVVrP9LPowuPB3I9iUwKN94m6+xq6/GfaA eizCEo03X2AV55HLVaTRV46qBxdLnWuaR+dYxBv+gtt+dEh/lSs=
=GCMY
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Samstag, 11. M�rz 2023, 13:17:12 CET Michael wrote:

On Saturday, 11 March 2023 12:03:41 GMT Alexander Puchmayr wrote:

Hi there,

After having done a world update, neither sddm nor lightdm do start an Xserver anymore. The X server itself runs fine, I can start it from the console and I after setting DISPLAY properly can even start programs using it, but the login managers do not start X for some reason.

No hint so far in the logs, and no ideas where I should looking.

The system is running inside a virtualbox VM, with Win10 as host operating system.

Any ideas?

Thanks

Alex

Asking the obvious, but is display-manager service running?

Of course. I even tried starting it on the command line with the -d option to see whether I get any useful information.

lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=1176
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using Xephyr for X servers
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User2002 added
^C[+27.38s] DEBUG: Got signal 2 from process 0
[+27.38s] DEBUG: Caught Interrupt signal, shutting down
[+27.38s] DEBUG: Stopping display manager
[+27.38s] DEBUG: Display manager stopped
[+27.38s] DEBUG: Stopping daemon
[+27.38s] DEBUG: Exiting with return value 0

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In lightdm.conf, try to set :

logind-check-graphical=false

Then restart the service.

Does this help ?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am Samstag, 11. M�rz 2023, 16:21:01 CET schrieb netfab:

In lightdm.conf, try to set :

logind-check-graphical=false

Then restart the service.

Does this help ?

No. Same as before.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Samstag, 11. M�rz 2023, 13:03:41 CET Alexander Puchmayr wrote:

Hi there,

After having done a world update, neither sddm nor lightdm do start an Xserver anymore. The X server itself runs fine, I can start it from the console and I after setting DISPLAY properly can even start programs using it, but the login managers do not start X for some reason.

No hint so far in the logs, and no ideas where I should looking.

The system is running inside a virtualbox VM, with Win10 as host operating system.

Its even getting more strange, the very same image copied from the windows laptop to a linux box and started with kvm/libvirt works fine, but in windows/ virtualbox it doesn't.

Now I have two completely identical systems which only differn in the hypervisor they're started with, named "virtualbox" and "libvirt". On both systems, I start lightdm from the command line with -d option, and compare the results.

Intrestingly the "libvirt" system writes "New seat added from logind: seat0", the "virtualbox" system does not, which seems to be the relevant difference (see log output below)

Further, I found the following command in another forum:

Gdbus introspect --system --dest org.freedesktop.login1 --object-path /org/ freedesktop/login1/seat/seat0

And the relevant difference here is in the org.freedesktop.login1.Seat properties section

...
readonly b CanGraphical = false;
...

on virtualbox. The same command on "libvirt" machine shows "true" here.

So, what is required for a login seat to be treated as "graphical"?

Thanks
Alex


[virtualbox] # lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=867
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User2002 added
...waiting for ctrl-C and no login screen ...

[libvirt] # lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=793
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/ root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 799: /usr/bin/X :0 -seat seat0 -auth /var/ run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/ DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.18s] DEBUG: User /org/freedesktop/Accounts/User2002 added
[+0.40s] DEBUG: Got signal 10 from process 799
[+0.40s] DEBUG: XServer 0: Got signal from X server :0
[+0.40s] DEBUG: XServer 0: Connecting to XServer :0
[+0.40s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.40s] DEBUG: Session pid=815: Started with service 'lightdm-greeter', username 'root'
[+0.55s] DEBUG: Session pid=815: Authentication complete with return value 0: Success
[+0.55s] DEBUG: Seat seat0: Session authenticated, running command
[+0.55s] DEBUG: Session pid=815: Running command /usr/sbin/lightdm-gtk-greeter [+0.55s] DEBUG: Creating shared data directory /var/lib/lightdm-data/root [+0.55s] DEBUG: Session pid=815: Logging to /var/log/lightdm/seat0-greeter.log [+0.55s] DEBUG: Activating VT 7
[+0.81s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false [+1.40s] DEBUG: Greeter start authentication for alex
[+1.40s] DEBUG: Session pid=855: Started with service 'lightdm', username 'alex'
[+1.41s] DEBUG: Session pid=855: Got 1 message(s) from PAM
[+1.41s] DEBUG: Prompt greeter with 1 message(s)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dave

On Sun, Mar 12, 2023, 11:09 Alexander Puchmayr <
[email protected]> wrote:

On Samstag, 11. März 2023, 13:03:41 CET Alexander Puchmayr wrote:

Hi there,

After having done a world update, neither sddm nor lightdm do start an Xserver anymore. The X server itself runs fine, I can start it from the console and I after setting DISPLAY properly can even start programs

using

it, but the login managers do not start X for some reason.

No hint so far in the logs, and no ideas where I should looking.

The system is running inside a virtualbox VM, with Win10 as host

operating

system.

Its even getting more strange, the very same image copied from the windows laptop to a linux box and started with kvm/libvirt works fine, but in windows/
virtualbox it doesn't.

Now I have two completely identical systems which only differn in the hypervisor they're started with, named "virtualbox" and "libvirt". On both systems, I start lightdm from the command line with -d option, and compare the
results.

Intrestingly the "libvirt" system writes "New seat added from logind:
seat0",
the "virtualbox" system does not, which seems to be the relevant
difference
(see log output below)

Further, I found the following command in another forum:

Gdbus introspect --system --dest org.freedesktop.login1 --object-path /org/ freedesktop/login1/seat/seat0

And the relevant difference here is in the org.freedesktop.login1.Seat properties section

...
readonly b CanGraphical = false;
...

on virtualbox. The same command on "libvirt" machine shows "true" here.

So, what is required for a login seat to be treated as "graphical"?

Thanks
Alex

[virtualbox] # lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=867
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation
local
(GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process
?plymouth? (No such file or directory)
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User2002 added
...waiting for ctrl-C and no login screen ...

[libvirt] # lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=793
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/ lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation
local
(GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process
?plymouth? (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/ root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 799: /usr/bin/X :0 -seat seat0 -auth
/var/
run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/ DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.18s] DEBUG: User /org/freedesktop/Accounts/User2002 added
[+0.40s] DEBUG: Got signal 10 from process 799
[+0.40s] DEBUG: XServer 0: Got signal from X server :0
[+0.40s] DEBUG: XServer 0: Connecting to XServer :0
[+0.40s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.40s] DEBUG: Session pid=815: Started with service 'lightdm-greeter', username 'root'
[+0.55s] DEBUG: Session pid=815: Authentication complete with return value
0:
Success
[+0.55s] DEBUG: Seat seat0: Session authenticated, running command
[+0.55s] DEBUG: Session pid=815: Running command /usr/sbin/lightdm-gtk-greeter
[+0.55s] DEBUG: Creating shared data directory /var/lib/lightdm-data/root [+0.55s] DEBUG: Session pid=815: Logging to /var/log/lightdm/seat0-greeter.log
[+0.55s] DEBUG: Activating VT 7
[+0.81s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false [+1.40s] DEBUG: Greeter start authentication for alex
[+1.40s] DEBUG: Session pid=855: Started with service 'lightdm', username 'alex'
[+1.41s] DEBUG: Session pid=855: Got 1 message(s) from PAM
[+1.41s] DEBUG: Prompt greeter with 1 message(s)

<div dir="auto"><br><br><div data-smartmail="gmail_signature">Dave</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 12, 2023, 11:09 Alexander Puchmayr &lt;<a href="mailto:[email protected]">alexander.
[email protected]</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Samstag, 11. März 2023, 13:03:41 CET Alexander Puchmayr wrote:<br>
&gt; Hi there,<br>
&gt; <br>
&gt; After having done a world update, neither sddm nor lightdm do start an<br> &gt; Xserver anymore. The X server itself runs fine, I can start it from the<br>
&gt; console and I after setting DISPLAY properly can even start programs using<br>
&gt; it, but the login managers do not start X for some reason.<br>
&gt; <br>
&gt; No hint so far in the logs, and no ideas where I should looking.<br>
&gt; <br>
&gt; The system is running inside a virtualbox VM, with Win10 as host operating<br>
&gt; system.<br>
&gt; <br>

Its even getting more strange, the very same image copied from the windows <br> laptop to a linux box and started with kvm/libvirt works fine, but in windows/<br>
virtualbox it doesn&#39;t.<br>

Now I have two completely identical systems which only differn in the <br> hypervisor they&#39;re started with, named &quot;virtualbox&quot; and &quot;libvirt&quot;. On both <br>
systems, I start lightdm from the command line with -d option, and compare the <br>
results.<br>

Intrestingly the &quot;libvirt&quot; system writes &quot;New seat added from logind: seat0&quot;, <br>
the &quot;virtualbox&quot; system does not, which seems to be the relevant difference <br>
(see log output below)<br>

Further, I found the following command in another forum:<br>

Gdbus introspect --system --dest org.freedesktop.login1 --object-path /org/<br> freedesktop/login1/seat/seat0<br>

And the relevant difference here is in the org.freedesktop.login1.Seat <br> properties section<br>

...<br>
readonly b CanGraphical = false;<br>
...<br>

on virtualbox. The same command on &quot;libvirt&quot; machine shows &quot;true&quot; here.<br>

So, what is required for a login seat to be treated as &quot;graphical&quot;?  <br>

Thanks<br>
    Alex<br>


[virtualbox] # lightdm -d<br>
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log<br>
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=867<br> [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/<br> lightdm.conf.d<br>
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/<br> lightdm.conf.d<br>
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d<br>
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf<br> [+0.00s] DEBUG: Registered seat module local<br>
[+0.00s] DEBUG: Registered seat module xremote<br>
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager<br>
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local <br>
(GLocalVfs) for ?gio-vfs?<br>
[+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will <br> deadlock if server is GDBus &lt; 2.73.3)<br>
[+0.02s] DEBUG: Monitoring logind for seats<br>
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager<br>
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process <br>
?plymouth? (No such file or directory)<br>
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts<br>
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User2001 added<br>
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added<br>
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User2002 added<br>
...waiting for ctrl-C and no login screen ...<br>

[libvirt] # lightdm -d<br>
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log<br>
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=793<br> [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/<br> lightdm.conf.d<br>
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/<br> lightdm.conf.d<br>
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d<br>
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf<br> [+0.00s] DEBUG: Registered seat module local<br>
[+0.00s] DEBUG: Registered seat module xremote<br>
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager<br>
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will <br> deadlock if server is GDBus &lt; 2.73.3)<br>
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local <br>
(GLocalVfs) for ?gio-vfs?<br>
[+0.01s] DEBUG: Monitoring logind for seats<br>
[+0.01s] DEBUG: New seat added from logind: seat0<br>
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*<br> [+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no<br>
[+0.01s] DEBUG: Seat seat0: Starting<br>
[+0.01s] DEBUG: Seat seat0: Creating greeter session<br>
[+0.01s] DEBUG: Seat seat0: Creating display server of type x<br>
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process <br>
?plymouth? (No such file or directory)<br>
[+0.01s] DEBUG: Using VT 7<br>
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7<br>
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log<br>
[+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/<br> root/:0<br>
[+0.01s] DEBUG: XServer 0: Launching X Server<br>
[+0.01s] DEBUG: Launching process 799: /usr/bin/X :0 -seat seat0 -auth /var/<br>
run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch<br>
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0<br> [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager<br>
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/<br> DisplayManager/Seat0<br>
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts<br>
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User2001 added<br>
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added<br>
[+0.18s] DEBUG: User /org/freedesktop/Accounts/User2002 added<br>
[+0.40s] DEBUG: Got signal 10 from process 799<br>
[+0.40s] DEBUG: XServer 0: Got signal from X server :0<br>
[+0.40s] DEBUG: XServer 0: Connecting to XServer :0<br>
[+0.40s] DEBUG: Seat seat0: Display server ready, starting session <br> authentication<br>
[+0.40s] DEBUG: Session pid=815: Started with service &#39;lightdm-greeter&#39;, <br>
username &#39;root&#39;<br>
[+0.55s] DEBUG: Session pid=815: Authentication complete with return value 0: <br>
Success<br>
[+0.55s] DEBUG: Seat seat0: Session authenticated, running command<br>
[+0.55s] DEBUG: Session pid=815: Running command /usr/sbin/lightdm-gtk-greeter<br>
[+0.55s] DEBUG: Creating shared data directory /var/lib/lightdm-data/root<br> [+0.55s] DEBUG: Session pid=815: Logging to /var/log/lightdm/seat0-greeter.log<br>
[+0.55s] DEBUG: Activating VT 7<br>
[+0.81s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false<br> [+1.40s] DEBUG: Greeter start authentication for alex<br>
[+1.40s] DEBUG: Session pid=855: Started with service &#39;lightdm&#39;, username <br>
&#39;alex&#39;<br>
[+1.41s] DEBUG: Session pid=855: Got 1 message(s) from PAM<br>
[+1.41s] DEBUG: Prompt greeter with 1 message(s)<br>




</blockquote></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)