Failed to connect to socket /sys/fs/cgroup/cgmanager/sock: No such file or directory

Bug #1535416 reported by Barry Warsaw
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
schroot (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Since a recent Xenial dist-upgrade, schroot spews dbus errors, but doesn't seem to affect operation.

% schroot -u root -c xenial-amd64
Failed opening dbus connection: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /sys/fs/cgroup/cgmanager/sock: No such file or directory
(xenial-amd64)root@limelight:/home/barry#

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: schroot 1.6.10-1ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 18 14:03:54 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-07-12 (1650 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
SourcePackage: schroot
UpgradeStatus: Upgraded to xenial on 2011-12-23 (1486 days ago)
modified.conffile..etc.schroot.default.fstab: [modified]
mtime.conffile..etc.schroot.default.fstab: 2014-12-02T11:25:38.692897

Revision history for this message
Barry Warsaw (barry) wrote :
Revision history for this message
Barry Warsaw (barry) wrote :

Of course, running sbuild with any chroot spews *tons* of these errors, so it's fairly annoying.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in schroot (Ubuntu):
status: New → Confirmed
Changed in schroot (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.