[Bug 2067814] [NEW] não entra no app e não consegue instalar nada

[Alessandra Menezes Martins]

Public bug reported:

Comprei o computador recentemente e tentei instalar jogos nele e percebi que 
não instalava porque o Ubuntu não abria o aplicativo e assim não consigo 
instalar nada.
Espero que arrumem esse problema em breve.
Fiz o que você pediu, mas não achei as informações sobre a versão do Ubuntu e 
do pacote

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.15.0-107.117~20.04.1-generic 5.15.149
Uname: Linux 5.15.0-107-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  1 21:18:55 2024
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz blacklist=r8169 
modprobe.blacklist=r8169 nomodeset systemd.debug-shell boot=casper 
automatic-ubiquity noprompt quiet splash nopersistent ---
InstallationDate: Installed on 2024-05-27 (5 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal oem-config ubiquity-20.04.15.19

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067814

Title:
  não entra no app e não consegue instalar nada

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

[Fabio Augusto Miranda Martins]

Based on discussions at https://github.com/nfs-ganesha/nfs-
ganesha/issues/1123, it seems this is something released with nfs-
ganesha V4, so IIUC, this is something that will only be available to an
Openstack + Manila + Ceph + NFS Ganesha in Noble Numbat, since it offers
nfs-ganesha 4.3-8ubuntu1

** Changed in: nfs-ganesha (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064657

Title:
  Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

[Fabio Augusto Miranda Martins]

This is also being discussed upstream: https://github.com/nfs-
ganesha/nfs-ganesha/issues/1123

** Bug watch added: github.com/nfs-ganesha/nfs-ganesha/issues #1123
   https://github.com/nfs-ganesha/nfs-ganesha/issues/1123

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064657

Title:
  Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

[Fabio Augusto Miranda Martins]

Hi Peter,

The NFS client is a Jammy VM running nfs-common 1:2.6.1-1ubuntu1.2 and
kernel 5.15.0-102-generic.

I'm running a sosreport and will attach it here soon.

Regards,
Fabio

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064657

Title:
  Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

[Fabio Augusto Miranda Martins]

** Attachment added: "sosreport-jammy-130612-2024-05-22-dnjwtoi.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+attachment/5781410/+files/sosreport-jammy-130612-2024-05-22-dnjwtoi.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064657

Title:
  Add support for CEPH ceph.file.layout and ceph.dir.layout xattr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066383] [NEW] PlayOnLinux: include mandatory dependency

[Rodrigo Bertoldo de Sousa Martins]

Public bug reported:

PlayOnLinux requires asyncore from python3 to work. The deb package
doesn't include this depend, so to fix this bug is necessary to include
python3-pyasyncore in mandatory dependency to get working without
issues.

Without this package, the playonlinux doesn't work:

rodrigo@rodrigo:~/Downloads$ playonlinux
Looking for python3... 3.12.3 - selected
/usr/share/playonlinux/python/mainwindow.py:710: SyntaxWarning: invalid escape 
sequence '\|'
  self.SupprotedIconExt = 
"All|*.xpm;*.XPM;*.png;*.PNG;*.ico;*.ICO;*.jpg;*.JPG;*.jpeg;*.JPEG;*.bmp;*.BMP\
1.0
Traceback (most recent call last):
  File "/usr/share/playonlinux/python/mainwindow.py", line 41, in 
import options, threading, debug
  File "/usr/share/playonlinux/python/options.py", line 21, in 
from asyncore import dispatcher
ModuleNotFoundError: No module named 'asyncore'

The python3 asyncore module installation solves this issue.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: playonlinux 4.3.4-3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 22 11:33:14 2024
InstallationDate: Installed on 2024-05-21 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
PackageArchitecture: all
ProcEnviron:
 LANG=pt_BR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: playonlinux
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066383

Title:
  PlayOnLinux: include mandatory dependency

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048938] Re: [needs-packaging] Intel quickassist (QAT) : openssl QAT engine

[Ricardo Martins]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048938

Title:
  [needs-packaging] Intel quickassist (QAT) : openssl QAT engine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2048938/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048950] Re: [needs-packaging] Intel quickassist (QAT) : zip compression library and application utility

[Ricardo Martins]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048950

Title:
  [needs-packaging] Intel quickassist (QAT) : zip compression library
  and application utility

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2048950/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048895] Re: [needs-packaging] Intel quickassist (QAT) : qatlib

[Ricardo Martins]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048895

Title:
  [needs-packaging] Intel quickassist (QAT) : qatlib

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2048895/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060745] Re: nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble)

[Thiago Martins]

It seems to be an upstream issue:
https://github.com/NetworkBlockDevice/nbd/issues/156

** Bug watch added: github.com/NetworkBlockDevice/nbd/issues #156
   https://github.com/NetworkBlockDevice/nbd/issues/156

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060745

Title:
  nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04
  (Noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060745] [NEW] nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble)

[Thiago Martins]

Public bug reported:

[ Impact ]

NBD users who want to use /etc/nbdtab will face issues when trying to
start the NBD Client. Trying to use the `systemd` service also doesn't
work.

[ Test Plan ]

Inside a Noble VM (not a container):

# apt update
# apt install -y nbd-client nbd-server
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service

Verify that NBD is working properly:

# nbd-client localhost /dev/nbd0 -name vol0

It should work.

To clean it up:

# nbd-client -d /dev/nbd0

Now, trigger the problem:

# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0

You should see the error:

# nbd-client nbd0
Error: Socket failed: Connection refused

Further attempts with `systemd` also fail:

# systemctl restart nbd@nbd0
Job for nbd@nbd0.service failed because the control process exited with error 
code.
See "systemctl status nbd@nbd0.service" and "journalctl -xeu nbd@nbd0.service" 
for details.

And the logs:

# journalctl -u nbd@nbd0.service -n 25
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
Apr 09 21:56:17 noble-nbd-1 systemd[1]: Starting nbd@nbd0.service - NBD client 
connection for nbd0...
Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Socket failed: Connection refused
Apr 09 21:56:17 noble-nbd-1 nbd-client[5698]: Error: Socket failed: Connection 
refused
Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Exiting.
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Main process exited, 
code=exited, status=1/FAILURE
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Failed with result 
'exit-code'.
Apr 09 21:56:17 noble-nbd-1 systemd[1]: Failed to start nbd@nbd0.service - NBD 
client connection for nbd0.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060745

Title:
  nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04
  (Noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059152] [NEW] PyMol has a gear icon on dash

[Junior Martins]

Public bug reported:

PyMOL should have its icon on dash, like other apps, but instead shows a
gear icon.

Using `Alt+F2 > lg > Windows`, Pymol shows as "" with
"python3" as its wmclass.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pymol 2.5.0+dfsg-1build3 [modified: usr/bin/pymol 
usr/share/applications/pymol.desktop]
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 14:27:47 2024
ExecutablePath: /usr/bin/pymol
InstallationDate: Installed on 2023-07-25 (245 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterpreterPath: /usr/bin/dash
PackageArchitecture: all
SourcePackage: pymol
UpgradeStatus: Upgraded to mantic on 2023-10-29 (149 days ago)

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


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

** Attachment added: "Pymol gear dash icon"
   
https://bugs.launchpad.net/bugs/2059152/+attachment/5759725/+files/Screenshot%20from%202024-03-26%2014-31-07.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059152

Title:
  PyMol has a gear icon on dash

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058425] [NEW] pymol console does not scroll

[Junior Martins]

Public bug reported:

The console is unresponsive to scroll events and doesn't actually update its 
textual contents until an alt+tab.
When you type a command, its output is not shown until an alt+tab, and 
selecting the console's text renders parts of the updated content.

Ubuntu 23.10 (GNOME 45 on Wayland)
pymol:
  Installed: 2.5.0+dfsg-1build3
  Candidate: 2.5.0+dfsg-1build3
  Version table:
 *** 2.5.0+dfsg-1build3 500
500 http://archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pymol 2.5.0+dfsg-1build3 [modified: usr/bin/pymol]
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 19 19:58:18 2024
ExecutablePath: /usr/bin/pymol
InstallationDate: Installed on 2023-07-25 (238 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterpreterPath: /usr/bin/dash
PackageArchitecture: all
SourcePackage: pymol
UpgradeStatus: Upgraded to mantic on 2023-10-29 (142 days ago)

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


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

** Attachment added: "Screenshot after a scroll event followed by selecting 
anything on the screen"
   
https://bugs.launchpad.net/bugs/2058425/+attachment/5757296/+files/Screenshot%20from%202024-03-19%2020-03-10.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058425

Title:
  pymol console does not scroll

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054343] Re: arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039 still open)

[Fabio Augusto Miranda Martins]

** Tags added: rls-ff-incoming rls-jj-incoming rls-mm-incoming rls-nn-
incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054343

Title:
  arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039
  still open)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2054343/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

[Fabio Augusto Miranda Martins]

It seems 0.142ubuntu19 would be exposed to the bug. To test whether or
not my use case would be affected by it, I've booted a Jammy instance
with initramfs-tools 0.142ubuntu19, and I can't hit the problem. It is
booting well through iscsi. My cmdline is as below, so it might not be
exposed to the issue (and hence, please ignore my comment above as a
valid test for the patch, given that I wasn't exposed to it to begin
with):

BOOT_IMAGE=/boot/vmlinuz-6.5.0-1018-oracle
root=UUID=2792ceda-655f-4995-bf29-6a714f9a200b ro console=tty1
console=ttyS0 nvme.shutdown_timeout=10 libiscsi.debug_libiscsi_eh=1
crash_kexec_post_notifiers

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187

Title:
  fails to configure BOOTIF when using iscsi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056354] Re: qat: Improve error/reset handling

[Ricardo Martins]

** Changed in: linux (Ubuntu Noble)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056354

Title:
  qat: Improve error/reset handling

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056460] [NEW] cloud-init in degraded state on Oracle instance with "Invalid network-config provided"

[Fabio Augusto Miranda Martins]

Public bug reported:

When booting a Noble Numbat (Ubuntu 24.04) instance on Oracle Cloud,
clout-init ends up in a degraded state reporting "Invalid network-config
provided". Details are displayed below:

ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init status -l
status: done
extended_status: degraded done
boot_status_code: enabled-by-generator
last_update: Thu, 07 Mar 2024 14:42:12 +
detail: DataSourceOracle
errors: []
recoverable_errors:
WARNING:
- Invalid network-config provided: Please run 'sudo cloud-init schema 
--system' to see the schema errors.

ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init schema --system
Found cloud-config data types: user-data, network-config

1. user-data at 
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/cloud-config.txt:
Empty 'cloud-config' found at 
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/cloud-config.txt.
 Nothing to validate.

2. network-config at 
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/network-config.json:
  Invalid network-config 
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/network-config.json
  Error: Cloud config schema errors: config.0.subnets.0: Additional properties 
are not allowed ('broadcast' was unexpected)

Error: Invalid schema: network-config

ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo jq . 
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/network-config.json
{
  "config": [
{
  "mac_address": "b8:3f:d2:c3:fd:7c",
  "name": "ens300f0np0",
  "subnets": [
{
  "broadcast": "10.0.0.255",
  "control": "manual",
  "dns_nameservers": [
"169.254.169.254"
  ],
  "gateway": "10.0.0.1",
  "netmask": "255.255.255.0",
  "type": "dhcp"
}
  ],
  "type": "physical"
}
  ],
  "version": 1
}

ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init --version
/usr/bin/cloud-init 24.1-0ubuntu1

Attaching the logs.

** Affects: cloud-init (Ubuntu)
 Importance: High
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056460

Title:
  cloud-init in degraded state on Oracle instance with "Invalid network-
  config provided"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056460] Re: cloud-init in degraded state on Oracle instance with "Invalid network-config provided"

[Fabio Augusto Miranda Martins]

** Attachment added: "cloud-init.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+attachment/5753817/+files/cloud-init.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056460

Title:
  cloud-init in degraded state on Oracle instance with "Invalid network-
  config provided"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

[Fabio Augusto Miranda Martins]

I've tested launching a Oracle Cloud baremetal instance (which boots
from iSCSI) using such patch, and all worked well:

https://pastebin.ubuntu.com/p/3cdFdYBVFG/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187

Title:
  fails to configure BOOTIF when using iscsi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056194] Re: Networking broken in early boot on Oracle Native instances

[Fabio Augusto Miranda Martins]

I've tested the patch and it fixes the issue. I can confirm the MTU
settings are now correct and curl works fine. I also confirmed it
allowed cloud-init to run and fully complete the boot process:

https://pastebin.ubuntu.com/p/KfcP7wmjjV/

There are no cloud-init errors:

https://pastebin.ubuntu.com/p/jtkTWkDGVN/
https://pastebin.ubuntu.com/p/vZSyTJ3RsH/

All I noticed was a delay / hang during dhcp probe, followed by a
timeout and it worked in the first retry:

https://pastebin.ubuntu.com/p/hXWKYCypXM/

Overall, everything worked well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056194

Title:
  Networking broken in early boot on Oracle Native instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2056194/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056194] Re: Networking broken in early boot on Oracle Native instances

[Fabio Augusto Miranda Martins]

Between initramfs-tools 0.142ubuntu8 and 0.142ubuntu9, we've Replaced
dhclient by dhcpcd (LP: #2024164).

When a DHCP server provides MTU settings to dhcpcd, it configures the
routes with the appropriate mtu value (due to "option interface_mtu" in
/etc/dhcpcd.conf), but it does not configure the MTU setting in the
interface. So, we end up having a mismatch between interface and route
MTU setting, as observed below:

root@(none):/# ip a
1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 02:00:17:05:ee:5a brd ff:ff:ff:ff:ff:ff
altname enp0s3
inet 10.0.0.21/24 brd 10.0.0.255 scope global dynamic noprefixroute ens3
   valid_lft 86048sec preferred_lft 75248sec
inet6 fe80::17ff:fe05:ee5a/64 scope link 
   valid_lft forever preferred_lft forever
root@(none):/# ip route show
default via 10.0.0.1 dev ens3 proto dhcp src 10.0.0.21 metric 1002 mtu 9000 
10.0.0.0/24 dev ens3 proto dhcp scope link src 10.0.0.21 metric 1002 mtu 9000 
169.254.0.0/16 dev ens3 proto dhcp scope link src 10.0.0.21 metric 1002 mtu 9000

If we go back to initramfs-tools 0.142ubuntu8 (and, consequently to
dhclient), the MTU settings will match:

root@(none):/# ip a
1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3:  mtu 9000 qdisc mq state UP group 
default qlen 1000
link/ether 02:00:17:05:ee:5a brd ff:ff:ff:ff:ff:ff
altname enp0s3
inet 10.0.0.21/24 brd 10.0.0.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::17ff:fe05:ee5a/64 scope link 
   valid_lft forever preferred_lft forever
root@(none):/# ip route show
default via 10.0.0.1 dev ens3 
10.0.0.0/24 dev ens3 proto kernel scope link src 10.0.0.21 
169.254.0.0/16 dev ens3 scope link 

Due to this mismatch when using dhcpcd, certain network activities might
fail. For example, in Oracle instances, a curl to the DataSource will
just hang:

curl --connect-timeout 10 --max-time 15 -H "Authorization: Bearer
Oracle" -L http://169.254.169.254/opc/v2/instance/

If you either reduce the route MTU setting down to 1500 OR increase the
interface MTU setting to 9000, curl works:

option 1 - Reduce route setting:

ip route delete 169.254.0.0/16 dev ens3 proto dhcp scope link src 10.0.0.21 
metric 1002 mtu 9000
ip route add 169.254.0.0/16 dev ens3 scope link

option 2 - Increase interface setting:

ip link set mtu 9000 ens3

The correct MTU setting here is 9000. When you fully boot the instance,
the MTU gets configured appropriately (outside of initramfs)

I also checked the Paravirtualized instances (uses virtio_net interfaces
instead of mlx5_core) and the mismatch is also there, but curl still
works, so the Paravirtualized instance is also exposed to the bug but
more resistant to it.

While investigating this, I noticed that in past releases of dhcpcd, we
had a hook 10-mtu, that would automatically configure the mtu setting
based on information it received from the dhcp server. This file was
removed by the following commit:

https://github.com/NetworkConfiguration/dhcpcd/commit/ca6cdf5847cda720b65793ea6827b1b373c62382

There are some discussion around why this was removed here:

https://github.com/NetworkConfiguration/dhcpcd/issues/67

Anyway, this causes such mismatch between interface and route settings,
which cause curl to the IMDS to hang and cloud-init to fail.

** Bug watch added: github.com/NetworkConfiguration/dhcpcd/issues #67
   https://github.com/NetworkConfiguration/dhcpcd/issues/67

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056194

Title:
  Networking broken in early boot on Oracle Native instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2056194/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily

[Thiago Martins]

Hi! I was `do-release-upgrade -d` an Ubuntu 22.04 to Ubuntu 24.04 to
test and got bitten by this bug too! lol

The command `/usr/lib/grub/grub-multi-install --target=x86_64-efi`
returns 10, causing `dpkg --configure grub-efi-amd64-signed` to fail.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055294

Title:
  /usr/lib/grub/grub-multi-install fails on noble-daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

** Description changed:

  The `systemd` service for starting the NBD Clients on boot isn't
  working.
  
  ### Steps to Reproduce:
  
  0. Install NBD
  
  -
  apt install nbd-server nbd-client
  -
  
- 
  1. Prepare an NBD server with a disk image to share. For instance:
  
  -
  truncate -s 1T /vol-0.img
  -
  
- 
- 2. Configure the NBD server by adding the following to 
`/etc/nbd-server/conf.d/exports.conf`:
+ 2. Configure the NBD server by adding the following to `/etc/nbd-
+ server/conf.d/exports.conf`:
  
  -
  [vol0]
  exportname = /vol-0.img
  -
- 
  
  3. Configuring the client connection in `/etc/nbdtab`:
  
  Contents of `/etc/nbdtab`:
  
  -
  nbd0 localhost vol0
  -
- 
  
  4. Enable it on `systemd`:
  
  -
  systemctl enable nbd@nbd0
  -
  
  Here's what I see:
  
  -
  # systemctl enable nbd@nbd0
  Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service 
→ /lib/systemd/system/nbd@.service.
  Unit /lib/systemd/system/nbd@.service is added as a dependency to a 
non-existent unit dev-nbd0.device.
  -
  
- 
  5. Add `nbd` auto-load to system'd boot:
  
  echo nbd > /etc/modules-load.d/nbd.conf
- 
  
  6. Reboot
  
  -
  sudo reboot
  -
  
- 
  7. The service not coming up on the system's boot. Look:
  
  After rebooting the system, the NBD clien for `nbd0` isn't running (but
  it's enabled on systemd).
  
  -
- root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
+ root@demo-nbd-test:~# systemctl status nbd@nbd0
  ○ nbd@nbd0.service - NBD client connection for nbd0
   Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
     Docs: man:nbd-client
  
- Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
+ Feb 21 22:54:22 demo-nbd-test systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
  -
  
  But if you try to start it again. It'll work:
  
  -
- root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0
- root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
+ root@demo-nbd-test:~# systemctl start nbd@nbd0
+ root@demo-nbd-test:~# systemctl status nbd@nbd0
  ● nbd@nbd0.service - NBD client connection for nbd0
   Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
     Docs: man:nbd-client
  Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
     Main PID: 1096 (code=exited, status=0/SUCCESS)
  CPU: 4ms
  
- Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client 
connection for nbd0...
- Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 
3145728MB
- Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0
- Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client 
connection for nbd0.
+ Feb 21 22:57:37 demo-nbd-test systemd[1]: Starting NBD client connection for 
nbd0...
+ Feb 21 22:57:37 demo-nbd-test nbd-client[1096]: Negotiation: ..size = 
3145728MB
+ Feb 21 22:57:37 demo-nbd-test nbd-client[1096]: Connected /dev/nbd0
+ Feb 21 22:57:37 demo-nbd-test systemd[1]: Finished NBD client connection for 
nbd0.
  -
  
  So this forces me to have the following `/etc/rc.local` file as a
  workaround:
  
  -
  #!/bin/bash
  sleep 6
  systemctl start nbd@nbd0
  -
  
  Make it executable:
  
  -
  chmod +x /etc/rc.local
  -
  
  Reboot again, it'll be started on next boot!
  
  I don't think that the `/etc/rc.local` should be part of this
  procedure...  =P
  
  NOTE: Don't need to run `update-initramfs -k all -u`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

** Description changed:

  The `systemd` service for starting the NBD Clients on boot isn't
  working.
  
  ### Steps to Reproduce:
  
  0. Install NBD
  
-```
-apt install nbd-server nbd-client
-```
+ -
+ apt install nbd-server nbd-client
+ -
+ 
  
  1. Prepare an NBD server with a disk image to share. For instance:
-```bash
-truncate -s 1T /vol-0.img
-```
+ 
+ -
+ truncate -s 1T /vol-0.img
+ -
+ 
  
  2. Configure the NBD server by adding the following to 
`/etc/nbd-server/conf.d/exports.conf`:
-```
-[vol0]
-exportname = /vol-0.img
-```
+ 
+ -
+ [vol0]
+ exportname = /vol-0.img
+ -
+ 
  
  3. Configuring the client connection in `/etc/nbdtab`:
  
  Contents of `/etc/nbdtab`:
  
-```
-nbd0 localhost vol0
-```
+ -
+ nbd0 localhost vol0
+ -
+ 
  
  4. Enable it on `systemd`:
  
-```bash
-systemctl enable nbd@nbd0
-```
+ -
+ systemctl enable nbd@nbd0
+ -
  
  Here's what I see:
  
- ```
+ -
  # systemctl enable nbd@nbd0
  Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service 
→ /lib/systemd/system/nbd@.service.
  Unit /lib/systemd/system/nbd@.service is added as a dependency to a 
non-existent unit dev-nbd0.device.
- ```
+ -
+ 
  
  5. Add `nbd` auto-load to system'd boot:
  
- ```
- echo nbd > /etc/modules-load.d/nbd.conf
- ```
+ echo nbd > /etc/modules-load.d/nbd.conf
+ 
  
  6. Reboot
  
-```
-sudo reboot
-```
+ -
+ sudo reboot
+ -
+ 
  
  7. The service not coming up on the system's boot. Look:
  
  After rebooting the system, the NBD clien for `nbd0` isn't running (but
  it's enabled on systemd).
  
- ```
+ -
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ○ nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: inactive (dead)
-Docs: man:nbd-client
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: inactive (dead)
+    Docs: man:nbd-client
  
  Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
- ```
+ -
  
  But if you try to start it again. It'll work:
  
- ```
+ -
  root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ● nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
-Docs: man:nbd-client
- Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
-Main PID: 1096 (code=exited, status=0/SUCCESS)
- CPU: 4ms
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
+    Docs: man:nbd-client
+ Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
+    Main PID: 1096 (code=exited, status=0/SUCCESS)
+ CPU: 4ms
  
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client 
connection for nbd0...
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 
3145728MB
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client 
connection for nbd0.
- ```
+ -
  
  So this forces me to have the following `/etc/rc.local` file as a
  workaround:
  
- ```
+ -
  #!/bin/bash
  sleep 6
  systemctl start nbd@nbd0
- ```
+ -
  
  Make it executable:
  
- ```
+ -
  chmod +x /etc/rc.local
- ```
+ -
  
  Reboot again, it'll be started on next boot!
  
  I don't think that the `/etc/rc.local` should be part of this
  procedure...  =P
  
  NOTE: Don't need to run `update-initramfs -k all -u`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

I've updated the description to include all the steps necessary to
reproduce the issue on Ubuntu 22.04 (Cloud Image - Server Minimal
install).

This seems to be a `systemd` thing! lol

** Description changed:

  The `systemd` service for starting the NBD Clients on boot isn't
  working.
  
  ### Steps to Reproduce:
+ 
+ 0. Install NBD
+ 
+```
+apt install nbd-server nbd-client
+```
  
  1. Prepare an NBD server with a disk image to share. For instance:
 ```bash
 truncate -s 1T /vol-0.img
 ```
  
  2. Configure the NBD server by adding the following to 
`/etc/nbd-server/conf.d/exports.conf`:
 ```
 [vol0]
 exportname = /vol-0.img
 ```
  
  3. Configuring the client connection in `/etc/nbdtab`:
  
  Contents of `/etc/nbdtab`:
  
 ```
 nbd0 localhost vol0
 ```
  
  4. Enable it on `systemd`:
  
 ```bash
 systemctl enable nbd@nbd0
 ```
  
- 5. The service not coming up on the system's boot. Look:
+ Here's what I see:
+ 
+ ```
+ # systemctl enable nbd@nbd0
+ Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service 
→ /lib/systemd/system/nbd@.service.
+ Unit /lib/systemd/system/nbd@.service is added as a dependency to a 
non-existent unit dev-nbd0.device.
+ ```
+ 
+ 5. Add `nbd` auto-load to system'd boot:
+ 
+ ```
+ echo nbd > /etc/modules-load.d/nbd.conf
+ ```
+ 
+ 6. Reboot
+ 
+```
+sudo reboot
+```
+ 
+ 7. The service not coming up on the system's boot. Look:
  
  After rebooting the system, the NBD clien for `nbd0` isn't running (but
  it's enabled on systemd).
  
  ```
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ○ nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: inactive (dead)
-    Docs: man:nbd-client
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: inactive (dead)
+Docs: man:nbd-client
  
  Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
  ```
  
- Then, after a restart, it works:
+ But if you try to start it again. It'll work:
  
  ```
- root@cephao-1-ceph-osd-1:~# systemctl restart nbd@nbd0
+ root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ● nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
-    Docs: man:nbd-client
- Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
-    Main PID: 1096 (code=exited, status=0/SUCCESS)
- CPU: 4ms
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
+Docs: man:nbd-client
+ Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
+Main PID: 1096 (code=exited, status=0/SUCCESS)
+ CPU: 4ms
  
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client 
connection for nbd0...
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 
3145728MB
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client 
connection for nbd0.
  ```
  
  So this forces me to have the following `/etc/rc.local` file as a
  workaround:
  
  ```
  #!/bin/bash
- systemctl restart nbd@nbd0
+ sleep 6
+ systemctl start nbd@nbd0
  ```
  
- If this is not the proper way of automatically starting a `nbd0` NBD
- client, please, let me know! Perhaps documentation should be more clear.
+ Make it executable:
  
- Interesting reference:
- https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054470
+ ```
+ chmod +x /etc/rc.local
+ ```
+ 
+ Reboot again, it'll be started on next boot!
+ 
+ I don't think that the `/etc/rc.local` should be part of this
+ procedure...  =P
+ 
+ NOTE: Don't need to run `update-initramfs -k all -u`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04

[Thiago Martins]

Oops, wrong bug report. Ignore my previous message.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054470

Title:
  NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and
  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

I'm testing on Ubuntu 22.04.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

Hi Mitchell,

No worries at all!

I forgot to mention another step I took:

```
echo nbd > /etc/modules-load.d/nbd.conf
```

Otherwise it won't load the module on boot.

Perhaps there's also a need to `update-initramfs -k all -u`, not 100%
sure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04

[Thiago Martins]

Hi Sergio,

Thank you for taking the taking to troubleshoot this!

I forgot to mention another step I took:

```
echo nbd > /etc/modules-load.d/nbd.conf
```

Perhaps there's also a need to `update-initramfs -k all -u`?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054470

Title:
  NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and
  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054856] [NEW] Icon theme is reset on dark/light theme switch

[Junior Martins]

Public bug reported:

### Affected version
GNOME Shell 45.2 on Ubuntu 23.10 (Wayland)

### Bug summary

When you switch between dark and light mode the icon theme is reset.
This also affects other theming options, such as the "Legacy
applications" theme option in Gnome Tweaks. I suspect that it also
affects the primary color settings, since I remember having it changed
to the default orange after switching from light to dark some days ago,
but I don't remember what setting I changed before this.

### Steps to reproduce

1. On Gnome Tweaks > Appearance, change the icon theme (I used Papyrus dark)
2. On the quick toggles, switch between dark and light mode
3. Switch again between dark and light mode

### What happened

The icon theme is changed to "Yaru-blue" and then to "Yaru-blue-dark"

### What did you expect to happen

No change to my icon theme, or at least use its light variant.

### Relevant info

Some `gsettings` options:

```bash
# After changing the icon theme
org.gnome.desktop.interface color-scheme 'prefer-dark'
org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark'
org.gnome.desktop.interface icon-theme 'Papirus-Dark'

# After switching to light mode
org.gnome.desktop.interface color-scheme 'default'
org.gnome.desktop.interface gtk-theme 'Yaru-blue'
org.gnome.desktop.interface icon-theme 'Yaru-blue'

# After switching to dark mode again
org.gnome.desktop.interface color-scheme 'prefer-dark'
org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark'
org.gnome.desktop.interface icon-theme 'Yaru-blue-dark'
```

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.2-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 21:57:38 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-07-25 (213 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
RelatedPackageVersions: mutter-common 45.2-0ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-10-29 (117 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054856

Title:
  Icon theme is reset on dark/light theme switch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054856/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977633] [NEW] iotop raises "UnboundLocalError: local variable 'pgpgin' referenced before assignment" in a ProxMox KVM

[Gilberto "Kowalsky" Martins]

Public bug reported:

Hello.

iotop just does not work in my ProxMox KVM boxes:
 $ iotop
 Traceback (most recent call last):
   File "/usr/sbin/iotop", line 10, in 
 from iotop.ui import main
   File "/usr/lib/python3/dist-packages/iotop/ui.py", line 46, in 
 from iotop.data import find_uids, TaskStatsNetlink, ProcessList, Stats
   File "/usr/lib/python3/dist-packages/iotop/data.py", line 51, in 
 vmstat_f = VmStat()
   File "/usr/lib/python3/dist-packages/iotop/vmstat.py", line 23, in __init__
 self.vmstat = self.read()
   File "/usr/lib/python3/dist-packages/iotop/vmstat.py", line 40, in read
 return pgpgin, pgpgout
 UnboundLocalError: local variable 'pgpgin' referenced before assignment


PVE Version:
 $ pveversion
 proxmox-ve: 6.4-1 (running kernel: 5.4.143-1-pve)

Ubuntu version:
 $ lsb_release -a
 No LSB modules are available.
 Distributor ID: Ubuntu
 Description:Ubuntu 20.04.4 LTS
 Release:20.04
 Codename:   focal

Kernel version:
 $ uname -a
 Linux prd1frm201 5.4.0-1065-kvm #68-Ubuntu SMP Wed May 18 23:28:33 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux


iotop version:
 $ sudo iotop -h
 Traceback (most recent call last):
   File "/usr/sbin/iotop", line 10, in 
 from iotop.ui import main
   File "/usr/lib/python3/dist-packages/iotop/ui.py", line 46, in 
 from iotop.data import find_uids, TaskStatsNetlink, ProcessList, Stats
   File "/usr/lib/python3/dist-packages/iotop/data.py", line 51, in 
 vmstat_f = VmStat()
   File "/usr/lib/python3/dist-packages/iotop/vmstat.py", line 23, in __init__
 self.vmstat = self.read()
   File "/usr/lib/python3/dist-packages/iotop/vmstat.py", line 40, in read
 return pgpgin, pgpgout
 UnboundLocalError: local variable 'pgpgin' referenced before assignment

 $ sudo apt show iotop |& grep -i version
 Version: 0.6-24-g733f3f8-1

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977633

Title:
  iotop raises "UnboundLocalError: local variable 'pgpgin' referenced
  before assignment" in a ProxMox KVM

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04

[Fabio Augusto Miranda Martins]

Hi Brian,

Thanks for that. I've tested and validated that ec2-instance-connect
from jammy-proposed fixes the issue. Here are the evidences:

https://pastebin.ubuntu.com/p/dPD6vyS6g4/

Cheers,
Fabio Martins

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973114

Title:
   Key trust verification fails on Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04

[Fabio Augusto Miranda Martins]

I also tested with mssh to make it works well:

When running ec2-instance-connect 1.1.14-0ubuntu1 (from Jammy) and
trying to connect with mssh:

fabio@fabio-canonical:~/.aws$ mssh ubuntu@i-0af3232b4fb6ed642
ubuntu@3.91.56.142: Permission denied (publickey).

Due to the bug, we can see the key being pushed, but then the client
denying the connection:

https://pastebin.ubuntu.com/p/7StqsfQdJp/

Back in the instance, I've changed the sources.list to point to kinetic
repos and upgraded ec2-instance-connect to kinetic's version:

ubuntu@ip-10-0-1-226:~$ sudo apt-cache policy ec2-instance-connect
ec2-instance-connect:
  Installed: 1.1.14-0ubuntu2
  Candidate: 1.1.14-0ubuntu2
  Version table:
 *** 1.1.14-0ubuntu2 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu kinetic/main amd64 
Packages
100 /var/lib/dpkg/status


And now mssh works fine:

fabio@fabio-canonical:~/.aws$ mssh ubuntu@i-0af3232b4fb6ed642
Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1004-aws x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  System information as of Fri May 13 14:16:20 UTC 2022

  System load:  0.2421875 Processes: 128
  Usage of /:   21.1% of 7.58GB   Users logged in:   1
  Memory usage: 1%IPv4 address for eth0: 10.0.1.226
  Swap usage:   0%


74 updates can be applied immediately.
To see these additional updates run: apt list --upgradable


Last login: Fri May 13 13:47:05 2022 from 189.19.160.174
ubuntu@ip-10-0-1-226:~$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973114

Title:
   Key trust verification fails on Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

I've also updated the [Test Plan] section of the bug description

** Description changed:

  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.
  
  [Test Plan]
+ 
+ - Check that the ipconfig utility is able to obtain an IP through dhcp:
+ 
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig ens9; date
+ 
+ - Check if it respects the timeout (i.e. 2 seconds in the example
+ below):
+ 
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
+ 
+ - The original issue is that timeout is being ignored when not receiving
+ any reply from a DHCP Server, so for this test you have to stop your
+ DHCP Server (i.e. dnsmasq) and then test the timeouts:
+ 
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
+ 
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date
+ 
+ Make sure it times out respectivelly in 2 and 5 seconds.
  
  [racb: pending agreement with the SRU team; please see comment 37]
  
  Any situation where ipconfig encounters an error sending the DHCP
  packet, it will automatically set a delay of 10 seconds, which could be
  longer than the user-specified timeout. It can be reproduced by creating
  a dummy interface and attempting to run ipconfig on it with a timeout
  value of less than 10:
  
  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021
  
  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.
  
  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).
  
  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.
  
  [Original Description]
  
  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.
  
  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again later"
  at time equal now + 10 seconds by setting
  
  s->expire = now + 10;
  
  This can happen at any time during the main event loop, which can end up
  extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".
  
  I believe a patch like the following is needed to avoid this problem:
  
  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)
  
  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }
  
  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:
  
  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }
  
  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:
  
  IP-Config: no response after 2 secs - giving up
  
  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.
  
  The suggested code-change ensures that the timeout that is actually used
  never exceeds the user-specified timeout.
  
  [ Regression potential ]
  
  This change ensures that user-specified timeouts are never exceeded, which is 
a problem that appears to happen only in case of interface errors.
  It may be that someone is relying on current behaviour where they receive 
DHCP offers after their specified timeout (but within the 10-second error 
timeout). However, 1) that is buggy behaviour and should be exposed. Such a 
user would need to update their specified timeout to make it long enough to 
receive the DHCP offer (setting the timeout to 10 would keep the existing 
behaviour). 2) I think it is unlikely that such a scenario exists at all. The 
10-second timeout problem happens when 

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

Hello Robie,

I've validated that the package from -proposed works well, testing in my
VM based environment. I haven't tested it on Oracle bare metal (where
the original issue happened) as that is a type of instance hard to get
access to. Given that the test packages had proven to fix the original
problem that we were targetting to address, I believe the package from
-proposed should also work well. Let me know if it is necessary to also
test that it addresses the original issue with Oracle BM host and I'll
get access to one and validate.

Regarding your question below:

> ...would it be practical and/or useful to verify that, with a timeout
of 2s, a DHCP reply sent after 1.5s works, but a DHCP reply sent after
2.5s does not?

That has been addressed in comment #30 (and now also in #39 with the
package from -proposed).

Regarding your question if upstream had accepted the patch, I would have
to defer that to Khaled, but I also agree that it seems a deliberate
upstream design decision not to accept it.

Regarding your comment below:

> In Ubuntu, we might decide to maintain the patch as a delta but then
drop that delta in subsequent releases when we no longer need that
functionality.

That is indeed just needed for Bionic. To confirm/clarify my
understanding, if this moves to -updates, in theory this is not going to
be reverted (from Bionic) in the future, right? Once it lands there, it
is expected that any newer klibc-utils packages that gets released to
Bionic will continue to carry this patch?

Thank you in advance!

Regards,
Fabio Martins

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

I've tested the package from -proposed and I can confirm it fixes the
problem:

Installed from -proposed:

root@ubuntu:~# apt-cache policy klibc-utils
klibc-utils:
  Installed: 2.0.4-9ubuntu2.2
  Candidate: 2.0.4-9ubuntu2.18.04.1
  Version table:
 2.0.4-9ubuntu2.18.04.1 500
500 http://ppa.launchpad.net/mfo/lp1947099/ubuntu bionic/main amd64 
Packages
 *** 2.0.4-9ubuntu2.2 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 2.0.4-9ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 2.0.4-9ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages


Working well without timeout:

root@ubuntu:~# ip l set dev ens9 down
root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig ens9; date
Thu May 12 12:54:48 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
IP-Config: ens9 complete (dhcp from 192.168.150.2):
 address: 192.168.150.105  broadcast: 192.168.150.255  netmask: 255.255.255.0   
 gateway: 192.168.150.1dns0 : 192.168.150.2dns1   : 0.0.0.0 
 domain : sts.lab 
 rootserver: 192.168.150.2 rootpath: 
 filename  : 
Thu May 12 12:55:01 UTC 2022


Timeout being honored:

root@ubuntu:~# ip l set dev ens9 down
root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
Thu May 12 12:55:44 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
Lowered timeout to match user request = (2 s) 
IP-Config: no response after 2 secs - giving up
Thu May 12 12:55:46 UTC 2022


Testing the original issue (timeout being ignored when not receiving any reply 
from a DHCP Server), which is now also getting honored:

root@ubuntu:~# ip l set dev ens9 down
root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
Thu May 12 12:56:32 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
Lowered timeout to match user request = (2 s) 
IP-Config: no response after 2 secs - giving up
Thu May 12 12:56:34 UTC 2022

root@ubuntu:~# ip l set dev ens9 down
root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date
Thu May 12 12:56:43 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
Lowered timeout to match user request = (5 s) 
IP-Config: no response after 5 secs - giving up
Thu May 12 12:56:48 UTC 2022

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Vitor Martins]

Comment #51 fixed all my problems.
unsafe legacy renegotiation disabled & SSL_connect error:0A0C0103:SSL 
routines::internal error

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

Should this bug be changed  to Fix Committed at this point?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Vitor Martins]

Also tried seclevel=0 and go no success.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Vitor Martins]

I tried also #22 + #36 + reboot, still having "0A0C0103:SSL
routines::internal error"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Vitor Martins]

Can someone explain how to fix "0A0C0103:SSL routines::internal error" ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

I've tested the new patch from ppa:mfo/lp1947099v2 and I can confirm it
resolves the problem:

- Without the patch:

https://pastebin.ubuntu.com/p/RksNcBGSzn/


It took 396,940865−220,447147 = 176,493718 seconds in the IP-Config section. 
Total boot time: 


ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time
Startup finished in 4min 1.355s (firmware) + 2min 24.433s (loader) + 6min 
8.464s (kernel) + 41.466s (userspace) = 13min 15.719s
graphical.target reached after 41.068s in userspace


- With the patch:

https://pastebin.ubuntu.com/p/46nVYCYyDZ/

It took 246,556749−212,019368 = 34,537381 seconds in the IP-Config
section. Total boot time:

ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time
Startup finished in 4min 1.246s (firmware) + 2min 24.170s (loader) + 3min 
42.915s (kernel) + 39.010s (userspace) = 10min 47.343s
graphical.target reached after 38.634s in userspace


ubuntu@gpu48-ubuntu18:~$ sudo apt-cache policy klibc-utils
klibc-utils:
  Installed: 2.0.4-9ubuntu2.18.04.1
  Candidate: 2.0.4-9ubuntu2.18.04.1
  Version table:
 *** 2.0.4-9ubuntu2.18.04.1 500
500 http://ppa.launchpad.net/mfo/lp1947099v2/ubuntu bionic/main amd64 
Packages
100 /var/lib/dpkg/status
 2.0.4-9ubuntu2.1 500
500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu 
bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 2.0.4-9ubuntu2 500
500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu bionic/main 
amd64 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

Thank you, Mauricio, for the build process details and for adding the
update here. I'm including some evidence of my tests showing that the
patch you suggested did work well:

Details of the build process:

https://pastebin.ubuntu.com/p/dmVWH2fxpy/

Test package installed:

https://pastebin.ubuntu.com/p/qxyWBGrm3P/

Working well without specifying a timeout:

https://pastebin.ubuntu.com/p/byftnFk33C/

Timeout is also being honored:

https://pastebin.ubuntu.com/p/spFsTRhXTz/


Testing the original issue (timeout being ignored when not receiving any reply 
from a DHCP Server), which is now also getting honored:

https://pastebin.ubuntu.com/p/KHVRj7BdRw/


I'm working to get access to another instance to test that the boot time 
optimiizations are still fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

@Łukasz / @Robie, do you think the above comments are enough to proceed
with this SRU?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

I've tested the klibc-utils patch using Mauricio's ppa:

sudo add-apt-repository ppa:mfo/lp1947099
sudo apt install klibc-utils
sudo update-initramfs -u -k all

And I can confirm that it does improve the boot time in more than 3
minutes, without causing any noticeable issues.

- Without the patch:

https://pastebin.ubuntu.com/p/6M7M2FfCGQ/

root@ubuntu1804:~# sudo systemd-analyze time
Startup finished in 4min 2.098s (firmware) + 2min 23.684s (loader) + 6min 226ms 
(kernel) + 38.766s (userspace) = 13min 4.776s
graphical.target reached after 38.374s in userspace


We can see it spent 6min 226ms in kernel, and looking through the serial 
console (or dmesg) it was running the ipconfig commands for each of the 
Mellanox NICs from 211.972259 up to 386.155116 = 174.182857 seconds


- With the patch:

https://pastebin.ubuntu.com/p/JxDs8WPqc4/

root@ubuntu1804:~# sudo systemd-analyze time
Startup finished in 4min 890ms (firmware) + 2min 23.278s (loader) + 3min 
46.413s (kernel) + 40.734s (userspace) = 10min 51.317s
graphical.target reached after 40.354s in userspace

We can see the kernel time decreased to a bit more than 3 minutes and we
spent only 41 seconds (as opposed to 174 seconds) in the ipconfig
commands:

210.675050 to 252.432441 = 41.757391 seconds

That definitely has helped to resolve the issue we are chasing here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

I tried using klibc-utils from the ppa (containing the patch):

root@ubuntu:~# sudo apt-cache policy klibc-utils
klibc-utils:
  Installed: 2.0.4-9ubuntu2.18.04.1
  Candidate: 2.0.4-9ubuntu2.18.04.1
  Version table:
 *** 2.0.4-9ubuntu2.18.04.1 500
500 http://ppa.launchpad.net/mfo/lp1947099/ubuntu bionic/main amd64 
Packages
100 /var/lib/dpkg/status
 2.0.4-9ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

[1] But now when I try to obtain an IP using dhcp without specifying any
timeout, it dumps lots of "Lowered timeout to match user request"
messages. Is that expected?

https://pastebin.ubuntu.com/p/5Tpc5Rwdkq/

[2] Other than that, it worked well. We can see from the pastebin below
that the timeout is getting respected:

https://pastebin.ubuntu.com/p/TJbCzx7hFC/


[3] And also the main issue was the timeout being ignored when not receiving 
any reply from a DHCP Server, which is now also getting honored:

https://pastebin.ubuntu.com/p/BvKk6fJJDc/

I will try to test this package in a OCI BM.GPU4.8 instance to see the
improvements with the main optimization, but it would be good to get
clarification on [1]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944574] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary

[Fabio Augusto Miranda Martins]

I believe the "EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned
on 64k boundary" that was reported on this bug is not what is preventing
the VM from booting. If you look into the full log you provided, that
message is logged both on the boot that succeeded and in the one that
got stuck.

I believe whatever was done in the VM in between these reboots, might
have caused the problem you are observing.

There's also a known problem on linux-oracle kernel that prevents you
from seeing the serial console. That is being fixed for Focal images on
the linux-oracle 5.13.0.1023.28~20.04.1 kernel, which is currenlty in
focal-proposed. If this is something you can reproduce with Focal
images, using the kernel from proposed might help you see what is really
preventing the VM from starting.

We'll review the 'kernel image not aligned on 64k boundary' error anyway
to assess what might be causing it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944574

Title:
  EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k
  boundary

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

I've setup a Lab with dnsmasq acting as DHCP Server, which I can use the
dhcp-reply-delay option to introduce a delay between the DHCPDISCOVER
and DHCPOFFER, as in the example below:

Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPDISCOVER(ens3) 
52:54:00:d7:10:13 
Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: 4195928115 reply delay: 3
Mar 30 18:26:37 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPOFFER(ens3) 
192.168.150.119 52:54:00:d7:10:13 

Just minor note that the delay only happens between DHCPDISCOVER and
DHCPOFFER, but not between DHCPREQUEST and DHCPACK:

Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPREQUEST(ens3) 
192.168.150.119 52:54:00:d7:10:13 
Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPACK(ens3) 192.168.150.119 
52:54:00:d7:10:13 ubuntu

So, if this is a new interface (new mac) looking for an IP, the delay
will be added, but if this is an interface which was previously
configured and is asking to re-use the same IP (DHCPREQUEST), there
won't be any delays.

I believe this Lab will help reproducing the issue with and without the
proposed patch.

1. In a ideal scenario, where no delays were added (dhcp-reply-delay is
commented out), ipconfig will take approximately to do its job: it sends
a DHCPREQUEST, then DHCPDISCOVER and then another DHCPREQUEST in this
process:

- From the ipconfig perspective:

root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date
Wed Mar 30 19:25:44 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
IP-Config: ens9 complete (dhcp from 192.168.150.2):
 address: 192.168.150.105  broadcast: 192.168.150.255  netmask: 255.255.255.0   
 gateway: 192.168.150.1dns0 : 192.168.150.2dns1   : 0.0.0.0 
 domain : sts.lab 
 rootserver: 192.168.150.2 rootpath: 
 filename  : 
Wed Mar 30 19:25:54 UTC 2022

- From the dhcp server perspective:

Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e ubuntu
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e 


2. Adding a 5 seconds delay in dnsmasq (dhcp-reply-delay=5) and without 
enforcing a timeout in ipconfig:

- From ipconfig perspective:

root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date
Wed Mar 30 19:34:09 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
IP-Config: ens9 complete (dhcp from 192.168.150.2):
 address: 192.168.150.105  broadcast: 192.168.150.255  netmask: 255.255.255.0   
 gateway: 192.168.150.1dns0 : 192.168.150.2dns1   : 0.0.0.0 
 domain : sts.lab 
 rootserver: 192.168.150.2 rootpath: 
 filename  : 
Wed Mar 30 19:34:27 UTC 2022


- From the dhcpserver perspective:

Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e ubuntu
Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5
Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5
Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e 

It takes 18 seconds for the process to complete, as dnsmasq adds 3x 5
seconds delay in the process


3. Using the -t to specify a 15 seconds timeout (when the actual process takes 
18 seconds):

- From the ipconfig perspective:

root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig -t 15 ens9; date
Wed Mar 30 19:37:11 UTC 

[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Fabio Augusto Miranda Martins]

Hi Robie,

The user story here is about improving the time it takes to boot a
Bionic instance on Oracle Cloud in a specific bare metal shape, called
BM.GPU4.8. This is a pretty large instance, with 18x Ethernet controller
[0200]: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
[15b3:1019]:

https://www.oracle.com/uk/cloud/compute/gpu.html

Comparing the time it takes to boot Bionic with a CentOS instance we can
see a big delta both in kernel and userspace:

CentOS:
Startup finished in 4min 3.548s (firmware) + 2min 23.525s (loader) + 3min 
17.984s (kernel) + 1min 37.825s (initrd) + 38.723s (userspace) = 12min 1.608s
multi-user.target reached after 38.714s in userspace

Ubuntu:
Startup finished in 4min 621ms (firmware) + 2min 23.174s (loader) + 7min 
34.767s (kernel) + 5min 48.219s (userspace) = 19min 46.782s
graphical.target reached after 5min 47.854s in userspace

The userspace difference is a cloud-init problem that is being handled
by other launchpad bugs. Here we are trying to focus on the kernel
difference, which further was narrowed down to be related to klibc and
it is what we are trying to address with this bug. Some details:

Looking into details, here are the dmesg output from CentOS and Ubuntu,
for kernel comparison:

Ubuntu: https://pastebin.canonical.com/p/X7GFVjdV3b/
CentOS: https://pastebin.canonical.com/p/gNhFwJjyjw/

Looking there, one area that looks promising is around mlx5_core driver,
where Ubuntu spends 218 seconds, while CentOS spends 44 seconds

Khalid did a nice job investigating and found that the problem came from
ipconfig from initramfs. Here are the details:


The delay from the kernel side is due to the fact that every interface (18 in 
total) takes over 10 seconds each to initialize.

The interfaces are brought up and used for DHCP as part of the iscsi
initialization, during the initramfs stage. Specifically the script
```/usr/share/initramfs-tools/scripts/local-top/iscsi``` which is
included in the initramfs and is installed as part of open-iscsi

To initialize the network interfaces this script calls other helper
functions that are part of the initramfs, specifically
"configure_networking" in ```/usr/share/initramfs-
tools/scripts/functions``` which is installed as part of initramfs-
tools-core.

The configure_networking function initializes networking by looping over
all interfaces and issuing this call:

```
ipconfig -t 2 
```

where it is calling the ipconfig utility (part of klibc-utils) which
also gets bundled in the initramfs. The -t 2 specifies a timeout of 2
seconds.


This ipconfig tool attempts to perform DHCP on the given interface, within the 
specified timeout (always 2 seconds for each interface)

Normally, ipconfig does not perform only one DHCP attempt - it performs
multiple DHCP attempts, each attempt waiting for an exponentially
increasing amount of time (1s, 2s, 4s, ..etc) up until the total amount
of time has passed that is equal the user-specified timeout (2 in this
case, so it should wait 1 second, followed by 1 second, for a total of 2
seconds).

However, it appears ipconfig has a bug. In case it encounters an error
sending a DHCP request on an interface (which is the case for 17 out of
the 18 interfaces on this instance), it attempts to "try again later"
and sets a timer of 10 seconds for the next attempt - ignoring
completely the user-specified value (2 seconds). I believe this is a bug
in ipconfig and have a working fix to limit the delay to the user-
specified timeout so each interface actually takes a maximum of 2
seconds for initialization, even in error cases.

The above is for bionic, which has the reported problem. In focal, even
though the kernel and klibc-utils are identical to bionic, the version
of initramfs-tools-core is different. In the focal version,
configure_networking() has been reworked to avoid using ipconfig
entirely. Instead, it uses ```dhclient```. And instead of doing that 18
times, dhclient is called only once with the full list of interfaces, as
such:

```
dhclient -v -1 -cf /etc/dhcp/dhclient.conf.2 -pf /tmp/dhclient.pid.2 -4 
enp12s0f0np0 enp12s0f1np1 enp138s0f0np0 enp138s0f1np1 enp148s0f0np0 
enp148s0f1np1 enp195s0f0np0 enp195s0f1np1 enp209s0f0np0 enp209s0f1np1 
enp22s0f0np0 enp22s0f1np1 enp45s0f0np0 enp45s0f1np1 enp72s0f0np0 enp72s0f1np1 
enp76s0f0np0 enp76s0f1np1
```

dhclient does DHCP on all those interfaces at the same time,
asynchronously, and it daemonizes (goes in the background) as soon as it
gets a DHCP response which happens relatively quickly (on interface
enp45s0f0np0 usually) and so the boot-up continues *much* faster
compared to bionic (180+ seconds are reduced to just 5-10 seconds).

I'm sure there might be other use cases, but this is what we have been
reported and are trying to work with. I hope this helps clarifying.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not 

[Bug 1946211] Re: [SRU] "radosgw-admin bucket limit check" has duplicate entries if bucket count exceeds 1000 (max_entries)

[Fabio Augusto Miranda Martins]

Hi,

I've verified that the package from ussuri-proposed fixes the issue.

Without the patch:

https://pastebin.ubuntu.com/p/PFrkX7BkCT/

With the patch:

https://pastebin.ubuntu.com/p/yytzD3sjV9/

Cheers and thank you for fixing it.

- Fabio

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946211

Title:
  [SRU] "radosgw-admin bucket limit check" has duplicate entries if
  bucket count exceeds 1000 (max_entries)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1946211/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946211] Re: [SRU] "radosgw-admin bucket limit check" has duplicate entries if bucket count exceeds 1000 (max_entries)

[Fabio Augusto Miranda Martins]

Hi, I can confirm that the packages from -propose will resolve the
issue. See evidences bellow:

- While using 15.2.12, we can see the bug:

https://pastebin.ubuntu.com/p/jYg8x4Q7vR/


- After installing 15.2.14 from -proposed, the bug is resolved:

https://pastebin.ubuntu.com/p/mKFrTjddX7/

Thank you for your help addressing this issue.

Regards,
Fabio Martins

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946211

Title:
  [SRU] "radosgw-admin bucket limit check" has duplicate entries if
  bucket count exceeds 1000 (max_entries)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1946211/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1940759] Re: [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay between on and off modes

[Junior Martins]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1948556] [NEW] calendar has low contrast in both default themes

[Junior Martins]

Public bug reported:

Both default dark and light themes of calendar have very low contrast
between event and text colour of events. Text colour is always some kind
of light grey (dark and light modes) or dark grey (light mode only).

On dark theme, setting an account calendar to bright colours doesn't
affect the text colour (light text on light background), while the
opposite doesn't happen on light theme (text changes colour
automatically to dark or light according to background colour).

Also, the colours themselves are differently applied than expected:
changing an account colour to white while in dark mode changes it to a
whitish purple instead of actual white, while changing it to black on
light mode changes it to dark grey.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-calendar 41.0-1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 23 19:10:08 2021
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2021-04-20 (185 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to impish on 2021-10-23 (0 days ago)

** Affects: gnome-calendar (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "Screenshots of light and dark mode with account color set 
to black or white"
   
https://bugs.launchpad.net/bugs/1948556/+attachment/5535476/+files/screenshots.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948556

Title:
  calendar has low contrast in both default themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1948556/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944763] Re: sed temp file appears in nautilus but not in ls -a

[Junior Martins]

I'm using GNOME 3.38.4 and I just tried mv, touch, mkdir, rmdir and cp,
and Nautilus updated instantly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944763

Title:
  sed temp file appears in nautilus but not in ls -a

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944763] Re: sed temp file appears in nautilus but not in ls -a

[Junior Martins]

I used "gio monitor ." at the directory. I don't know what my filesystem
is, but in AskUbuntu it was mentioned that I could use "df -T", I hope
this helps.

DIRNAME is the absolute path of the directory (I can't show it, it has upper 
and lowercase characters and also spaces, it that's relevant), and it seemed to 
get worse, since now both 
sedFJdiNs and sedoH8a25 showed in Nautilus. They disappeared when I pressed F5 
about a minute later.


After  sed -i 's/CAD/cad/g' dados_snps_AMR.tsv 

.: DIRNAME/sedFJdiNs: created
.: DIRNAME/sedFJdiNs: changes done
.: DIRNAME/sedFJdiNs: attributes changed
.: DIRNAME/sedFJdiNs: changed
.: DIRNAME/sedFJdiNs: changes done
.: DIRNAME/sedFJdiNs: renamed to DIRNAME/dados_snps_AMR.tsv

After sed -i 's/cad/CAD/g' dados_snps_AMR.tsv

.: DIRNAME/sedoH8a25: created
.: DIRNAME/sedoH8a25: changes done
.: DIRNAME/sedoH8a25: attributes changed
.: DIRNAME/sedoH8a25: changed
.: DIRNAME/sedoH8a25: changes done
.: DIRNAME/sedoH8a25: renamed to DIRNAME/dados_snps_AMR.tsv

>>>df -T
Sist. Arq. Tipo  Blocos de 1K Usado Disponível Uso% Montado em
tmpfs  tmpfs  1625208  20321623176   1% /run
/dev/sda2  ext4 459924552 236713100  199778800  55% /
tmpfs  tmpfs  8126032 494088076624   1% /dev/shm
tmpfs  tmpfs 5120 4   5116   1% /run/lock
tmpfs  tmpfs 4096 0   4096   0% /sys/fs/cgroup
/dev/sda1  vfat523248  8332 514916   2% /boot/efi
tmpfs  tmpfs  1625204   9401624264   1% /run/user/1000

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944763

Title:
  sed temp file appears in nautilus but not in ls -a

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944763] [NEW] sed temp file appears in nautilus but not in ls -a

[Junior Martins]

Public bug reported:

**Expected behaviour**:
Temp files created by sed should disappear from Nautilus after automatic 
deletion

**Observed behaviour**:
Temp files showed in Nautilus for some time.

**Description**:

After using:
sed -i 's/CAD/cad/g' FILENAME

The temp files created by sed (sed#) continued showing in Nautilus
for some minutes (they disappear if I close and reopen Nautilus), and I
could interact with them (see permissions, double click to open (which
errored out by not finding an app to open it), but couldn't change them
(move, change permissions, delete)

These temp files did not appear with ls -a.

The file is 3.6kb long.

The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but
only with: sed -i 's/CAD/cad/g' FILENAME

**Outputs**:

>>>df .
Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em
/dev/sda2 459924552 235486388  201005512  54% /

>>>lsb_release -rd:
Description:Ubuntu 21.04
Release:21.04

>>>apt-cache policy nautilus
nautilus:
  Instalado: 1:3.38.2-1ubuntu2
  Candidato: 1:3.38.2-1ubuntu2
  Tabela de versão:
 *** 1:3.38.2-1ubuntu2 500
500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:3.38.2-1ubuntu1 500
500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nautilus 1:3.38.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 23 15:51:04 2021
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'initial-size' b'(860, 495)'
 b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2021-04-20 (155 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SourcePackage: nautilus
UpgradeStatus: Upgraded to hirsute on 2021-06-08 (107 days ago)
usr_lib_nautilus:
 evince40.1-1
 file-roller   3.38.1-1
 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
 nautilus-share0.7.3-2ubuntu3

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


** Tags: amd64 apport-bug hirsute

** Description changed:

  **Expected behaviour**:
  Temp files created by sed should disappear from Nautilus after automatic 
deletion
  
  **Observed behaviour**:
  Temp files showed in Nautilus for some time.
  
  **Description**:
  
  After using:
  sed -i 's/CAD/cad/g' FILENAME
  
  The temp files created by sed (sed#) continued showing in Nautilus
- for some time (about 20m), and I could interact with them (see
- permissions, double click to open (which errored out by not finding an
- app to open it), but couldn't change them (move, change permissions,
- delete)
+ for some minutes (they disappear if I close and reopen Nautilus), and I
+ could interact with them (see permissions, double click to open (which
+ errored out by not finding an app to open it), but couldn't change them
+ (move, change permissions, delete)
  
  These temp files did not appear with ls -a.
  
  The file is 3.6kb long.
  
  The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but
  only with: sed -i 's/CAD/cad/g' FILENAME
  
  **Outputs**:
  
  >>>df .
  Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em
  /dev/sda2 459924552 235486388  201005512  54% /
  
  >>>lsb_release -rd:
  Description:  Ubuntu 21.04
  Release:  21.04
  
  >>>apt-cache policy nautilus
  nautilus:
-   Instalado: 1:3.38.2-1ubuntu2
-   Candidato: 1:3.38.2-1ubuntu2
-   Tabela de versão:
-  *** 1:3.38.2-1ubuntu2 500
- 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages
- 100 /var/lib/dpkg/status
-  1:3.38.2-1ubuntu1 500
- 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages
+   Instalado: 1:3.38.2-1ubuntu2
+   Candidato: 1:3.38.2-1ubuntu2
+   Tabela de versão:
+  *** 1:3.38.2-1ubuntu2 500
+ 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  1:3.38.2-1ubuntu1 500
+ 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  

[Bug 1932579] Re: snap pt_BR locale shows warning every time

[Junior Martins]

What is your output of "apt-cache policy snapd" and what version of
snapd is shown by "snap list"?

I checked their GitHub page, and at

the description is different from comment #4 since it also includes "in
locale "pt_BR"", which itself was changed fairly recently on May 18,
2021 with the commit


The conditional expression itself didn't change though, so I think the
bug itself should be before that or was created after it in the
translation sources (I don't know how/where to check them though, any
help is greatly appreciated)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932579

Title:
  snap pt_BR locale shows warning every time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881287] Re: crash creating a new package

[Michael Martins]

Same error here.
Ubuntu 20.04.3

bzr dh-make hello 2.10 hello-2.10.tar.gz
brz: ERROR: AttributeError: 'NoneType' object has no attribute 
'initialize_on_transport'

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/breezy/plugins/debian/dh_make.py", line 
26, in _get_tree
tree = workingtree.WorkingTree.open(".")
  File "/usr/lib/python3/dist-packages/breezy/workingtree.py", line 201, in open
control = controldir.ControlDir.open(path, _unsupported=_unsupported)
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 706, in open
return klass.open_from_transport(t, probers=probers,
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 736, in 
open_from_transport
transport, format = _mod_transport.do_catching_redirections(
  File "/usr/lib/python3/dist-packages/breezy/transport/__init__.py", line 
1613, in do_catching_redirections
return action(transport)
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 724, in 
find_format
return transport, ControlDirFormat.find_format(transport,
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 1166, in 
find_format
raise errors.NotBranchError(path=transport.base)
breezy.errors.NotBranchError: Not a branch: 
"/home/michael/projetos/empacota_deb/".

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/breezy/plugins/debian/dh_make.py", line 
37, in _get_tree
a_controldir = controldir.ControlDir.open_from_transport(
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 736, in 
open_from_transport
transport, format = _mod_transport.do_catching_redirections(
  File "/usr/lib/python3/dist-packages/breezy/transport/__init__.py", line 
1613, in do_catching_redirections
return action(transport)
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 724, in 
find_format
return transport, ControlDirFormat.find_format(transport,
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 1166, in 
find_format
raise errors.NotBranchError(path=transport.base)
breezy.errors.NotBranchError: Not a branch: 
"/home/michael/projetos/empacota_deb/hello/".

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/breezy/commands.py", line 1016, in 
exception_to_return_code
return the_callable(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/breezy/commands.py", line 1202, in 
run_bzr
ret = run(*run_argv)
  File "/usr/lib/python3/dist-packages/breezy/commands.py", line 759, in 
run_argv_aliases
return self.run(**all_cmd_args)
  File "/usr/lib/python3/dist-packages/breezy/commands.py", line 784, in run
return self._operation.run_simple(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/breezy/cleanup.py", line 136, in 
run_simple
return _do_with_cleanups(
  File "/usr/lib/python3/dist-packages/breezy/cleanup.py", line 166, in 
_do_with_cleanups
result = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/breezy/plugins/debian/cmds.py", line 
1385, in run
tree = dh_make.import_upstream(
  File "/usr/lib/python3/dist-packages/breezy/plugins/debian/dh_make.py", line 
83, in import_upstream
tree = _get_tree(package_name)
  File "/usr/lib/python3/dist-packages/breezy/plugins/debian/dh_make.py", line 
42, in _get_tree
branch = create_branch(to_transport.base,
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 660, in 
create_branch_convenience
controldir = klass.create(base, format, possible_transports)
  File "/usr/lib/python3/dist-packages/breezy/controldir.py", line 859, in 
create
return format.initialize_on_transport(t)
AttributeError: 'NoneType' object has no attribute 'initialize_on_transport'

You can report this problem to Bazaar's developers by running
apport-bug /var/crash/brz.1000.2021-09-08T22:25.crash
if a bug-reporting window does not automatically appear.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881287

Title:
  crash creating a new package

To manage notifications about this bug go to:
https://bugs.launchpad.net/brz/+bug/1881287/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942475] [NEW] application does not start

[Michael Martins]

Public bug reported:

Application returns errors when trying to open blueman-manager:

Traceback (most recent call last):
  File "/usr/bin/blueman-manager", line 18, in 
from blueman.main.Manager import Blueman
  File "/usr/lib/python3/dist-packages/blueman/main/Manager.py", line 8, in 

from blueman.gui.manager.ManagerDeviceList import ManagerDeviceList
  File 
"/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py", line 
7, in 
from blueman.gui.DeviceList import DeviceList
  File "/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py", line 9, in 

from _blueman import conn_info, ConnInfoReadError
ImportError: /lib/x86_64-linux-gnu/libbluetooth.so.3: cabeçalho de ELF inválido

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: blueman 2.1.2-1ubuntu0.2
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Sep  2 17:31:00 2021
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: blueman
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942475

Title:
  application does not start

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Re: [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay between on and off modes

[Junior Martins]

Is there any difference between turning bluetooth on and off in the
Settings window versus the top-right bar? Or how they receive/read the
bluetooth status? Because the differences I see are that mine applies to
both turning on and off and that it also affects the Settings window.

Since the top-right bar is behaving strangely with rfkill, switch or
pressing "turn off", I didn't test it, but only the Settings window. I
also didn't test it using my laptop airplane mode.

rfkill output and behaviours:
The ID for bluetooth device hci0 changes after execution of "rfkill block 1" or 
switch off. Also, hci0 reappears with a new ID (+1 the previous).


>>>rfkill (bluetooth is on)
ID TYPE  DEVICE  SOFT  HARD
 0 wlan  acer-wireless  unblocked unblocked
 1 bluetooth acer-bluetooth unblocked unblocked
 2 wlan  phy0   unblocked unblocked
21 bluetooth hci0   unblocked unblocked

>>>rfkill (bluetooth is off due to switch or rfkill block 1)
ID TYPE  DEVICE  SOFT  HARD
 0 wlan  acer-wireless  unblocked unblocked
 1 bluetooth acer-bluetooth   blocked unblocked
 2 wlan  phy0   unblocked unblocked

>>>rfkill (bluetooth is off due to rfkill block 53)
ID TYPE  DEVICE  SOFT  HARD
 0 wlan  acer-wireless  unblocked unblocked
 1 bluetooth acer-bluetooth unblocked unblocked
 2 wlan  phy0   unblocked unblocked
53 bluetooth hci0 blocked unblocked

If bluetooth is currently on and if I use the switch to turn it off and
on again, or if bluetooth is currently off and I use the switch to turn
it on, the delay mentioned in the bug description will appear as
described.


ACER-BLUETOOTH DEVICE

If bluetooth is currently on: "rfkill block 1" will make Settings window 
instantly show as off while the switch stays on, it doesn't goes off until I 
change panels and come back.
If bluetooth is currently off due to "rfkill block 1": "rfkill unblock 1" will 
make Settings window show as on after 3-8s
If bluetooth is currently off due to "rfkill block 46": "rfkill unblock 1" 
won't work
If bluetooth is currently off due to switch: "rfkill unblock 1" will make 
Settings window and switch show as on after 6-8s (the command itself returns 
earlier, after 3s, and it is already updated with acer-bluetooth as unblocked)


HCI0 DEVICE

It should be noted that "rfkill block 46" followed by "rfkill unblock
46" didn't reproduce the delay, but kept the disparity between switch
and state (Settings window)/"Off and turn off" (top-right bar).


If bluetooth is currently on: "rfkill block 46" will display the same behaviour 
as "rfkill block 1"
If bluetooth is currently off due to "rfkill block 1": I cannot use "rfkill 
unblock 46" as it doesn't exist and would return with ID 47.
If bluetooth is currently off due to "rfkill block 46": "rfkill unblock 46" 
will make Settings window show as on immediately.
If bluetooth is currently off due to switch: hci0 disappears from rfkill output.
-Unblocking via switch takes a lot of time, rfkill itself updates immediately 
to show acer-bluetooth as unblocked, but hci0 reappears only after the change 
takes effect in Settings window.
-Unblocking via "rfkill unblock 1" will update the Settings window after 8s 
(the command itself returns immediately, but the same behaviour is present 
(immediate for acer-bluetooth, delayed for hci0)).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Re: [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay between on and off modes

[Junior Martins]

Thank you, so this is a duplicate, and 4 years old one at that! How can
I close mine and mark it as such?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Re: [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay between on and off modes

[Junior Martins]

Bug 1925318 might be related, but my computer doesn't have a problem of
connecting and disconnecting, but with this delay between the mode
itself and what is shown to the user.

This also affects the top-right bar, if I disconnect from there, it will
show as "Bluetooth off", but will still have the option to turn it off
available below.

** Attachment added: "Screenshot with bluetooth modes overlapping at top-right 
bar"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940759/+attachment/5520521/+files/Captura%20de%20tela%20de%202021-08-25%2011-32-18.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] RfKill.txt

[Junior Martins]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1940759/+attachment/5520519/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] UdevDb.txt

[Junior Martins]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1940759/+attachment/5520520/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] ProcModules.txt

[Junior Martins]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520517/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] PulseList.txt

[Junior Martins]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520518/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] ProcCpuinfo.txt

[Junior Martins]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520513/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] ProcInterrupts.txt

[Junior Martins]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520516/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] ProcEnviron.txt

[Junior Martins]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520515/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] ProcCpuinfoMinimal.txt

[Junior Martins]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520514/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] PaInfo.txt

[Junior Martins]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1940759/+attachment/5520512/+files/PaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Lsusb-t.txt

[Junior Martins]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520510/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Lsusb-v.txt

[Junior Martins]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520511/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Lspci-vt.txt

[Junior Martins]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520509/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Lspci.txt

[Junior Martins]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1940759/+attachment/5520508/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] IwConfig.txt

[Junior Martins]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520507/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Re: [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay between on and off modes

[Junior Martins]

apport information

** Tags added: apport-collected

** Description changed:

  When I switch bluetooth on or off in Control Center, it has a delay
  (5-30s) between the switch icon and the actual screen output, some times
  I need to switch between options on the side bar or even close the
  Control Center.
  
  outputs:
  >>>lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 22 00:46:45 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-04-20 (123 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to hirsute on 2021-06-08 (75 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  junior 1611 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2021-04-20 (126 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc. HD WebCam
+  Bus 001 Device 031: ID 04ca:3014 Lite-On Technology Corp. Qualcomm Atheros 
Bluetooth
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Acer Aspire E5-574
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=6767043c-143f-4c3a-976f-1c786765d862 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-31-generic N/A
+  linux-backports-modules-5.11.0-31-generic  N/A
+  linux-firmware 1.197.3
+ Tags:  hirsute
+ Uname: Linux 5.11.0-31-generic x86_64
+ UpgradeStatus: Upgraded to hirsute on 2021-06-08 (78 days ago)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/04/2016
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: V1.14
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: Zoro_SL
+ dmi.board.vendor: Acer
+ dmi.board.version: V1.14
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Chassis Manufacturer
+ dmi.chassis.version: Chassis Version
+ dmi.ec.firmware.release: 2.70
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd03/04/2016:br0.0:efr2.70:svnAcer:pnAspireE5-574:pvrV1.14:rvnAcer:rnZoro_SL:rvrV1.14:cvnChassisManufacturer:ct10:cvrChassisVersion:
+ dmi.product.family: SKL
+ dmi.product.name: Aspire E5-574
+ dmi.product.sku: Aspire E5-574_100C_1.14
+ dmi.product.version: V1.14
+ dmi.sys.vendor: Acer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520504/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] CurrentDmesg.txt

[Junior Martins]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5520506/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] CRDA.txt

[Junior Martins]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1940759/+attachment/5520505/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay
  between on and off modes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] Re: bluetooth settings have a delay between on and off modes

[Junior Martins]

My laptop is an Acer Aspire E5-574-592S.

** Attachment added: "Outputs for journalctl, lspci and lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1940759/+attachment/5520319/+files/outputs.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  bluetooth settings have a delay between on and off modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1940759/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940759] [NEW] bluetooth settings have a delay between on and off modes

[Junior Martins]

Public bug reported:

When I switch bluetooth on or off in Control Center, it has a delay
(5-30s) between the switch icon and the actual screen output, some times
I need to switch between options on the side bar or even close the
Control Center.

outputs:
>>>lsb_release -rd
Description:Ubuntu 21.04
Release:21.04

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 22 00:46:45 2021
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2021-04-20 (123 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to hirsute on 2021-06-08 (75 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

** Attachment added: "bluetooth.png"
   
https://bugs.launchpad.net/bugs/1940759/+attachment/5519723/+files/bluetooth.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940759

Title:
  bluetooth settings have a delay between on and off modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1940759/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

[Martins]

It's 2021 and it still here. 
I dunno if it is a bug but I have a exactly case here: 
https://i.imgur.com/3cuCCFZ.png
Maybe it's more ALSA or Pulseaudio related than Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002952

Title:
  [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932028] Re: missing version dependency on distro-info

[Thiago Martins]

Hi,

I also see this problem with fresh installed Xenial.

It's interesting to see that it's a bit tricky to reproduce this
problem. I have to upgrade "ubuntu-advantage-tools" shortly after
installing Xenial.

Cheers!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932028

Title:
  missing version dependency on distro-info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1932028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932579] [NEW] snap pt_BR locale shows warning every time

[Junior Martins]

Public bug reported:

The following warning appears every time I type a snap command, and thus
breaks auto-completion.

2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
"" is lowercase in locale "pt_BR": "o directório de destino"

The problem seems locale dependent, since "LANG=C snap" doesn't show
this warning. I'm currently using Ubuntu 21.04, and this bug happens
since I upgraded from 20.10. (I don't know if this is off-topic or where
I can help, but "directório" is more pt_PT than pt_BR, which could be
"pasta/diretório")

echo $LANG output:
pt_BR.UTF-8

lsb_release -rb output:
Description:Ubuntu 21.04
Release:21.04

apt-cache policy snapd output:
snapd:
  Instalado: 2.49.2+21.04ubuntu1
  Candidato: 2.49.2+21.04ubuntu1
  Tabela de versão:
 *** 2.49.2+21.04ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status

snap list output:
...[other packages]...
snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
snapd  2.5112159  latest/stable
canonical✓   snapd

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932579

Title:
  snap pt_BR locale shows warning every time

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931767] [NEW] Ubuntu 20.04 freezes when I connect external monitor through USB-C

[Martins Zeltins]

Public bug reported:

When I connect an external monitor through USB-C my system freezes
completely and the fans start spinning full speed and I can't do
anything. It was working before but now all of the sudden it has stopped
working. I used to be able to connect 2 extra external monitors (through
HDMI and USB-C)

*P.S. When I connect the monitor and then turn on the computer then it
hangs at the splash loading screen.*

Here is my setup:


Laptop - Lenovo Legion 5 (1 HDMI port and 1 USB-C port)
Intel i5 10th gen
NVIDIA GeForce GTX 1650 (with NVIDIA proprietary driver installed)


What I have tried so far but did not help

`apt update && apt upgrade`

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931767

Title:
  Ubuntu 20.04 freezes when I connect external monitor through USB-C

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929302] [NEW] no ubuntu-minimal in source-list

[Gilcio Amaral Martins]

Public bug reported:

Tryimg to upgrade from 16.04 to 18.04 and system complain of no ubuntu-
minimal in package source list

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.32
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
CrashDB: ubuntu
Date: Sat May 22 15:33:21 2021
InstallationDate: Installed on 2021-05-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2021-05-22 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2021-05-22 15:29:00.446769
 Log time: 2021-05-22 15:29:09.116824
 Log time: 2021-05-22 15:31:22.670816
 Log time: 2021-05-22 15:33:22.957009
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929302

Title:
  no ubuntu-minimal in source-list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929302/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925429] Re: Flickering of the graphical environment (i915 [drm] GPU HANG)

[Martins K.]

Attaching a screenshot showing some of the early symptoms (see the
scrambled content of the terminal, the horizontal line, as well as the
oddly colored apport tab in tint2).

Usually the effects are dynamic (e.g., an icon or some part of the
window gets drawn, disappears, gets drawn again, ad infinitum), so a
screencast probably could be more illustrative (if necessary, I can find
out how to record one).

** Attachment added: "screen.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925429/+attachment/5490892/+files/screen.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925429

Title:
  Flickering of the graphical environment (i915 [drm] GPU HANG)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925429] [NEW] Flickering of the graphical environment (i915 [drm] GPU HANG)

[Martins K.]

Public bug reported:

Ubuntu 20.10
uname -r: 5.8.0-50-generic
Machine: Lenovo T440s

1) The graphical environment starts flickering, drawing the windows and
their content scrambled, flashing, etc. Over the time the graphical
environment disintegrates completely (scrambled windows, horizontal
lines and solid squares all over the screen, impossible to use any
controls or even to understand where they are), rendering any further
work impossible (the only remedy is to reboot the system). At the onset
of those symptoms dmesg or the like do not contain anything informative;
however, usually the graphical environment also at some point freezes
for a moment. When this happens, the dmesg gets appended with lines
informing about a gpu hang:

[28620.924309] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:dfdef4fe, in 
Renderer [104270]
[28620.924474] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on 
rcs0
[28621.027257] i915 :00:02.0: [drm] Renderer[104270] context reset due to 
GPU hang
[28654.972181] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:0020, in 
Renderer [104270]
[28654.973039] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on 
rcs0
[28655.075025] i915 :00:02.0: [drm] Renderer[104270] context reset due to 
GPU hang


This is the probably the only possibly relevant info I could find in the logs. 

2) Reproducing: no specific steps are known. I noticed that using
Firefox usually speeds up the onset of the problems, but the bug
presents itself also when using other programs (e.g., Wolfram
Mathematica).

3) The bug started to manifest itself since updating to the kernel
5.8.0-49 via apt upgrade. Most tellingly, booting with 5.8.0-48 leads to
stable, working system without any of the described problems.

4) The only recent relevant report I could find seems to be this one:
https://gitlab.freedesktop.org/drm/intel/-/issues/2986

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-50-generic 5.8.0-50.56
ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: skip
Date: Thu Apr 22 09:31:48 2021
InstallationDate: Installed on 2015-03-18 (2226 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20ARS45900
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash elevator=noop vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-50-generic N/A
 linux-backports-modules-5.8.0-50-generic  N/A
 linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-10-23 (180 days ago)
dmi.bios.date: 01/09/2015
dmi.bios.release: 2.32
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET82WW (2.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARS45900
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: Not Available
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET82WW(2.32):bd01/09/2015:br2.32:efr1.9:svnLENOVO:pn20ARS45900:pvrThinkPadT440s:rvnLENOVO:rn20ARS45900:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20ARS45900
dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925429

Title:
  Flickering of the graphical environment (i915 [drm] GPU HANG)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow

[Fabio Augusto Miranda Martins]

Another customer has provided positive feedback that it fixes the issue
on Focal:

5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921104

Title:
  net/mlx5e: Add missing capability check for uplink follow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 581796] Re: grub-installer ignores grub2/linux_cmdline_default in preseed

[Thiago Martins]

I'm thinking about this.. Maybe, this is by design! Right?

The way it's today, the options used during the Packer builds, for
example, don't end up on the image! Sounds like a good idea actually.

Gonna take a look at "debian-installer/add-kernel-opts"!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581796

Title:
  grub-installer ignores grub2/linux_cmdline_default in preseed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/581796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 581796] Re: grub-installer ignores grub2/linux_cmdline_default in preseed

[Thiago Martins]

I was so annoyed that my "presseded" installations of Ubuntu 20.04
Legacy ISO Server with Packer were ending up with a black screen that
only "ALT + Arrow Right" was bringing the `tty1` back to life...

Then, I realized that the "Packer builds were adding" the "quiet splash"
to the /etc/default/grub file, no matter what I did to pressed regular
options, and this problem brought me to this... 11 years old bug
report!!! Wht?!

So, the workaround proposed on comment #1 worked like a charm, and
finally, my Packer builds produces awesome server images with a nice
verbose boot that goes straight to tty1!

It looks like that won't be fixed since Canonical is moving to the new
subiquity, Cloud-Init based `autoinstall`. Kinda sad. I don't like the
new "Live Server" install media, legacy is way, way better.

Thank you Mathieu!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581796

Title:
  grub-installer ignores grub2/linux_cmdline_default in preseed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/581796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923115] Re: Networkd vs udev nic renaming race condition

[Fabio Augusto Miranda Martins]

Customer has provided a positive feedback that the package in -proposed
fixed this bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923115

Title:
  Networkd vs udev nic renaming race condition

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919261] [NEW] Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed

[Fabio Augusto Miranda Martins]

Public bug reported:

In a host where ceph-mds is installed, upgrading from
14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails
with:

dpkg: error processing archive 
/tmp/apt-dpkg-install-Zen6uw/9-ceph-common_15.2.8-0ubuntu0.20.04.1~cloud0_amd64.deb
 (--unpack):
 trying to overwrite '/usr/bin/cephfs-data-scan', which is also in package 
ceph-mds 14.2.11-0ubuntu0.19.10.1~cloud4
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 
/tmp/apt-dpkg-install-Zen6uw/9-ceph-common_15.2.8-0ubuntu0.20.04.1~cloud0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

The problem happens because /usr/bin/cephfs-data-scan is provided by
ceph-mds in 14.2.11-0ubuntu0.19.10.1~cloud4:

# dpkg -S /usr/bin/cephfs-data-scan
ceph-mds: /usr/bin/cephfs-data-scan

However in 15.2.8-0ubuntu0.20.04.1~cloud0 it is provided by ceph-common:

# dpkg -S /usr/bin/cephfs-data-scan
ceph-common: /usr/bin/cephfs-data-scan

A quick workaround is to temporarily remove ceph-mds before the upgrade
(dpkg -r ceph-mds) and then perform the upgrade process using apt
install. It will upgrade all packages and reinstall ceph-mds.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919261

Title:
  Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to
  15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857383] Re: Fractional scaling applies to both monitors when you only want it on one

[Antonio Cardoso Martins]

I continue to see this issue under ubuntu 20.10 and Wayland

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
Release:20.10
Codename:   groovy

$ loginctl
SESSION  UID USER   SEAT  TTY 
  2 1000 an-crd seat0 tty2

1 sessions listed.
$ loginctl show-session 2 -p Type
Type=wayland

It seemed that we would not see a fix for X11, but how about Wayland?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857383

Title:
  Fractional scaling applies to both monitors when you only want it on
  one

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1857383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842417] Re: Ubiquity needs support for fscrypt

[Thiago Martins]

I do want home-based encryption but, what about the new `systemd-homed`?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842417

Title:
  Ubiquity needs support for fscrypt

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882993] Re: Package needs newer version with v2 encryption policy

[Thiago Martins]

I can't wait for it!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882993

Title:
  Package needs newer version with v2 encryption policy

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

[Marco Paulo Martins Sousa]

The same issue.

Ubuntu broke my Windows EFI system partition, installing Ubuntu EFI on
it, despìte I have told Ubuntu to use the external drive.


*To fix the Windows EFI system partition:*

* Boot on Windows CMD using a Recovery Partition/USB Drive
** Windows Bootloader Recovery -> System Restore – > Troubleshoot-> Command 
Prompt
diskpart
list disk
list partition
list volume
sel disk 0 (Select the disk with the Windows EFI system partition)

Assign the drive letter K: to the hidden EFI volume:
select volume 1 (select the volument with the Windows EFI system partition)
assign letter K:
exit

cd /d K:\efi\microsoft\boot\
attrib BCD -s -h -r
ren BCD BCD.bak
bcdboot C:\Windows /l en-us /s k: /f ALL


*Don't use this commands, because this are only for MBR not UEFI mode:*
* bootrec /fixboot
* bootrec /scanos
* bootrec /rebuildbcd
* or even:
* bootrec /FixMbr

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906998] Re: no headphone sound after update 18.04.5 kernel 5.4.0-56-generic

[Danilo Martins]

Follow the print from the screen running the pavucontrol

** Attachment added: "ubuntu-pavucontrol-sound-issue1.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1906998/+attachment/5444330/+files/ubuntu-pavucontrol-sound-issue1.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906998

Title:
  no headphone sound after update 18.04.5 kernel 5.4.0-56-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1906998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906998] Re: no headphone sound after update 18.04.5 kernel 5.4.0-56-generic

[Danilo Martins]

The headphone sound issue was temporarily resolved.

I launched pavucontrol > input devices > and in the "sof-hda-dsp Headphone 
Microphone + Headset Microphone" I selected "Headphone Microphone" in the 
"Port" field.
As default, the "Headset Microphone" is set.

I have no idea why this worked.

But every time I connect my headphone, I need to change the settings as
mentioned above.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906998

Title:
  no headphone sound after update 18.04.5 kernel 5.4.0-56-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1906998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command

[Thiago Martins]

I totally agree with this!

The Additional Drivers doesn't work if your Netplan uses rendered:
networked.

Then, the command line is useless too... How does it work?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818746

Title:
  `ubuntu-drivers list` output doesn't bear any relation to the input to
  the install command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818746/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs