Bug#840618: /etc/xdg/autostart/at-spi-dbus-bus.desktop: 90 second delay during login

2016-11-08 Thread Antonio Ospite 
Package: at-spi2-core
Version: 2.22.0-3
Followup-For: Bug #840618

Dear Maintainer,

I am still experiencing this issue with 2.22.0-3 when using
gnome-flashback.

Sam (Morris), are you too?

AFAICS it does not happen with a normal gnome-session.

Do you have any suggestion about how I can verify if this is a problem
specific to gnome-flashback?

I looked at the logs when launching a normal gnome-session and I could not
find any mention to at-spi-dbus-bus.desktop, so I tried to remove
/etc/xdg/autostart/at-spi-dbus-bus.desktop and the problem goes away
with gnome-flashback-session too, now I see the service started via
systemd:

  dbus-daemon[1736]: Activating via systemd: service name='org.a11y.Bus' 
unit='at-spi-dbus-bus.service'

When /etc/xdg/autostart/at-spi-dbus-bus.desktop was in place I did not
get this message.

Do the two mechanisms conflict? I mean /etc/xdg/autostart/ and using
systemd user units?

I am attaching an excerpt of the journalctl output of when I get the
problem. I also noticed some assertion failures but they don't seem to
be harmful.

Thanks,
   Antonio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages at-spi2-core depends on:
ii  libatspi2.0-0  2.22.0-3
ii  libc6  2.24-5
ii  libdbus-1-31.10.12-1
ii  libglib2.0-0   2.50.2-1
ii  libx11-6   2:1.6.3-1
ii  libxtst6   2:1.2.2-1+b1

at-spi2-core recommends no packages.

at-spi2-core suggests no packages.

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: X.Org X Server 1.18.4
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: Release Date: 2016-07-19
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: X Protocol Version 11, 
Revision 0
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: Build Operating System: 
Linux 3.16.0-4-amd64 x86_64 Debian
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: Current Operating 
System: Linux jcn 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 
root=UUID=604c68ad-bd5f-4617-9f62-1e0cada91687 ro quiet video=1024x768
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: Build Date: 06 September 
2016  01:32:44PM
nov 08 09:44:25 jcn /usr/lib/gdm3/gdm-x-session[1788]: xorg-server 2:1.18.4-2 
(https://www.debian.org/support)
...
nov 08 09:44:26 jcn systemd[1773]: Started D-Bus User Message Bus.
nov 08 09:44:26 jcn dbus-daemon[1796]: Successfully activated service 
'org.freedesktop.systemd1'
nov 08 09:44:26 jcn /usr/lib/gdm3/gdm-x-session[1788]: /etc/gdm3/Xsession: 
Beginning session setup...
nov 08 09:44:26 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting 
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
nov 08 09:44:26 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting DISPLAY=:0
nov 08 09:44:26 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting 
XAUTHORITY=/run/user/1000/gdm/Xauthority
nov 08 09:44:29 jcn /usr/lib/gdm3/gdm-x-session[1788]: localuser:ao2 being 
added to access control list
nov 08 09:44:29 jcn dbus-daemon[1796]: Activating service name='ca.desrt.dconf'
nov 08 09:44:29 jcn dbus-daemon[1796]: Successfully activated service 
'ca.desrt.dconf'
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting LANG=it_IT.utf8
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting GDM_LANG=it_IT.utf8
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting DISPLAY=:0
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting USERNAME=ao2
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting USER=ao2
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting 
DESKTOP_SESSION=gnome-flashback-metacity
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]: 
dbus-update-activation-environment: setting PWD=/home/ao2
nov 08 09:44:30 jcn /usr/lib/gdm3/gdm-x-session[1788]:

Bug#840618: /etc/xdg/autostart/at-spi-dbus-bus.desktop: 90 second delay during login

2016-10-19 Thread Sam Morris 
> Which dm are you using? (lightdm, gdm, xdm, something else?)

gdm3, and I should have mentioned that I'm using the gnome-flashback
session.

> Could you run 

> ps axfu 

> in a text console during that 90s delay?

As attached.

> Does it happen when using startx instead?

Yes (I am running 'startx
/usr/lib/gnome-flashback/gnome-flashback-metacity').

-- 
Sam Morris 
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 2  0.0  0.0  0 0 ?S10:25   0:00 [kthreadd]
root 3  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[ksoftirqd/0]
root 5  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[kworker/0:0H]
root 7  0.0  0.0  0 0 ?S10:25   0:00  \_ [rcu_sched]
root 8  0.0  0.0  0 0 ?S10:25   0:00  \_ [rcu_bh]
root 9  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[migration/0]
root10  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[lru-add-drain]
root11  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[watchdog/0]
root12  0.0  0.0  0 0 ?S10:25   0:00  \_ [cpuhp/0]
root13  0.0  0.0  0 0 ?S10:25   0:00  \_ [cpuhp/1]
root14  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[watchdog/1]
root15  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[migration/1]
root16  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[ksoftirqd/1]
root18  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[kworker/1:0H]
root19  0.0  0.0  0 0 ?S10:25   0:00  \_ [kdevtmpfs]
root20  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [netns]
root21  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[khungtaskd]
root22  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[oom_reaper]
root23  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [writeback]
root24  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[kcompactd0]
root26  0.0  0.0  0 0 ?SN   10:25   0:00  \_ [ksmd]
root27  0.0  0.0  0 0 ?SN   10:25   0:00  \_ 
[khugepaged]
root28  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [crypto]
root29  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[kintegrityd]
root30  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [bioset]
root31  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [kblockd]
root32  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[devfreq_wq]
root33  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [watchdogd]
root34  0.0  0.0  0 0 ?S10:25   0:00  \_ 
[kworker/1:1]
root35  0.0  0.0  0 0 ?S10:25   0:00  \_ [kswapd0]
root36  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [vmstat]
root49  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [kthrotld]
root50  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[ipv6_addrconf]
root56  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [deferwq]
root94  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [kpsmoused]
root97  0.0  0.0  0 0 ?S<   10:25   0:00  \_ [ata_sff]
root   106  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_0]
root   107  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_0]
root   108  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_1]
root   109  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_1]
root   110  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_2]
root   111  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_2]
root   112  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_3]
root   113  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_3]
root   114  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_4]
root   115  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_4]
root   116  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_5]
root   117  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_5]
root   118  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_6]
root   119  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_6]
root   120  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_7]
root   121  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_7]
root   122  0.0  0.0  0 0 ?S10:25   0:00  \_ [scsi_eh_8]
root   123  0.0  0.0  0 0 ?S<   10:25   0:00  \_ 
[scsi_tmf_8]
root   124  0.0  0.0  0 0 ?S10:25   0:00  \_

Bug#840618: /etc/xdg/autostart/at-spi-dbus-bus.desktop: 90 second delay during login

2016-10-18 Thread Samuel Thibault 
Hello,

Sam Morris, on Thu 13 Oct 2016 11:31:50 +0100, wrote:
> When logging into gnome-flashback there is a 90 second delay during
> which only a black screen is displayed, before nautilus/gnome-panel etc
> appear.

Which dm are you using? (lightdm, gdm, xdm, something else?)

Could you run 

ps axfu 

in a text console during that 90s delay?

Does it happen when using startx instead?

Samuel

Bug#840618: /etc/xdg/autostart/at-spi-dbus-bus.desktop: 90 second delay during login

2016-10-13 Thread Sam Morris 
Package: at-spi2-core
Version: 2.22.0-1
Severity: normal
File: /etc/xdg/autostart/at-spi-dbus-bus.desktop

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

When logging into gnome-flashback there is a 90 second delay during
which only a black screen is displayed, before nautilus/gnome-panel etc
appear.

According to the logs, this is caused by at-spi2-core:

Oct 13 11:17:04 wintermute at-spi-dbus-bus.desktop[1933]: Activating service 
name='org.a11y.atspi.Registry'
Oct 13 11:17:04 wintermute at-spi-dbus-bus.desktop[1933]: Successfully 
activated service 'org.a11y.atspi.Registry'
Oct 13 11:17:04 wintermute org.a11y.atspi.Registry[1940]: SpiRegistry daemon is 
running with well-known name - org.a11y.atspi.Registry
Oct 13 11:17:05 wintermute gnome-settings-[1941]: g_task_return_error: 
assertion 'error != NULL' failed
Oct 13 11:18:33 wintermute gnome-session[1800]: gnome-session-binary[1800]: 
WARNING: Application 'at-spi-dbus-bus.desktop' failed to register before timeout
Oct 13 11:18:33 wintermute gnome-session-binary[1800]: WARNING: Application 
'at-spi-dbus-bus.desktop' failed to register before timeout
Oct 13 11:18:34 wintermute gnome-panel[2123]: Theme parsing error: 
gnome-panel-dark.css:25:8: not a number
Oct 13 11:18:34 wintermute gnome-panel[2123]: Theme parsing error: 
gnome-panel-dark.css:25:15: Using Pango syntax for the font: style property is 
deprecated; please use CSS syntax
Oct 13 11:18:34 wintermute gnome-panel[2123]: Theme parsing error: 
gnome-panel-dark.css:25:8: not a number
Oct 13 11:18:34 wintermute gnome-panel[2123]: Theme parsing error: 
gnome-panel-dark.css:25:15: Using Pango syntax for the font: style property is 
deprecated; please use CSS syntax
Oct 13 11:18:35 wintermute gnome-flashback[2133]: Failed to launch ibus-daemon: 
Failed to execute child process "ibus-daemon" (No such file or directory)
Oct 13 11:18:36 wintermute gnome-panel.desktop[2123]: Unable to open desktop 
file /usr/share/applications/gnome-terminal.desktop for panel launcher: No such 
file or directory
Oct 13 11:18:36 wintermute tracker-store.desktop[2240]: (uint32 1,)
Oct 13 11:18:37 wintermute git-annex.desktop[2239]: git-annex: Nothing listed 
in /home/sam/.config/git-annex/autostart
Oct 13 11:18:37 wintermute gnome-session-binary[1800]: Entering running state
Oct 13 11:18:37 wintermute at-spi-bus-laun[1933]: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (550, 'testing-debug'), (550, 'testing'), (520, 
'unstable-debug'), (520, 'unstable'), (510, 'experimental-debug'), (510, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages at-spi2-core depends on:
ii  libatspi2.0-0  2.22.0-1
ii  libc6  2.24-3
ii  libdbus-1-31.10.10-1
ii  libglib2.0-0   2.50.0-2
ii  libx11-6   2:1.6.3-1
ii  libxtst6   2:1.2.2-1+b1

at-spi2-core recommends no packages.

at-spi2-core suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIvBAEBCAAZBQJX/2KLEhxzYW1Acm9ib3RzLm9yZy51awAKCRDSC0ICXNonuR1B
D/9r0/D1bpS/8iFKZUmYGItI3F53R9KNyPjW7b4NDW4QOdFb4IWBiuNUyVp78Qlm
xL4LnI/WKBFjSUsc9+lHc8rXG3rH5Pw3fPlsOJbQcwjE65Qb6PitKZxA8PkBuWOi
I6WSgjQIuxTveDO32sGDllRyozlEfVTMM9nbcDEMVDMnvaVHCC+Pm8LmTJokUf0J
VlSDbhAsPsgdAtyP/hWH94CN88yIx3TsZOJfQeSLBK97T/iKUIFzQTeoz3zwRKzM
dwY2DkXj1FpF4cO48KEWn7fgWSlKmdegKkvs6tiic149yFdI8tDB+NugBHUGnndU
J6M+zcQM8yD3jIa8y5TlXPKnhJM/vePWguAgM+FKZLZhuOK5VVZSzmSEBSfhpdHl
ZJKd2Ee+Spt4es5X5uDJ+A3dYf5VziA2Wb03wPe+YAXFDrUTHyKDpBku4Pc0Acff
pAFtXZnJg436Y0IJrstVha3WG1/FwuRFark7sPuPE4Ewk3ZwHkLcEn2fkY5tbcwo
uftnVCtFc7WVFM6H7SRADulBXQwVXXchFb7QgEOiwf+nKzaBm0aj4FGEjUBfNZuQ
/ZzNwrJ1W0KMetSeTL/9t/fjlqvJmImsIa2baNZOACaGWEIxBy7D8eegyupuW9PN
y1ARLuBVuUGYiqGsQnmtOI7beBzPu5ovSwLBtQWN6mzmAg==
=GtG0
-END PGP SIGNATURE-