[desktop] apps don't start, missing logs

[dinamic]

update. Fresh install of 17.04 same result, the apps don't start

Ubuntu 17.04 + proposed (unity8 desktop session)
unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic]

apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8

[Daniel van Vugt (vanvugt)]

Which apps don't start?

If you're referring to native apps that don't have icons then please try:
  ubuntu-app-launch ...
like:
  ubuntu-app-launch qterminal

[dinamic (dinamic6661)]

none of the app starts, native, X11, snaps

[dinamic (dinamic6661)]

none of the app starts, native, X11 with libertine, snaps native, Qt5, Gtk3+ with ubuntu-app-launch

[dinamic (dinamic6661)]

from .xsession-errors (when i try to launch apps)

upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539157340067) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539157340067) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (tiled-1478539421897621) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (tiled-1478539421897621) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (tiled-1478539423294864) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (tiled-1478539423294864) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539424742531) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539424742531) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Fa...

[dinamic (dinamic6661)]

cgmanager/zesty,now 0.41-2 amd64 [installed,automatic]

[dinamic (dinamic6661)]

looks similar to this bug https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1535058

[dinamic (dinamic6661)]

sudo systemctl status cgmanager
● cgmanager.service - Cgroup management daemon
   Loaded: loaded (/lib/systemd/system/cgmanager.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2016-11-07 19:18:01 EET; 27min ago
 Main PID: 1698 (code=exited, status=1/FAILURE)
      CPU: 0

Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Service hold-off time over, scheduling restart.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: Stopped Cgroup management daemon.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Start request repeated too quickly.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: Failed to start Cgroup management daemon.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state.
Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'.

[dinamic (dinamic6661)]

 systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
● cgmanager.service loaded failed failed Cgroup management daemon
● isc-dhcp-server.service loaded failed failed ISC DHCP IPv4 server
● snap.unity8-session.cgmanager.service loaded failed failed Service for snap application unity8-session.cgmanager

[dinamic (dinamic6661)]

unity8-desktop-session-mir/zesty,zesty,now 1.0.13+17.04.20161103.1-0ubuntu1 all [installed]
unity8-session-snap/zesty,zesty,now 1.0.13+17.04.20161103.1-0ubuntu1 all [installed]

[dinamic (dinamic6661)]

ok, so "gedit -- --desktop_file_hint=unity8.desktop" starts but "ubuntu-app-launch gedit" doesn't so..
it's probably related to U-A-L and cgmanager and systemd (i have no idea what i'm talking about lol)

[dinamic (dinamic6661)]

so i've removed the snap session but nothing changed

systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
● cgmanager.service loaded failed failed Cgroup management daemon
● isc-dhcp-server.service loaded failed failed ISC DHCP IPv4 server

[dinamic (dinamic6661)]

journalctl -u cgmanager
-- Logs begin at Mon 2016-11-07 22:43:26 EET, end at Mon 2016-11-07 23:17:01 EET. --
Nov 07 22:43:41 pixel-MS-7369 systemd[1]: Started Cgroup management daemon.
Nov 07 22:43:41 pixel-MS-7369 cgmanager[1140]: cgmanager: Error mounting unified: No such file or directory
Nov 07 22:43:41 pixel-MS-7369 cgmanager[1140]: cgmanager: failed to collect cgroup subsystems
Nov 07 22:43:45 pixel-MS-7369 systemd[1]: cgmanager.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 22:43:45 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state.
Nov 07 22:43:45 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Service hold-off time over, scheduling restart.
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: Stopped Cgroup management daemon.
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: Started Cgroup management daemon.
Nov 07 22:43:46 pixel-MS-7369 cgmanager[1383]: cgmanager: Error mounting unified: No such file or directory
Nov 07 22:43:46 pixel-MS-7369 cgmanager[1383]: cgmanager: failed to collect cgroup subsystems
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state.
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Service hold-off time over, scheduling restart.
Nov 07 22:43:46 pixel-MS-7369 systemd[1]: Stopped Cgroup management daemon.

[Serge Hallyn (serge-hallyn)]

This is related to the other open bugs caused by systemd starting to mount the unified hierarchy. There had been a branch of cgmanager able to handle unified, around June 2015, but it was only experimental.

Does unity still require cgmanager? Note that cgmanager's deprecation (https://linuxcontainers.org/) was announced some time ago.

[dinamic (dinamic6661)]

clean 17.04 install, same errors

===============================================================

upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478612117783514) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478612117783514) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (ubuntu-system-settings-) main process: unable to connect to CGManager: Unknown error 196609
upstart: application-legacy (ubuntu-system-settings-) post-stop process (7197) terminated with status 255
upstart: Failed to spawn application-legacy (webbrowser-app-) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (webbrowser-app-) post-stop process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (webbrowser-app-) main process: unable to connect to CGManager: Unknown error 196609
upstart: Failed to spawn application-legacy (webbrowser-app-) post-stop process: unable to connect to CGManager: Unknown error 196609

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christopher Townsend (townsend)]

I'm seeing this behavior too on Zesty.

@serge-hallyn,

Yes, parts of the Unity 8 stack are still relying on cgmanager. The future plan is to use systemd and get rid of the cgmanager dependence, but The Future is not now:)

[Ted Gould (ted)]

Fix released for UAL we're using systemd now so there's no cgmanager issue.

[Christian Ehrhardt  (paelzer)]

Thanks for the update and fix to UAL, given the latest comment setting the cgmanager task to invalid to reflect the updated status.