[Pkg-utopia-maintainers] Bug#884897: dbus-x11: .xinitrc requires "dbus-update-activation-environment --all"

[Simon McVittie]

Control: tags -1 + moreinfo

On Thu, 21 Dec 2017 at 01:34:32 -0200, Carlos Eduardo M. Santos wrote:
> The following problems started after dist-upgrading from jessie to buster

I hope you upgraded from jessie to stretch first, and then from stretch
to buster. Upgrades that skip a release are not supported by Debian.
(If it worked, then it's *probably* OK, but please go via stretch on any
other machines you upgrade in the same way.)

> 1. startx takes a lot of time to launch X;
> 2. gnome-terminal doesn't start.

How do you get into the environment from which you run startx? Is it a
text-mode console (getty/login) or something else?

Is dbus-user-session installed? Is libpam-systemd installed?

What's in your /etc/X11/Xsession.options?

If you drop a script into /etc/X11/Xsession.d/01debug-early or similar
that runs

    env | LC_ALL=C sort | logger -t Xsession-early

then look at the systemd journal, what environment variables are set
there? (In particular LANG, LANGUAGE, LC_anything, DBUS_anything,
XDG_RUNTIME_DIR)

Similarly, if you put

    env | LC_ALL=C sort | logger -t Xsession-late

right at the beginning of 95dbus_update-activation-env, what happens there?

> In journalctl, I found 2 famous messages:
> - gnome-terminal-server[18005]: Unable to init server: Could not connect: Connection refused
> - Failed to activate service 'org.gnome.Terminal': timed out (service_start_timeout=120000ms)

I'm sure you get more messages than just those two. Please show me the
rest of what's logged when you:

- start from not being logged in
- log in at the text-mode prompt, or whatever else you do to get into the
  environment from which you want to run startx
- put a marker in the log: logger -t marker "now I am logged in"
- run startx

The output of systemd-cgls after you get into your GUI session (use
a non-D-Bus-related terminal like xterm) would also be useful
information.

Regards,
    smcv