Unity greeter show the cursor 0.2 seconds and end
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-greeter (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Maybe something goes bad during some updates. If I want to use lightdm, I needed to fallback to lightdm-gtk-greeter instead of unity-greeter.
Here is my config files:
$ find /etc/lightdm/
/etc/lightdm/
/etc/lightdm/
/etc/lightdm/
/etc/lightdm/
/etc/lightdm/
/etc/lightdm/
/etc/lightdm/
/etc/lightdm/
From the log I can read in /var/log/
Failed to register client: GDBus.Error:
[..]
[+0,21s] WARNING: Failed to open configuration file: Aucun fichier ou dossier de ce type
[+0,21s] WARNING: Failed to open sessions directory: Erreur à l'ouverture du répertoire « /usr/share/
[..]
[+0,22s] DEBUG: unity-greeter.
[+0,22s] DEBUG: unity-greeter.
(gnome-
[END]
Wheras in /var/log/
(EE) Server terminated successfully (0). Closing log file.
[END]
$ dpkg -l | awk '{print $2}' | egrep -i "(lightdm|greeter)"
liblightdm-
lightdm
lightdm-gtk-greeter
lightdm-
lightdm-
unity-greeter
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-8-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
Date: Sat Oct 19 09:26:22 2013
InstallationDate: Installed on 2013-07-01 (109 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130701)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: unity-greeter
UpgradeStatus: No upgrade log present (probably fresh install)
Interesting: sometimes it works normally at boot, sometimes it does not but it works if I restart lightdm service one or two times (without doing anything else). It may be a race condition that may be link with bug #1029790 (but this one should be fixed now).
When it fails, it stop just before "[+0,23s] DEBUG: background. vala:470: Regenerating backgrounds". In fact I see the mouse on black background and then it's gone.
I attach both fail (*.old) and working logs (the second one just after restarting lightdm service twice).