[Touch-packages] [Bug 1774419] Re: easy_install command is missing

2019-04-16 Thread Metta Crawler 
Work-around

pip install --user setuptools

then set $PATH to include ~/.local/bin


** Also affects: python-setuptools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896652
   Importance: Unknown
   Status: Unknown

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

Title:
  easy_install command is missing

Status in python-setuptools package in Ubuntu:
  Confirmed
Status in python-setuptools package in Debian:
  Unknown

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Package: python-setuptools
  Version:  39.0.1-2

  This package installs the easy_install module, but the command is
  missing:

  deploy@controller0:~$ which easy_install
  deploy@controller0:~$ echo $?
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+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 1731566] Re: systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

2017-12-13 Thread Metta Crawler 
Re: But the inner PV is only for the guest to use - no?

The intent is that the inner PV is only for the guest to use.  What has
happened for years and years is that unless you mask using
/etc/lvm/lvm.conf the host will vgscan the inner PV and vgchange it too.
Until 17.10 (possibly 17.04, I skipped that one) this was mostly a
cosmetic issue, now it adds four minutes to the boot time.

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

Title:
  systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an
  LV

Status in systemd package in Ubuntu:
  New
Status in udev package in Debian:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Expected:

  Ubuntu 17.10 booting up as fast as Ubuntu 16.04

  What happened instead:

  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.

  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s

  The second one is from /scripts/init-bottom/lvm where 'udevadm
  --settle' is run.

  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi

  Reproducing:

  Where $vg is some existing volume group name:

  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot

  Use case:

  KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.
  This is somewhat involuntary as certain appliance VMs come configured this 
way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 18:29:33 2017
  InstallationDate: Installed on 2017-11-05 (5 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  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.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  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/1731566/+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 1731566] Re: systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

2017-12-11 Thread Metta Crawler 
** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  
  Expected:
  
  Ubuntu 17.10 booting up as fast as Ubuntu 16.04
  
  What happened instead:
  
  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.
  
  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s
  
  The second one is from /scripts/init-bottom/lvm where 'udevadm --settle'
  is run.
  
  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi
  
  Reproducing:
  
  Where $vg is some existing volume group name:
  
  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot
  
  Use case:
  
  KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.
- 
+ This is somewhat involuntary as certain appliance VMs come configured this 
way.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 18:29:33 2017
  InstallationDate: Installed on 2017-11-05 (5 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  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.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an
  LV

Status in systemd package in Ubuntu:
  New
Status in udev package in Debian:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Expected:

  Ubuntu 17.10 booting up as fast as Ubuntu 16.04

  What happened instead:

  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.

  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s

  The second one is from /scripts/init-bottom/lvm where 'udevadm
  --settle' is run.

  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi

  Reproducing:

  Where $vg is some existing volume group name:

  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot

  Use case:

  KVM/Qemu li

[Touch-packages] [Bug 1714301] Re: systemd-networkd hangs my boot (wireless)

2017-11-28 Thread Metta Crawler 
If you are looking for newer bug reports with this issue try
LP: #1717152
LP: #1728181

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  août 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoû

[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

2017-11-28 Thread Metta Crawler 
This bug may be a duplicate of LP #1717152

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

2017-11-28 Thread Metta Crawler 
I'm not using cloud-init. My network devices are not managed because I disabled 
NetworkManager.service shortly after installing 17.10 on bare metal Nov 5, 2017 
9:44 AM EDT.  I think there were too many fires then and I didn't want to try 
to convince NetworkManager to use a bridge.  I just lived with the two minute 
delay while working on the four minute delay LP 1731566
and the "BUG: unable to handle kernel NULL pointer dereference at (null)" LP 
1730374 until work on that last issue lead to the two minute delay clearing up 
as a side-effect.

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

2017-11-28 Thread Metta Crawler 
This morning I found out that if I boot
linux-image-4.13.0-17-generic
I get a hang at
Nov 23 07:12:47 lakshmi NetworkManager[1795]:  [1511439167.0455] manager: 
rfkill: WWAN hardware radio set enabled
Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed: 
Connection timed out

But if I boot
linux-image-4.14.2-041402-generic
there is no two minute delay.

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1714301] Re: systemd-networkd hangs my boot (wireless)

2017-11-28 Thread Metta Crawler 
This morning I found out that if I boot
linux-image-4.13.0-17-generic
I get a hang at
Nov 23 07:12:47 lakshmi NetworkManager[1795]:   [1511439167.0455] 
manager: rfkill: WWAN hardware radio set enabled
Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed: 
Connection timed out

But if I boot
linux-image-4.14.2-041402-generic
there is no two minute delay.

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  août 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Se

[Touch-packages] [Bug 1731566] [NEW] systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

2017-11-10 Thread Metta Crawler 
Public bug reported:

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

$ apt-cache policy udev
udev:
  Installed: 234-2ubuntu12.1
  Candidate: 234-2ubuntu12.1
  Version table:
 *** 234-2ubuntu12.1 500
500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
100 /var/lib/dpkg/status
 234-2ubuntu12 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

Expected:

Ubuntu 17.10 booting up as fast as Ubuntu 16.04

What happened instead:

During boot up the system will hang and then a timeout will allow it
continue. This happens twice.

The first one occurs right after the network interfaces are renamed. Example:
[5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
[  121.345255] raid6: sse2x1   gen()  4431 MB/s

The second one is from /scripts/init-bottom/lvm where 'udevadm --settle'
is run.

# we cannot properly synthesize LVM LV change events with udevadm trigger, so
# if we use LVM, we need to let it finish; otherwise we get missing LV symlinks
# (LP #1185394)
if [ -x /sbin/vgchange ]; then
udevadm settle --timeout=121 || true
fi

Reproducing:

Where $vg is some existing volume group name:

lvcreate -n pvtest -L 20m $vg
pvcreate /dev/$vg/pvtest
reboot

Use case:

KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.


ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: udev 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 10 18:29:33 2017
InstallationDate: Installed on 2017-11-05 (5 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3029
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A89GTD-PRO/USB3
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.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: udev (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug artful wayland-session

** Bug watch added: Debian Bug tracker #867368
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867368

** Also affects: udev (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867368
   Importance: Unknown
   Status: Unknown

** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ apt-cache policy udev
  udev:
-   Installed: 234-2ubuntu12.1
-   Candidate: 234-2ubuntu12.1
-   Version table:
-  *** 234-2ubuntu12.1 500
- 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  234-2ubuntu12 500
- 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
+   Installed: 234-2ubuntu12.1
+   Candidate: 234-2ubuntu12.1
+   Version table:
+  *** 234-2ubuntu12.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  234-2ubuntu12 500
+ 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  
  Expected:
  
  Ubuntu 17.10 booting up as fast as Ubuntu 16.04
  
  What happened instead:
  
  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.
  
  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s
  
  The second one is from /scripts/init-bottom/lvm where 'udevadm --settle'
  is run.
  
  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise w

[Touch-packages] [Bug 434835] Re: unattended-upgrades hangs system on shutdown

2017-09-29 Thread Metta Crawler 
This might be the same issue that was fixed in Bug #1654600

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

Title:
  unattended-upgrades hangs system on shutdown

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: unattended-upgrades

  I am running Kubuntu-Netbook, based on Karmic I believe, my problem
  relates to shutting down the netbook.

  version appears as: Installed 0.52ubuntu1

  I'd expect the machine to shutdown, reboot when requested.

  Instead it appears to shut down nicely until I see

  *Shutting down ALSA   [ OK ]
  Checking for running unattended-upgrades:* Asking all remaining processess to 
terminate_

  and it will just sit there, forever.

  The unattended-upgrades script in /etc/init.d has been run on a
  seperate machine by hand and appears to hang on that machine also.

  My bug reporting is not much up to scratch, so I hope I've covered it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/434835/+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 1301776] Re: Update manager is really small and not resizeable

2014-08-14 Thread Metta Crawler 
Just out of curiosity has anyone tried:

sudo apt-get install gnome-packagekit
gpk-update-viewer

as a work-around?  When I get some time to play in a VM I'll do it
myself.

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

Title:
  Update manager is really small and not resizeable

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  In Progress
Status in “update-manager” package in Ubuntu:
  Invalid
Status in “compiz” source package in Trusty:
  Triaged
Status in “unity” source package in Trusty:
  Confirmed
Status in “update-manager” source package in Trusty:
  Invalid

Bug description:
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  : "The Updates
  Available window should be manually resizable only when it is in this
  expanded state."

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301776/+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