Public bug reported:
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.
** Affects: upstart (Ubuntu)
Importance: Medium
Status: Confirmed
** Tags: avengers r31
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255569
Title:
session-init-less session-init session
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1255569/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
