[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Tais P. Hansen]

Thanks for the tip. Not sure why both were enabled but disabling
systemd-networkd.service fixes the long wait during boot for me.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Tais P. Hansen]

Tested 252.5-2ubuntu3.2 on Ubuntu 23.04 (lunar) and it still hangs for 2
minutes during boot.

$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 7
Found link 6
Found link 5
Found link 4
Found link 3
Found link 2
Found link 1
lo: link is ignored
wlp6s0: link is not managed by networkd (yet?).
virbr2: link is not managed by networkd (yet?).
enp5s0: link is not managed by networkd (yet?).
enp4s0: link is not managed by networkd (yet?).
virbr0: link is not managed by networkd (yet?).
tailscale0: link is not managed by networkd (yet?).
Timeout occurred while waiting for network connectivity.

Desktop system.

Both systemd-networkd and NetworkManager services are running and
active.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 520546] Re: Alt-f2 switches to virtual terminal 2

[Tais P. Hansen]

** Tags added: xenial

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1771962] Re: hanging at boot for about 30 seconds since upgrade to bionic

[Tais P. Hansen]

Note that this also applies if your swap is on ZFS. Ubuntu will attempt
to use it automatically and cause a 30 second delay as the swap
partition will not be available during early boot. Ie.

I: The initramfs will attempt to resume from /dev/zd0
I: (UUID=a0c4e220-8b9f-447b-b2e2-d2abeb2f6c39)
I: Set the RESUME variable to override this.

and

Aug  2 14:58:00 taisph-enodatio kernel: [3.822995] Btrfs loaded, 
crc32c=crc32c-intel
Aug  2 14:58:00 taisph-enodatio kernel: [   35.038644] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)


Setting RESUME=none is currently necessary to work around this.

Tested with initramfs-tools 0.130ubuntu3.1.

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

Title:
  hanging at boot for about 30 seconds since upgrade to bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, even if the swap 
device is ephemeral (i.e. swap encrypted with a random key).  This adds an 
inappropriate 30-second boot delay to any system with randomly-crypted swap, 
which includes any system that was installed with encrypted home directories in 
earlier releases.

  [Test case]
  1. Install the ecryptfs-utils package.
  2. Enable encrypted swap by running 'sudo ecryptfs-setup-swap'.
  3. Run 'update-initramfs -u' to regenerate the initramfs.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language.  An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users.  A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A `dmesg` 
shows

  ```
  [3.407230] clocksource: Switched to clocksource tsc
  [   34.632583] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  ```

  This is 100% reproducable and is always 30s minimum. I do not know in
  which package to report this properly – please excuse me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: i3
  Date: Fri May 18 09:40:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-03 (1444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized

   This incident has been reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771962/+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 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock

[Tais P. Hansen]

I am on 16.04 LTS Xenial and my Lenovo W520 in a dock with two external
monitors suspends about 20 seconds after login as long as the laptop lid
is closed.

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

Title:
  [HP, Dell notebooks] suspends on closed lid, does not recognized
  external monitors/dock

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Using systemd as init system on a HP zbook15 notebook having 2 external 
monitors connected using a docking station and starting with lid closed the 
system goes to sleep after successfully booting and starting lightdm greeter. 
Sometimes there's enough time to enter username and password but system goes to 
sleep every time after a few seconds.
  The system can be woken up and used after this happens but it will not let me 
shutdown later.

  The problem is just present in docked situation starting with closed
  lid using systemd a init system.

  If notebook is used in non-docked situation with open lid and systemd
  the problem does not occur.

  Workaround: A switch back to upstart as init system resolves the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv 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
  Date: Wed Apr 29 14:46:09 2015
  InstallationDate: Installed on 2015-04-27 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock

[Tais P. Hansen]

... Sorry, Lenovo W540 ... I haven't tested on my W520 yet.

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

Title:
  [HP, Dell notebooks] suspends on closed lid, does not recognized
  external monitors/dock

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Using systemd as init system on a HP zbook15 notebook having 2 external 
monitors connected using a docking station and starting with lid closed the 
system goes to sleep after successfully booting and starting lightdm greeter. 
Sometimes there's enough time to enter username and password but system goes to 
sleep every time after a few seconds.
  The system can be woken up and used after this happens but it will not let me 
shutdown later.

  The problem is just present in docked situation starting with closed
  lid using systemd a init system.

  If notebook is used in non-docked situation with open lid and systemd
  the problem does not occur.

  Workaround: A switch back to upstart as init system resolves the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv 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
  Date: Wed Apr 29 14:46:09 2015
  InstallationDate: Installed on 2015-04-27 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 919489] Re: gsettings crashed with SIGSEGV in g_settings_schema_source_ref()

[Tais P. Hansen]

** Tags added: xenial

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

Title:
  gsettings crashed with SIGSEGV in g_settings_schema_source_ref()

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Updated. rebooted, crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: libglib2.0-bin 2.31.10-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
  Uname: Linux 3.2.0-10-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 20 20:04:53 2012
  ExecutablePath: /usr/bin/gsettings
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20111214)
  ProcCmdline: gsettings get org.gnome.desktop.interface toolkit-accessibility
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5d433f84b3 :   
lock addl $0x1,0x10(%rdi)
   PC (0x7f5d433f84b3) ok
   source "$0x1" ok
   destination "0x10(%rdi)" (0x0010) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   g_settings_schema_source_ref () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   ?? ()
  Title: gsettings crashed with SIGSEGV in g_settings_schema_source_ref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/919489/+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