[Touch-packages] [Bug 1597876] Re: daemon-reload in running system can result in prompt for cryptoswap passphrase

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

-- 
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/1597876

Title:
  daemon-reload in running system can result in prompt for cryptoswap
  passphrase

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This is an extremely odd bug that requires a very specific scenario to
  reproduce:

  1) You need to be using an ecryptfs-style cryptoswap partition (as
  would be setup when you choose "Encrypt my home directory" during the
  installation)

  2) The underlying physical swap partition used for the cryptoswap
  needs to be on a GPT partitioned drive

  3) The GUID specific bit 63 ("no auto mounting") must *not* be set on
  the underlying physical swap partition

  In this scenario, installing/upgrading/reinstalling seemingly *any*
  package with a systemd service will result in the user getting *twice*
  prompted for a passphrase to unlock their cryptoswap partition. If
  upgrades are performed using the graphical Software Updater, the user
  wont be aware of this issue unless they've expanded the details,
  resulting in the Software Updater hanging indefinitely.

  For example, if you have the needed setup, you can easily reproduce
  this bug with:

  sudo apt-get install --reinstall whoopsie

  After which you'll encounter something like this:

  (Reading database ... 177827 files and directories currently installed.)
  Preparing to unpack .../whoopsie_0.2.52.1_amd64.deb ...
  Please enter passphrase for disk primary (cryptswap1) on none! 
  Unpacking whoopsie (0.2.52.1) over (0.2.52) ...
  Preparing to unpack .../libwhoopsie0_0.2.52.1_amd64.deb ...
  Unpacking libwhoopsie0:amd64 (0.2.52.1) over (0.2.52) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Setting up libwhoopsie0:amd64 (0.2.52.1) ...
  Setting up whoopsie (0.2.52.1) ...
  Please enter passphrase for disk primary (cryptswap1) on none! 
  Processing triggers for libc-bin (2.23-0ubuntu3) ...

  (You can just hit enter each time the "Please enter passphrase for..."
  prompt comes up.)

  For some background: in modern systemd times, ecryptfs-style
  cryptoswaps are broken when the underlying physical GPT swap partition
  does not have bit 63 set:

  https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1447282

  During the boot the user is erroneously prompted for a passpharase to
  unlock the cryptoswap (you can hit enter for an empty passphrase, or
  enter any passphrase you want... either way, nothing seems to actually
  be done with it). After the boot completes, the underlying physical
  swap partition will be mounted normally (ie, you wont actually be
  using encrypted swap... so a false sense of security, which is of
  course concerning).

  Although lp:1447282 has been fixed for the most common hardware
  configurations, it's still possible for users to encounter this
  problem in the real-word: ecryptfs-setup-swap currently fails to set
  bit 63 when the physical GPT swap partition is on an NVMe or MMC
  drive:

  https://bugs.launchpad.net/ecryptfs/+bug/1597154

  So one way to reproduce this is to install Ubuntu 16.04 onto an NVMe
  drive and choose "Encrypt my home directory" during the installation.

  To make debugging this easier without requiring an NVMe drive (and
  especially so it's easier to debug in a UEFI VM), I'm attaching a
  script that will unset bit 63 on the underlying GPT swap partitions
  used by any ecryptfs-style cryptoswaps that are present.

  If you run my script:

  sudo python3 unset-bit-63.py

  And then reboot, you should now be able to reproduce this bug.

  Even though fixing lp:1597154 will mean users shouldn't encounter
  (during normal real-world usage) this strange behavior when
  installing/upgrading/reinstalling packages that contain systemd
  services, I have a strong hunch that the fact this can happen at all
  indicates something is quite wonky in either systemd itself or in the
  Debian/Ubuntu specific systemd trigger handling.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+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 1600525] Re: systemd fails to mount on startup via /etc/fstab

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1600525

Title:
  systemd fails to mount on startup via /etc/fstab

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hello!

  (partially) informations first:

  #Kubuntu 16.04:
  #uname -a
  Linux desktop 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04 LTS
  Release:16.04
  Codename:   xenial

  #sudo blkid
  /dev/sda5: LABEL="Daten" UUID="fa600d38-2bda-4a98-8297-4f6bd7ca909c" 
TYPE="ext4" PARTUUID="4dc4a374-05"

  #/etc/fstab (yes, there's an empty line at the end)
  UUID=fa600d38-2bda-4a98-8297-4f6bd7ca909c /home/schiggn/Daten ext4 defaults 0 0

  #journalctl -b -r | grep "Daten"
  Jul 09 20:09:20 desktop systemd[1]: Mounted /home/schiggn/Daten.
  Jul 09 20:09:20 desktop systemd[1]: Mounting /home/schiggn/Daten...
  Jul 09 20:09:20 desktop systemd[1]: Found device WDC_WD10EARS-00Y5B1 Daten.

  #show folder after startup
  root@desktop:~# ls -lha /home/schiggn/Daten/
  insgesamt 8,0K
  drwxrwxr-x  2 schiggn schiggn 4,0K Jun 30 21:35 .
  drwx-- 25 schiggn schiggn 4,0K Jul  9 20:09 ..
  root@desktop:~#

  #mount -v -l
  /dev/sda5 on /home/schiggn/Daten type ext4 (rw,relatime,data=ordered) [Daten]

  #Status
  root@desktop:~# systemctl status home-schiggn-Daten.mount
  ● home-schiggn-Daten.mount - /home/schiggn/Daten
     Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
     Active: active (mounted) since Sa 2016-07-09 20:09:20 CEST; 52min ago
  Where: /home/schiggn/Daten
   What: /dev/sda5
   Docs: man:fstab(5)
     man:systemd-fstab-generator(8)
    Process: 753 ExecMount=/bin/mount 
/dev/disk/by-uuid/fa600d38-2bda-4a98-8297-4f6bd7ca909c /home/schiggn/D

  Jul 09 20:09:20 desktop systemd[1]: Mounting /home/schiggn/Daten...
  Jul 09 20:09:20 desktop systemd[1]: Mounted /home/schiggn/Daten.
  root@desktop:~#

  #systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Problem is, that systemd is mounting correctly with no errors, but the
  folder is still empty.

  sudo mount -a results in an "/home/schiggn/Daten  : already
  mounted"

  a manually "sudo mount /dev/sda5 /home/schiggn/Daten" works as
  expected and the files are shown.

  Can you please help me how to track this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1600525/+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 1601876] Re: /lib/systemd/systemd-journald:6:readlinkat:readlinkat:readlinkat_malloc:readlink_malloc:readlink_and_make_absolute

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1601876

Title:
  /lib/systemd/systemd-
  
journald:6:readlinkat:readlinkat:readlinkat_malloc:readlink_malloc:readlink_and_make_absolute

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  229-4ubuntu6, the problem page at
  https://errors.ubuntu.com/problem/558f8d1b90d53990eddec91858e7def5a61c2f33
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1601876/+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 1599446] Re: 16.04, wrong units start order

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1599446

Title:
  16.04, wrong units start order

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hello!

  squid uses ldap and mysql for authorization , so I added them to squid
  dependencies:

  ### BEGIN INIT INFO
  # Provides:  squid
  # Required-Start:$network $remote_fs $syslog mysql slapd

  
  After=systemd-journald.socket basic.target systemd-journald-dev-log.socket 
mysql.service remote-fs.target network-online.target nss-lookup.target 
system.slice sysinit.target slapd.service


  And symlinks are created in right order:

  S03slapd
  S04mysql
  S05squid

  But really squid is started before mysql (mariadb) and slapd are
  started:

  journalctl -u squid
  -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:44:41 
SAMT. --
  июл 06 13:10:31 inetgw2 systemd[1]: Starting LSB: Squid HTTP Proxy version 
3.x...

  journalctl -u slapd
  -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:36 
SAMT. --
  июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...

  journalctl -u mysql
  -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:46 
SAMT. --
  июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: Start and stop the mysql 
database server daemon...
  июл 06 13:10:43 inetgw2 mysql[2647]:  * Starting MariaDB database server 
mysqld

  
  i.e. real start order is:
  sqiud
  slapd
  mysql

  Expected result is folowing
  slapd
  mysql
  squid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1599446/+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 1605433] Re: [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1605433

Title:
  [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The touchpad does not work as expected. It can't be enabled or
  disabled through FN+F11 combination.

  The light (in the pad) always turns on, regardless of its non
  functionality.

  The problem seems related to bug #1523738, and some say solution #24
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24)
  works, but it didn't for me.

  WORKAROUND: Executing the following via a terminal allows one to disable and 
enable the touchpad:
  xinput set-prop 13 "Device Enabled" 1
  xinput set-prop 13 "Device Enabled" 0

  But it only works if it is enabled from the beginning from the systems
  configuration GUI. If it is disabled, it doesn't do the expected
  behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jul 21 21:07:42 2016
  InstallationDate: Installed on 2016-07-03 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-07-16T11:29:07.694480
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adin   4247 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd
  InstallationDate: Installed on 2016-07-03 (24 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Alienware Alienware 17 R3
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.3
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.3
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+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 1606767] Re: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1606767

Title:
  package systemd 229-4ubuntu7 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I am trying to upgrade from 14 to 15 to 16 LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jul 26 20:42:38 2016
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu7_amd64.deb ...
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu7_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  DuplicateSignature:
   package:systemd:229-4ubuntu7
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu7_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2013-11-04 (995 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=UUID=01bbbe85-6a97-4afc-bc61-f394bbd7bf52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-07-27 (0 days ago)
  dmi.bios.date: 05/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Z77 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/14/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1606767/+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 1606979] Re: /lib/systemd/systemd-journald:6:access:device_set_syspath:sd_device_new_from_syspath:sd_device_new_from_subsystem_sysname:sd_device_new_from_device_id

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1606979

Title:
  /lib/systemd/systemd-
  
journald:6:access:device_set_syspath:sd_device_new_from_syspath:sd_device_new_from_subsystem_sysname:sd_device_new_from_device_id

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  229-4ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/94224ff5cfe3b0330ac4bb07c81eaae03a1593fa
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1606979/+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 1605750] Re: package udev 229-4ubuntu7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1605750

Title:
  package udev 229-4ubuntu7 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  update via synaptic today (22.07.2016) resulted in error message (see
  summary)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CustomUdevRuleFiles: 99_smfpautoconf_samsung.rules 
98_smfpautoconf_samsung.rules
  Date: Fri Jul 22 21:25:58 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2016-07-15 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 3259MAG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=d7f1b4dd-fcc8-44f8-b89a-3e2275279c3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu7 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET74WW (2.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3259MAG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET74WW(2.08):bd11/14/2012:svnLENOVO:pn3259MAG:pvrThinkPadEdgeE530:rvnLENOVO:rn3259MAG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3259MAG
  dmi.product.version: ThinkPad Edge E530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605750/+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 1603135] Re: systemd-journald crashed with SIGABRT in lz_encoder_prepare()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1603135

Title:
  systemd-journald crashed with SIGABRT in lz_encoder_prepare()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Just came up after a dist-upgrade in yakkety and a reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-7
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jul 14 10:44:21 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2013-12-06 (950 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/liblzma.so.5
   ?? () from /lib/x86_64-linux-gnu/liblzma.so.5
   ?? () from /lib/x86_64-linux-gnu/liblzma.so.5
   lzma_block_buffer_encode () from /lib/x86_64-linux-gnu/liblzma.so.5
   lzma_stream_buffer_encode () from /lib/x86_64-linux-gnu/liblzma.so.5
  Title: systemd-journald crashed with SIGABRT in lzma_block_buffer_encode()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1603135/+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 1612294] Re: Boot messages in /var/log/syslog are out of order and with mostly "useless" timestamp

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1612294

Title:
  Boot messages in /var/log/syslog are out of order and with mostly
  "useless" timestamp

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On boot, early kernel boot messages get displayed out of order with
  userspace services starting.  for example.

  _
  Aug  8 21:13:55 ubuntu systemd[1]: Started LVM2 metadata daemon.
  Aug  8 21:13:55 ubuntu systemd[1]: Mounting FUSE Control File System...
  Aug  8 21:13:55 ubuntu systemd[1]: Starting Apply Kernel Variables...
  Aug  8 21:13:55 ubuntu systemd[1]: Starting Create Static Device Nodes in 
/dev...
  Aug  8 21:13:55 ubuntu systemd[1]: Starting Load/Save Random Seed...
  Aug  8 21:13:55 ubuntu systemd[1]: Activating swap /swap.img...
  Aug  8 21:13:55 ubuntu systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Aug  8 21:13:55 ubuntu systemd[1]: Starting udev Coldplug all Devices...
  Aug  8 21:13:55 ubuntu rsyslogd-2039: Could not open output pipe 
'/dev/xconsole':: No such file or directory [v8.16.0 try 
http://www.rsyslog.com/e/2039 ]
  Aug  8 21:13:55 ubuntu systemd[1]: Mounted FUSE Control File System.
  Aug  8 21:13:55 ubuntu systemd[1]: Started Apply Kernel Variables.
  Aug  8 21:13:55 ubuntu systemd[1]: Started Load/Save Random Seed.
  Aug  8 21:13:55 ubuntu rsyslogd-2007: action 'action 12' suspended, next 
retry is Mon Aug  8 21:14:25 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Aug  8 21:13:55 ubuntu systemd[1]: Started Create Static Device Nodes in /dev.
  Aug  8 21:13:55 ubuntu systemd[1]: Started Flush Journal to Persistent 
Storage.
  Aug  8 21:13:55 ubuntu systemd[1]: Starting udev Kernel Device Manager...
  Aug  8 21:13:55 ubuntu systemd[1]: Started udev Kernel Device Manager.
  Aug  8 21:13:55 ubuntu systemd[1]: Started udev Coldplug all Devices.
  Aug  8 21:13:55 ubuntu systemd[1]: Started Dispatch Password Requests to 
Console Directory Watch.
  Aug  8 21:13:55 ubuntu systemd[1]: Activated swap /swap.img.
  Aug  8 21:13:55 ubuntu systemd[1]: Reached target Swap.
  Aug  8 21:13:55 ubuntu systemd-udevd[1507]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f0, key code 152): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f1, key code 238): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f2, key code 227): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f3, key code 205): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f4, key code 225): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f5, key code 224): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1456]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event2' (scan code 0x900f8, key code 372): Invalid 
argument
  Aug  8 21:13:55 ubuntu systemd-udevd[1497]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  Aug  8 21:13:55 ubuntu kernel: [0.00] Initializing cgroup subsys 
cpuset
  Aug  8 21:13:55 ubuntu systemd[1]: Found device 82578DM Gigabit Network 
Connection.
  Aug  8 21:13:55 ubuntu kernel: [0.00] Initializing cgroup subsys cpu
  Aug  8 21:13:55 ubuntu kernel: [0.00] Initializing cgroup subsys 
cpuacct
  Aug  8 21:13:55 ubuntu systemd-udevd[1506]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  Aug  8 21:13:55 ubuntu kernel: [0.00] Linux version 4.4.0-34-generic 
(buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) 
#53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 (Ubuntu 4.4.0-34.53-generic 4.4.15)
  Aug  8 21:13:55 ubuntu kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=1931f21a-ee2e-4f02-abf6-6a0527f62df3 ro
  Aug  8 21:13:55 ubuntu systemd[1]: Listening on Load/Save RF Kill Switch 
Status /dev/rfkill Watch.
  Aug  8 21:13:55 ubuntu kernel: [0.00] KERNEL supported cpus:
  Aug  8 21:13:55 ubuntu kernel: [0.00]   Intel GenuineIntel
  Aug  8 21:13:55 ubuntu systemd[1]: Reached target Sound Card.
  Aug  8 21:13:55 ubuntu kernel: [0.00]   AMD AuthenticAMD
  Aug  8 21:13:55 ubuntu kernel: [0.00]   Centaur CentaurHauls
  Aug  8 21:13:55 ubuntu systemd[1]: 

[Touch-packages] [Bug 1612340] Re: document that PrivateTmp does not work for user instances

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

** Changed in: systemd (Ubuntu)
   Status: Invalid => Won't Fix

-- 
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/1612340

Title:
  document that PrivateTmp does not work for user instances

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  When setting the option PrivateTmp to "yes" in a unit file, I expect
  that files created by the service shouldn't be visible to the outside
  world.

  To reproduce:

  $ systemctl  --user  edit  --full privatetmpdir.service
  [Unit]
  Description=TestService

  [Service]
  Type=oneshot
  ExecStart=/usr/bin/touch /tmp/1234.txt
  PrivateTmp=yes

  $ ls /tmp/1234.txt
  ls: cannot access '/tmp/1234.txt': No such file or directory

  $ systemctl --user restart privatetmpdir.service
  $ ls /tmp/1234.txt
  /tmp/1234.txt

  here i expect there to not be a file "/tmp/1234.txt", but there is.

  Running the same unit file on the system systemd behaves as expected,
  the file in /tmp is not visible to the outside world.

  Ubuntu 16.04.1 LTS
  Kernel: 4.4.0-34-generic
  Package: systemd
  Version: 229-4ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1612340/+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 1608880] Re: systemd doesnt work with timed fsck, only with counted mount fsck

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1608880

Title:
  systemd doesnt work with timed fsck, only with counted mount fsck

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Updated my homserver from 14.04 to 16.04. Got a "/dev/sda1 will be
  fscked on next reboot" hint in the MOTD. Did some reboots and the fsck
  never happend. Tried with "sudo touch /forcefsck" but the message
  didnt go away. Thought it was an error of the MOTD scripts and tried
  to fiddle with them. But it reappeard ever time.

  Looked at the syslogs logs and saw the fsck never happend.

  Looked at the output from dumpe2fs and it showed several interesting 
informations:
   * the mount count was 12 and the maximum mountcount of 34 was not reached
   * the timed fsck date was reached
   * the last fsck was long ago (next confirmation the /forcefsck didnt work at 
all)

  i changed the mount count to 35 with "sudo tune2fs -C 35 /dev/sda1"
  which made the fsck on next reboot.

  So what works: 
   * mount count fsck on reboot

  what doesnt work:
   * setting /forcefsck manually
   * timed fsck 

  what should work?
   * all 3 of them should work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1608880/+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 1606000] Re: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 6

Status in apt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  bug error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 09:52:56 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  InstallationDate: Installed on 2015-09-20 (308 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apt
  Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 6
  UpgradeStatus: Upgraded to xenial on 2016-07-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1606000/+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 1608359] Re: Power "When the lid is closed" setting does nothing

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1608359

Title:
  Power "When the lid is closed" setting does nothing

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  Probably the opposite of LP: #1574120, after upgrading from Xenial to
  Yakkety (alpha 2), it seems my laptop automatically goes into suspend
  when the lid is closed even though I have "When the lid is closed"
  setting set to "Do nothing".

  I'm not sure what's changed, has the HandleLidSwitch default in logind
  changed? Also, any chance of fixing the "Power" setting so it
  correctly handles updating logind?

  I had to update /etc/systemd/logind.conf and add
  "HandleLidSwitch=ignore".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1608359/+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 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

-- 
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/1609546

Title:
  DNS lookup through Netgear DG834G V4 router slow or times out

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Update:
  On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather 
than just a slow resolution. The workaround in comment #6 which disables DNSSEC 
still corrects the problem.
  ---

  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+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 1610721] Re: Ctrl+S in terminal causes shutdown/reboot (init) to hang

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1610721

Title:
  Ctrl+S in terminal causes shutdown/reboot (init) to hang

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  1. Boot an Ubuntu 16.04 machine that doesn't have an X server installed
  2. When you get the terminal log-in prompt (on tty1), instead of logging in, 
press Ctrl+S to stop terminal flow
  3. Connect to the machine via SSH
  4. Run "sudo init 0" via SSH

  The init command hangs. Only when you press Ctrl+Q in the terminal
  does the machine shut down.

  This behavior is confusing when you accidentally hit Ctrl+S. It also
  means that you cannot shut down or reboot the machine remotely if
  someone has pressed Ctrl+S locally.

  Pressing the power button instead of running "init 0" produces the
  behavior as well - nothing happens until you press Ctrl+Q.

  I'm attaching a screen recording to illustrate the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1610721/+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 1608077] Re: package udev 229-4ubuntu7 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1608077

Title:
  package udev 229-4ubuntu7 failed to install/upgrade: el subproceso
  instalado el script post-installation devolvió el código de salida de
  error 1

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Cada vez que inicio presenta varias veces error en sistema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules
  Date: Fri Jul 29 20:57:14 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-10-13 (290 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=b5bc76e2-d1c3-4343-926f-4d9c78eb24fd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu7 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B85M-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1608077/+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 1610684] Re: ubuntu 16.04 won't shutdown : Reached target Shutdown[ok] also ubuntu 14.04 won't shut down : killing all procces [fail]

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1610684

Title:
  ubuntu 16.04 won't shutdown : Reached target Shutdown[ok] also ubuntu
  14.04 won't shut down : killing all procces [fail]

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:

  I had ubuntu 14.04 (DELL laptop INSPIRON N-4110 ) shutdown and reboot
  worked correctly and without any problem but after a long time I
  wasn't able to reboot or shutdown my machine.

  and that was the log message was shown by pressing Esc during
  shutdown:

  killing all procceses  [fail]

  and I tried all the tips I saw in askubuntu and others(like changing
  the grub and shutdown - h now etc none of them have worked ! )

  then I clean installed ubuntu 16.04 (current) but issue is not going
  to solve.

  now the log shows:

  [ok] Reached target Shutdown 
  [135.486156] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0X0 action 0x6 frozen
  [135.846776] ata2.00: cmd a0/00: 00:00:00:00/00:00:00:00:00/s0 tag 4 pio 
16392 in
  [135.846776] get event status notification 4a  01 00 10 00 00 00 00 00res 
40/00:00:00:00
  [135.848020] ata2.00:status: { DRDY }
  [141.182090] ata2.00 revalidation failed  (errno=-5)

  I checked bug #1464917 and did instructions also but nothings changed
  .

  UPDATE:

  after updating to 16.04.1 (boot install) Ubuntu will shutdown if i do
  it fast when OS is coming up but after a while it's not going to power
  off again and Esc key won't work and does not show me log any more

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1610684/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu)
   Status: Invalid => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Incomplete

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in pm-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 1559643] Re: kswapd0 high cpu

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1559643

Title:
  kswapd0 high cpu

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  kswapd0 high cpu load.
  System doesn't have swap partition / swap file.

  Using AWS t2.nano

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
   crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 20 07:57:52 2016
  Ec2AMI: ami-b7443fc0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559643/+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 1556804] Re: bootdata collector doesn't stop until /dev/.bootchart it full

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1556804

Title:
  bootdata collector doesn't stop until /dev/.bootchart it full

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Using current 16.04 (updated from 14.04 in 2016-03-06) I got the problem that 
the bootdata collector isn't stopped when the maschine start is complete, so it 
filles /dev/.bootchart until the ramdisk is full (4 Gb in my case)
  Even the compressed ps_proc.log (3,7 GB -> 1 GB) is too big to upload, but 
I've uploaded the other ones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556804/+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 1555282] Re: systemd-journald crashed with SIGABRT in server_read_dev_kmsg.lto_priv()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1555282

Title:
  systemd-journald crashed with SIGABRT in
  server_read_dev_kmsg.lto_priv()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Mar  7 14:15:30 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-03-25 (350 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   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: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x558a2237a540, argc=1, argv=0x7ffdc8bee4a8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdc8bee498) at libc-start.c:289
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-vivid
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1555282/+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 1561832] Re: package systemd 225-1ubuntu9.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1561832

Title:
  package systemd 225-1ubuntu9.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This error happened this morning at startup of my system. 
  Don't have  clue where this comes from. Looks like yesterday an update was 
done that required a restart but it fails completing after restart (this 
morning).

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Mar 21 11:57:25 2016
  DuplicateSignature: package:systemd:225-1ubuntu9.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-19 (218 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=7dd60890-1263-493b-b46b-506af50eac11 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-09-24 (182 days ago)
  dmi.bios.date: 03/19/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.32
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30D9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.32:bd03/19/2008:svnHewlett-Packard:pnCompaqPresarioC700NotebookPC:pvrF.32:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Compaq Presario C700 Notebook PC
  dmi.product.version: F.32
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561832/+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 1627546] Re: Use safe mount for USB devices

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1627546

Title:
  Use safe mount for USB devices

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  For years ubuntu has been plagued by horrible user experience when dealing 
with usb drives:
  - user forget to unmount device
  - fs is corrupted
  - user insert device back and is overwritten/lost

  Luckily solution is finally available: ubuntu should use systemd-mount for 
all usb devices so they are
  - mount only when it's really necessary
  - aggressively unmounted to prevent data loss
  - fscked before mounting

  This will lead to much nicer situation where new users will not blame
  ubuntu anymore for data loss.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1627546/+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 1562589] Re: USB DVDRW's No Longer Function Correctly in 15.10 or 16.04

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1562589

Title:
  USB DVDRW's No Longer Function Correctly in 15.10 or 16.04

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading several systems from 15.04 to 15.10, none of the
  systems were able to recognize the DVDRW in userland. This was tested
  with two different USB DVDRW's

  *-cdrom
 description: DVD-RAM writer
 product: SuperMultiPA3761
 vendor: Toshiba
 physical id: 0.0.0
 bus info: scsi@4:0.0.0
 logical name: /dev/cdrom
 logical name: /dev/cdrw
 logical name: /dev/dvd
 logical name: /dev/dvdrw
 logical name: /dev/sr0
 version: TO01
 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
 configuration: status=ready
   *-medium
physical id: 0
logical name: /dev/cdrom

  
  And

*-cdrom
 description: DVD-RAM writer
 product: DVD RW DRU-830A
 vendor: SONY
 physical id: 0.0.0
 bus info: scsi@5:0.0.0
 logical name: /dev/cdrom
 logical name: /dev/cdrw
 logical name: /dev/dvd
 logical name: /dev/dvdrw
 logical name: /dev/sr0
 version: SS15
 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
 configuration: status=ready
   *-medium
physical id: 0
logical name: /dev/cdrom

  This was also tested on 4 different systems. Three with Ubuntu and one
  with Kubuntu. I upgraded Kubuntu to 16.04. The difference in 16.04 is
  peculiar. The DVD player does not appear in any file manager. However,
  I could access the DVD via VLC. Attempting to play the DVD failed
  however. There was no sound and any option  chosen on the DVD menu
  resulted in a blank/black screen.

  This bug seems to afflict other users:

  http://askubuntu.com/questions/692934/after-upgrade-to-ubuntu-15-10
  -can-no-longer-access-video-files-on-cd-dvd

  I've also included this report here:

  https://bugs.launchpad.net/ubuntu/+source/udev/+bug/646293?comments=all

  But am filing a new bug since the other seems to be dead and/or
  outdated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562589/+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 1564159] Re: vbox guest rules should be included by default

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1564159

Title:
  vbox guest rules should be included by default

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Since vivid, Ubuntu ships the VirtualBox drivers as part of the main
  kernel package, by incorporating the virtualbox-guest-dkms package
  directly. See
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418743 .
  However, the udev rules (/lib/udev/rules.d/60-virtualbox-guest-
  dkms.rules) from the same DKMS package are not beind shipped with the
  main udev installation. This leads to incorrect permissions of the
  /dev/vboxuser device. Since Ubuntu ships the kernel modules "by
  default" it should do the same for the udev rules. This is broken in
  vivid, wily and xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564159/+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 1558511] Re: systemd-journald crashed with SIGABRT

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1558511

Title:
  systemd-journald crashed with SIGABRT

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Crashed shortly after logging in to my laptop.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Thu Mar 10 21:12:39 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-02-13 (398 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 1420
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=71fcab68-425b-4dae-a9ec-13245f989fe1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0DT492
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0DT492:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1558511/+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 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

-- 
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/1567744

Title:
  USB NICs get too long name for ifupdown aliases or bridge names

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+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 1563354] Re: systemd-tmpfiles-setup.service fails after switching SELinux to enforcing

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1563354

Title:
  systemd-tmpfiles-setup.service fails after switching SELinux to
  enforcing

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  After switching SELinux to enforcing, the systemd-tmpfiles-
  setup.service failed:

  Mar 29 16:12:42  systemd-tmpfiles[546]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path "/var/log", ignoring.
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/log: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/lib: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /home: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /srv: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/lib/systemd: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/lib/systemd/coredump: Permission denied
  Mar 29 16:12:43  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/cache: Permission denied
  Mar 29 16:12:43  systemd[1]: systemd-tmpfiles-setup.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar 29 16:12:43  systemd[1]: Failed to start Create Volatile Files and 
Directories.
  Mar 29 16:12:43  systemd[1]: systemd-tmpfiles-setup.service: Unit entered 
failed state.
  Mar 29 16:12:43  systemd[1]: systemd-tmpfiles-setup.service: Failed with 
result 'exit-code'.

  No further AVC or audit.log is logged. When manually setting
  'setenforce 0' and starting this service, it obviously works fine.

  My environment:

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  (Build  / packages from last night)

  # apt-cache policy systemd
  systemd:
Installed: 229-3ubuntu1
Candidate: 229-3ubuntu1

  If you need more infos, please drop a short note.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1563354/+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 1554795] Re: timeout on restart or shutdown with LUKS root

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1554795

Title:
  timeout on restart or shutdown with LUKS root

Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Using the server install ISO, it's possible to specify root on LUKS
  and variations thereof - for instance, root on LUKS on MD-RAID, root
  on LVM on LUKS on MD-RAID, and so forth. The installer does the right
  thing and initramfs-tools does everything necessary to support booting
  this sort of thing.

  However, systemd gives a 90-second timeout on restart or shutdown,
  presumably because it cannot dispose of the things beneath root.

  It's wholly unclear to me where the 90-second timeout is specified,
  should I wish to shorten it to reboot without the futile delay, but
  more to the point, there seems to be infrastructure for handling this
  kind of situation that doesn't exist in Ubuntu at present.

  I was pointed at this:

  https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/

  However, Ubuntu seems not to have anything in its initramfs-tools to
  facilitate "shutdown-initrd" functionality.

  I haven't tested this, but I suspect this problem will exist for folks
  running root on MD-RAID without the LUKS as well. Either way, a
  relatively common vanilla install will force 90-second timeouts on
  users, which is unfortunate.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  8 18:06:45 2016
  InstallationDate: Installed on 2016-02-24 (13 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  Lsusb:
   Bus 002 Device 002: ID 1058:0820 Western Digital Technologies, Inc. My 
Passport Ultra (WDBMWV, WDBZFP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
   Bus 001 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X150M-PRO ECC-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd12/04/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX150M-PROECC-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1554795/+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 1573322] Re: several packages failed to install/upgrade: triggers looping, abandoned

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1573322

Title:
  several packages failed to install/upgrade: triggers looping,
  abandoned

Status in dpkg package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Appeared as soon as the computer started

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 21 20:09:31 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-11-23 (150 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=2faac09b-9252-4043-85b9-c6bfed793b7c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 05/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z97 Killer
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Killer:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1573322/+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 1570310] Re: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1570310

Title:
  package systemd 229-4ubuntu4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I was upgrading from 15.10 to 16.04 when this error occur.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 13 21:41:53 2016
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ...
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  DuplicateSignature:
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2016-01-08 (96 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X455LJ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=70fa96eb-e0d8-4e65-b049-9cb150759b40 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-04-13 (0 days ago)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LJ.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX455LJ.203:bd04/22/2015:svnASUSTeKCOMPUTERINC.:pnX455LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X455LJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1570310/+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 1580192] Re: systemd-nspawn --network-interface= disappears when container exits

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1580192

Title:
  systemd-nspawn --network-interface= disappears when container exits

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On Ubuntu xenial,

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu4
  Candidate: 229-4ubuntu4
  Version table:
 *** 229-4ubuntu4 500
500 http://apt/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

  The systemd-nspawn manpage states that the existing --network-
  interface= device should be returned to the host's namespace on exit:

 --network-interface=
 Assign the specified network interface to the container. This will 
remove the specified interface from the calling namespace
 and place it in the container. *When the container terminates, it 
is moved back to the host namespace*. Note that
 --network-interface= implies --private-network. This option may be 
used more than once to add multiple network interfaces to
 the container.

  However, this does not appear to be the case for a VLAN interface
  (created using systemd-networkd):

$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:03 brd ff:ff:ff:ff:ff:ff
3: eno2:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:04 brd ff:ff:ff:ff:ff:ff
6: vlan-terom-dev@eno1:  mtu 1500 qdisc noop state 
DOWN mode DEFAULT group default qlen 1000
link/ether 66:c9:35:09:49:74 brd ff:ff:ff:ff:ff:ff
$ sudo systemd-nspawn -M obelix-terom-dev 
--network-interface=vlan-terom-dev bash
Spawning container obelix-terom-dev on 
/var/lib/machines/.#machine.obelix-terom-devfc1e2f39f5df67dd.
Press ^] three times within 1s to kill container.
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: No such file or directory
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: Invalid argument
/etc/localtime is not a symlink, not updating container timezone.
root@obelix-terom-dev:/# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
6: vlan-terom-dev@if2:  mtu 1500 qdisc noop state 
DOWN mode DEFAULT group default qlen 1000
link/ether 66:c9:35:09:49:74 brd ff:ff:ff:ff:ff:ff link-netnsid 0
root@obelix-terom-dev:/# exit
Container obelix-terom-dev exited successfully.
$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:03 brd ff:ff:ff:ff:ff:ff
3: eno2:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:04 brd ff:ff:ff:ff:ff:ff
$ sudo systemd-nspawn -M obelix-terom-dev 
--network-interface=vlan-terom-dev bash
Spawning container obelix-terom-dev on 
/var/lib/machines/obelix-terom-dev.
Press ^] three times within 1s to kill container.
Failed to resolve interface vlan-terom-dev: No such device
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: No such file or directory
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: Invalid argument
/etc/localtime is not a symlink, not updating container timezone.
$ 

  Possibly related upstream mailing list thread, including workarounds:

  https://lists.freedesktop.org/archives/systemd-
  devel/2015-April/030934.html

  Is this just a documentation bug in the man page?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1580192/+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 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1577885

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577885/+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 1572338] Re: /lib/systemd/systemd-journald:6:jenkins_hashlittle2:hash64:journal_file_append_data:journal_file_append_entry:write_to_journal

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1572338

Title:
  /lib/systemd/systemd-
  
journald:6:jenkins_hashlittle2:hash64:journal_file_append_data:journal_file_append_entry:write_to_journal

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  229-4ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/3d138865dc977e0da294a2e2a68fe710c6a4cbf2
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1572338/+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 1577575] Re: NFS share does not mount on boot using fstab

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1577575

Title:
  NFS share does not mount on boot using fstab

Status in nfs-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  What I expected to happen?

  I want an NFS share to be mounted on startup using

  
  192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ 
/media/captainplanet/banane/ nfs rw 0 0

  What happened instead?

  It does not mount on startup. Systemd waits 91sec instead and finally
  starts after failing.

  I can successfully mount the NFS share with

  sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575
  /media/captainplanet/banane/

  When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS
  share manually before shutdown fixes the second problem.

  
  Do you need more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  2 23:10:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20DM003XUK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JFET44WW(1.21)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DM003XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DM003XUK
  dmi.product.version: ThinkPad S3 Yoga 14
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+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 1573257] Re: [Xenial] systemctl isolate xxxxx.target fails

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1573257

Title:
  [Xenial] systemctl isolate x.target  fails

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  when logged in normally::

  typed from terminal:
  systemctl isolate rescue.target

  expected:
  root prompt (or friendly rescue menu)

  instead:
  login prompt
  system reports "shutdown" whenever I try to login
  login fails

  
  when in rescue mode::

  typed from terminal:
  systemctl isolate graphical.target

  expected:
  lightdm greeter

  instead:
   hang on splash (plymouth)

  It doesn't matter if I use systemctl , init or telinit; results stay
  the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1573257/+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 1579695] Re: apport hook does not show the status of failed services

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1579695

Title:
  apport hook does not show the status of failed services

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  See bug 1579475. I can manually follow through and see that the output
  of "systemctl status amavis.service" is required for the report to be
  helpful. Can the apport hook figure out the same thing?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579695/+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 1579130] Re: need to support renaming of devices in container and on first boot

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1579130

Title:
  need to support renaming of devices in container and on first boot

Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  We're interested in supporting network configuration of cloud
  instances including lxc containers via maas/cloud-init yaml format.

  For Containers, the end goal is to do:
  $ lxc init xenial x1
  $ ncpath=/var/lib/cloud/seed/nocloud-net/network-config
  $ sudo tee /var/lib/lxd/containers/x1/rootfs/$ncpath < 
into 'eth0').
   That is implemented by check of 
/sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed.

   c.) systemd.link will not attempt to rename a device that does not have a 
driver.
     To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0
     http://paste.ubuntu.com/16261974/

   d.) on first boot of a cloud instance, the systemd.link files in the
  initramfs are either pristine or from the previous instance.  The
  devices will leave the initramfs either named incorrectly or named
  with standard persistent naming and will have already been renamed.

  To force these systemd.link files to run in spite of 'b' on kvm guests
  or bare metal, we have found that unbind and rebind of the device will
  clear the state and rename would occur.  that can be done as shown in
  https://bugs.launchpad.net/ubuntu/+source/cloud-
  init/+bug/1577844/comments/3 but since there is no 'driver' we cannot
  unbind and rebind veth devices.

  To do this right, we need to support:
   1.) renaming on first boot with initramfs and with 'stale' initramfs
   2.) renaming in lxc containers
   3.) user updating whatever files or mechanism is used post first boot.  For 
example, if the user wrote a 25-my-rules.link after first boot, a reboot should 
prefer their provided names to whatever were originally there.
   4.) if cloud-init networking is disabled, the renaming should not occur.

  Related Bugs:
   * bug 1594546: no need to write systemd.link files 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May  6 15:42:52 2016
  MachineType: LENOVO 33672B7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G8ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33672B7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 33672B7
  dmi.product.version: ThinkPad X131e
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1579130/+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 1578141] Re: Predictable interface names partially broken with igb driver

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1578141

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT-HF+
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9DRT-HF+
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Touch-packages] [Bug 1576536] Re: timer messages unnecessarily sent to /dev/kmsg

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1576536

Title:
  timer messages unnecessarily sent to /dev/kmsg

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The random adjustments to the apt timer seem to spam the kernel
  ringbuffer, which is entirely unnecessary:

  [ 5452.648222] systemd[1]: apt-daily.timer: Adding 10h 42min 21.562799s 
random time.
  [ 5454.038740] systemd[1]: apt-daily.timer: Adding 7h 11min 7.994692s random 
time.
  [ 5457.381779] systemd[1]: apt-daily.timer: Adding 10h 43min 34.008994s 
random time.
  [ 5457.495120] systemd[1]: apt-daily.timer: Adding 7h 9min 28.335411s random 
time.
  [ 5457.743417] systemd[1]: apt-daily.timer: Adding 7h 5min 47.291509s random 
time.
  [ 5778.374365] systemd[1]: apt-daily.timer: Adding 8h 26min 267.164ms random 
time.
  [ 5778.495711] systemd[1]: apt-daily.timer: Adding 9h 52min 9.289682s random 
time.
  [ 5778.667351] systemd[1]: apt-daily.timer: Adding 8h 39min 41.199389s random 
time.
  [ 5778.924784] systemd[1]: apt-daily.timer: Adding 2h 38min 40.786228s random 
time.
  [ 5779.035421] systemd[1]: apt-daily.timer: Adding 10h 48min 34.808379s 
random time.
  [ 5779.107951] systemd[1]: apt-daily.timer: Adding 6h 19min 45.904476s random 
time.
  [ 7236.115354] systemd[1]: apt-daily.timer: Adding 5h 12min 18.073639s random 
time.
  [ 7268.716558] systemd[1]: apt-daily.timer: Adding 7h 19min 40.411960s random 
time.
  [ 7269.151388] systemd[1]: apt-daily.timer: Adding 8h 21min 54.857412s random 
time.
  [ 7270.702642] systemd[1]: apt-daily.timer: Adding 8h 33min 10.633964s random 
time.
  [ 7281.835523] systemd[1]: apt-daily.timer: Adding 11h 43min 43.923801s 
random time.
  [ 7339.639840] systemd[1]: apt-daily.timer: Adding 9h 8.911515s random time.
  [ 7340.512389] systemd[1]: apt-daily.timer: Adding 1h 45min 25.722497s random 
time.
  [ 7343.611383] systemd[1]: apt-daily.timer: Adding 22min 8.489125s random 
time.
  [ 7344.186645] systemd[1]: apt-daily.timer: Adding 10h 6min 50.541602s random 
time.
  [ 7346.111888] systemd[1]: apt-daily.timer: Adding 11h 47min 57.661764s 
random time.
  [ 7350.893164] systemd[1]: apt-daily.timer: Adding 3h 10min 23.393765s random 
time.
  [ 7355.747731] systemd[1]: apt-daily.timer: Adding 1h 2min 54.946554s random 
time.
  [ 7355.825972] systemd[1]: apt-daily.timer: Adding 4h 40min 28.148047s random 
time.
  [ 7529.692671] systemd[1]: apt-daily.timer: Adding 10h 20min 39.786553s 
random time.
  [ 7539.109562] systemd[1]: apt-daily.timer: Adding 7h 45min 54.766189s random 
time.
  [ 7539.187368] systemd[1]: apt-daily.timer: Adding 2h 20min 28.098533s random 
time.
  [ 7539.617356] systemd[1]: apt-daily.timer: Adding 10h 36min 4.411352s random 
time.
  [ 7540.960539] systemd[1]: apt-daily.timer: Adding 43min 17.875784s random 
time.
  [ 7541.477412] systemd[1]: apt-daily.timer: Adding 5h 33min 59.201230s random 
time.
  [ 7550.068289] systemd[1]: apt-daily.timer: Adding 6h 41min 2.480405s random 
time.
  [ 7734.981411] systemd[1]: apt-daily.timer: Adding 9h 54min 39.888137s random 
time.
  [ 7735.230060] systemd[1]: apt-daily.timer: Adding 6h 8min 31.925492s random 
time.
  [ 7736.287077] systemd[1]: apt-daily.timer: Adding 4h 56min 30.657866s random 
time.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-07-13 (291 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BXCTO1WW
  Package: systemd 229-4ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-lowlatency.efi.signed 
root=UUID=6fe2ef4e-b82c-468b-a35a-86d8753787d1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  yakkety
  Uname: Linux 4.4.0-21-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  d

[Touch-packages] [Bug 1574100] Re: System won't power off

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1574100

Title:
  System won't power off

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Since I clean installed Ubuntu 16.04 LTS my system won't power off
  anymore on itself, I have to hold the powerbutton.

  Ubuntu 15.04 and 15.10 had no problems turning off my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 21:46:35 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z420 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574100/+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 1579336] Re: systemd-udevd crashes system with manipulated DOS partition table

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1579336

Title:
  systemd-udevd crashes system with manipulated DOS partition table

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I wanted to test how operating systems react if the DOS partition
  table of a storage medium was manipulated. I created a DOS partition
  table with a few extended partitions. Because extended partitions are
  constructed like a linked list, I linked the "NEXT" field of the last
  extended partition to the first extended partition. This way, I
  created a loop in the partition table. Tools like fdisk detect that
  something is fishy in this partition table and output an error
  message. To test how operating systems react to it, I copied this
  image to an USB storage device and plugged it to my computer.

  The systemd/udev process that handles this device seems to not check
  the DOS partition table for sanity. The process "/lib/systemd/systemd-
  udevd --daemon" completely uses all CPU time and all available memory.
  This crashes the system. Sometimes, it is able to recover by killing
  the process, but not every time.

  I attached a screenshot (a real screenshot with a camera, because the
  system does not react anymore ;) ) of htop to show what the system
  does.

  Cheers,

  sqall

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.19
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 99-usb-disks.rules
  Date: Sat May  7 10:43:21 2016
  InstallationDate: Installed on 2014-11-12 (541 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic 
root=/dev/mapper/xubuntu--vg-root ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.asset.tag: CZC2033ZHD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrAC02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: AC02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579336/+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 1579969] Re: Xenial: impossible to rename an interface with a .link file

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1579969

Title:
  Xenial: impossible to rename an interface with a .link file

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  Impossible to rename an interface with a .link file in a updated
  Ubuntu Xenial. It's a fresh and basic install without GUI, just a ssh
  server (it's a VirtualBox VM).

  Here is my environment:

  ---
  root@xenial-clean:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial
  ---

  According to the manpage "systemd.link" (example 2), I can rename an
  interface with a .link file like this:

  ---
  root@xenial-clean:~# ll /etc/systemd/network/10-eth0.link 
  -rw-r--r-- 1 root root 57 May 10 02:07 /etc/systemd/network/10-eth0.link

  root@xenial-clean:~# cat /etc/systemd/network/10-eth0.link 
  [Match]
  MACAddress=08:00:27:be:14:c2

  [Link]
  Name=eth0
  ---

  Currently the interface name is enp0s3 because the OS is not yet
  rebooted:

  ---
  root@xenial-clean:~# ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: enp0s3:  mtu 1500 qdisc pfifo_fast state 
UP mode DEFAULT group default qlen 1000
  link/ether 08:00:27:be:14:c2 brd ff:ff:ff:ff:ff:ff
  ---

  And now I reboot the OS. But, after the reboot, the interface name is
  still enp0s3:

  ---
  root@xenial-clean:~# ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: enp0s3:  mtu 1500 qdisc pfifo_fast state 
UP mode DEFAULT group default qlen 1000
  link/ether 08:00:27:be:14:c2 brd ff:ff:ff:ff:ff:ff
  ---

  Just for information:

  ---
  root@xenial-clean:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=03363c3a-58b5-4398-82a8-6997ec1a00e5 ro quiet splash

  root@xenial-clean:~# apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu4
Candidate: 229-4ubuntu4
Version table:
   *** 229-4ubuntu4 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  ---

  
  Note: the .link file is taken into account _only_ if I set the 
"net.ifnames=0" kernel boot parameter. But, according to the manpage "man 
systemd.link", this is normally not necessary.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579969/+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 1580266] Re: Computer hangs on reboot or shutdown, typically for >10 mins, Ubuntu 16.04 and previous versions

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1580266

Title:
  Computer hangs on reboot or shutdown, typically for >10 mins, Ubuntu
  16.04 and previous versions

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I am aware of the thread here:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917

  People there are asking that if you have the same/similar bug to
  report it separately, so that's what I'm doing.

  What I've noticed is that my shutdown process hangs as some point,
  usually with the screen being black or with a single cursor.  After
  >10 mins, the computer will finally shut off.  I've had this issue I
  think since 15.04, definitely in 15.10, and now still in 16.04.

  I've tried the fix

  $ sudo systemctl reboot

  which worked one time, but not another time.

  I've also tried

  $ sudo swapoff -a sudo systemctl reboot

  and that appeared to work, but I haven't tested it enough times to say
  it always works.  For what it's worth, turning off the swap probably
  took longer than my typical black screen shutdown so it's really not a
  stopgap fix either way.

  I know this isn't enough information to be sure I'm having the
  swap/systemd failure, so let me know what else you need.  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1580266/+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 1554662] Re: First client to invoke Xorg via systemd socket activation gets stuck

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1554662

Title:
  First client to invoke Xorg via systemd socket activation gets stuck

Status in systemd package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Briefly: if one has a pair of systemd .socket/.service unit files to
  start Xorg via socket activation, the first X11 client which triggers
  this socket activation gets stuck (waits forever) , although Xorg
  starts properly. A second X11 client will then work as expected. For
  more details, see these upstream bug reports:

  https://bugs.freedesktop.org/show_bug.cgi?id=93072

  https://github.com/systemd/systemd/issues/2765

  I've tested Xorg socket activation in Ubuntu 15.10 and 16.04 beta1, as
  well as openSUSE Leap 42.1 and Tumbleweed. Both Ubuntu releases are
  affected by this bug, but both openSUSE releases are immune to it.
  Thus I presume this is a Debian/Ubuntu specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1554662/+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 1554065] Re: Logitech presenter only working partially

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1554065

Title:
  Logitech presenter only working partially

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The Logitech R400 presenter's buttons for starting a presentation and
  toggling the screen to black does not work any more since at least
  Ubuntu 13.10 [1] (it had worked in a previous Ubuntu version I do not
  remember exactly and it still worked in Debian 7 Wheezy but also does
  not work any more in Debian 8 Jessie). The buttons for the next and
  previous slide still do.

[1] https://forum.ubuntuusers.de/topic/probleme-mit-logitech-r400
  -presenter-unter-13-/

  This presenter model has probably been one of the most widely spread
  ones since many years. I've bought mine in 2010 and it still is the
  best selling presenter on amazon.com and amazon.de. So really a lot of
  people are affected (moreover, similar Logitech models do exist, too).

  The problem seems to be in file /lib/udev/hwdb.d/60-keyboard.hwdb –
  the "displaytoggle" and "presentation" entries do not seem to be
  mapped to a key correctly (I do not understand how that mapping works
  in more detail). As a workaround, the Logitech R400 entry in this file
  can be changed (see attached patch) followed by

  sudo udevadm hwdb --update

  but it does not seem to be a real solution as other devices are
  probably affected, too. The real solution would probably be to get the
  "toggledisplay" etc. entries in this configuration file to be mapped
  correctly.

  latest Ubuntu version tested: 15.10
  udev package version: 225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1554065/+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 1582394] Re: [16.04, lxc] Failed to reset devices.list on ...

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1582394

Title:
  [16.04, lxc] Failed to reset devices.list on ...

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This seems to be identical to Bug #1413193 which affected 15.04 and
  was marked Fix Released.

  On a 16.04 host with a 16.04 container:

  $ lxc-create -t download -n vpn01 -- -d ubuntu -r xenial -a amd64
  $ lxc-start -n vpn02 -d

  the container syslog shows repeated instances of "Failed to reset
  devices.list on ..." and continues generating such messages:

  $ grep devices.list .local/share/lxc/vpn01/rootfs/var/log/syslog

  May 16 14:37:20 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-remount-fs.service: Operation not permitted
  May 16 14:37:20 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-random-seed.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/rc-local.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/resolvconf.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/getty-static.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-user-sessions.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/console-getty.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-update-utmp-runlevel.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/rc-local.service: Operation not permitted
  May 16 14:52:51 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-tmpfiles-clean.service: Operation not permitted
  May 16 14:52:51 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/ondemand.service: Operation not permitted
  May 16 15:29:30 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/console-getty.service: Operation not permitted
  May 16 15:31:11 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/console-getty.service: Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582394/+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 1581640] Re: package libpam-systemd:amd64 229-4ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1581640

Title:
  package libpam-systemd:amd64 229-4ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  During installation of this package my PC froze and the only way was
  to make reboot after switching to console (GUI was totally frozen)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May 13 20:14:26 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-02-28 (75 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1581640/+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 1582191] Re: Boot stalls for 90 seconds on mdadm

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1582191

Title:
  Boot stalls for 90 seconds on mdadm

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for
  exactly 90 seconds when using a fairly complex partitioning setup.
  After this, everything works as expected.

  The partitioning is as follows:
  /sda GPT
  /sda1 ESP (/boot/efi)
  /sda2 raid1 md0 ext4 (/boot)
  /sda3 raid1 md1 luks,passphrase ext4 (/)
  /sda4 raid1 md2 luks,key zfs
  /sdb GPT
  /sdb1 ESP (copy of /boot/efi)
  /sdb2 raid1 md0 ext4 (/boot)
  /sdb3 raid1 md1 luks,passphrase ext4 (/)
  /sdb4 raid1 md2 luks,key zfs
  /sdc GPT
  /sdc1 luks,key xfs
  /sdd GPT
  /sdd1 luks,key xfs
  /sdd2 luks,random swap

  This may be an installer or mdadm bug instead - I have not been able
  to exactly determine the cause of the bug.

  I have several identical servers, all showing the same symptom, so it
  should not be due to broken hardware (although design flaws are on the
  table).

  The key seems to be in these lines from journalctl:
  ...
  May 16 14:06:08 molnix kernel: bridge: automatic filtering via 
arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter 
if you need this.
  May 16 14:06:08 molnix kernel: device eno1 entered promiscuous mode
  May 16 14:06:08 molnix systemd-udevd[689]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  May 16 14:06:08 molnix systemd-udevd[701]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  May 16 14:06:08 molnix systemd-udevd[707]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  May 16 14:06:08 molnix systemd[1]: Started Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling.
  May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental 
/dev/sda2 --offroot' failed with exit code 1.
  May 16 14:06:08 molnix systemd-udevd[707]: Process '/sbin/mdadm --incremental 
/dev/sda3 --offroot' failed with exit code 1.
  May 16 14:06:08 molnix systemd[1]: Found device Samsung_SSD_850_EVO_250GB 
EFI\x20System\x20Partition.
  May 16 14:06:08 molnix systemd-udevd[708]: Process '/sbin/mdadm --incremental 
/dev/sda4 --offroot' failed with exit code 1.
  May 16 14:06:08 molnix systemd-udevd[689]: Process '/sbin/mdadm --incremental 
/dev/sdb3 --offroot' failed with exit code 1.
  May 16 14:06:08 molnix systemd[1]: Reached target Local File Systems (Pre).
  May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental 
/dev/sdb4 --offroot' failed with exit code 1.
  May 16 14:06:08 molnix systemd-udevd[699]: Process '/sbin/mdadm --incremental 
/dev/sdb2 --offroot' failed with exit code 1.
  May 16 14:06:08 molnix systemd-udevd[706]: Process '/lib/udev/hdparm' failed 
with exit code 5.
  May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: The BMC does not support 
clearing the recv irq bit, compensating, but the BMC needs to be fixed.
  May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 
0x002a7c, prod_id: 0x086d, dev_id: 0x20)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 16 14:17:31 2016
  InstallationDate: Installed on 2016-05-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=0ca65308-3f70-4231-8f5f-e68583a6d5b3 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SDV-4C-TLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/04/2016:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-4C-TLN4F:rvr2.00:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
htt

[Touch-packages] [Bug 1580810] Re: /lib/systemd/systemd-udevd:6:recvmsg:udev_monitor_receive_device:on_uevent:on_inotify:source_dispatch

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1580810

Title:
  /lib/systemd/systemd-
  
udevd:6:recvmsg:udev_monitor_receive_device:on_uevent:on_inotify:source_dispatch

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  229-4ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/aab87e97600baa6c2fb2a7e38f257fb24d5e4b5d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1580810/+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 1583372] Re: 73-special-net-names.rules is renaming manually created wifi interface

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1583372

Title:
  73-special-net-names.rules is renaming manually created wifi interface

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The 73-special-net-names.rules file from 229-4ubuntu5 is renaming USB
  wifi network interfaces that I create manually with "iw phy phy0
  interface add wifi0 type managed":

  # Use MAC based names for network interfaces which are directly or indirectly
  # on USB and have an universally administered (stable) MAC address (second bit
  # is 0).
  ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", 
ATTR{address}=="?[014589cd]:*", IMPORT{builtin}="net_id", 
NAME="$env{ID_NET_NAME_MAC}"

  
  The device is being renamed by udev as soon as it is created:
  KERNEL[3299.499637] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0 (net)
  KERNEL[3299.500180] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
  KERNEL[3299.500388] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
  KERNEL[3299.500548] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
  KERNEL[3299.500680] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
  KERNEL[3299.500811] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
  KERNEL[3299.502911] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
  UDEV  [3299.546165] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
  UDEV  [3299.547977] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
  UDEV  [3299.549123] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
  UDEV  [3299.550082] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
  UDEV  [3299.550353] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
  UDEV  [3299.550495] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
  UDEV  [3299.552404] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1583372/+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 1581035] Re: systemd fails

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
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/1581035

Title:
  systemd fails

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  getting about a dozen systemd bugs on startup. all seems to indicate
  that start order is incorrect for system bring-up.

  IE:
  net is loaded too late but clam wants the net.
  and similar stupid garbage.

  also AMD FX causes cpufreq to fail to load for some reason. Thermal
  drivers are loaded. This chip supports as-needed overclock above
  stated speed OOBE, at least on sindows.

  --

  May 09 09:38:08 livingroom kernel: acpi PNP0A03:00: _OSC failed 
(AE_NOT_FOUND); disabling ASPM
  May 09 09:38:08 livingroom kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  May 09 09:38:09 livingroom systemd-udevd[639]: Process 
'/usr/bin/jscal-restore /dev/input/js0' failed with exit code 1.
  May 09 09:38:30 livingroom auditctl[1323]: failure 1
  -- Subject: Unit networking.service has failed
  -- Unit networking.service has failed.
  -- The result is failed.
  May 09 09:38:30 livingroom systemd[1]: networking.service: Unit entered 
failed state.
  May 09 09:38:30 livingroom audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=networking comm="systemd" 
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
  May 09 09:38:31 livingroom cpufreqd[1653]:...fail!
  -- Subject: Unit cpufreqd.service has failed
  -- Unit cpufreqd.service has failed.
  -- The result is failed.
  May 09 09:38:31 livingroom audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=cpufreqd comm="systemd" 
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
  May 09 09:38:31 livingroom systemd[1]: cpufreqd.service: Unit entered failed 
state.
  May 09 09:38:32 livingroom loadcpufreq[1635]:...fail!

  
  May 09 09:38:37 livingroom freshclam[1792]: Reading CVD header (main.cvd): 
WARNING: Can't get information about db.local.clamav.net: Temporary failure in 
name resolution
  May 09 09:38:37 livingroom freshclam[1792]: Can't get information about 
db.local.clamav.net: Temporary failure in name resolution
  May 09 09:38:37 livingroom console-kit-daemon[4627]: (process:4709): 
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
  May 09 09:38:41 livingroom NetworkManager[1659]:   [1462804721.3228] 
device (wlp12s0): state change: disconnected -> unavailable (reason 
'supplicant-failed') [30 20 10]
  May 09 09:38:41 livingroom dhclient[3916]: receive_packet failed on enp3s0: 
Network is down
  May 09 09:38:41 livingroom dhclient[3916]: receive_packet failed on enp3s0: 
Network is down
  May 09 09:38:42 livingroom NetworkManager[1659]:   [1462804722.3828] 
rdisc[0x1c11220,"enp3s0"]: failure sending router solicitation: Network is 
unreachable (101)
  May 09 09:38:42 livingroom freshclam[1792]: Reading CVD header (main.cvd): 
WARNING: Can't get information about db.local.clamav.net: Temporary failure in 
name resolution
  May 09 09:38:42 livingroom freshclam[1792]: Can't get information about 
db.local.clamav.net: Temporary failure in name resolution
  May 09 09:38:46 livingroom NetworkManager[1659]:   [1462804726.3849] 
rdisc[0x1c11220,"enp3s0"]: failure sending router solicitation: Cannot assign 
requested address (99)
  -- Subject: Unit NetworkManager-wait-online.service has failed
  -- Unit NetworkManager-wait-online.service has failed.
  -- The result is failed.
  May 09 09:39:03 livingroom audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online 
comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? 
res=failed'
  May 09 09:39:03 livingroom systemd[1]: NetworkManager-wait-online.service: 
Unit entered failed state.
  May 09 09:39:21 livingroom NetworkManager[1659]: dhcp6_start_with_link_ready: 
assertion 'll_addr' failed
  May 09 09:39:22 livingroom ntpd[7705]: bind(26) AF_INET6 
2601:3cb:0:d576:b80a:5f2d:92ca:9fbc#123 flags 0x11 failed: Cannot assign 
requested address
  May 09 09:39:22 livingroom ntpd[7705]: failed to init interface for address 
2601:3cb:0:d576:b80a:5f2d:92ca:9fbc
  May 09 09:39:22 livingroom ntpd[7705]: bind(26) AF_INET6 
2601:3cb:0:d576:b0ab:eea4:8364:4c9e#123 flags 0x11 fail

[Touch-packages] [Bug 1580984] Re: procps postinst fails when inside lxd

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1580984

Title:
  procps postinst fails when inside lxd

Status in lxd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  lxc launch ubuntu:xenial test
  lxc exec test bash
  systemctl status systemd-sysctl.service  # note that this is failed
  dpkg-reconfigure procps  # this attempts to start the service and fails with 
exit status 1

  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for systemd-sysctl.service failed because the control process exited with 
error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" 
for details.
  invoke-rc.d: initscript procps, action "start" failed.

  This causes a dist-upgrade from wily inside a container to fail.
  Workaround: "systemctl mask systemd-sysctl.service" before doing
  anything.

  I see that /lib/systemd/system/systemd-sysctl.service already defines
  "ConditionPathIsReadWrite=/proc/sys/". If this is expected to work,
  presumably it isn't?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1580984/+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 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1582011

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This bug has been affecting me since 15.04
  Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
  I have followed bug #1464917 and installed Xenial-proposed with systemd 
229-4ubuntu5 package.  
  I have finally collected shutdown info using vt9.  
  Issues collecting info due to what I believe is a timeout where vt9 is not 
activated when ctl+alt+F9 is pressed.  I was able to collect info in vt9 to 
file "shutdown.text" I appended outputs to file "shutdown.text" the following 
commands in this order:
  systemctl list-jobs >>shutdown.text
  systemctl --failed >>shutdown.text
  uname -a >>shutdown.text
  systemd --version >>shutdown.text
  lsblk >>shutdown.text
  blkid >>shutdown.text
  journalctl -b >>shutdown.text
  systemctl -all >>shutdown.text
  journalctl -xe >>shutdown.text

  After gaining these data I was only able to finish the reboot with the 
alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
  Each output I separated upon next boot by hand with a line 
# for easier perusing.

  As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
  && systemctl poweroff' or 'sudo swapoff -a && reboot'  which
  occasionally fails if SWAP has more data than available RAM.  In that
  latter case I am left waiting for the hang and then using
  alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
  before SWAP has a chance to gain data, then I can use any form of
  halt, poweroff or menu to shutdown.

  I have been unable to get answers from AskUbuntu or the above listed
  bug #1464917 "Reached target Shutdown"  I am filing this bug per
  instructions requested in that bug.  Other systemd bugs I have
  researched #788303 Debian bug reports, #2930 Github and #3087 Github.

  Thanks for your time and efforts to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 15 12:08:34 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-06-29 (321 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VGN-FW250J
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro 
resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
  dmi.bios.date: 07/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1090Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1090Y0:bd07/25/2008:svnSonyCorporation:pnVGN-FW250J:pvrC6011MLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FW250J
  dmi.product.version: C6011MLK
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582011/+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 1506798] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1506798

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  pitti, bug 1433320 seems still not be fixed on my QEMU VM ...

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: udev 225-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Fri Oct  9 22:02:21 2015
  ExecutablePath: /lib/systemd/systemd-udevd
  ExecutableTimestamp: 1444057442
  InstallationDate: Installed on 2015-03-25 (204 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   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: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55e387f5d870, argc=1, argv=0x7ffc3db0a708, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc3db0a6f8) at libc-start.c:289
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506798/+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 1506206] Re: systemd abort

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1506206

Title:
  systemd abort

Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd package in Fedora:
  Won't Fix

Bug description:
  

  sudo systemctl stop mariadb

  # needs to be fast, do not sleep more than 1 sec

  sudo systemctl start mariadb

  # delay does not matter

  sudo systemctl disable mariadb

  # delay does not matter

  sudo systemctl enable mariadb

  # delay does not matter

  sudo systemctl status mariadb

  

  Here the service starts showing the infamous

  

  ● mariadb.service - MariaDB database server
  Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
  preset: enabled)
 Drop-In: /etc/systemd/system/mariadb.service.d
  └─migrated-from-my.cnf-settings.conf
  Active: inactive (dead) since Wed 2015-10-14 15:04:58 UTC; 58s ago
Main PID: 880 (mysqld)
  Status: "Taking your SQL requests now..."
  CGroup: /system.slice/mariadb.service
  └─880 /usr/sbin/mysqld

  

  If I then shut down the MariaDB server, e.g. via the shutdown command 
  (or just SIGTERM the process), I get

  

  Broadcast message from systemd-journald@ubuntu-vivid-amd64 (Wed 
  2015-10-14 15:14:18 UTC):

  systemd[1]: Caught , dumped core as pid 960.

  
  Broadcast message from systemd-journald@ubuntu-vivid-amd64 (Wed 
  2015-10-14 15:14:18 UTC):

  systemd[1]: Freezing execution.

  

  systemd:

  ii  libpam-systemd:amd64219-7ubuntu3 
  amd64system and service manager - PAM module
  ii  libsystemd0:amd64   219-7ubuntu3 
  amd64systemd utility library
  ii  systemd 219-7ubuntu3 
  amd64system and service manager
  ii  systemd-sysv219-7ubuntu3 
  amd64system and service manager - SysV links

  
  with also occurs on Redhat - backtrace: 
https://bugzilla.redhat.com/show_bug.cgi?id=1271832

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506206/+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 1503773] Re: Drop ondemand init script

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1503773

Title:
  Drop ondemand init script

Status in systemd package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Fix Released

Bug description:
  Ondemand init script is not inherited from Debian, it's an Ubuntu
  specific change.

  Some reasons to get rid of it:
  On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance 
with no ability to change frequency..
  In the init script we don't run this for android
  Why don't we just always use whatever is that kernel's default?

  There are a number of other reported problems with it:
  https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1503773/+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 1508263] Re: systemd-journald crashed with SIGABRT in socket()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1508263

Title:
  systemd-journald crashed with SIGABRT in socket()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Happened after resuming my VM after it was paused due to the host's
  disk being almost full.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 20 20:12:05 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-09-18 (397 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140917)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=ff25ae92-8872-4d77-9510-b560a64e8d53 ro quiet splash 
init=/lib/systemd/systemd
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   socket () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5607d101a440, argc=1, argv=0x7ffdc5128ba8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdc5128b98) at libc-start.c:289
  Title: systemd-journald crashed with SIGABRT in socket()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1508263/+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 1500193] Re: systemd-journald crashed with SIGABRT in dev_kmsg_record()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1500193

Title:
  systemd-journald crashed with SIGABRT in dev_kmsg_record()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I don't know details

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 27 01:21:55 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-09-26 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Lsusb:
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 064e:c341 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed 
root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff46d4c1e8) at libc-start.c:289
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __libc_start_main()
  UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/16/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.61
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1500193/+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 1506139] Re: 15.10beta crashes encrypted swap partition

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1506139

Title:
  15.10beta crashes encrypted swap partition

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  I'm usually using a setup with three partitions on a disk

  Partition 1:  plain ext4 boot partition mounted on  /boot
  Partition 2:  luks-encrypted swap
  Partition 3: luks-encrypted btrfs for /  /home ...

  both mentioned in /etc/crypttab like

  sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
  sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

  
  With several machines I have installed 15.10 beta on and in several cases I 
experienced the problem that the swap is not activated at boot time and that 
/dev/disks/by-uuid does not contain a link to the swap partition, and the 
previously created luks-encrypted swap is destroyed after boot: It is not a 
luks partition anymore and filled with random (presumably encrypted) bytes 
without structure. 

  I first thought that this is a problem of the setup process, and
  repaired the swap manually. But then I found the partition destroyed
  again. This happend several times on several machines.

  I am not sure yet what exactly would destroy the partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cryptsetup 2:1.6.6-5ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 14 18:12:58 2015
  InstallationDate: Installed on 2015-10-08 (5 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab:
   sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
   sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+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 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1504254

Title:
  IdleAction=suspend specified in logind.conf must systematically be
  inhibited during user interaction

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I want my computer to suspend when there is NO opened user session.

  So, I have activated following lines inside '/etc/systemd/logind.conf' :
  IdleAction=suspend
  IdleActionSec=15min

  -  Systematically , under Ubuntu Vivid (15.04), this works correctly :
 During user interaction, the computer does NOT automatically suspend, but 
stays continuously alive.
 Once all users have closed their session, the computer automatically 
suspends after 15 min.

  -  But systematically , under Ubuntu Wily (15.10 beta2), the computer 
automatically suspends after 15 min EVEN during user interaction.
 Hitting the keyboard makes the computer resume without data loss, but this 
is still annoying.
 In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must 
systematically be inhibited during user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z_admin1665 F pulseaudio
   /dev/snd/controlC1:  z_admin1665 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  8 19:26:59 2015
  HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140
  InstallationDate: Installed on 2015-09-27 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1504254/+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 1513526] Re: Rapid resume & suspend could damage laptop

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1513526

Title:
  Rapid resume & suspend could damage laptop

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I suspended my laptop when battery 15%, put it in bag, suspended at
  15:58, at night (22:00) I found my laptop very hot and it seems
  rapidly resume & suspend.

  WORKAROUND: Add in /etc/systemd/logind.conf :
  HandleLidSwitch=poweroff

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-31-generic 3.19.0-31.36
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  khad   2193 F pulseaudio
   /dev/snd/pcmC1D0p:   khad   2193 F...m pulseaudio
   /dev/snd/controlC1:  khad   2193 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  5 22:51:05 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=baaa6fcc-61cf-4070-8f6a-57c140bca2bc
  MachineType: LENOVO 20DCA02WIA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic.efi.signed 
root=/dev/mapper/Onyx-Ubuntu15.04 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-31-generic N/A
   linux-backports-modules-3.19.0-31-generic  N/A
   linux-firmware 1.143.4
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J5ET46WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DCA02WIA
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET46WW(1.17):bd07/15/2015:svnLENOVO:pn20DCA02WIA:pvrThinkPadE450:rvnLENOVO:rn20DCA02WIA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DCA02WIA
  dmi.product.version: ThinkPad E450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513526/+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 1510511] Re: machinectl pull-raw fails: No space left on device

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1510511

Title:
  machinectl pull-raw fails: No space left on device

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1510511/+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 1539348] Re: udevadm info reports wrong ID_MODEL_ID and ID_VENDOR_ID for USB serial port

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1539348

Title:
  udevadm info reports wrong ID_MODEL_ID and ID_VENDOR_ID for USB serial
  port

Status in qtserialport-opensource-src package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Running udevadm info with the device path of a virtual serial port
  created by a USB device (in this case a Particle Photon development
  board) returns the ID_MODEL_ID and ID_VENDOR_ID for the USB host
  controller instead of the Particle device.

  The consequence is mis-detection of the device associated with a
  virtual serial port in applications.

  udevadm info with the virtual serial port. Expect ID_MODEL_ID=c00a and
  ID_VENDOR_ID=2b04

  $ udevadm info --query=property -p 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/tty/ttyACM0
  DEVLINKS=/dev/serial/by-id/pci-Particle_Electron_050C-if00 
/dev/serial/by-path/pci-:00:14.0-usb-0:1:1.0
  DEVNAME=/dev/ttyACM0
  DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/tty/ttyACM0
  ID_BUS=pci
  ID_MODEL=Electron
  ID_MODEL_ENC=Electron
  ID_MODEL_FROM_DATABASE=7 Series/C210 Series Chipset Family USB xHCI Host 
Controller (Zenbook Prime UX31A)
  ID_MODEL_ID=0x1e31
  ID_PATH=pci-:00:14.0-usb-0:1:1.0
  ID_PATH_TAG=pci-_00_14_0-usb-0_1_1_0
  ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
  ID_PCI_INTERFACE_FROM_DATABASE=XHCI
  ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
  ID_REVISION=0200
  ID_SERIAL=Particle_Electron_050C
  ID_SERIAL_SHORT=050C
  ID_TYPE=generic
  ID_USB_CLASS_FROM_DATABASE=Communications
  ID_USB_DRIVER=cdc_acm
  ID_USB_INTERFACES=:020201:0a:
  ID_USB_INTERFACE_NUM=00
  ID_VENDOR=Particle
  ID_VENDOR_ENC=Particle
  ID_VENDOR_FROM_DATABASE=Intel Corporation
  ID_VENDOR_ID=0x8086
  MAJOR=166
  MINOR=0
  SUBSYSTEM=tty
  TAGS=:systemd:
  USEC_INITIALIZED=4586285779

  Running udevadm info with the base device path gives expected IDs

  $ udevadm info --query=property -p /devices/pci:00/:00:14.0/usb1/1-1
  BUSNUM=001
  DEVNAME=/dev/bus/usb/001/008
  DEVNUM=008
  DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Electron
  ID_MODEL_ENC=Electron
  ID_MODEL_ID=c00a
  ID_REVISION=0200
  ID_SERIAL=Particle_Electron_050C
  ID_SERIAL_SHORT=050C
  ID_USB_INTERFACES=:020201:0a:
  ID_VENDOR=Particle
  ID_VENDOR_ENC=Particle
  ID_VENDOR_ID=2b04
  MAJOR=189
  MINOR=7
  PRODUCT=2b04/c00a/200
  SUBSYSTEM=usb
  TYPE=2/0/0
  USEC_INITIALIZED=4585731209

  Running lsusb gives the expected IDs.

  $ lsusb -v
  Bus 001 Device 008: ID 2b04:c00a  
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass2 Communications
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x2b04 
idProduct  0xc00a 
bcdDevice2.00
iManufacturer   1 Particle
iProduct2 Electron
iSerial 3 050C
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   67
  bNumInterfaces  2
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0xc0
Self Powered
  MaxPower  100mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 2 Communications
bInterfaceSubClass  2 Abstract (modem)
bInterfaceProtocol  1 AT-commands (v.25ter)
iInterface  0 
CDC Header:
  bcdCDC   1.10
CDC Call Management:
  bmCapabilities   0x00
  bDataInterface  1
CDC ACM:
  bmCapabilities   0x02
line coding and serial state
CDC Union:
  bMasterInterface0
  bSlaveInterface 1 
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0008  1x 8 bytes
  bInterval 255
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber1
bAlternateSetting   0
bNumEndpoints   2
bInterfaceClass   

[Touch-packages] [Bug 1521744] Re: Entry in fstab with x-initrd.mount not mounted at boot

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1521744

Title:
  Entry in fstab with x-initrd.mount not mounted at boot

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I am running a system with a separate /var partition - this causes
  errors due to various services being started before the /var partition
  is mounted. As an attempt to fix this, I have tried adding the
  x-initrd.mount option to the entry in /etc/fstab for the /var
  partition, according to
  http://www.freedesktop.org/software/systemd/man/systemd.special.html
  this should add the partition to the sysroot-usr.mount target.

  Example fstab entry

  UUID={*irrelevant to bug report*}  /varext4
  defaults,x-initrd.mount0   2

  What actually happens is that this causes the partition not to be
  mounted at all after boot. Using sudo mount -a does nevertheless
  successfully mount the partition.

  Reproducible: always

  In searching for information about this issue, I came across the
  following in the Red Hat Bugzilla:
  https://bugzilla.redhat.com/show_bug.cgi?id=1249513

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Dec  1 20:46:20 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-31 (31 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. CG8270
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=15dd477c-fc5c-42ba-a9b1-54282be263ad ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CG8270
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd08/29/2012:svnASUSTeKCOMPUTERINC.:pnCG8270:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCG8270:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CG8270
  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/1521744/+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 1524511] Re: Systemd Ubuntu 15.10 Crashes at random places during boot up

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1524511

Title:
   Systemd Ubuntu 15.10 Crashes at random places during boot up

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Systemd Ubuntu 15.10 freezes at random places during boot up, the
  freezes seemed to be related to different services however now I
  believe its a crash in systemd-logind.

  I have attached crash file as I cannot get it to upload

  Description:  Ubuntu 15.10
  Release:  15.10

  sudo apt-cache policy systemd

  systemd:
Installed: 225-1ubuntu9
Candidate: 225-1ubuntu9
Version table:
   *** 225-1ubuntu9 0
  500 http://au.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Dec 10 08:20:01 2015
  DistroRelease: Ubuntu 15.10
  ExecutablePath: /lib/systemd/systemd-logind
  ExecutableTimestamp: 1444910536
  ProcCmdline: /lib/systemd/systemd-logind

  Expect the system to complete login successfully each time a reboot
  occurs

  What Happens - randomly boot up stops at random services start points.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1524511/+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 1539465] Re: invoking "sudo systemctl start network-1manager.service" in systemd rescue shell causes it to be unresponsive

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1539465

Title:
  invoking "sudo systemctl start network-1manager.service" in systemd
  rescue shell causes it to be unresponsive

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  After a corruption of a btrfs mountpoint in `/etc/fstab` (not `/` or
  `/home/`) the `systemd` rescue shell was started. After invoking `sudo
  systemctl start network-manager.service`

  Error getting authority: Error initializing authority: Could not connect: 
No such file or directory (g-io-quark, 1)
  Hung up

  was printed and the shell became unresponsive to keyboard input (only
  Ctrl+Alt+F[>1] changed to screens with blinking cursors; not even 7
  Ctrl+Alt+Del within two seconds triggered reboot which normally
  happends in `systemd` rescue shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  Uname: Linux 4.3.3-040303-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 28 05:16:47 2016
  InstallationDate: Installed on 2015-12-12 (46 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.3-040303-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1539465/+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 1516314] Re: Ubuntu/Xubuntu 15.10 do not boot succcessfully on Inspiron 1012

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1516314

Title:
  Ubuntu/Xubuntu 15.10 do not boot succcessfully on Inspiron 1012

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have run into major system freezes and other problems booting
  Ubuntu/Xubuntu 15.10 on my laptop (Inspiron 1012).

  Xubuntu 15.04 works fine on this laptop. Xubuntu/Ubuntu 15.10 have issues 
when installed directly on this laptop.
  Ubuntu 15.10 works fine on my other computer, an Inspiron 518 desktop w/ AMD 
graphics, (using the same hard drive) but the OS has issues when the hard drive 
is transplanted to this computer.
  ---
  Specific experiences below.

  I'll start by describing my experience with Xubuntu 15.10:

  ~What works with Xubuntu 15.10:

  * First boot works fine. (However, As soon as I reboot, the systemd
  option gets stuck before the boot screen.)

  * "Upstart" boot option in advanced options in GRUB sort of works,
  after updating packages. (but I can't join a wifi network after boot,
  and I get strange systemd-related or inadequate permissions errors
  when doing certain things, including joining a wifi network or trying
  to mount partitions.)

  * Recovery mode lets me drop to command line, but other actions result
  in a freeze.

  ~What doesn't work with Xubuntu 15.10:

  * default "systemd" boot option (freezes up before login screen.
  Strange errors. Ctrl+Alt+Del does nothing at this point.
  Ctrl+Alt+PrntScr + R - E - I - S - U - B does nothing. I have to press
  and hold power button to get out of the frozen/bugged boot sequence)
  (applies to second boot and onwards)

  * recovery mode (boots successfully into the recover screen. Trying to
  activate networking results in strange errors, and an unescapable
  system freeze. trying to do an fsck results in an unescapable system
  freeze. Pressing "resume" to continue booting results in errors and a
  freeze.)

  ---

  My experience with Ubuntu 15.10 is different. I got issues even
  without updating my packages.

  ~What works/fails with Ubuntu 15.10 (after installing on Inspiron 518
  desktop w/ AMD graphics, then transplanting hard-drive to Inspiron
  1012 laptop):

  * either systemd or upstart session gets to the login screen, plays
  the "bongos" startup sound... then system immediately freezes and has
  to be shut down via holding the power button.

  * "recovery mode" allows drop to command line (anything else results
  in a freeze.)

  ~What doesn't work with Ubuntu 15.10 (after using the net installer on
  Inspiron 1012 laptop) :

  * systemd or upstart session freeze before any GUI shows up

  * recovery mode allows drop to command line, but everything else
  causes freezes.

  Very hard for me to know what the exact issue is. But I wanted to
  report this major boot issue, so there is some chance of finding the
  cause and fixing it. I am able to do further troubleshooting if asked.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-release-upgrader-core 1:15.04.14.3
  ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic i686
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sat Nov 14 16:12:48 2015
  InstallationDate: Installed on 2015-11-14 (0 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1516314/+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 1531677] Re: Live CD dosen't shutdown

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1531677

Title:
  Live CD dosen't shutdown

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Shutting down or restarting from the live CD installer ("Install Ubuntu" in 
GRUB) doesn't work.
  It gets to the part where it says "Please remove the installation medium, 
then press ENTER:", but when I do that, the screen just flashes black for a 
second, and then it returns to the same screen, and sits their with the 
progress bar moving and nothing happening. If I hit Ctrl+Alt+D at this point it 
gives me a log with the following at the bottom:

  Starting Power-Off.
  [FAILED] Failed to start Power-Off.
  See 'systemctl status systemd-poweroff.service' for details.
  [DEPEND] Dependency failed for Power-Off.

  This does not happen with the "Try Ubuntu" option.
  Tested on Xenial Daily (5/1/16) amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1531677/+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 1526111] Re: RAID1 + LVM in 14.04.3 causes intermittent boot failure

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1526111

Title:
  RAID1 + LVM in 14.04.3 causes intermittent boot failure

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This problem seems to be related to a timing bug within `udev`, and has been 
experienced by other users as seen here;
  
http://serverfault.com/questions/567579/boot-failure-with-root-on-md-raid1-lvm-udev-event-timing

  Changing `/dev/md/0` to `/dev/md0` inside `/etc/mdadm/mdadm.conf`
  seems to resolve the problem. However unless you apply this patch, the
  system will intermittently fail to boot correctly, getting stuck here;

  kernel: [3.003506] md: bind
  kernel: [3.007705] md/raid1:md0: active with 1 out of 1 mirrors
  kernel: [3.007768] md0: detected capacity change from 0 to 499972440064
  kernel: [3.047284]  md0: unknown partition table
  kernel: [3.124709] device-mapper: table: 252:0: linear: dm-linear: Device 
lookup failed
  kernel: [3.124759] device-mapper: ioctl: error adding target to table
  kernel: [3.125156] device-mapper: table: 252:1: linear: dm-linear: Device 
lookup failed
  kernel: [3.125196] device-mapper: ioctl: error adding target to table

  There is also an example `/lib/udev/rules.d/` patch inside the thread
  I posted above, which proposes to add a `sleep` statement into LVM
  udev rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1526111/+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 1548057] Re: rfkill state is not restored on reboot

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1548057

Title:
  rfkill state is not restored on reboot

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  For fun having

  rfkill block bluetooth

  in rc.local does not work either

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rfkill 0.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 21 13:37:39 2016
  InstallationDate: Installed on 2013-05-17 (1010 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: rfkill
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1548057/+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 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1545707

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root@ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Operation failed: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+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 1538681] Re: custom pre/post suspend scripts shoud not live in /lib

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

-- 
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/1538681

Title:
  custom pre/post suspend scripts shoud not live in /lib

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The systemd-sleep manpage mentions the following:

 Finally, systemd-hybrid-sleep.service is pulled in by hybrid-
  sleep.target to execute hybrid hibernation with system suspend.

 Immediately before entering system suspend and/or hibernation 
systemd-suspend.service (and the other mentioned units, respectively) will run 
all executables in /lib/systemd/system-sleep/ and pass two arguments to them. 
The first argument
 will be "pre", the second either "suspend", "hibernate", or 
"hybrid-sleep" depending on the chosen action. Immediately after leaving system 
suspend and/or hibernation the same executables are run, but the first argument 
is now "post". All
 executables in this directory are executed in parallel, and execution 
of the action is not continued until all executables have finished.

 Note that scripts or binaries dropped in /lib/systemd/system-sleep/ 
are intended for local use only and should be considered hacks. If applications 
want to be notified of system suspend/hibernation and resume, there are much 
nicer interfaces
 available.

  
  It is unfortunate that such "hacks" are generally still required to get a 
laptop to suspend/hibernate and resume correctly.   

  However, I don't think /lib is the proper place for such scripts,
  especially for those that are added by local administrators. As far as
  I know, /lib is handled by dpkg and it should never be required to add
  stuff there manually.  Note that the FHS is also quite specific in
  this regard: "The /lib directory contains those shared library images
  needed to boot the system and run the commands in the root filesystem,
  ie. by binaries in /bin and /sbin.".  This doesn't seem to include
  custom scripts as used here.

   A better place would probably be /etc/systemd (similar to the
  obsolete /etc/pm/sleep.d).  At the very least, /lib/systemd/systemd-
  sleep should contain a script that calls user-provided scripts from a
  more appropriate location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1538681/+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 1523675] Re: Microsoft Ergonomic Keyboard 4000 has two input devices

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: systemd (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

** Changed in: udev (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: udev (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

-- 
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/1523675

Title:
  Microsoft Ergonomic Keyboard 4000 has two input devices

Status in systemd package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Won't Fix
Status in systemd source package in Trusty:
  Won't Fix
Status in udev source package in Trusty:
  Won't Fix

Bug description:
  Recently I have noticed that Zoom In/Out slider on my Microsoft
  Ergonomic Keyboard 4000 stopped working. I tried investigating what's
  wrong and noticed that my keyboard reports as two different input
  devices according to evtest

  sudo evtest output:
  (...)
  /dev/input/event2:  Microsoft Natural® Ergonomic Keyboard 4000
  /dev/input/event3:  Microsoft Natural® Ergonomic Keyboard 4000
  (...)

  /dev/input/event2 responds to normal keys
  /dev/input/event3 responds to multimedia keys and zoom in/out keys

  The most puzzling thing is that multimedia keys actually work and be
  bound. For example I have bound KEY_F17 to Next track in Amarok.
  Play/pause, Vol. Up/Down and Mute worked out of box.

  uname -a:
  Linux demonbane 3.16.0-55-generic #74~14.04.1-Ubuntu SMP Tue Nov 17 10:15:59 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -rd:
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523675/+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 1544747] Re: Strange device names for USB NICs

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Invalid

-- 
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/1544747

Title:
  Strange device names for USB NICs

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Fresh install of Xenial on an intel NUC with 1 onboard GigE and one
  USB GigE NIC.

  I was setting up networking for MAAS and discovered that the device
  names were ridiculous:

  bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
  eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
  enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

  In the previous Trusty install on this NUC with the same USB dongle,
  they were named eth0 and em1.  The predictable standard device names.

  Looking at udevadm:
  P: /devices/pci:00/:00:19.0/net/eno1
  E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
  E: ID_MODEL_ID=0x1502
  E: ID_NET_DRIVER=e1000e
  E: ID_NET_LABEL_ONBOARD=en L1U1
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enxeca86bfb9f66
  E: ID_NET_NAME_ONBOARD=eno1
  E: ID_NET_NAME_PATH=enp0s25
  E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
  E: ID_PATH=pci-:00:19.0
  E: ID_PATH_TAG=pci-_00_19_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Intel Corporation
  E: ID_VENDOR_ID=0x8086
  E: IFINDEX=2
  E: INTERFACE=eno1
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=5400250

  P: 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: ID_BUS=usb
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL=AX88178
  E: ID_MODEL_ENC=AX88178\x20
  E: ID_MODEL_FROM_DATABASE=AX88178
  E: ID_MODEL_ID=1780
  E: ID_NET_DRIVER=asix
  E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
  E: ID_NET_NAME=enx8cae4cff4099
  E: ID_NET_NAME_MAC=enx8cae4cff4099
  E: ID_NET_NAME_PATH=enp0s29u1u5
  E: ID_OUI_FROM_DATABASE=Plugable Technologies
  E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
  E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0
  E: ID_REVISION=0001
  E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02
  E: ID_SERIAL_SHORT=02
  E: ID_TYPE=generic
  E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
  E: ID_USB_DRIVER=asix
  E: ID_USB_INTERFACES=:00:
  E: ID_USB_INTERFACE_NUM=00
  E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass
  E: ID_VENDOR=ASIX_Elec._Corp.
  E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp.
  E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp.
  E: ID_VENDOR_ID=0b95
  E: IFINDEX=3
  E: INTERFACE=enx8cae4cff4099
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 
/sys/subsystem/net/devices/enx8cae4cff4099
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=8700146

  And finally, looking in /etc/udev:
  bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/rules.d:
  ..  .

  /etc/udev/hwdb.d:
  ..  .

  There are NO rules at all in udev for persistent names.  Not even some
  samples and defaults.

  Looking at a completely different Xenial system with a single GigE NIC:
  bladernr@galactica:~$ ifconfig
  enp2s0Link encap:Ethernet  HWaddr 40:8d:5c:51:5b:0d  

  P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller
  E: ID_MODEL_ID=0xe091
  E: ID_NET_DRIVER=alx
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enx408d5c515b0d
  E: ID_NET_NAME_PATH=enp2s0
  E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD.
  E: ID_PATH=pci-:02:00.0
  E: ID_PATH_TAG=pci-_02_00_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros
  E: ID_VENDOR_ID=0x1969
  E: IFINDEX=2
  E: INTERFACE=enp2s0
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp2s0
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=752502

  and again, nothing in the udev rules:
  bladernr@galactica:~$ ls -a /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/hwdb.d:
  .  ..

  /etc/udev/rules.d:
  .  ..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 228-6ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb 11 16:36:35 2016
  Installa

[Touch-packages] [Bug 1548284] Re: systemd-journald crashed with SIGABRT in __memcpy_avx_unaligned()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1548284

Title:
  systemd-journald crashed with SIGABRT in __memcpy_avx_unaligned()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Feb 20 12:58:49 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-03-25 (333 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   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: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __memcpy_avx_unaligned () at 
../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:119
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __memcpy_avx_unaligned()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-vivid
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1548284/+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 1545272] Re: reboot fails with "Failed to start reboot.target: Transaction is destructive."

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1545272

Title:
  reboot fails with "Failed to start reboot.target: Transaction is
  destructive."

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  `sudo reboot` fails with

  Failed to start reboot.target: Transaction is destructive.

  Broadcast message from richter@richter-lenovo-IdeaPad-U410 on
  pts/1 (Sa 2016-02-13 13:36:30 CET):

  The system is going down for reboot NOW!

  which seems to be caused by an incomplete suspend as stated in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253 which
  isn't a duplicate because the reason seem to be a btrfs issue there
  which I don't suffer from.

  I'd suggest to let the suspend time out, provide the user with the
  information that a suspend is pending and might timeout or succeed (or
  something similar, more useful than "Failed to start reboot.target:
  Transaction is destructive.") so that reboot is possible again after
  some time.

  The issue should be fixed in the kernel as well, it makes sense as
  well to handle this situation in `systemd` because assuming that the
  kernel is always stable is naive and adding such a timeout improves
  stability and better feedback usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 13 13:36:10 2016
  InstallationDate: Installed on 2013-10-17 (848 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: LENOVO IdeaPad U410
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-29-generic 
root=UUID=8c488557-8173-43a2-a3a8-df0a24695c08 ro 
rootflags=subvol=ubuntu-main-root quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to wily on 2015-11-19 (85 days ago)
  dmi.bios.date: 09/25/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 65CN90WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo U410
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr65CN90WW:bd09/25/2012:svnLENOVO:pnIdeaPadU410:pvrLenovoU410:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoU410:
  dmi.product.name: IdeaPad U410
  dmi.product.version: Lenovo U410
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545272/+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 1543039] Re: /lib/systemd/systemd-udevd:6:__open_nocancel:open:synthesize_change:on_inotify:source_dispatch

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1543039

Title:
  /lib/systemd/systemd-
  udevd:6:__open_nocancel:open:synthesize_change:on_inotify:source_dispatch

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  228-5ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/6e788ab7e0bfbfa5aac15cd5066b41da132f04fd
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1543039/+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 1544627] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1544627

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The computer was one... I was not even using it...

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: udev 228-5ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb 11 14:59:05 2016
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2016-02-03 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: HP HP ZBook Studio G3
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic 
root=UUID=a9634764-1439-45e7-a0ca-8c2d030238e6 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.03
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.03:bd12/25/2015:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.38:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1544627/+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 1531181] Re: package systemd 228-2ubuntu2 failed to install/upgrade: trigger failed with "connection timed out"

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1531181

Title:
  package systemd 228-2ubuntu2 failed to install/upgrade: trigger failed
  with "connection timed out"

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  When i copy file from external disk using NTFS my system stop and
  shutdown.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 228-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Tue Jan  5 11:17:10 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-12-04 (32 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151204.1)
  MachineType: Hewlett-Packard HP Compaq Pro 4300 AiO BR 20 PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed 
root=UUID=ed8fc301-d79d-4aa3-98a7-87fdaa216a78 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.10
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf

   3 overridden configuration files found.
  Title: package systemd 228-2ubuntu2 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
  UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.12
  dmi.board.asset.tag: BRJ425C8WQ
  dmi.board.name: 18DD
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: BRJ425C8WQ
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.12:bd06/09/2014:svnHewlett-Packard:pnHPCompaqPro4300AiOBR20PC:pvr1.00:rvnPEGATRONCORPORATION:rn18DD:rvr1.02:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Pro 4300 AiO BR 20 PC
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1531181/+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 1492850] Re: Dell pro venue 11 - No wireless connections after sleep

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1492850

Title:
  Dell pro venue 11 - No wireless connections after sleep

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I try for a long time to set-up the wifi for my dell pro venue 11
  v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi
  connection is perfect until the computer is suspend. After a suspend,
  even activating the wifi from network manager is impossible. After
  suspend even an exit doesn't reconnect to the wifi connection. It
  seems that the wifi chipset is off and it's impossible to wake up.

  Recently 15.04 has been update to 4.2 RC8. Nothing new !

  A file unload_modules has been created.
  /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any 
effect.

  sudo service network-manager restart doesn't work too !

  Before suspend

  @utopie:~$ sudo lshw -C network
  *-network
  description: Interface réseau sans fil
  produit: Wireless 7260
  fabriquant: Intel Corporation
  identifiant matériel: 0
  information bus: pci@:01:00.0
  nom logique: wlan0
  version: 83
  numéro de série: 5c:51:4f:d9:2e:75
  bits: 64 bits
  horloge: 33MHz
  fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
  configuration: broadcast=yes driver=iwlwifi 
driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 
latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
  ressources: irq:49 mémoire:f7d0-f7d01fff
  *-network DÉSACTIVÉ
  description: Ethernet interface
  identifiant matériel: 1
  nom logique: wwan0
  numéro de série: 1e:51:e0:b8:e1:da
  fonctionnalités: ethernet physical
  configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 
firmware=CDC MBIM link=no multicast=yes

  After suspend (no more wifi chipset !).
  @utopie:~$ sudo lshw -C network
  *-network DÉSACTIVÉ
  description: Ethernet interface
  identifiant matériel: 1
  nom logique: wwan0
  numéro de série: 1e:51:e0:b8:e1:da
  fonctionnalités: ethernet physical
  configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 
firmware=CDC MBIM link=no multicast=yes

  ---
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baly   1169 F pulseaudio
   /dev/snd/controlC1:  baly   1169 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=729324f1-42a5-45f8-9585-f6e0169f2d64
  InstallationDate: Installed on 2015-04-23 (144 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Venue 11 Pro 7130 vPro
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-29-generic.efi.signed 
root=UUID=35cde4a5-bbc3-442b-b239-d3f917925a94 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-29-generic N/A
   linux-backports-modules-3.19.0-29-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 3.19.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0T69G0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd02/18/2014:svnDellInc.:pnVenue11Pro7130vPro:pvr01:rvnDellInc.:rn0T69G0:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Venue 11 Pro 7130 vPro
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492850/+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 1495723] Re: Connecting USB devices failing

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
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/1495723

Title:
  Connecting USB devices failing

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  rob@DesktopUbuntu:~$ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  Ubuntu Software Center 13.10  (XUbuntu)

  I have had a problem with connecting my phone as a memory/disk device
  on Ubuntu 14.04 and found the same with a live install of 15.04. I
  recently bought an expensive 3-D Robox-CEL printer and was also
  experiencing no joy at all with extremely flaky connections.
  Fortunately one of the engineers at Robox-CEL published a patch to the
  udev .rules files and this cured the 3-D Printer connections and when
  I applied the same to the mobile phone .rules file it has been
  reliable as well.  His assertion was the later Linux's (I am not sure
  how wide he sees this problem here) have some sort of 'improvement'
  that interrogates the USB devices and in my case these two devices
  don't work with this new 'feature' and are extremely flaky.

  Here are the two new .rules I have added, that work for me

  # Samsung
  ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685b", 
ENV{ID_MM_DEVICE_IGNORE}="1"
  SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685b", 
GROUP="plugdev", NAME="GalaxySII", MODE="0666", OWNER=""

  #Robox Rules to stop the Linux sending disruptive commands to the 3D-Printer
  ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="081b", 
ENV{ID_MM_DEVICE_IGNORE}="1"
  #Establish a standard name for the Robox tty interface
  SUBSYSTEM=="tty", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="081b", 
SYMLINK="robox%n", MODE="0666"

  The first line in the .rules is the really critical one.

  This has been a huge problem for me, and I registering it as a 'bug'
  as I believe the OS should be a bit more clever with these devices and
  should not require this sort of user work-around.  Over the last two
  years my phone went from super reliable to unusable, wasting huge
  amounts of my time, and recently made my 14 day old 3-D Printer from a
  quality manufacturer useless.

  Thank you for your time and patience. I can send you a log of the
  transactions of the Robox machine's interactions with the USB port if
  you need them.  However the above two files should give a good lead on
  where I feel the problems lie.

  Cheers, Rob Ward

  PS The Robox people also altered the shell script in their software to
  look for the newly named 'robox0' connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495723/+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 1492088] Re: juju bootstrap fails inside a wily container

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1492088

Title:
  juju bootstrap fails inside a wily container

Status in juju-core:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Running juju 1.24.5 and attempting to do a local bootstrap inside a
  wily container fails with the following:

  [DEBUG: 09-03 20:49:56, container.py:139] Error with command: [Output]
  '2015-09-03 20:49:35 INFO juju.cmd supercommand.go:37 running juju
  [1.24.5-wily-amd64 gc]

  2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:109 Made
  dir /home/ubuntu/.cloud-install/juju/environments

  2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:245
  checking state port

  2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:245
  checking API port

  2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:38
  opening environment "local"

  2015-09-03 20:49:35 DEBUG juju.container.kvm kvm.go:71 kvm-ok output:

  INFO: /dev/kvm exists

  KVM acceleration can be used


  2015-09-03 20:49:35 DEBUG juju.provider.local environ.go:325 found
  "10.0.6.1" as address for "lxcbr0"

  2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:308
  writing jenv file

  2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:432
  writing jenv file to /home/ubuntu/.cloud-
  install/juju/environments/local.jenv

  2015-09-03 20:49:35 INFO juju.network network.go:194 setting prefer-
  ipv6 to false

  2015-09-03 20:49:35 INFO juju.cmd cmd.go:113 Bootstrapping environment
  "local"

  2015-09-03 20:49:35 DEBUG juju.environs.bootstrap bootstrap.go:98
  environment "local" supports service/machine networks: false

  2015-09-03 20:49:35 DEBUG juju.environs.bootstrap bootstrap.go:100
  network management by juju enabled: true

  2015-09-03 20:49:35 DEBUG juju.provider.local environ.go:325 found
  "10.0.6.1" as address for "lxcbr0"

  2015-09-03 20:49:35 INFO juju.cmd cmd.go:113 Starting new instance for
  initial state server

  2015-09-03 20:49:35 INFO juju.environs.bootstrap bootstrap.go:184
  newest version: 1.24.5.1

  2015-09-03 20:49:36 INFO juju.environs.bootstrap bootstrap.go:212
  picked bootstrap tools version: 1.24.5.1

  2015-09-03 20:49:36 INFO juju.cmd cmd.go:113 Building tools to upload
  (1.24.5.1-wily-amd64)

  2015-09-03 20:49:36 DEBUG juju.environs.sync sync.go:304 Building
  tools

  2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:122 looking
  for: juju

  2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:161 checking:
  /usr/bin/jujud

  2015-09-03 20:49:36 INFO juju.environs.tools build.go:167 found
  existing jujud

  2015-09-03 20:49:36 INFO juju.environs.tools build.go:177 target: /tmp
  /juju-tools782467678/jujud

  2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:232 forcing
  version to 1.24.5.1

  2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:38 adding
  entry: &tar.Header{Name:"FORCE-VERSION", Mode:436, Uid:0, Gid:0,
  Size:8, ModTime:time.Time{sec:63576910176, nsec:90190527,
  loc:(*time.Location)(0x2c9b140)}, Typeflag:0x30, Linkname:"",
  Uname:"ubuntu", Gname:"ubuntu", Devmajor:0, Devminor:0,
  AccessTime:time.Time{sec:63576910176, nsec:90190527,
  loc:(*time.Location)(0x2c9b140)},
  ChangeTime:time.Time{sec:63576910176, nsec:90190527,
  loc:(*time.Location)(0x2c9b140)}, Xattrs:map[string]string(nil)}

  2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:38 adding
  entry: &tar.Header{Name:"jujud", Mode:493, Uid:0, Gid:0,
  Size:67623560, ModTime:time.Time{sec:63576910176, nsec:90190527,
  loc:(*time.Location)(0x2c9b140)}, Typeflag:0x30, Linkname:"",
  Uname:"ubuntu", Gname:"ubuntu", Devmajor:0, Devminor:0,
  AccessTime:time.Time{sec:63576910176, nsec:90190527,
  loc:(*time.Location)(0x2c9b140)},
  ChangeTime:time.Time{sec:63576910176, nsec:90190527,
  loc:(*time.Location)(0x2c9b140)}, Xattrs:map[string]string(nil)}

  2015-09-03 20:49:42 INFO juju.environs.sync sync.go:323 built tools
  1.24.5.1-wily-amd64 (13769kB)

  2015-09-03 20:49:42 INFO juju.cmd cmd.go:113 Installing Juju agent on
  bootstrap instance

  2015-09-03 20:49:42 DEBUG juju.cloudconfig.instancecfg
  instancecfg.go:521 Setting numa ctl preference to false

  2015-09-03 20:49:42 INFO juju.provider.local environ.go:156 local
  provider; disabling refreshing OS updates.

  2015-09-03 20:49:42 INFO juju.provider.local environ.go:162 local
  provider; disabling OS upgrades.

  Logging to /home/ubuntu/.cloud-install/juju/local/cloud-init-
  output.log on remote host

  Installing package: curl

  Installing package: cpu-checker

  Installing package: bridge-utils

  Installing package: rsyslog-gnutls

  Installing package: cloud-utils

  Installing package: cloud-image-utils

  Installing package: tmux

  Bootstra

[Touch-packages] [Bug 1474426] Re: systemctl status globbing does not work with .service suffix on version 222

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1474426

Title:
  systemctl status globbing does not work with .service suffix on
  version 222

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I am writing a test that executes systemctl status docker_docker-
  daemon_*.service to get if the docker service is running.

  This works in systemd 219, the version we have in vivid:

  (amd64)ubuntu@test:~$ systemd --version
  systemd 219
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN
  (amd64)ubuntu@test:~$ systemctl status docker_docker-daemon_*.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:41:10 UTC; 15min ago
   Main PID: 11860 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─11860 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─11868 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.0...
 └─12664 sleep 2

  On version 222, the version we have in wily it doesn't work:

  (amd64)ubuntu@localhost:~$ systemctl status docker_docker-
  daemon_*.service

  (nothing is returned)
  Changing the * by the version, it works:

  (amd64)ubuntu@localhost:~$ systemctl status 
docker_docker-daemon_1.6.1.002.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:45:31 UTC; 12min ago
   Main PID: 789 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─ 789 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─ 800 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.00...
 └─1372 sleep 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1474426/+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 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1457400

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

Status in lvm2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
  onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

  I checked the shutdown log messages and I get the follow message.

  A stop job is running for Session c2 of user * (25s/ 1min 30 s)

  It count downs till 1:30 minutes and then shutdown the machine.

  Why is it happening.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1457400/+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 1470745] Re: Non-skippable filesystem check at boot time

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
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/1470745

Title:
  Non-skippable filesystem check at boot time

Status in plymouth package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  In the past, whenever a filesystem check was forced at boot time the
  user was notified by a message on the splash screen and had the option
  to cancel the check by pressing "C".

  At some point this situation regressed into the current state where:

  1) There is no notification any more. The boot process won't complete
  for apparently no reason, showing an empty splash or simply black
  screen. You have to manually step through the consoles and find the
  one where the actual boot messages appear to find out that there is a
  fs check running.

  2) There is no way of cancelling a fs check any more. This is most
  intolerable for a productive system since it renders you whole machine
  useless in a time where you need it to get some work done or if you
  want to start it for a presentation.

  If Ubuntu enforces fs checks on boot a skip-option is an absolute
  requirement for users with large drives. For me, checking a 1TB drive
  takes 30 minutes! This wouldn't be much of an issue if Ubuntu let me
  choose when to check it, but it forces me to wait half an hour for a
  system I might be needing right now.

  These long fsck times aren't uncommon, other users are reporting this as well:
  http://ubuntuforums.org/showthread.php?t=1815997
  http://ubuntuforums.org/showthread.php?t=1436446

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Thu Jul  2 09:01:24 2015
  InstallationDate: Installed on 2014-07-15 (351 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.19.0-22-generic 
root=UUID=d4590e7b-385b-4c87-bdf1-bcf43bf33b5a ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1470745/+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 1488954] Re: systemctl is-active on aliased names returns unknown

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1488954

Title:
  systemctl is-active on aliased names returns unknown

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  There is a symlink in /lib/systemd/system from udev.service to
  systemd-udevd.service, however, running "systemctl is-active udev"
  returns "unknown" instead of "active" initially. This can be solved by
  running "systemctl status udev" once, but for monitoring the service
  it would be nicer if the "is-active" would be working out of the box.

  $ lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04

  $ apt-cache policy udev
  udev:
Installed: 219-7ubuntu6
Candidate: 219-7ubuntu6
Version table:
   *** 219-7ubuntu6 0
  500 http://eu.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   219-7ubuntu3 0
  500 http://eu.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1488954/+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 1456730] Re: Hangs on shutdown after installing and running serviio

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1456730

Title:
  Hangs on shutdown after installing and running serviio

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Ran serviio during the vivid cycle with no problem - either using
  systemd or upstart.

  Installed wily.

  Grabbed,extracted serviio from
  http://download.serviio.org/releases/serviio-1.5.2-linux.tar.gz

  Installed openjdk-8-jre.

  Set ~/serviio-1.5.2/bin/serviio.sh and ~/serviio-1.5.2/bin/serviio-
  console.sh to run at start.

  Reboot using systemd,serviio starts.

  Reboot hangs for 90s.

  Kill java tasks associated with serviio - reboot takes place in time
  expected.

  Boot with upstart - reboot takes place in time expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 219-9ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
  Uname: Linux 3.19.0-17-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 19 18:19:40 2015
  InstallationDate: Installed on 2015-05-12 (6 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512)
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic 
root=UUID=6bcbfcc1-c493-4dbe-9421-ef270047a82a ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+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 1467943] Re: system shutdown hangs if btrfs on file image (mounted via cifs) is mounted

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
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/1467943

Title:
  system shutdown hangs if btrfs on file image (mounted via cifs) is
  mounted

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This happens if the network connection already failed before the
  shutdown has been requested. `systemd` should get into state where it
  refuses to proceed in shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  Uname: Linux 4.1.0-040100-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 23 15:14:18 2015
  InstallationDate: Installed on 2015-06-08 (15 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20221
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100-generic 
root=UUID=d665563a-2f33-4d06-bf9c-6838fe5ae3e9 ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-06-09 (14 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467943/+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 1475094] Re: Warning because an already existing user is tried to be created

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Warning because an already existing user is tried to be created

Status in adduser package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in adduser package in Debian:
  Fix Released

Bug description:
  I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the
  last upgrades I have noticed that these packages are trying to create
  users which already exists. On reinstalling them udev shows on setting
  up "addgroup: The group `input' already exists as a system group.
  Exiting." and systemd shows on setting up "addgroup: The group
  `systemd-journal' already exists as a system group. Exiting." and
  "addgroup: The group `systemd-journal-remote' already exists as a
  system group. Exiting.". Maybe it could be checked if a user exists to
  avoid showing a warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1475094/+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 1475522] Re: Ubuntu 15.04 - Machine do not reboot/shutdown when ISCSI LUNs are connected and do not connect automatically at boot time.

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
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/1475522

Title:
  Ubuntu 15.04 - Machine do not reboot/shutdown when ISCSI LUNs are
  connected and do not connect automatically at boot time.

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I am having issues while shutting down my Ubuntu 15.04 machine when
  ISCSI LUNs are connected to machine.  I have checked kern.log,
  boot.log and journalctl -b , journalctl -b -1 but it does not indicate
  or show errors which faced at reboot. So I have attached the
  screenshot of the error message. I have tried sync && reboot -f and it
  works fine and system reboots. I am running 3.19-22 kernel with Xen
  Hypervisor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475522/+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 1498381] Re: journald 100% CPU and fill the drive

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1498381

Title:
  journald 100% CPU and fill the drive

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  Sometimes journald takes 100% of the CPU and fill my drive entirely in
  a few minutes if I don't stop it.

  It began just after Ubuntu 15.04 installation, stopped a few months
  ago, and re-appeared yesterday.

  If I look in /var/log/syslog, I get thousands of messages repeating
  these two lines :

  gnome-session[1671]: page: Error: 
/usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm: File corrupted, or 
not a TFM file
  gnome-session[1671]: page: Warning: font `cmr10' not found, trying metric 
files instead

  If I restart journald (sudo systemctl restart systemd-journald), the
  problem disappears.

  Do not hesitate to ask if I can provide more information.

  Thanks for your time and work,
  Yvan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 22 11:04:35 2015
  InstallationDate: Installed on 2015-06-11 (102 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteBook Folio 1040 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=96529e88-e0e5-455c-acb1-f1a906022ab4 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M76 Ver. 01.02
  dmi.board.name: 2270
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 81.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM76Ver.01.02:bd03/10/2015:svnHewlett-Packard:pnHPEliteBookFolio1040G2:pvrA3008C510003:rvnHewlett-Packard:rn2270:rvrKBCVersion81.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1040 G2
  dmi.product.version: A3008C510003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1498381/+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 1445512] Re: journalctl not showing all content in the log.

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1445512

Title:
  journalctl not showing all content in the log.

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  so the manual say this..
  ---
 If called without parameters, it will show the full contents of the 
journal, starting with the oldest entry collected.
  ---

  This is not happening for me. if I do the following command

  journalctl | grep [program name]

  I get less output than if I do

  journalctl _COMM=[program name]

  
  My guess is that this is happening for the same reason that my previous bug 
where --list-boots did not work. 

  Namely there seems to be a major problem when the log is corrupted and
  things behave inconsistently.

  journalctl --verify

  shows several corruptions but that should not make this type of
  inconsistent behavior. The systemd people have said repeatedly that
  there is no need for a repair tool and that systemd can handle
  corruptions just fine. Not my experience.

  Now the reason I get corruptions is probably due to unreliable
  suspend/resume where resume is not working an a power cycle is needed.
  This is not a uncommon thing suspend/resume just is not gong to be
  100% and people are going to end up with journal that is corrupted.

  Note that the copy I get in syslog contain all the output I get when I
  run journalctl with the _COMM option.

  systemd journal handling needs to improve substantial so it can handle
  corruption better and at least be consistent with itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 17 15:59:13 2015
  InstallationDate: Installed on 2015-04-09 (7 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Apple Inc. MacBookPro11,2
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic.efi.signed 
root=UUID=f84ca03e-c0d4-45ad-80f3-c45d4ad106dd ro rootflags=subvol=@ noprompt 
persistent quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B14.1501071031
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-3CBD00234E554E41
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-3CBD00234E554E41
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B14.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41:
  dmi.product.name: MacBookPro11,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1445512/+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 1437963] Re: systemd-journald crashed with SIGABRT in pending_prioq_compare()

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu)
   Status: Invalid => Won't Fix

-- 
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/1437963

Title:
  systemd-journald crashed with SIGABRT in pending_prioq_compare()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  logging in after an upgrade and restore of data and this happened
  right after ui displayed

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 29 16:21:57 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-03-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150325)
  MachineType: System76, Inc. Gazelle Professional
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=ff5bcd5d-b5e2-426d-a259-82e1bb05f47c ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp8
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp8
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1437963/+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 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1450396

Title:
  Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
  lan setting

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  === Update: This bug was reported from BIOS version F13 of my board,
  in the meantime I upgraded to the most recent version F14, but this
  had no impact on the bug. ===

  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1450396/+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 1448070] Re: shutdown -h/-r now "wall message" message does not send wall

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1448070

Title:
  shutdown -h/-r now "wall message" message does not send wall

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,

  As far as I know, shutdown command (and other reboot/poweroff/halt
  commands) are now just alias for systemctl which inits the right
  target, so I am reporting this bug to systemd package.

  I noted a strange thing : shutdown -h now "wall message" do not send
  the wall message, but shutdown -h + does.

  I conduct this test in TTY also, it seems that when the timer is "now" (or 
+0), the wall is sent after shuting down services like OpenSSH, so users logged 
in cannot see it.
  When the time value is +1 or more, the wall is properly displayed.

  Step to reproduce :

  Ubuntu Version : 15.04 from a fresh Released install (seems to not be
  the case in 14.10 where systemd is not completely used, as all
  shutdown/halt/poweroff/reboot commands are symlink to reboot and not
  "systemctl").

  - sudo shutdown -r now "This is a maintenance reboot as we discuss earlier, 
server will be back in few seconds."
  -> No one of my logged user saw this notice

  - sudo shutdown -r +3 "This is an unscheduled URGENT maintenance. Please save 
your work and prepare to immediate reboot in 3 minutes"
  -> It's working.

  Regards,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448070/+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 1447879] Re: fscking btrfs consisting of multiple partitions fails

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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/1447879

Title:
  fscking btrfs consisting of multiple partitions fails

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have two SSDs in raid0 (striped) configuration with my root and home
  as separate subvolumes.  This setup has worked fine for several Ubuntu
  releases, but fails with systemd on 15.04.  systemd does manage to
  mount root, but then looks like it is trying to fsck the "disk" for
  home which is nonsensical.  After 90 seconds it drops into a useless
  shell where I can't fix things.

  Relevant lines from /etc/fstab

  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@
 0   1
  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home
 0   2

  
  Note how the lines are identical except for the subvol value.  I originally 
didn't have the device= bits either but had to add it for root because of how 
`btrfs device scan` is run.  With or without it present doesn't make any 
difference for home.

  There is no such problem booting with upstart

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 23 19:45:38 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+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 1451032] Re: keyscript option in crypttab not implemented

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1451032

Title:
  keyscript option in crypttab not implemented

Status in systemd package in Ubuntu:
  Invalid
Status in systemd package in Debian:
  Confirmed

Bug description:
  The setup for unlocking an encrypted volume during boot using (only) a
  keyfile (on a detachable USB drive) usually calls for a keyscript to
  be specified as one of the encrypted volume's options. But with
  systemd, such encrypted volumes can only be unlocked during boot by
  typing in a passphrase.

  Steps to reproduce:
  1. Have a LUKS encrypted volume.
  2. Have said volume specified in /etc/crypttab, with keyscript= option 
pointing to your script for outputting the unlocking key.
  3. Boot.

  What I expect to happen:
  To have the volume unlocked by the script at boot time without manual 
intervention.

  What happens instead:
  Plymouth shows a prompt to enter a valid passphrase for the volume.

  Workarounds:
  Apparently the options for unlocking encrypted drives, including keyscript, 
can also be specified at the kernel command-line, without crypttab, and 
according to yaantc at Hacker News [1] this can be used to work around the 
issue. I haven't personally tried this.

  * [1] https://news.ycombinator.com/item?id=8477913

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  2 15:39:07 2015
  InstallationDate: Installed on 2014-10-18 (196 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=2185885c-b860-49a8-973f-fa3b52d3eecf ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (8 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1451032/+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 1438595] Re: systemd: fsck of ext4 filesystem does not show progress

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1438595

Title:
  systemd: fsck of ext4 filesystem does not show progress

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  When booting following a crash fsck is triggered for the root volume
  (LVM containing ext4 filesystem).  This is correctly announced by
  systemd/plymouth and remains announced for the duration of the fsck,
  however the percentage complete is always 0.0% for the entire duration
  of the check.  For those of us with no disk lights this is very off
  putting.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 31 10:10:41 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-20 (648 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  MachineType: Intel Corporation 2012 Client Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro debug splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (505 days ago)
  dmi.bios.date: 07/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Latexo FFRD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2012 Client Platform
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1438595/+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