from:"Junior"

** Description changed:

[ Impact ]

Some versions of Windows hang on reboot if their TSC value is greater
than 2^54. The calibration of the Hyper-V reference time overflows
and fails; as a result the processors' clock sources are out of sync.

[ Test Plan ]

As suggested by Mauricio, testing will be done in stages.

1) unit test, with such rdtsc/print loop (and confirm the tsc value
decreases after system_reset).

This can be done by using x86/tsc.flat from the following repository:

https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git

Follow the steps below:

Inside a Jammy system (privileged container/VM, bare metal, etc.):

# apt update && apt install gcc make -y
# git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
# cd kvm-unit-tests
- # ... TODO ...
+ # wget
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2064914/+attachment/5784045/+files/tsc.c.patch
-O- | patch -p1
+ # ./configure && make
+
+ Make sure x86/tsc exists. Now you can install qemu and perform the
+ test:
+
+ # apt install -y qemu-system-x86
+ # qemu-system-x86_64 -serial file:/tmp/bogus-output -accel kvm -kernel
x86/tsc.flat -monitor stdio -nographic
+
+ Wait a couple of seconds and issue a "system_reset" command. Then, wait
+ a couple more seconds and issue a "quit" command.
+
+ You can now open /tmp/bogus-output and check the values of rdtsc. You
+ will notice that its value increments after the "system_reset", which is
+ exactly what we don't want.
+
+ Afterwards, you can update qemu and test the fix by doing the same steps
+ (make sure you adjust the "file:/tmp/..." path).

2) regression test, booting Ubuntu kernel/initrd pairs (installer's
should be enough) from supported releases, and checking they boot/reach
a prompt.

[ Where problems could occur ]

This is a change impacting normal x86 code, so although the patch is
small and well contained, in the unlikely case that we find a regression
it will impact more users. As such, and under Mauricio's advice, the
test plan is being extended to really guarantee that the common
virtualization scenarios are not impacted. If we find a problem with
this update, there is the possibility of reverting it temporarily until
we can devise a proper fix.

[ Original Description ]

Description:
Some versions of Windows hang on reboot if their TSC value is greater
than 2^54. The calibration of the Hyper-V reference time overflows
and fails; as a result the processors' clock sources are out of sync.

The issue is that the TSC _should_ be reset to 0 on CPU reset and
QEMU tries to do that. However, KVM special cases writing 0 to the
TSC and thinks that QEMU is trying to hot-plug a CPU, which is
correct the first time through but not later. Thwart this valiant
effort and reset the TSC to 1 instead, but only if the CPU has been
run once.

For this to work, env->tsc has to be moved to the part of CPUArchState
that is not zeroed at the beginning of x86_cpu_reset.

Solution: [PATCH] target/i386: properly reset TSC on reset

I created and tested a ppa ubuntu package already. The patch fixes this issue.
Link to ppa:
https://launchpad.net/~bhinz83/+archive/ubuntu/openstack-rds/+packages

It affects only jammy 22.04 package. The newest version is:
qemu-1:6.2+dfsg-2ubuntu6.19

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

Title:
Windows guest hangs after reboot from the guest OS

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

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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

** Description changed:

[ Impact ]

[ Test Plan ]

As suggested by Mauricio, testing will be done in stages.

1) unit test, with such rdtsc/print loop (and confirm the tsc value
decreases after system_reset).

This can be done by using x86/tsc.flat from the following repository:

https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
+
+ Follow the steps below:
+
+ Inside a Jammy system (privileged container/VM, bare metal, etc.):
+
+ # apt update && apt install gcc make -y
+ # git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
+ # cd kvm-unit-tests
+ # ... TODO ...

2) regression test, booting Ubuntu kernel/initrd pairs (installer's
should be enough) from supported releases, and checking they boot/reach
a prompt.

[ Where problems could occur ]

[ Original Description ]

For this to work, env->tsc has to be moved to the part of CPUArchState
that is not zeroed at the beginning of x86_cpu_reset.

Solution: [PATCH] target/i386: properly reset TSC on reset

I created and tested a ppa ubuntu package already. The patch fixes this issue.
Link to ppa:
https://launchpad.net/~bhinz83/+archive/ubuntu/openstack-rds/+packages

It affects only jammy 22.04 package. The newest version is:
qemu-1:6.2+dfsg-2ubuntu6.19

** Patch added: "tsc.c.patch"

https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2064914/+attachment/5784045/+files/tsc.c.patch

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

Title:
Windows guest hangs after reboot from the guest OS

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

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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

** Changed in: qemu (Ubuntu Jammy)
   Status: Incomplete => In Progress

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

** Changed in: qemu (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

** Description changed:

  [ Impact ]
  
  Some versions of Windows hang on reboot if their TSC value is greater
  than 2^54.  The calibration of the Hyper-V reference time overflows
  and fails; as a result the processors' clock sources are out of sync.
  
  [ Test Plan ]
  
- TBD.
+ As suggested by Mauricio, testing will be done in stages.
+ 
+ 1) unit test, with such rdtsc/print loop (and confirm the tsc value
+ decreases after system_reset).
+ 
+ This can be done by using x86/tsc.flat from the following repository:
+ 
+ https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
+ 
+ 2) regression test, booting Ubuntu kernel/initrd pairs (installer's
+ should be enough) from supported releases, and checking they boot/reach
+ a prompt.
  
  [ Where problems could occur ]
  
- TBD.
+ This is a change impacting normal x86 code, so although the patch is
+ small and well contained, in the unlikely case that we find a regression
+ it will impact more users.  As such, and under Mauricio's advice, the
+ test plan is being extended to really guarantee that the common
+ virtualization scenarios are not impacted.  If we find a problem with
+ this update, there is the possibility of reverting it temporarily until
+ we can devise a proper fix.
  
  [ Original Description ]
  
  Description:
  Some versions of Windows hang on reboot if their TSC value is greater
  than 2^54.  The calibration of the Hyper-V reference time overflows
  and fails; as a result the processors' clock sources are out of sync.
  
  The issue is that the TSC _should_ be reset to 0 on CPU reset and
  QEMU tries to do that.  However, KVM special cases writing 0 to the
  TSC and thinks that QEMU is trying to hot-plug a CPU, which is
  correct the first time through but not later.  Thwart this valiant
  effort and reset the TSC to 1 instead, but only if the CPU has been
  run once.
  
  For this to work, env->tsc has to be moved to the part of CPUArchState
  that is not zeroed at the beginning of x86_cpu_reset.
  
  Solution: [PATCH] target/i386: properly reset TSC on reset
  
  I created and tested a ppa ubuntu package already. The patch fixes this issue.
  Link to ppa: 
https://launchpad.net/~bhinz83/+archive/ubuntu/openstack-rds/+packages
  
  It affects only jammy 22.04 package. The newest version is:
  qemu-1:6.2+dfsg-2ubuntu6.19

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

Hi Mauricio,

Apologies for taking long to reply.  As you know, I've been busy with
other stuff.

Thank you very much for your considerations.  It seems that I jumped the
gun on this SRU and uploaded without finishing the SRU text; sorry.
Also, I liked your suggestions for more testing.  I was able to perform
the first one using tsc.flat from this repo: https://gitlab.com/kvm-
unit-tests/kvm-unit-tests.git.  I'll post my results later.

I'm not entirely sure I'll be able to perform test (2) from your list,
but I will try.

As for test (3), I can also work on it.

I'll update the SRU text accordingly.  Thanks.

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2067388] Re: New upstream microreleases 12.19, 14.12 and 15.7

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-16/+git/postgresql-16/+merge/466614

** Description changed:

  [Impact]
  
-  * MRE for latest stable fixes of Postgres 12, 14, and 15 released on
+  * MRE for latest stable fixes of Postgres 12, 14, 15 and 16 released on
  May 2024.
  
  [Test Case]
  
   * The Postgres MREs traditionally rely on the large set of autopkgtests
     to run for verification. In a PPA, those are all already pre-checked to
     be good for this upload.
  
  [Regression Potential]
  
   * Upstream tests are usually great and in addition in the Archive there
     are plenty of autopkgtests that in the past caught issues before being
     released.
     But nevertheless there always is a risk for something to break. Since
     these are general stable releases I can't pinpoint them to a most-likely 
area.
     - usually this works smoothly except a few test hiccups (flaky) that need 
to be clarified to be sure. Pre-checks will catch those to be discussed upfront 
(as last time)
  
  [Other Info]
  
   * This is a reoccurring MRE, see below and all the references
   * CVEs addressed by this MRE:
-   - CVE-2024-4317 (only applicable for versions 14 and 15)
+   - CVE-2024-4317 (only applicable for versions 14, 15 and 16)
  
  Current versions in supported releases that got updates:
  
   postgresql-12 | 12.18-0ubuntu0.20.04.1 | focal-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
   postgresql-14 | 14.11-0ubuntu0.22.04.1 | jammy-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
   postgresql-15 | 15.6-0ubuntu0.23.10.1 | mantic-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
+  postgresql-16 | 16.2-1ubuntu4 | noble | source, amd64, arm64, 
armhf, i386, ppc64el, riscv64, s390x
  
  Special cases:
- - Since there is 1 CVE being fixed here on versions 14 and 15, we will push 
these versions through the security pocket.
+ - Since there is 1 CVE being fixed here on versions 14, 15 and 16, we will 
push these versions through the security pocket.
  - Version 12 will be uploaded to the updates pocket, since it's not affected 
by the CVE.
  
  Standing MRE - Consider last updates as template:
  
  - https://pad.lv/1637236
  - https://pad.lv/1664478
  - https://pad.lv/1690730
  - https://pad.lv/1713979
  - https://pad.lv/1730661
  - https://pad.lv/1747676
  - https://pad.lv/1752271
  - https://pad.lv/1786938
  - https://pad.lv/1815665
  - https://pad.lv/1828012
  - https://pad.lv/1833211
  - https://pad.lv/1839058
  - https://pad.lv/1863108
  - https://pad.lv/1892335
  - https://pad.lv/1915254
  - https://pad.lv/1928773
  - https://pad.lv/1939396
  - https://pad.lv/1950268
  - https://pad.lv/1961127
  - https://pad.lv/1973627
  - https://pad.lv/1978249
  - https://pad.lv/1984012
  - https://pad.lv/1996770
  - https://pad.lv/2006406
  - https://pad.lv/2019214
  - https://pad.lv/2028426
  - https://pad.lv/2040469
  
  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.
  
  Once ready, the test packages should be available at
  https://launchpad.net/~canonical-server/+archive/ubuntu/postgresql-sru-
  preparation/+packages

** Also affects: postgresql-16 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: postgresql-16 (Ubuntu)
   Status: New => Triaged

** Changed in: postgresql-16 (Ubuntu)
   Status: Triaged => Invalid

** Also affects: postgresql-12 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: postgresql-14 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: postgresql-15 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: postgresql-16 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: postgresql-16 (Ubuntu Noble)
   Status: New => Triaged

** Changed in: postgresql-16 (Ubuntu Noble)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** No longer affects: postgresql-15 (Ubuntu Noble)

** No longer affects: postgresql-14 (Ubuntu Noble)

** No longer affects: postgresql-12 (Ubuntu Noble)

** Summary changed:

- New upstream microreleases 12.19, 14.12 and 15.7
+ New upstream microreleases 12.19, 14.12, 15.7 and 16.3

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

Title:
  New upstream microreleases 12.19, 14.12, 15.7 and 16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/2067388/+subscriptions


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

[Bug 2067397] Re: package sssd-proxy 2.6.3-1ubuntu3.2 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret

*** This bug is a duplicate of bug 1972076 ***
https://bugs.launchpad.net/bugs/1972076

Thank you for taking the time to file a bug report.

From DpkgTerminalLog.txt, we can see that the problem seems to come from
this operation:

Setting up python3 (3.10.6-1~22.04) ...
  File "/usr/share/games/renpy/launcher/game/gui7/code.py", line 283
l = re.sub(ur'_\((\".*?\")\)', replace, l)
 
SyntaxError: invalid syntax
error running python rtupdate hook renpy
dpkg: error processing package python3 (--configure):
 installed python3 package post-installation script subprocess returned error 
exit status 4
dpkg: dependency problems prevent configuration of sssd-common:
 sssd-common depends on python3; however:
  Package python3 is not configured yet.

This is unfortunately a known bug (#1972076) that hasn't been fixed yet.
My advice is to uninstall renpy and try installing sssd again.

Since this is not a bug with sssd but it is a known issue with renpy, I
will mark it as a duplicate of the bug mentioned above.  Please leave a
comment there if you face more issues.

Thank you.

** This bug has been marked a duplicate of bug 1972076
   package renpy 7.3.5+dfsg-2 failed to install/upgrade: installed renpy 
package post-installation script subprocess returned error exit status 1

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

Title:
  package sssd-proxy 2.6.3-1ubuntu3.2 failed to install/upgrade:
  afhængighedsproblemer - efterlader den ukonfigureret

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


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

[Bug 2067348] Re: ruby build-in readline gem do not handle utf-8 input

Thank you for taking the time to file a bug in Ubuntu.

I can confirm the problem.  I did:

# dpkg-reconfigure locales

Chose ru_RU.UTF-8 as the default locale.  Logged out and in again.

Then, I launched ruby3.2 and tried to paste a Russian character, like ю
or б.  They're not properly handled by the prompt.

I also verified that bash can handle these characters fine, which is an
interesting data point because bash also uses readline under the hood.

Anyway, I'll mark this bug as Triaged and subscribe the Ubuntu Server
team.  Hopefully someone will have the capacity to look into it soon.

Thanks.

** Changed in: ruby3.2 (Ubuntu)
   Status: New => Triaged

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

Title:
  ruby build-in readline gem do not handle utf-8 input

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby3.2/+bug/2067348/+subscriptions


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

[Bug 2066914] Re: tmux 3.4 stalls during active pane zoom

** Changed in: tmux (Ubuntu)
   Status: New => Incomplete

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

Title:
  tmux 3.4 stalls during active pane zoom

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


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

[Bug 2067388] Re: New upstream microreleases 12.19, 14.12 and 15.7

** Changed in: postgresql-12 (Ubuntu Focal)
   Status: Triaged => 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/2067388

Title:
  New upstream microreleases 12.19, 14.12 and 15.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/2067388/+subscriptions


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

[Bug 2067388] Re: New upstream microreleases 12.19, 14.12 and 15.7

** Description changed:

  [Impact]
  
-  * MRE for latest stable fixes of Postgres 12, 14, and 15 released on
+  * MRE for latest stable fixes of Postgres 12, 14, and 15 released on
  May 2024.
  
  [Test Case]
  
-  * The Postgres MREs traditionally rely on the large set of autopkgtests
-to run for verification. In a PPA, those are all already pre-checked to
-be good for this upload.
+  * The Postgres MREs traditionally rely on the large set of autopkgtests
+    to run for verification. In a PPA, those are all already pre-checked to
+    be good for this upload.
  
  [Regression Potential]
  
-  * Upstream tests are usually great and in addition in the Archive there
-are plenty of autopkgtests that in the past caught issues before being
-released.
-But nevertheless there always is a risk for something to break. Since
-these are general stable releases I can't pinpoint them to a most-likely 
area.
-- usually this works smoothly except a few test hiccups (flaky) that need 
to be clarified to be sure. Pre-checks will catch those to be discussed upfront 
(as last time)
+  * Upstream tests are usually great and in addition in the Archive there
+    are plenty of autopkgtests that in the past caught issues before being
+    released.
+    But nevertheless there always is a risk for something to break. Since
+    these are general stable releases I can't pinpoint them to a most-likely 
area.
+    - usually this works smoothly except a few test hiccups (flaky) that need 
to be clarified to be sure. Pre-checks will catch those to be discussed upfront 
(as last time)
  
  [Other Info]
  
-  * This is a reoccurring MRE, see below and all the references
-  * CVEs addressed by this MRE:
-   - CVE-2024-4317
+  * This is a reoccurring MRE, see below and all the references
+  * CVEs addressed by this MRE:
+   - CVE-2024-4317 (only applicable for versions 14 and 15)
  
  Current versions in supported releases that got updates:
  
-  postgresql-12 | 12.18-0ubuntu0.20.04.1 | focal-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
-  postgresql-14 | 14.11-0ubuntu0.22.04.1 | jammy-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
-  postgresql-15 | 15.6-0ubuntu0.23.10.1 | mantic-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
+  postgresql-12 | 12.18-0ubuntu0.20.04.1 | focal-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
+  postgresql-14 | 14.11-0ubuntu0.22.04.1 | jammy-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
+  postgresql-15 | 15.6-0ubuntu0.23.10.1 | mantic-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
  
  Special cases:
- - Since there is 1 CVE being fixed here, we will push this through the 
security pocket.
+ - Since there is 1 CVE being fixed here on versions 14 and 15, we will push 
these versions through the security pocket.
+ - Version 12 will be uploaded to the updates pocket, since it's not affected 
by the CVE.
  
  Standing MRE - Consider last updates as template:
  
  - https://pad.lv/1637236
  - https://pad.lv/1664478
  - https://pad.lv/1690730
  - https://pad.lv/1713979
  - https://pad.lv/1730661
  - https://pad.lv/1747676
  - https://pad.lv/1752271
  - https://pad.lv/1786938
  - https://pad.lv/1815665
  - https://pad.lv/1828012
  - https://pad.lv/1833211
  - https://pad.lv/1839058
  - https://pad.lv/1863108
  - https://pad.lv/1892335
  - https://pad.lv/1915254
  - https://pad.lv/1928773
  - https://pad.lv/1939396
  - https://pad.lv/1950268
  - https://pad.lv/1961127
  - https://pad.lv/1973627
  - https://pad.lv/1978249
  - https://pad.lv/1984012
  - https://pad.lv/1996770
  - https://pad.lv/2006406
  - https://pad.lv/2019214
  - https://pad.lv/2028426
  - https://pad.lv/2040469
  
  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.
  
  Once ready, the test packages should be available at
  https://launchpad.net/~canonical-server/+archive/ubuntu/postgresql-sru-
  preparation/+packages

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

Title:
  New upstream microreleases 12.19, 14.12 and 15.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/2067388/+subscriptions


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

[Bug 2067052] Re: snmpinform sends PDUs containing a GET request SNMP_MSG_GET

Hello Rudolf,

Thank you for this bug report.  Would you be able to provide a small
reproducer for the problem you're experiencing?  This would make it much
easier for us to understand the issue and try to find a fix for it.

Also, since you appear comfortable dealing with source code, would you
mind taking a look at the upstream project and seeing if there's any
similar bug reported?

I am going to set the status of this bug to Incomplete to reflect the
fact that we're waiting on more information from your side; please set
its status back to New once you've provided the requested data.

Thanks!

** Changed in: net-snmp (Ubuntu)
   Status: New => Incomplete

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

Title:
  snmpinform sends PDUs containing a GET request SNMP_MSG_GET

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


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

[Bug 2067061] Re: package postgresql-15 15.5-0ubuntu0.23.04.1 failed to install/upgrade: installed postgresql-15 package post-installation script subprocess returned error exit status 1

I also noticed this:

Start-Date: 2024-05-24  17:16:19
Commandline: apt-get remove --purge postgresql-15
Requested-By: kartik (1000)
Purge: postgresql-15:amd64 (15.5-0ubuntu0.23.04.1), postgresql-contrib:amd64 
(15+248), postgresql:amd64 (15+248)
End-Date: 2024-05-24  17:16:27

These version numbers are strange; it seems like the postgresql packages
are coming from two different sources (the Ubuntu repository + the
upstream repo, maybe?).

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

Title:
  package postgresql-15 15.5-0ubuntu0.23.04.1 failed to install/upgrade:
  installed postgresql-15 package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-15/+bug/2067061/+subscriptions


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

[Bug 2067388] Re: New upstream microreleases 12.19, 14.12 and 15.7

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-12/+git/postgresql-12/+merge/466514

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-14/+git/postgresql-14/+merge/466515

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-15/+git/postgresql-15/+merge/466516

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

Title:
  New upstream microreleases 12.19, 14.12 and 15.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/2067388/+subscriptions


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

[Bug 2067388] [NEW] New upstream microreleases 12.19, 14.12 and 15.7

Public bug reported:

[Impact]

 * MRE for latest stable fixes of Postgres 12, 14, and 15 released on
May 2024.

[Test Case]

 * The Postgres MREs traditionally rely on the large set of autopkgtests
   to run for verification. In a PPA, those are all already pre-checked to
   be good for this upload.

[Regression Potential]

 * Upstream tests are usually great and in addition in the Archive there
   are plenty of autopkgtests that in the past caught issues before being
   released.
   But nevertheless there always is a risk for something to break. Since
   these are general stable releases I can't pinpoint them to a most-likely 
area.
   - usually this works smoothly except a few test hiccups (flaky) that need to 
be clarified to be sure. Pre-checks will catch those to be discussed upfront 
(as last time)

[Other Info]

 * This is a reoccurring MRE, see below and all the references
 * CVEs addressed by this MRE:
  - CVE-2024-4317

Current versions in supported releases that got updates:

 postgresql-12 | 12.18-0ubuntu0.20.04.1 | focal-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 postgresql-14 | 14.11-0ubuntu0.22.04.1 | jammy-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 postgresql-15 | 15.6-0ubuntu0.23.10.1 | mantic-updates  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x

Special cases:
- Since there is 1 CVE being fixed here, we will push this through the security 
pocket.

Standing MRE - Consider last updates as template:

- https://pad.lv/1637236
- https://pad.lv/1664478
- https://pad.lv/1690730
- https://pad.lv/1713979
- https://pad.lv/1730661
- https://pad.lv/1747676
- https://pad.lv/1752271
- https://pad.lv/1786938
- https://pad.lv/1815665
- https://pad.lv/1828012
- https://pad.lv/1833211
- https://pad.lv/1839058
- https://pad.lv/1863108
- https://pad.lv/1892335
- https://pad.lv/1915254
- https://pad.lv/1928773
- https://pad.lv/1939396
- https://pad.lv/1950268
- https://pad.lv/1961127
- https://pad.lv/1973627
- https://pad.lv/1978249
- https://pad.lv/1984012
- https://pad.lv/1996770
- https://pad.lv/2006406
- https://pad.lv/2019214
- https://pad.lv/2028426
- https://pad.lv/2040469

As usual we test and prep from the PPA and then push through
SRU/Security as applicable.

Once ready, the test packages should be available at
https://launchpad.net/~canonical-server/+archive/ubuntu/postgresql-sru-
preparation/+packages

** Affects: postgresql-12 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: postgresql-14 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: postgresql-15 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: postgresql-12 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: Triaged

** Affects: postgresql-14 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: Triaged

** Affects: postgresql-15 (Ubuntu Mantic)
 Importance: Undecided
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: Triaged


** Tags: server-todo

** Also affects: postgresql-12 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: postgresql-14 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: postgresql-15 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: postgresql-14 (Ubuntu Focal)

** No longer affects: postgresql-15 (Ubuntu Focal)

** Also affects: postgresql-12 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: postgresql-14 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: postgresql-15 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: postgresql-12 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: postgresql-14 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: postgresql-15 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: postgresql-12 (Ubuntu Jammy)

** No longer affects: postgresql-12 (Ubuntu Mantic)

** No longer affects: postgresql-14 (Ubuntu Mantic)

** No longer affects: postgresql-15 (Ubuntu Jammy)

** Changed in: postgresql-12 (Ubuntu Focal)
   Status: New => Triaged

** Changed in: postgresql-14 (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: postgresql-15 (Ubuntu Mantic)
   Status: New => Triaged

** Changed in: postgresql-12 (Ubuntu)
   Status: New => Invalid

** Changed in: postgresql-14 (Ubuntu)
   Status: New => Invalid

** Changed in: postgresql-12 (Ubuntu Focal)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Changed in: postgresql-15 (Ubuntu Mantic)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Tags added: server-todo

** Changed in: postgresql-14 (Ubuntu Jammy)
 Assignee: (unassigned) => Sergio Durigan Ju

[Bug 2065546] Re: postfix configuration must be set on 24.04 before apt package manager can be used

2024-05-16 Thread Sergio Durigan Junior

Hello William,

You can find instructions on how to report a bug against a Debian
package here: https://www.debian.org/Bugs/Reporting

Thanks.

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

Title:
  postfix configuration must be set on 24.04 before apt package manager
  can be used

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


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

[Bug 2065737] Re: pam_radius_auth module doesn't work if ipv6 disabled

2024-05-16 Thread Sergio Durigan Junior

Thank you for reporting a bug.

I am going to add it to our backlog, but this is not not a priority for
the team, so it may take some time before the bug is fixed.  Would you
like to drive this SRU yourself?  That could make things faster.

Thanks!

** Changed in: libpam-radius-auth (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  pam_radius_auth module doesn't work if ipv6 disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpam-radius-auth/+bug/2065737/+subscriptions


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

[Bug 2065546] Re: postfix configuration must be set on 24.04 before apt package manager can be used

2024-05-15 Thread Sergio Durigan Junior

Hi William,

The culprit for pulling in postfix when installing the set of packages
you mentioned in the description is Emacs.  This is a side effect of a
change that I made when I last merged the last version from Debian, in
an attempt to reduce the delta and make it possible to eventually sync
Emacs again.

There are a few ways you can workaround this issue.

1) You can invoke apt using "--no-install-recommends" when installing
Emacs.  This will prevent apt from installing the packages that Emacs
recommended, and mailutils (which actually installs postfix) is one of
them.

2) As Lucas said above, you can define the DEBIAN_FRONTEND environment
variable to "noninteractive".  You can do it like:

DEBIAN_FRONTEND=noninteractive apt install 

Note that the DEBIAN_FRONTEND variable was *not* set on Jammy either;
the problem here relies solely on the fact that Emacs started
recommending mailutils (like it does in Debian), instead of suggesting
it.

I will add an Emacs task to the bug, but I consider this a wishlist and
believe that it should be raised with Debian first.  Could you open a
bug against the Debian Emacs package and let us know when you do it,
please?

Thank you.

** Also affects: emacs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: emacs (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: emacs (Ubuntu)
   Status: New => Triaged

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

Title:
  postfix configuration must be set on 24.04 before apt package manager
  can be used

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-05-15 Thread Sergio Durigan Junior

Thanks for the reply, Simon.

I was about to say exactly the same thing.  To the extent of my
knowledge, the issue has been (at least partially) addressed on LXD, so
it should be possible to launch VMs with more than 288 vCPUs with it.

Either way, this bug has been fixed in QEMU so I am going to set its
status back to Fix Released.

Thanks.

** Changed in: qemu (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2065579] Re: [UBUNTU 22.04] OS guest boot issues on 9p filesystem

2024-05-13 Thread Sergio Durigan Junior

Thank you for the report.

Given that this is an upstream regression and there is a related
upstream bug about it, I believe it's best to wait for their
input/feedback before moving forward.

** Also affects: qemu
   Importance: Undecided
   Status: New

** No longer affects: qemu

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  [UBUNTU 22.04] OS guest boot issues on 9p filesystem

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


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

[Bug 2065541] [NEW] package thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 failed to install/upgrade: o subprocesso do pacote thunderbird, novo script pre-installation retornou erro do status de saída

2024-05-12 Thread Luiz Eneas Costa Junior

Public bug reported:

Occured when upgrading from 23.10 to 24.04

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1
Uname: Linux 6.7.2-060702-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:eneas  2962 F pipewire
 /dev/snd/controlC0:  eneas  2965 F wireplumber
 /dev/snd/controlC1:  eneas  2965 F wireplumber
BuildID: 20240417192958
CasperMD5CheckResult: pass
Channel: Unavailable
Date: Sun May 12 19:38:09 2024
ErrorMessage: o subprocesso do pacote thunderbird, novo script pre-installation 
retornou erro do status de saída 1
ForcedLayersAccel: False
InstallationDate: Installed on 2023-12-15 (149 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
IpRoute:
 default via 192.168.100.1 dev wlo1 proto dhcp src 192.168.100.8 metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.100.0/24 dev wlo1 proto kernel scope link src 192.168.100.8 metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1.1
 apt  2.7.3ubuntu0.1
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 failed to 
install/upgrade: o subprocesso do pacote thunderbird, novo script 
pre-installation retornou erro do status de saída 1
UpgradeStatus: Upgraded to mantic on 2024-05-12 (0 days ago)
dmi.bios.date: 01/15/2024
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G614JU.325
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G614JU
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.72
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG614JU.325:bd01/15/2024:br5.27:efr0.72:svnASUSTeKCOMPUTERINC.:pnROGStrixG614JU_G614JU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG614JU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G614JU_G614JU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package mantic 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/2065541

Title:
  package thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 failed to
  install/upgrade: o subprocesso do pacote thunderbird, novo script pre-
  installation retornou erro do status de saída 1

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


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

[Bug 2064430] Re: Merge net-snmp from Debian unstable for oracular

Nothing to merge yet.

** Changed in: net-snmp (Ubuntu)
   Status: New => Incomplete

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

Title:
  Merge net-snmp from Debian unstable for oracular

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


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

[Bug 2064478] Re: Merge vsftpd from Debian unstable for oracular

We're ahead of Debian, so there's nothing to merge.

** Changed in: vsftpd (Ubuntu)
   Status: New => Incomplete

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

Title:
  Merge vsftpd from Debian unstable for oracular

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


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

[Bug 2064499] Re: Recent qemu packages for Ubuntu 22.04 missing rbd support

Hi Linh,

Thanks for the bug report.

It's strange that you're noticing this discrepancy in behaviour between
minor QEMU versions.  I just double checked and confirmed that there
were no changes to Depends/Recommends relationships between the versions
you mentioned.

I also launched a LXD container here and installed qemu-system-x86
1:6.2+dfsg-2ubuntu6.19.  I can confirm that qemu-block-extra is
automatically installed as well.

Given that I can't reproduce the problem, I am marking this bug as
Incomplete.  Can you please provide more information regarding how to
reproduce it?

Thank you in advance.

** Changed in: qemu (Ubuntu)
   Status: New => Incomplete

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

Title:
  Recent qemu packages for Ubuntu 22.04 missing rbd support

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


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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

** Also affects: qemu (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1975840
   Importance: Unknown
   Status: Unknown

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

Hi again, Björn,

Could you please give the following PPA a try and tell me if the package
works?

https://launchpad.net/~sergiodj/+archive/ubuntu/qemu

The QEMU version there is 1:6.2+dfsg-2ubuntu6.20~ppa1.

Thanks a lot.

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

** Description changed:

+ [ Impact ]
+ 
+ Some versions of Windows hang on reboot if their TSC value is greater
+ than 2^54.  The calibration of the Hyper-V reference time overflows
+ and fails; as a result the processors' clock sources are out of sync.
+ 
+ [ Test Plan ]
+ 
+ TBD.
+ 
+ [ Where problems could occur ]
+ 
+ TBD.
+ 
+ [ Original Description ]
+ 
  Description:
  Some versions of Windows hang on reboot if their TSC value is greater
  than 2^54.  The calibration of the Hyper-V reference time overflows
  and fails; as a result the processors' clock sources are out of sync.
  
  The issue is that the TSC _should_ be reset to 0 on CPU reset and
  QEMU tries to do that.  However, KVM special cases writing 0 to the
  TSC and thinks that QEMU is trying to hot-plug a CPU, which is
  correct the first time through but not later.  Thwart this valiant
  effort and reset the TSC to 1 instead, but only if the CPU has been
  run once.
  
  For this to work, env->tsc has to be moved to the part of CPUArchState
  that is not zeroed at the beginning of x86_cpu_reset.
  
  Solution: [PATCH] target/i386: properly reset TSC on reset
  
  I created and tested a ppa ubuntu package already. The patch fixes this issue.
  Link to ppa: 
https://launchpad.net/~bhinz83/+archive/ubuntu/openstack-rds/+packages
  
  It affects only jammy 22.04 package. The newest version is:
  qemu-1:6.2+dfsg-2ubuntu6.19

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

Thank you Björn for reporting the bug, and Paride for the initial
triage.

As Paride said, we have to make sure this is not affecting other
versions of QEMU as well.  If the patch mentioned in the description is
indeed the only one needed to fix the bug, then I think we're good:

$ git tag --contains 5286c3662294119dc2dd1e9296757337211451f6
v7.0.0
v7.0.0-rc2
v7.0.0-rc3
v7.0.0-rc4
v7.1.0
v7.1.0-rc0
v7.1.0-rc1
v7.1.0-rc2
v7.1.0-rc3
v7.1.0-rc4
v7.2.0
v7.2.0-rc0
v7.2.0-rc1
v7.2.0-rc2
v7.2.0-rc3
v7.2.0-rc4
v7.2.1
v7.2.2
v7.2.3
v7.2.4
v7.2.5
v7.2.6
v7.2.7
v7.2.8
v7.2.9
v8.0.0
v8.0.0-rc0
v8.0.0-rc1
v8.0.0-rc2
v8.0.0-rc3
v8.0.0-rc4
v8.0.1
v8.0.2
v8.0.3
v8.0.4
v8.0.5
v8.1.0
v8.1.0-rc0
v8.1.0-rc1
v8.1.0-rc2
v8.1.0-rc3
v8.1.0-rc4
v8.1.1
v8.1.2
v8.1.3
v8.1.4
v8.1.5
v8.2.0
v8.2.0-rc0
v8.2.0-rc1
v8.2.0-rc2
v8.2.0-rc3
v8.2.0-rc4
v8.2.1

We have QEMU 8.0.4 on Mantic and 8.2.2 on Noble.

@Björn, while it would be good to have reproduction steps for the bug,
we can also rely on your help to verify the correctness of the fix (as
Paride explained).

I'll work on prepare an upload for Jammy meanwhile.

Thanks.

** Changed in: qemu (Ubuntu Jammy)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Windows guest hangs after reboot from the guest OS

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


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

2024-05-08 Thread Sergio Durigan Junior

Thank you, Simon.

I can also confirm that all autopkgtests passed.  Therefore, marking
this bug as verified for Jammy.

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

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

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 2064478] Re: Merge vsftpd from Debian unstable for oracular

2024-05-08 Thread Sergio Durigan Junior

** Changed in: vsftpd (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Merge vsftpd from Debian unstable for oracular

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


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

[Bug 2064028] Re: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn

It's also worth noting that ifupdown is being slowly deprecated in
favour of more modern solutions, like networkd-dispatcher.

Having said that, I tried placing a test script inside /etc/networkd-
dispatcher/routable.d/, but it still doesn't work.

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

Title:
  after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed
  after connecting to openconnect vpn

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


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

[Bug 2064028] Re: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn

Thanks for the bug report.

I am able to reproduce the problem.  There are two things to consider
here:

1) ifupdown is not part of the default desktop image and as such it
needs to be installed anyway.

2) However, even after installing ifupdown, scripts under
/etc/network/if-up.d/ don't get executed when an openvpn connection is
established.

It's still not clear why this is happening, though.

I am marking this bug as Triaged and adding it to our backlog.

** Changed in: openvpn (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed
  after connecting to openconnect vpn

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


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

[Bug 2064201] Re: Use Debian-specific partx path in kpartx rule

Sorry, forgot to comment something else.

In the "Test Plan" section of the SRU text, could you please expand it a
bit and also include an actual execution of the udev rule in question in
order to confirm that the systemd-udev error doesn't happen anymore?  It
is generally not enough to just check if the new udev rule has the
correct path for partx in it; we want to make sure that the execution of
the rule doesn't generate any (new) errors.

Thanks.

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

Title:
  Use Debian-specific partx path in kpartx rule

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


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

[Bug 2064201] Re: Use Debian-specific partx path in kpartx rule

Thank you for the patches.

I uploaded the Focal changes after verifying that the bug is indeed
present there.  Bionic is in ESM now so I decided not to touch it; IIRC
the changes will need to go through another process in this case.

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

Title:
  Use Debian-specific partx path in kpartx rule

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


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

[Bug 2064422] Re: Merge libvirt from Debian unstable for oracular

** Changed in: libvirt (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Merge libvirt from Debian unstable for oracular

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


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

[Bug 2064450] Re: Merge qemu from Debian unstable for oracular

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Merge qemu from Debian unstable for oracular

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


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

[Bug 2064469] Re: Merge sssd from Debian unstable for oracular

** Changed in: sssd (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Merge sssd from Debian unstable for oracular

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


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

[Bug 2064434] Re: Merge openldap from Debian unstable for oracular

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Merge openldap from Debian unstable for oracular

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


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

[Bug 2064457] Re: Merge rsync from Debian unstable for oracular

** Changed in: rsync (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Merge rsync from Debian unstable for oracular

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


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

[Bug 2064096] Re: rsyslog service timeout on noble numbat

2024-04-30 Thread Sergio Durigan Junior

Andreas and I spent some time this afternoon investigating this issue.
Here are our findings.

First, we noticed that the paths being reported by apparmor on dmesg
appear to be relative to /run.  This is just an impression, though: I
believe that, for some reason, apparmor/systemd/something-else is
actually seeing the paths as "/systemd/notify" instead of
"/run/systemd/notify".  Therefore, we decided to try to list those paths
inside the apparmor profile, like:

  /systemd/journal/dev-log rwkl,
  /systemd/notify  rwkl,

Note that we're using "rwkl" just because we don't want to deal with
limiting the scope of each access.

After adding these paths to /etc/apparmor.d/usr.sbin.rsyslogd and
reloading the profile, the service can finally be (re)started.  This
indicates that there's a discrepancy between the paths seeing by
apparmor/systemd/Linux and those seeing by the userspace application.

With that in mind, our next idea was to try to use "systemd-run" to
mimic what's happening with rsyslogd.  This could help us determine
which component is problematic, but unfortunately we were unable to make
the failure happen.  We tried many combinations of commands; some of
them are listed below:

# Try to "ls" the notify socket using different paths
systemd-run -p AppArmorProfile=rsyslogd ls /run/systemd/notify
systemd-run -p AppArmorProfile=rsyslogd ls /systemd/notify

# Likewise, but running the command using the syslog user
systemd-run --uid 102 -p AppArmorProfile=rsyslogd ls /run/systemd/notify
systemd-run --uid 102 -p AppArmorProfile=rsyslogd ls /systemd/notify

Strangely, "ls" was able to properly list the contents of
/run/systemd/notify on both cases (which it shouldn't, because the
apparmor profile doesn't allow it).  It also reported that
"/systemd/notify", which is correct but unexpected (because we thought
that systemd might be the problematic component which doesn't use "/run"
in the paths).  We also double checked and confirmed that the processes
started by "systemd-run" have "systemd" as their parent, so in theory we
should have seen the same problem here.

There is also the fact that these file accesses are being denied even
when the apparmor profile is running in complain mode.  AFAIU, this
shouldn't happen.  Unless apparmor is affecting the path resolution that
happens when the service tries to connect to the socket, effectively
mangling the final path...  but that would be very weird, I believe.

Either way, it is unclear:

1) Why we're seeing these "partial" paths in the logs.

2) Why these accesses are being denied even when the apparmor profile is
in complain mode.

3) Why "systemd-run" can't seem to reproduce the problem.

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

Title:
  rsyslog service timeout on noble numbat

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


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

[Bug 2061740] Re: update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond with 301 redirect to itself

2024-04-17 Thread Sergio Durigan Junior

Thank you for taking the time to file a bug report.

I installed the latest version of apache2 (Jammy) here and could not
reproduce the issue.  Could you please provide a minimal reproducer so
that we can determine if this is indeed a problem with the package?  If
you could, please provide the configuration files for apache2 that you
are using (make sure to remove any confidential/personal information
from them).

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: apache2 (Ubuntu)
   Status: New => Incomplete

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

Title:
  update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond
  with 301 redirect to itself

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


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

[Bug 2062013] [NEW] RM: telegraf from Noble; no longer maintained in Ubuntu

2024-04-17 Thread Sergio Durigan Junior

Public bug reported:

Hi,

Telegraf was added in Ubuntu back in 2020 as part of the LMA (Logging,
Monitoring and Alert) effort, but priorities have changed since then and
the package is no longer maintained in the distribution.  Telegraf is
also one of those "hard" packages to maintain because it requires
bundling of everything it depends on, which makes things very difficult
for the Security team, for example.

The package does not have any reverse dependencies.

** Affects: telegraf (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/2062013

Title:
  RM: telegraf from Noble; no longer maintained in Ubuntu

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


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

[Bug 2061911] Re: check if new addresses for b.root-servers.net is needed

2024-04-17 Thread Sergio Durigan Junior

Doesn't https://bugs.launchpad.net/ubuntu/+source/dns-root-
data/+bug/2045297 already address this?

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

Title:
  check if new addresses for b.root-servers.net is needed

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


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

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Hi Mauricio,

Thanks for the detailed explanations, as usual.

I took some time here to read your patch.  It took me down the rabbit
hole and I did some archaeology to find out what these "inhibit*"
pointers are about.  It was fun; I learned that they were introduced
back in 2012 as a means to allow drivers to signal libvirt when to
inhibit shutdown because there are still VMs around.  But I digress.

I liked your approach here and indeed, it seems simpler than the other
one (although the initial approach was also simple to grasp and elegant;
too bad it didn't work for all cases).

My only comment/question here would be this: the changes to
qemuProcessReconnect mention that they're being done in order to prevent
the XML "corruption" when there's a shutdown detected during
initialization, but (and I may be wrong here) it seems to me that this
new code path could be reached even after the initialization, couldn't
it?  Either way, this is not really important and doesn't affect the
patch (aside from the possible amends to the comments being added), and
it's OK if you don't know the answer, too.

My other source of "concern" here was the reference handling for the new
pointer, but I couldn't find any potential problems with what you did.
Worst case scenario (i.e., if we fail to consider a code path), we will
have a "memory leak" during shutdown, which is not the end of the world.
The lock/unlock dance is also simple and trivially verifiable.

Otherwise, the patch LGTM and I'm satisfied with the testing you did.
Feel free to go ahead and upload it.

Thanks again.

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


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

[Bug 2014964] Re: kea does not manage exported shared library symbols visibility

Still no further activity on the upstream bug, apparently.

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

Title:
  kea does not manage exported shared library symbols visibility

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


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

[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

This is not a bug in ssl-cert.  It's a bug in libapache2-mod-auth-
mellon, more specifically in the way it configures openssl to generate
its certificate.  From /usr/sbin/mellon_create_metadata:

cat >"$TEMPLATEFILE" < Triaged

** Changed in: ssl-cert (Ubuntu Jammy)
   Status: Confirmed => Fix Released

** Changed in: hplip (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

To manage notifications about this bug go to:
https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+subscriptions


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

[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Upstream fix:

https://github.com/latchset/mod_auth_mellon/commit/c6102de6ff651bf763400cb59202d9abe384f615

** Bug watch added: github.com/latchset/mod_auth_mellon/issues #105
   https://github.com/latchset/mod_auth_mellon/issues/105

** Also affects: mod-auth-mellon via
   https://github.com/latchset/mod_auth_mellon/issues/105
   Importance: Unknown
   Status: Unknown

** Tags added: bitesize

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

To manage notifications about this bug go to:
https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+subscriptions


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

** Changed in: squid (Ubuntu Jammy)
   Status: Triaged => 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/2040470

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

Performing the verification on Jammy.

First, verifying that we can reproduce the problem.

# apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:6.2+dfsg-2ubuntu6.18
  Candidate: 1:6.2+dfsg-2ubuntu6.18
  Version table:
 *** 1:6.2+dfsg-2ubuntu6.18 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:6.2+dfsg-2ubuntu6.16 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 1:6.2+dfsg-2ubuntu6 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

# qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split -device 
intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 
4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 
'pc-q35-jammy' is 288

Now, updating the package and verifying that the version from -proposed
fixes the issue:

# apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:6.2+dfsg-2ubuntu6.19
  Candidate: 1:6.2+dfsg-2ubuntu6.19
  Version table:
 *** 1:6.2+dfsg-2ubuntu6.19 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:6.2+dfsg-2ubuntu6.18 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 1:6.2+dfsg-2ubuntu6.16 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 1:6.2+dfsg-2ubuntu6 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

# qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel-irqchip=split 
-device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none 
-m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
...


This concludes the verification on Jammy.

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

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2058023] Re: New versions of amavis with security fixes

Hello Dominic,

Thanks for reporting a bug.

Noble is currently in Feature Freeze, which means that only bug fixes
can be uploaded to the archive.  Based on the release notes for version
2.13.1 of amavisd, there is at least one new feature being introduced in
this release, which makes it unsuitable to be backported right now.

The good news is that amavisd-new is officially supported by Canonical
and therefore the Security team will be able to upload any security
fixes that come out.  The same applies for the versions in Jammy and
Mantic, by the way.

I will make sure to bring this bug to their attention just in case.

Thanks.

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

Title:
  New versions of amavis with security fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/2058023/+subscriptions


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

[Bug 2060752] Re: package samba-common 2:4.15.13+dfsg-0ubuntu1.6 failed to install/upgrade: el subproceso instalado paquete samba-common script post-installation devolvió el código de salida de error

Thank you for taking the time to file a bug report.

This sounds like a local configuration problem.  If you believe this is
a bug in the package, could you please provide more technical details
about what is happening?  Log files from Samba, for example, would help
with the diagnostic.

I see that you also posted a DpkgTerminalLog.txt file, which contains
the following message:

root@alpfa-HP:/# apt-get install samba
E: No se pudo obtener un bloqueo /var/lib/dpkg/lock-frontend. Lo mantiene el 
proceso 4954 (dpkg)
N: Tenga en cuenta que eliminar el archivo de bloqueo no es una solución y 
puede dañar su sistema.
E: No se pudo obtener el bloqueo de la interfaz dpkg 
(/var/lib/dpkg/lock-frontend). ¿Hay otro proceso utilizándolo?
root@alpfa-HP:/# exit
exit
dpkg: error al procesar el paquete samba-common (--configure):
 el subproceso instalado paquete samba-common script post-installation devolvió 
el código de salida de error 1
Configurando libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.6) ...

This indicates that there is a bigger problem at play here; maybe some
leftover lockfile from an unsuccessful apt-get invocation?  Either way,
it doesn't seem to be related to Samba itself.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: samba (Ubuntu)
   Status: New => Incomplete

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

Title:
  package samba-common 2:4.15.13+dfsg-0ubuntu1.6 failed to
  install/upgrade: el subproceso instalado paquete samba-common script
  post-installation devolvió el código de salida de error 1

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


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

[Bug 2060826] Re: hxtools ftbfs in Noble

libhx doesn't FTBFS on Noble.  Closing this as Invalid.

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

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

Title:
  hxtools ftbfs in Noble

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


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

[Bug 2061005] Re: Merge qemu from Debian unstable for noble

2024-04-12 Thread Sergio Durigan Junior

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/qemu/+git/qemu/+merge/464242

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

Title:
  Merge qemu from Debian unstable for noble

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


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

[Bug 2061005] Re: Merge qemu from Debian unstable for noble

2024-04-12 Thread Sergio Durigan Junior

I will use this bug to track the merge of 8.2.2.

QEMU 8.2.3 will be released after the planned Final Freeze, so it may
not be possible to merge it after all.

** Changed in: qemu (Ubuntu)
   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/2061005

Title:
  Merge qemu from Debian unstable for noble

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


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

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

2024-04-12 Thread Sergio Durigan Junior

Hello Giuseppe,

Thank you.  I went ahead and backported the necessary patches.  In
total, I had to backport the following upstream commits:

fb00aa61267c8b9c57a2d1a1fa1e336d02e3bcd1
d7c72735f618a7ee27ee109d8b1468193734606a
cca0a000d06f897411a8af4402e5d0522bbe450b

I uploaded a version of QEMU with the patches to:

https://launchpad.net/~sergiodj/+archive/ubuntu/qemu/+packages

The version is 1:4.2-3ubuntu6.29~ppa1.  Could you take it for a spin,
please?  I'm interested in seeing the results of the scenarios suggested
by Jan (namely, migrating VMs between hosts that have differing states
for XSAVES).

Thank you.

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


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

[Bug 2061005] [NEW] Merge qemu from Debian unstable for noble

Public bug reported:

QEMU 8.2.3 will be released on 2024-04-22.  I will merge it into Noble.

** Affects: qemu (Ubuntu)
 Importance: High
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: New


** Tags: needs-merge upgrade-software-version

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

Title:
  Merge qemu from Debian unstable for noble

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


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

** Description changed:

  This bug tracks the following MRE updates for the Squid package:
  
  Jammy (22.04): 5.9
  
  This update includes bugfixes following the SRU policy exception defined
  at https://wiki.ubuntu.com/SquidUpdates.
  
  [Upstream changes]
  
  http://www.squid-cache.org/Versions/v5/ChangeLog.html
  (Jammy: 5.7..5.9)
  
  The two releases that we are MRE'ing here (5.8 and 5.9) do not contain
  major/noticeable changes per se.  There are quite a few bugfixes, some
  of them generic enough to benefit Ubuntu users, others specifically
  aimed at problems we don't experience (like LLVM-build fixes).  A few
  noteworthy bugfixes have been added to the d/changelog entry.
  
  [Test Plan]
  
  The proposed changes were applied in the following PPA:
  https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages
  
  Build logs can be found for the builds in the PPA linked above. Here are
  the amd64 one:
  
- https://launchpadlibrarian.net/722976147/buildlog_ubuntu-jammy-
- amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz
+ https://launchpadlibrarian.net/724125399/buildlog_ubuntu-jammy-
+ amd64.squid_5.9-0ubuntu0.22.04.1~ppa3_BUILDING.txt.gz
  
  All tests are passing during build time, as shown in the build log
  (builds would fail otherwise, see LP: #2004050).
  
  TODO: add results of local autopkgtest run against all the new Squid
  versions being uploaded here
  
  [Regression Potential]
  
  Upstream tests are always executed during build-time. Failures would
  prevent builds from succeeding.
  
  Squid does not have many reverse dependencies. However, any upgrade is a
  risk to introduce breakage to other packages. Whenever a regression
  occurs in autopkgtests, we will investigate and provide fixes.
  
  TODO: consider any other regression potential specific to the version
  being updated and list them here if any.
  
  [Other Info]
  
  No CVEs are being addressed this time. Therefore, this should go through
  the updates pockets.

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

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 1936449] Re: [SRU] numptyphysics segfault on startup on XUb 21.04

Thanks for the fix.

Uploaded to Focal.

** Changed in: numptyphysics (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: numptyphysics (Ubuntu Focal)
 Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)

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

Title:
  [SRU] numptyphysics segfault on startup on XUb 21.04

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


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

[Bug 1892558] Re: [SRU] binhex always segfaults

Thank you for the patch.

Uploaded to Focal.

** Changed in: macutils (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: macutils (Ubuntu Focal)
 Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)

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

Title:
  [SRU] binhex always segfaults

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


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

** Description changed:

  This bug tracks the following MRE updates for the Squid package:
  
  Jammy (22.04): 5.9
  
  This update includes bugfixes following the SRU policy exception defined
  at https://wiki.ubuntu.com/SquidUpdates.
  
  [Upstream changes]
  
  http://www.squid-cache.org/Versions/v5/ChangeLog.html
  (Jammy: 5.7..5.9)
  
- TODO: List the major changes introduced in this release
+ The two releases that we are MRE'ing here (5.8 and 5.9) do not contain
+ major/noticeable changes per se.  There are quite a few bugfixes, some
+ of them generic enough to benefit Ubuntu users, others specifically
+ aimed at problems we don't experience (like LLVM-build fixes).  A few
+ noteworthy bugfixes have been added to the d/changelog entry.
  
  [Test Plan]
  
  The proposed changes were applied in the following PPA:
  https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages
  
  Build logs can be found for the builds in the PPA linked above. Here are
  the amd64 one:
  
  https://launchpadlibrarian.net/722976147/buildlog_ubuntu-jammy-
  amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz
  
  All tests are passing during build time, as shown in the build log
  (builds would fail otherwise, see LP: #2004050).
  
  TODO: add results of local autopkgtest run against all the new Squid
  versions being uploaded here
  
  [Regression Potential]
  
  Upstream tests are always executed during build-time. Failures would
  prevent builds from succeeding.
  
  Squid does not have many reverse dependencies. However, any upgrade is a
  risk to introduce breakage to other packages. Whenever a regression
  occurs in autopkgtests, we will investigate and provide fixes.
  
  TODO: consider any other regression potential specific to the version
  being updated and list them here if any.
  
  [Other Info]
  
  No CVEs are being addressed this time. Therefore, this should go through
  the updates pockets.

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

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

** Description changed:

  This bug tracks the following MRE updates for the Squid package:
  
  Jammy (22.04): 5.9
  
  This update includes bugfixes following the SRU policy exception defined
  at https://wiki.ubuntu.com/SquidUpdates.
  
  [Upstream changes]
  
  http://www.squid-cache.org/Versions/v5/ChangeLog.html
  (Jammy: 5.7..5.9)
  
  TODO: List the major changes introduced in this release
  
  [Test Plan]
  
- TODO: link the build log containing all tests being executed
+ The proposed changes were applied in the following PPA:
+ https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages
  
- TODO: All tests are passing during build time, as shown in the build log
+ Build logs can be found for the builds in the PPA linked above. Here are
+ the amd64 one:
+ 
+ https://launchpadlibrarian.net/722976147/buildlog_ubuntu-jammy-
+ amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz
+ 
+ All tests are passing during build time, as shown in the build log
  (builds would fail otherwise, see LP: #2004050).
  
  TODO: add results of local autopkgtest run against all the new Squid
  versions being uploaded here
  
  [Regression Potential]
  
  Upstream tests are always executed during build-time. Failures would
  prevent builds from succeeding.
  
  Squid does not have many reverse dependencies. However, any upgrade is a
  risk to introduce breakage to other packages. Whenever a regression
  occurs in autopkgtests, we will investigate and provide fixes.
  
  TODO: consider any other regression potential specific to the version
  being updated and list them here if any.
  
  [Other Info]
  
- TODO-A: No CVEs are being addressed this time. Therefore, this should go
- through the updates pockets.
- 
- TODO-B: CVEs TBD are being addressed by these updates. Therefore, this
- update should go through the security pocket.
- 
- TODO: list previous MREs for this package, if any.
+ No CVEs are being addressed this time. Therefore, this should go through
+ the updates pockets.

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

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/squid/+git/squid/+merge/464045

** Changed in: squid (Ubuntu Jammy)
   Status: New => Triaged

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

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 2040470] Re: Upstream microrelease of squid 5.9

Ah, got it.  I've added "of squid" in the title now, should read better
on Pinot.  Thanks!

** Summary changed:

- Upstream microrelease 5.9
+ Upstream microrelease of squid 5.9

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

Title:
  Upstream microrelease of squid 5.9

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


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

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Tags added: server-todo

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


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

[Bug 2040470] Re: Upstream microrelease 5.9

Hi Bryce,

I'm following the same title pattern as established by Athos, which I
think is better in this case.  Just leaving the explanation here :-).

** Summary changed:

- Upstream microrelease of squid 5.9 for noble
+ Upstream microrelease 5.9

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

Title:
  Upstream microrelease 5.9

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


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

[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

2024-04-09 Thread Sergio Durigan Junior

I talked to Marc to understand whether the security team had any plans
to "fix" this problem, and he raised a valid point: from his perspective
(and the Security team's as well, I gather), this is not a bug because
we have two services trying to listen on the same port.  The "fix" here
is to adjust the local configuration, as mentioned in the comments
above.

I'm reverting this bug's state to Invalid, then.

** Changed in: dnsmasq (Ubuntu)
 Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

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


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

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

2024-04-08 Thread Sergio Durigan Junior

Hello Jan,

Thank you for reporting this bug, and for providing a good initial
analysis of the problem.

Would you have access to a host with an EPYC-Rome CPU where you can run
some tests?  This is something that needs to be done in order to proceed
here, especially if we indeed decide to SRU this change into Focal.

Thanks.

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


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

Re: [Bug 2058576] Re: FTBFS: armhf: build-time test failures

On Wednesday, April 03 2024, Andreas Hasenack wrote:

> It is enabled:
>
> Types: deb
> URIs: http://ports.ubuntu.com/ubuntu-ports
> Suites: noble noble-updates noble-backports noble-proposed
> Components: main universe restricted multiverse
> Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
>
>
> Or is there some other trick specific to the state noble is in now?

Not that I know of.  I only commented because you didn't mention
noble-updates on your first message and I thought it was worth bringing
it up.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  FTBFS: armhf: build-time test failures

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


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

Re: [Bug 2058576] Re: FTBFS: armhf: build-time test failures

On Wednesday, April 03 2024, Andreas Hasenack wrote:

> This is very hard to troubleshoot at the moment, because I just can't
> get the build-dependencies installed, either with noble or noble-
> proposed:

I think you need to enable noble-updates.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  FTBFS: armhf: build-time test failures

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


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

[Bug 2040470] Re: MRE updates of squid for noble

** Also affects: squid (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: squid (Ubuntu Noble)

** Changed in: squid (Ubuntu Jammy)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Tags added: server-todo

** Description changed:

- Backport squid as MRE to noble once the update for noble has been
- completed.
+ This bug tracks the following MRE updates for the Squid package:
  
- 
+ [Release codename] ([Release version]): Squid [Squid version]
+ [...] 
  
- [Impact]
- TBD
+ This update includes bugfixes following the SRU policy exception defined
+ at https://wiki.ubuntu.com/SquidUpdates.
  
- [Major Changes]
- TBD
+ [Upstream changes]
+ 
+ TODO: Add a link to the upstream changelog
+ 
+ TODO: List the major changes introduced in this release
  
  [Test Plan]
- TBD
+ 
+ TODO: link the build log containing all tests being executed
+ 
+ TODO: All tests are passing during build time, as shown in the build log
+ (builds would fail otherwise, see LP: #2004050).
+ 
+ TODO: add results of local autopkgtest run against all the new Squid
+ versions being uploaded here
  
  [Regression Potential]
- Upstream has an extensive build and integration test suite. So regressions 
would likely arise from a change in interaction with Ubuntu-specific 
integrations, such as in relation to the versions of dependencies available and 
other packaging-specific matters.
- 
+ 
+ Upstream tests are always executed during build-time. Failures would
+ prevent builds from succeeding.
+ 
+ Squid does not have many reverse dependencies. However, any upgrade is a
+ risk to introduce breakage to other packages. Whenever a regression
+ occurs in autopkgtests, we will investigate and provide fixes.
+ 
+ TODO: consider any other regression potential specific to the version
+ being updated and list them here if any.
+ 
+ [Other Info]
+ 
+ TODO-A: No CVEs are being addressed this time. Therefore, this should go
+ through the updates pockets.
+ 
+ TODO-B: CVEs TBD are being addressed by these updates. Therefore, this
+ update should go through the security pocket.
+ 
+ TODO: list previous MREs for this package, if any.

** Summary changed:

- MRE updates of squid for noble
+ Upstream microrelease 5.9

** Description changed:

  This bug tracks the following MRE updates for the Squid package:
  
- [Release codename] ([Release version]): Squid [Squid version]
- [...] 
+ Jammy (22.04): 5.9
  
  This update includes bugfixes following the SRU policy exception defined
  at https://wiki.ubuntu.com/SquidUpdates.
  
  [Upstream changes]
  
- TODO: Add a link to the upstream changelog
+ http://www.squid-cache.org/Versions/v5/ChangeLog.html
+ (Jammy: 5.7..5.9)
  
  TODO: List the major changes introduced in this release
  
  [Test Plan]
  
  TODO: link the build log containing all tests being executed
  
  TODO: All tests are passing during build time, as shown in the build log
  (builds would fail otherwise, see LP: #2004050).
  
  TODO: add results of local autopkgtest run against all the new Squid
  versions being uploaded here
  
  [Regression Potential]
  
  Upstream tests are always executed during build-time. Failures would
  prevent builds from succeeding.
  
  Squid does not have many reverse dependencies. However, any upgrade is a
  risk to introduce breakage to other packages. Whenever a regression
  occurs in autopkgtests, we will investigate and provide fixes.
  
  TODO: consider any other regression potential specific to the version
  being updated and list them here if any.
  
  [Other Info]
  
  TODO-A: No CVEs are being addressed this time. Therefore, this should go
  through the updates pockets.
  
  TODO-B: CVEs TBD are being addressed by these updates. Therefore, this
  update should go through the security pocket.
  
  TODO: list previous MREs for this package, if any.

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

Title:
  Upstream microrelease 5.9

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


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

[Bug 2060016] Re: package mysql-server-8.0 8.0.36-0ubuntu0.22.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

*** This bug is a duplicate of bug 2019003 ***
https://bugs.launchpad.net/bugs/2019003

Thank you for reporting a bug.

This is a duplicate of bug #2019003, so I marked it as such.  Please
take a look at that other bug, there may be a workaround available for
this case.

Thanks.

** This bug has been marked a duplicate of bug 2019003
   package mysql-server-8.0 8.0.33-0ubuntu0.22.04.1 failed to install/upgrade: 
Can't start server: Bind on TCP/IP port: Address already in use

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

Title:
  package mysql-server-8.0 8.0.36-0ubuntu0.22.04.1 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2060016/+subscriptions


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

[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

2024-04-02 Thread Sergio Durigan Junior

I was able to reproduce the bug on Focal, and since we seem to carry the
same version on Jammy/Mantic (and likely Noble), it's probable that the
bug also happens in those releases.

For future reference:

# apt install -y libvirt-daemon-system bind9 dnsmasq

Reboot, and try bringing up the "default" network on libvirt:

# virsh net-start default
error: Failed to start network default
error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: 
dnsmasq: failed to create listening socket for 192.168.122.1: Address already 
in use

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

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


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

[Bug 2060036] [NEW] No se ha podido calcular la actualización Se produjo un problema irresoluble al calcular la actualización. Esto podría deberse a: * Paquetes de software no oficiales, no propor

2024-04-02 Thread junior

Public bug reported:

No se ha podido calcular la actualización

Se produjo un problema irresoluble al calcular la actualización.

 Esto podría deberse a:
 * Paquetes de software no oficiales, no proporcionados por Ubuntu
Utilice la herramienta «ppa-purge» desde el paquete 
ppa-purge para quitar software de una PPA de Launchpad PPA e 
intente actualizar de nuevo.

Si nada de esto es aplicable, entonces informe de este error usando el
comando «ubuntu-bug ubuntu-release-upgrader-core» en una terminal. Si
quiere investigar el problema por su cuenta, los registros en
«/var/log/dist-upgrade» contienen detalles de la actualización; en
particular, consulte «main.log» y «apt.log».

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.41
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  2 15:35:48 2024
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2024-04-02 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade 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/2060036

Title:
  No se ha podido calcular la actualización  Se produjo un problema
  irresoluble al calcular la actualización.   Esto podría deberse a:  *
  Paquetes de software no oficiales, no proporcionados por Ubuntu
  Utilice la herramienta «ppa-purge» desde el paquete  ppa-purge para
  quitar software de una PPA de Launchpad PPA e  intente actualizar de
  nuevo.

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


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

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

2024-04-01 Thread Sergio Durigan Junior

Mauricio asked me to review the debdiff for Focal as well.

This debdiff is different because he had to implement some code to
synchronize the destruction of the worker threads with the free'ing of
the thread pool.

I looked at the new code, analyzed it as best as I could, asked a few
questions to Mauricio regarding the new environment variable being
created, and finally got convinced that everything seems OK.  The
implementation is sound and the concept is simple: qemuStateCleanupWait
acts similarly to a thread barrier and makes sure that all threads
previously created by qemuProcessReconnect are able to finish before
qemuStateCleanup can proceed.

In a nutshell: LGTM, +1.

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


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

[Bug 2059971] [NEW] .E: No se pudo obtener un bloqueo /var/lib/apt/lists/lock. Lo mantiene el proceso 7098 (jammy)

2024-04-01 Thread junior

Public bug reported:

$ sudo apt update
Leyendo lista de paquetes... Hecho
E: No se pudo obtener un bloqueo /var/lib/apt/lists/lock. Lo mantiene el 
proceso 7098 (jammy)
N: Tenga en cuenta que eliminar el archivo de bloqueo no es una solución y 
puede dañar su sistema.
E: No se pudo bloquear el directorio /var/lib/apt/lists/
$ sudo apt-get update
Leyendo lista de paquetes... Hecho
E: No se pudo obtener un bloqueo /var/lib/apt/lists/lock. Lo mantiene el 
proceso 7098 (jammy)
N: Tenga en cuenta que eliminar el archivo de bloqueo no es una solución y 
puede dañar su sistema.
E: No se pudo bloquear el directorio /var/lib/apt/lists/

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.41
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 21:53:28 2024
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2024-04-01 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade 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/2059971

Title:
  .E: No se pudo obtener un bloqueo /var/lib/apt/lists/lock. Lo mantiene
  el proceso 7098 (jammy)

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


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

[Bug 2055151] Re: kea-ctrl-agent segfault in ppc64el dep8 test

2024-03-28 Thread Sergio Durigan Junior

After some more debugging/testing, it seems like the problem is indeed
caused by compiler optimization.  More specifically, LTO.  Disabling it
seems to have done the trick, and I can't reproduce the segmentation
fault anymore.

Basically:

ifeq ($(DEB_HOST_ARCH),ppc64el)
export DEB_BUILD_MAINT_OPTIONS += optimize=-lto
endif

on d/rules.

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

Title:
  kea-ctrl-agent segfault in ppc64el dep8 test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/2055151/+subscriptions


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

[Bug 2051754] Re: Live migration fails (missing vmx features)

2024-03-28 Thread Sergio Durigan Junior

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

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

Title:
  Live migration fails (missing vmx features)

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-03-28 Thread Sergio Durigan Junior

Thank you, Andreas.

I will wait for bug #2046439 to clear -proposed.

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

Performing the verification on Mantic.

First, verifying that we can reproduce the problem.

# apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3
  Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3
  Version table:
 *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.0.4+dfsg-1ubuntu3.23.10.2 500
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
 1:8.0.4+dfsg-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

# qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split -device 
intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 
4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 
'pc-q35-jammy' is 288

# qemu-system-x86_64 -M pc-q35-mantic,accel=kvm,kernel-irqchip=split -device 
intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 
4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 
'pc-q35-mantic' is 288

Now, updating the package and verifying that the version from -proposed
fixes the issue:

# apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.5
  Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.5
  Version table:
 *** 1:8.0.4+dfsg-1ubuntu3.23.10.5 100
100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.0.4+dfsg-1ubuntu3.23.10.3 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
 1:8.0.4+dfsg-1ubuntu3.23.10.2 500
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
 1:8.0.4+dfsg-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

# qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel-irqchip=split 
-device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none 
-m 4096M -nographic -kern
el /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon 
chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0"
qemu-system-x86_64: warning: Number of SMP cpus requested (300) exceeds the 
recommended cpus supported by KVM (12)
qemu-system-x86_64: warning: Number of hotpluggable cpus requested (300) 
exceeds the recommended cpus supported by KVM (12)
...


# qemu-system-x86_64 -M pc-q35-mantic-maxcpus,accel=kvm,kernel-irqchip=split 
-device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none 
-m 4096M -nographic -kern
el /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon 
chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0"
qemu-system-x86_64: warning: Number of SMP cpus requested (300) exceeds the 
recommended cpus supported by KVM (12)
qemu-system-x86_64: warning: Number of hotpluggable cpus requested (300) 
exceeds the recommended cpus supported by KVM (12)
...



This concludes the verification on Mantic.

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

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

OK, I tested the fixed package from your PPA and verified that it indeed
solves the issue.

Just to reiterate, then: LGTM, +1!

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


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

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Hah, I didn't see your comment before I posted mine.  Mid air conflict!

Anyway, thanks for providing the PPA.  I'll take it for a spin :-).

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


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

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Mauricio,

Wow!  Such an awesome reproducer.  Very detailed and easy to follow.
Thanks for providing it.

I was able to verify the problem here, and looked at the upstream
patch[1] that fixes it.  The rationale makes sense to me, although that
cleanup function is pretty involved and it's hard to say if there can be
any fallout from moving the worker thread pool freeing action earlier.

I looked at the upstream repository and could not find any amends/fixes
to the commit in question.  It's present in Mantic and Noble, which is a
good sign.

Do you have a PPA build that I can try with the reproducer to check the
fix, please?

Otherwise, this LGTM and I'm +1 on proceeding with the SRU.  Thanks!

[1]: For reference:
https://gitlab.com/libvirt/libvirt/-/commit/152770333449cd3b78b4f5a9f1148fc1f482d842

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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

2024-03-26 Thread 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 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-03-25 Thread Sergio Durigan Junior

Fixed package uploaded to Mantic:
qemu_8.0.4+dfsg-1ubuntu3.23.10.5_source.changes

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-03-25 Thread Sergio Durigan Junior

Performing the verification on Mantic.

First, reproduce the problem.

# apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3
  Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3
  Version table:
 *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.0.4+dfsg-1ubuntu3.23.10.2 500
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
 1:8.0.4+dfsg-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

# qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split -device 
intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 
4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 
'pc-q35-jammy' is 288

# qemu-system-x86_64 -M pc-q35-mantic,accel=kvm,kernel-irqchip=split -device 
intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 
4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 
'pc-q35-mantic' is 288


Now, verifying that the package from mantic-proposed fixes the issue:

# apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.4
  Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.4
  Version table:
 *** 1:8.0.4+dfsg-1ubuntu3.23.10.4 100
100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.0.4+dfsg-1ubuntu3.23.10.3 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
 1:8.0.4+dfsg-1ubuntu3.23.10.2 500
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
 1:8.0.4+dfsg-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

# qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel-irqchip=split 
-device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none 
-m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
< all worked as expected >

# qemu-system-x86_64 -M pc-q35-mantic-maxcpus,accel=kvm,kernel-irqchip=split 
-device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none 
-m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev 
stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 
-append "console=ttyS0"
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 
'pc-q35-mantic-maxcpus' is 288

As can be seen above, there is a problem with the new pc-q35-mantic-
maxcpus machine type.  As such, I am tagging this bug as verification-
mantic-failed and will upload a fix for the issue.

** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-failed-mantic

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-03-21 Thread Sergio Durigan Junior

** Changed in: qemu (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: qemu (Ubuntu Mantic)
   Status: Confirmed => In Progress

** Changed in: qemu (Ubuntu Noble)
   Status: Confirmed => Fix Committed

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

Re: [Bug 2058576] [NEW] FTBFS: armhf: build-time test failures

2024-03-20 Thread Sergio Durigan Junior

On Wednesday, March 20 2024, Andreas Hasenack wrote:

> Public bug reported:
>
> sssd is currently failing to build on armhf due to build-time test
> failures[1]¨:

Without having checked anything: is this not related to the time_t
transition?  The build was passing before.

I'll check more tomorrow.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  FTBFS: armhf: build-time test failures

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-03-20 Thread Sergio Durigan Junior

** Tags added: server-todo

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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

2024-03-19 Thread 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 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

2024-03-19 Thread Sergio Durigan Junior

Hi Jeff,

Thanks for the offer.  Actually there is!

- If you could test Noble and double/triple check that we don't need to
do anything else there in order to support maxcpus, that'd be great.
Just use the "ubuntu" machine type and check if QEMU starts correct with
more than 288 vCPUs.

- Once the Jammy/Mantic SRUs are accepted, we will need to perform a
verification for both uploads.  I can do it my side, but it would be
very helpful if you could also verify the uploads on your side.

Thanks.

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

** Description changed:

  [ Impact ]
  
- QEMU users on Ubuntu Jammy who try to spawn a VM with more than 288
- vCPUs will not be able to do so, because the machine types available
+ QEMU users on Ubuntu Jammy/Mantic who try to spawn a VM with more than
+ 288 vCPUs will not be able to do so, because the machine types available
  don't support such scenario.  The following error will happen:
  
  qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by
  machine 'pc-q35-jammy' is 288
  
  [ Test Plan ]
  
  Ideally, the test should be performed in a machine with more than 288
  physical CPUs available.  However, due to the difficulty in finding such
  systems, it is possible to emulate the usage of more than 288 vCPUs.
  
- On a Jammy machine, you can do:
+ On a Jammy/Mantic machine, making sure to adjust the machine type
+ accordingly, you can do:
  
  $ sudo qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split
  -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm
  -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd
  /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon
  chardev=char0,mode=readline -serial chardev:char0 -append
  "console=ttyS0"
  
  You will notice that the command will fail, as expected.
  
- The proposed fix is to create a new machine type on Jammy, in order to
- minimize the possibility of regressions in deployments using the
- existing machine types.  This new type is named pc-{q35,i440fx}-jammy-
- maxcpus.  When doing the test, make sure to provide this new machine
- type (as part of the "-M" argument).
+ The proposed fix is to create a new machine type on Jammy/Mantic, in
+ order to minimize the possibility of regressions in deployments using
+ the existing machine types.  This new type is named
+ pc-{q35,i440fx}-{jammy,mantic}-maxcpus.  When doing the test, make sure
+ to provide this new machine type (as part of the "-M" argument).
  
  [ Where problems could occur ]
  
  As explained above, a new machine type was created in order to minimize
  the possibility of regressions.  As such, the existing
- "pc-{q35,i440fx}-jammy" machine types should continue to work as before,
- without any change.
+ "pc-{q35,i440fx}-{jammy,mantic}" machine types should continue to work
+ as before, without any change.
  
  [ Original Description ]
  
  During testing of an AMD Genoa CPU, it was discovered that qemu-system-
  amd64 doesn't support enough cpus.
  
  The specific error the tester received was:
  
  qemu-system-x86_64: Invalid SMP CPUs 384. The max supported by machine
  'pc-q35-7.1' is 288
  
  Looking at the sournce that seems to be an easy fix at first glance:
  
  https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c
  372machine_class_allow_dynamic_sysbus_dev(m, TYPE_VMBUS_BRIDGE);
  373m->max_cpus = 288;

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

** Description changed:

+ [ Impact ]
+ 
+ QEMU users on Ubuntu Jammy who try to spawn a VM with more than 288
+ vCPUs will not be able to do so, because the machine types available
+ don't support such scenario.  The following error will happen:
+ 
+ qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by
+ machine 'pc-q35-jammy' is 288
+ 
+ [ Test Plan ]
+ 
+ Ideally, the test should be performed in a machine with more than 288
+ physical CPUs available.  However, due to the difficulty in finding such
+ systems, it is possible to emulate the usage of more than 288 vCPUs.
+ 
+ On a Jammy machine, you can do:
+ 
+ $ sudo qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split
+ -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm
+ -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd
+ /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon
+ chardev=char0,mode=readline -serial chardev:char0 -append
+ "console=ttyS0"
+ 
+ You will notice that the command will fail, as expected.
+ 
+ The proposed fix is to create a new machine type on Jammy, in order to
+ minimize the possibility of regressions in deployments using the
+ existing machine types.  This new type is named pc-{q35,i440fx}-jammy-
+ maxcpus.  When doing the test, make sure to provide this new machine
+ type (as part of the "-M" argument).
+ 
+ [ Where problems could occur ]
+ 
+ As explained above, a new machine type was created in order to minimize
+ the possibility of regressions.  As such, the existing
+ "pc-{q35,i440fx}-jammy" machine types should continue to work as before,
+ without any change.
+ 
+ [ Original Description ]
+ 
  During testing of an AMD Genoa CPU, it was discovered that qemu-system-
  amd64 doesn't support enough cpus.
  
  The specific error the tester received was:
  
  qemu-system-x86_64: Invalid SMP CPUs 384. The max supported by machine
  'pc-q35-7.1' is 288
  
  Looking at the sournce that seems to be an easy fix at first glance:
  
  https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c
  372machine_class_allow_dynamic_sysbus_dev(m, TYPE_VMBUS_BRIDGE);
  373m->max_cpus = 288;

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

Title:
  qemu-system-amd64 max cpus is too low for latest processors

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


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

[Bug 2058278] Re: [Backport] libvirt-daemon-system won't install on Focal

Thanks, Guilherme.

I found:

https://salsa.debian.org/utopia-
team/polkit/-/commit/81c21cdadbe0a98ca016738b8c2cc7d4f225f067

and then:

https://salsa.debian.org/libvirt-
team/libvirt/-/commit/b9b2923abfae8ec80507bc267767db4b51fb4021

which explain why we're depending on polkitd.  So yeah, I believe
Guilherme's suggestion might be enough to fix this issue on Focal.

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

Title:
  [Backport] libvirt-daemon-system won't install on Focal

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


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

[Bug 2058278] Re: [Backport] libvirt-daemon-system won't install on Focal