Summary: twice, bug happened when service org.gtk.vfs.Daemon is
activating *after* org.a11y.atspi.Registry is activated.

Details below.

Bug just happened again on unlocking session (versus switching users).

I compared the output of journalctl.

## Around unlock time: nothing to see

Around unlock time, journalctl only shows lightdm cleanup activity.
Then, only when bug happens, lightdm starts again the whole sequence :

systemd[somepid]: Starting User Manager for UID 110...
systemd-logind[749]: New session c9 of user lightdm.
systemd[somepid]: Started Session c9 of user lightdm.
...

## Around lock time: same correlation between log order and bug
occurrence

Again

Indeed, bug happens when log is in this order:

at-spi-bus-launcher[25560]: dbus-daemon[25565]: Activating service 
name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=25557 
comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
at-spi-bus-launcher[25560]: dbus-daemon[25565]: Successfully activated service 
'org.a11y.atspi.Registry'
at-spi-bus-launcher[25560]: SpiRegistry daemon is running with well-known name 
- org.a11y.atspi.Registry
dbus-daemon[25559]: [session uid=110 pid=25559] Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' 
(uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")

and things go smoothly when log is in this order:

at-spi-bus-launcher[15685]: dbus-daemon[15690]: Activating service 
name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=15682 
comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
dbus-daemon[15684]: [session uid=110 pid=15684] Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' 
(uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
at-spi-bus-launcher[15685]: dbus-daemon[15690]: Successfully activated service 
'org.a11y.atspi.Registry'
at-spi-bus-launcher[15685]: SpiRegistry daemon is running with well-known name 
- org.a11y.atspi.Registry

Summary: twice, bug happened when service org.gtk.vfs.Daemon is
activating *after* org.a11y.atspi.Registry is activated.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1776475

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  New

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:      18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
    Installed: 1.26.0-0ubuntu1
    Candidate: 1.26.0-0ubuntu1
    Version table:
   *** 1.26.0-0ubuntu1 500
          500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to