Re: lightdm (testing): Long waiting time after login
On 16.05.2018 19:51 Dominic Knight wrote:
The output of systemd-analyze looks fine, I think. It really seems like
the bug reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 is causing the
On Wed, 2018-05-16 at 14:53 +0200, Dino wrote:
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=utf-8; format=flowed
This time with attachment...
Am 16.05.2018 um 09:28 schrieb firstname.lastname@example.org:
I just did a fresh install of testing with XFCE. After entering
login credentials the screen was black for 30-60 seconds before
desktop environment showed up. Assuming a bug in XFCE, I
another fresh install with MATE, but a similar effect occured:
login the background image is shown for 30-60 seconds before
desktop is fully loaded.
A look into /var/log/lightdm/lightdm.log showed that the delay
before VT is activated. The log file is attached.
Might this be a bug in lightdm or could a misconfiguragtion
side cause this issue?
[+7.71s] DEBUG: Session pid=691: Running command
[+7.71s] DEBUG: Creating shared data directory
[+7.71s] DEBUG: Session pid=691: Logging to .xsession-errors
[+40.89s] DEBUG: Activating VT 7
[+40.89s] DEBUG: Activating login1 session 2
[+40.89s] DEBUG: Seat seat0 changes active session to
[+40.89s] DEBUG: Seat seat0 changes active session to 2
[+40.89s] DEBUG: Session 2 is already active
what does .xsession-errors say?
what type of device are you installing to?
my recent installs with netinst for testing and having MATE
comes up ok (within a few seconds), but things may have changed
does a stable netinst give same results?
.xsession-errors contains one warning (file is attached), but I
think that it causes the delay.
The device I'm installing to is an UDOO X86
(https://www.udoo.org/udoo-x86/). Basically, it's standard hardware
an Intel CPU. I already had an installation of testing a few months
that didn't show this behaviour.
A stable netinst works just fine, the desktop is loaded almost
immediately. Hence, I assume a package changed recently is the
will give a clue as to what is taking its time?