Dino wrote:
This is a multi-part message in MIME format.
--------------D295C2A19D414A0F9C32AEE8
Content-Type: multipart/alternative;
boundary="------------51A034E61483D85CC097E79C"
--------------51A034E61483D85CC097E79C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
This time with attachment...
Am 16.05.2018 um 09:28 schrieb w...@hllmnn.de:
I just did a fresh install of testing with XFCE. After entering the
login credentials the screen was black for 30-60 seconds before the
desktop environment showed up. Assuming a bug in XFCE, I performed
another fresh install with MATE, but a similar effect occured: after
login the background image is shown for 30-60 seconds before the
desktop is fully loaded.
A look into /var/log/lightdm/lightdm.log showed that the delay happens
before VT is activated. The log file is attached.
Might this be a bug in lightdm or could a misconfiguragtion from my
side cause this issue?
...
[+7.71s] DEBUG: Session pid=691: Running command /etc/X11/Xsession default
[+7.71s] DEBUG: Creating shared data directory /var/lib/lightdm/data/USERNAME
[+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
in packages.
does a stable netinst give same results?
songbird
.xsession-errors contains one warning (file is attached), but I don't
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 with
an Intel CPU. I already had an installation of testing a few months ago
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 reason
for this.
Xsession: X session started for USERNAME at Wed May 16 13:57:36 CEST 2018
dbus-update-activation-environment: setting
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting
XAUTHORITY=/home/USERNAME/.Xauthority
localuser:USERNAME being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=USERNAME
dbus-update-activation-environment: setting LANGUAGE=en_US:en
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/USERNAME
dbus-update-activation-environment: setting DESKTOP_SESSION=lightdm-xsession
dbus-update-activation-environment: setting
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting LOGNAME=USERNAME
dbus-update-activation-environment: setting
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lightdm-xsession
dbus-update-activation-environment: setting
XAUTHORITY=/home/USERNAME/.Xauthority
dbus-update-activation-environment: setting
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/USERNAME
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=lightdm-xsession
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/USERNAME
dbus-update-activation-environment: setting
XDG_DATA_DIRS=/usr/share/mate:/usr/local/share/:/usr/share/
x-session-manager[773]: WARNING: Unable to find provider '' of required
component 'dock'
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh