session-init-less session-init session

[Dimitri John Ledkov]

Ursinha reports that upstart-app-launch fails, as it cannot connect to session-init.

Turns out there is a stale .session file with pid 1625, yet pid 1625 is not present. It appears that no other session-init started, nor original one respawned.

xsession-error suggests that it segfaulted, yet there are no init crash file from whoopsie (but there are a few other crash files isntead)

There are processes left, which clearly have been started by now absent session-init. Eg. dconf-service has the stale UPSTART_SESSION socket set in it's environ.

It's quite confusing. But it seems that nothing noticed that session-init segfaulted and nothing restarted it / recovered it. And no state information was serialised.

[Dimitri John Ledkov (xnox)]

process 1625: arguments to dbus_message_iter_open_container() were incorrect, assertion "(type == DBUS_TYPE_ARRAY && contained_signature && *contained_signature == DBUS_DICT_ENTRY_BEGIN_CHAR) || (contained_signature == NULL || _dbus_check_is_valid_signature (contained_signature))" failed in file ../../dbus/dbus-message.c line 2800.
This is normally a bug in some application using the D-Bus library.
Segmentation fault (core dumped)

Note that process 1625 was the session init process.

[James Hunt (jamesodhunt)]

This is very odd - #3 suggests the failure is in the auto-generated D-Bus binding code.