[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2016-05-01 Thread Tessa
Just ran into this tonight on a Xenial container running on a Xenial
host:

May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/ondemand.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting LSB: Set the CPU Frequency 
Scaling governor to "ondemand"...
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/mysql.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting LSB: Start and stop the mysql 
database server daemon...
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/irqbalance.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting LSB: daemon to balance 
interrupts for SMP systems...
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-user-sessions.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting Permit User Sessions...
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/apport.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting LSB: automatic crash report 
generation...
May  1 09:12:55 mysqlbench systemd[1]: Started LSB: Start and stop the mysql 
database server daemon.
May  1 09:12:55 mysqlbench systemd[1]: Started Permit User Sessions.
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/plymouth-quit.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting Terminate Plymouth Boot 
Screen...
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/plymouth-quit-wait.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Starting Hold until boot process 
finishes up...
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-user-sessions.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/mysql.service: Operation not permitted
May  1 09:12:55 mysqlbench systemd[1]: Started Hold until boot process finishes 
up.
May  1 09:12:55 mysqlbench systemd[1]: Started LSB: automatic crash report 
generation.
May  1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on 
/system.slice/console-getty.service: Operation not permitted

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413193

Title:
  [vivid]  Failed to reset devices.list

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Vivid i386 booted with systemd

  from syslog:

   dbus[668]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
   systemd[1]: Starting Hostname Service...
   systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
   systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
   dbus[668]: [system] Successfully activated service 
'org.freedesktop.hostname1'
   systemd[1]: Started Hostname Service.

  sys/fs/cgroup/devices/system.slice   owned by root and set 'read-only'
  sys/fs/cgroup/devices/user.slice  "   "   
   "

  (all the files are 0 bytes)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Wed Jan 21 13:23:53 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System 

[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2015-09-05 Thread David Favor
Still broken in systemd 219.

If someone knows how to fix this, please update this ticket. Thanks.

rmt-net8# lxc-create --version
1.1.2

rmt-net8# lxcfs --version
FUSE library version: 2.9.2
fusermount version: 2.9.2
using FUSE kernel interface version 7.19

rmt-net8# psall | grep lxcfs
root  1461  0.1  0.0  22060  2820 ?Ss   17:55   0:02 /usr/bin/lxcfs 
-f -s -o allow_other /var/lib/lxcfs/
root 13887  0.0  0.0   6616   796 pts/2S+   18:29   0:00 grep 
--color=auto lxcfs

___

rmt-net8# lxc-start -n rmt-lightweight-vivid -F
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK 
+SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID 
-ELFUTILS +KMOD -IDN)
Detected virtualization lxc.
Detected architecture x86-64.

Welcome to Ubuntu 15.04!

Set hostname to .
Failed to install release agent, ignoring: No such file or directory
Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket 
failed to load: No such file or directory.
Cannot add dependency job for unit display-manager.service, ignoring: Unit 
display-manager.service failed to load: No such file or directory.
[  OK  ] Reached target Encrypted Volumes.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid: Permission denied
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice: 
Permission denied
[  OK  ] Created slice System Slice.
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/systemd-setup-dgram-qlen.service: 
Permission denied
 Starting Increase datagram queue length...
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/system-getty.slice: Permission denied
[  OK  ] Created slice system-getty.slice.
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/system-container\x2dgetty.slice: 
Permission denied
[  OK  ] Created slice system-container\x2dgetty.slice.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Swap.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/user.slice: 
Permission denied
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Listening on Journal Socket.
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/resolvconf.service: Permission denied
 Starting Nameserver information manager...
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/systemd-remount-fs.service: Permission 
denied
 Starting Remount Root and Kernel File Systems...
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-mqueue.mount: Permission denied
 Mounting POSIX Message Queue File System...
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/udev-finish.service: Permission denied
 Starting Copy rules generated while the root was ro...
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-hugepages.mount: Permission denied
 Mounting Huge Pages File System...
[  OK  ] Reached target Remote File Systems (Pre).
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-cpuinfo.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-sys-net.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-uptime.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-lxc-tty2.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-sysrq\x2dtrigger.mount: Permission 
denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/sys-fs-fuse-connections.mount: 
Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/-.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-diskstats.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-stat.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-lxc-console.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/proc-meminfo.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-lxc-tty4.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-lxc-tty3.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/dev-lxc-tty1.mount: Permission denied
Failed to reset devices.list on 
/lxc/rmt-lightweight-vivid/system.slice/sys-kernel-debug.mount: Permission 

[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2015-02-15 Thread Martin Pitt
Yes, I know, but -10 isn't in vivid yet; this bug will be auto-closed
once  it migrates from vivid-proposed.

** Changed in: systemd (Ubuntu)
   Status: Fix Released = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413193

Title:
  [vivid]  Failed to reset devices.list

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Vivid i386 booted with systemd

  from syslog:

   dbus[668]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
   systemd[1]: Starting Hostname Service...
   systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
   systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
   dbus[668]: [system] Successfully activated service 
'org.freedesktop.hostname1'
   systemd[1]: Started Hostname Service.

  sys/fs/cgroup/devices/system.slice   owned by root and set 'read-only'
  sys/fs/cgroup/devices/user.slice
   

  (all the files are 0 bytes)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Wed Jan 21 13:23:53 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413193/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2015-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 218-10ubuntu1

---
systemd (218-10ubuntu1) vivid; urgency=medium

  [ Martin Pitt ]
  * Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also, check if devices are actually defined
  in /etc/network/interfaces as we don't use Debian's net.agent.
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

  * ifup@.service: Fix syntax error. (LP: #1421556, #1420601)

  [ Didier Roche ]
  * Add systemd-fsckd multiplexer and feed its output to plymouth. This
provides an aggregate progress report of running file system checks and
also allows cancelling them with ^C.
(LP: #1316796; Closes: #775093, #758902)

systemd (218-10) experimental; urgency=medium

  * Pull latest keymaps from upstream git. (LP: #1334968, #1409721)
  * rules: Fix by-path of mmc RPMB partitions and don't blkid them. Avoids
kernel buffer I/O errors and timeouts. (LP: #1333140)
  * Clean up stale mounts when ejecting CD drives with the hardware eject
button. (LP: #1168742)
  * Document systemctl --failed option. (Closes: #767267)
  * Quiesce confusing and irrelevant failed to reset devices.list warning.
(LP: #1413193)
  * When booting with systemd-bootchart, default to run systemd rather than
/sbin/init (which might not be systemd). (LP: #1417059)
  * boot-and-services autopkgtest: Add CgroupsTest to check cgroup
creation/cleanup behaviour. This reproduces #777601 and verifies the fix
for it.

systemd (218-9) experimental; urgency=medium

  [ Martin Pitt ]
  * debian/tests/logind: With dropped systemd-logind-launch we don't have a
visible /sys/fs/cgroup/systemd/ any more under cgmanager. So adjust the
test to check /proc/self/cgroup instead.
  * Add unit-config autopkgtest to check systemd unit/sysv init enabling and
disabling via systemctl. This also reproduces #777613.
  * systemctl: Always install/enable/disable native units, even if there is a
corresponding SysV script and we call update-rc.d; while the latter
handles WantedBy=, it does not handle Alias=. (Closes: #777613)
  * cgroup: Don't trim cgroup trees created by someone else, just the ones
that systemd itself created. This avoids cleaning up empty cgroups from
e.g. LXC. (Closes: #777601)
  * Don't parse /etc/mtab for current mounts, but /proc/self/mountinfo. If the
former is a file, it's most likely outdated on boot, leading to race
conditions and unmounts during boot. (LP: #1419623)

  [ Michael Biebl ]
  * Explicitly disable the features we don't want to build for those with
autodetection. This ensures reliable build results in dirty build
environments.
  * Disable AppArmor support in the udeb build.
  * core: Don't fail to 

[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2015-02-14 Thread dino99
That problem is gone with 218-10

** Changed in: systemd (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413193

Title:
  [vivid]  Failed to reset devices.list

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Vivid i386 booted with systemd

  from syslog:

   dbus[668]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
   systemd[1]: Starting Hostname Service...
   systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
   systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
   dbus[668]: [system] Successfully activated service 
'org.freedesktop.hostname1'
   systemd[1]: Started Hostname Service.

  sys/fs/cgroup/devices/system.slice   owned by root and set 'read-only'
  sys/fs/cgroup/devices/user.slice
   

  (all the files are 0 bytes)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Wed Jan 21 13:23:53 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413193/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2015-02-01 Thread Martin Pitt
This is fixed upstream, will be in 219:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=714e2e1d

** Changed in: systemd (Ubuntu)
   Status: Triaged = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413193

Title:
  [vivid]  Failed to reset devices.list

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Vivid i386 booted with systemd

  from syslog:

   dbus[668]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
   systemd[1]: Starting Hostname Service...
   systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
   systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
   dbus[668]: [system] Successfully activated service 
'org.freedesktop.hostname1'
   systemd[1]: Started Hostname Service.

  sys/fs/cgroup/devices/system.slice   owned by root and set 'read-only'
  sys/fs/cgroup/devices/user.slice
   

  (all the files are 0 bytes)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Wed Jan 21 13:23:53 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413193/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1413193] Re: [vivid] Failed to reset devices.list

2015-02-01 Thread Martin Pitt
** Changed in: systemd (Ubuntu)
   Importance: Undecided = Low

** Changed in: systemd (Ubuntu)
   Status: New = Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413193

Title:
  [vivid]  Failed to reset devices.list

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Vivid i386 booted with systemd

  from syslog:

   dbus[668]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
   systemd[1]: Starting Hostname Service...
   systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
   systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
   dbus[668]: [system] Successfully activated service 
'org.freedesktop.hostname1'
   systemd[1]: Started Hostname Service.

  sys/fs/cgroup/devices/system.slice   owned by root and set 'read-only'
  sys/fs/cgroup/devices/user.slice
   

  (all the files are 0 bytes)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Wed Jan 21 13:23:53 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413193/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp