date:20240826

Thanks for the bug report. Since most gnome-shell leaks are caused by
extensions, the first thing to try is to remove all extensions. Please
run:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

** Tags added: gnome-shell-leak

** Package changed: gnome-shell (Ubuntu) => ubuntu

** Changed in: 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/2077848

Title:
  gnome shell is using many rams ~ 2.6gb

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


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

[Bug 2077509] Re: Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz

Shouldn't this be backported to Jammy for hwe 6.11?

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

Title:
  Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2077509/+subscriptions


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

[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part

** Also affects: linux (Ubuntu Jammy)
   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/1959940

Title:
  [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer
  keys - kernel part

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


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

[Bug 2077600] Re: Noble update: upstream stable patchset 2024-08-22

drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc 
applies for CVE-2024-42228
 scsi: mpi3mr: Sanitise num_phys applied for CVE-2024-42159

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-42159

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-42228

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => 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/2077600

Title:
  Noble update: upstream stable patchset 2024-08-22

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


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

[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland

2024-08-26 Thread Nathan Teodosio

So you mean 'in Chrome', right?

I can indeed no longer reproduce #12.0... Either I screwed up during
testing or something changed in between, which is highly unlikely in
such a short time frame.

Anyway, added debug statements confirm that Chromium is running with
GTK3. Additionally, it DOES receive the resolution signal, but in Ozone
Wayland, it thinks the display configuration did nonetheless not change
and does not goes further.

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

Title:
  Gnome's large text accessibility setting not reflect in Chromium in
  Wayland

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


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

[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => 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/2072679

Title:
  Regression: unable to reach low idle states on Tiger Lake

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


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

[Bug 2076361] Re: Lenovo X12 Detachable Gen 2 unresponsive under light load

No need to include linux-signed and linux-signed-lowlatency. Linux will
suffice. Marking them as invalid

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

** Changed in: linux-signed (Ubuntu)
   Status: New => Invalid

** Changed in: linux-signed (Ubuntu Noble)
   Status: New => Invalid

** Changed in: linux-signed-lowlatency (Ubuntu)
   Status: New => Invalid

** Changed in: linux-signed-lowlatency (Ubuntu Noble)
   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/2076361

Title:
  Lenovo X12 Detachable Gen 2 unresponsive under light load

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


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

[Bug 2074376] Re: Disable PCI_DYNAMIC_OF_NODES in Ubuntu

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

Title:
  Disable PCI_DYNAMIC_OF_NODES in Ubuntu

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


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

[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part

Hello Janosch,
many thanks for the patch set!
I'm just back and will work on this soon-ish.
But just to clarify, are these all plain cherry-picks from upstream - or did 
you had to do any real backport work to get some of the commits applied to the 
jammy kernel (I mean if any real modifications of code or context were needed)?
I just need to add this to the PR/provenance - for our kernel team.
I could of course also compare the patches you've sent with what exists 
upstream, but I think you know it right away ...
(Of course talking about the kernel patches/commits only.)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Frank Heimes (fheimes)

** Changed in: linux (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/1959940

Title:
  [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer
  keys - kernel part

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


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

[Bug 2077515] Re: Network Manager applet shows back-slash escapes for non-latin characters

It's now in updates:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2074197

** Changed in: netplan.io (Ubuntu)
   Status: Fix Committed => 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/2077515

Title:
  Network Manager applet shows back-slash escapes for non-latin
  characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077515/+subscriptions


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

[Bug 2074197] Re: [SRU] Backport netplan.io 1.0.1-1ubuntu2 to 24.04

** Changed in: netplan.io (Ubuntu)
   Status: New => 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/2074197

Title:
  [SRU] Backport netplan.io 1.0.1-1ubuntu2 to 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2074197/+subscriptions


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

[Bug 2073695] Re: Deadlock occurs while suspending md raid

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => 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/2073695

Title:
   Deadlock occurs while suspending md raid

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


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

Re: [Bug 2077766] Re: Dell Ultrasharp 4919DW

2024-08-26 Thread Steven Andrew Lawrence

Thanks, so this is an X1 I have an office full of X1s running on this dell
I am using the Dell usb I have tried with a unetech cable. I will bring the
laptop to the office and try on a different 4919DW. just to add info. As I
said it did work with no hardware changes for about a year then after an
update it stopped working ( It stopped detecting that it was a dell
monitor) and stopped detecting the correct resolution

On Mon, 26 Aug 2024 at 08:30, Daniel van Vugt <2077...@bugs.launchpad.net>
wrote:

> I've noticed through multiple bug reports that recent kernels have
> become pedantic about bandwidth requirements and therefore which
> resolutions they are willing to offer.
>
> Also 5120x1440 at 60Hz is right near the limit of what the i7-8565U can
> do:
>
> https://ark.intel.com/content/www/us/en/ark/products/149091/intel-
> core-i7-8565u-processor-8m-cache-up-to-4-60-ghz.html#tab-blade-1-0-4
> 
>
> Still, if it worked before then you probably just need either:
>
>  * A higher grade USB-C (or better yet Thunderbolt) cable that will work
> on more kernel versions; or
>  * To try various older and newer kernel versions to see which are willing
> to offer the full resolution.
>
>
> ** No longer affects: mutter (Ubuntu)
>
> ** Summary changed:
>
> - Dell Ultrasharp 4919DW
> + [i915] Dell Ultrasharp 4919DW only achieves half of native resolution
>
> ** Tags added: regression-update
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2077766
>
> Title:
>   [i915] Dell Ultrasharp 4919DW only achieves half of native resolution
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   Hi :) hope all is well
>
>   The Dell Ultrasharp 4919DW monitor is no longer detected correctly in
>   Ubuntu after a recent update, causing it to only display a resolution
>   of 1024x768 instead of its native 5120x1440 (32:9) resolution over
>   USB-C.
>
>   Steps to Reproduce:
>
>   Connect the Dell Ultrasharp 4919DW monitor to a laptop running Ubuntu
> via USB-C.
>   Observe that the monitor is detected as a "PNP screen" instead of "Dell"
> and defaults to a resolution of 1024x768.
>   Attempt to change the screen mode to achieve higher resolution. The
> maximum available resolution is 2560x1440 (2K), but it only uses half of
> the screen. PBP mode on the screen
>   Reload the system with the latest Ubuntu LTS version.
>   Repeat the steps on another laptop using Linux Mint.
>   Expected Result:
>   The monitor should be detected as a Dell Ultrasharp 4919DW and should
> display at its full native resolution of 5120x1440.
>
>   Actual Result:
>   The monitor is detected as a generic "PNP screen" with a default
> resolution of 1024x768. Changing the screen mode to pbp only achieves
> 2560x1440, which utilizes only half of the screen.
>
>   Additional Information:
>
>   The issue persists after reloading the system with the latest Ubuntu LTS
> version.
>   The issue also occurs on another laptop running Linux Mint.
>   The monitor works correctly on a Windows system, displaying at its full
> 5120x1440 resolution.
>   thanks
>   Steve
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 24.04
>   Package: xorg 1:7.7+23ubuntu3
>   ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
>   Uname: Linux 6.8.0-38-generic x86_64
>   NonfreeKernelModules: zfs
>   ApportVersion: 2.28.1-0ubuntu3
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Aug 23 21:40:31 2024
>   DistUpgraded: Fresh install
>   DistroCodename: noble
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev
> 02) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2292]
>   InstallationDate: Installed on 2024-05-21 (95 days ago)
>   InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64
> (20240424)
>   MachineType: LENOVO 20QD001NZA
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_yno3im@/vmlinuz-6.8.0-38-generic
> root=ZFS=rpool/ROOT/ubuntu_yno3im ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/06/2022
>   dmi.bios.release: 1.56
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N2HET73W (1.56 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20QD001NZA
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0K17763 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis

[Bug 2077757] Re: nautilus crashes when trying to open a folder

2024-08-26 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. However, your crash report is either missing or challenging to deal 
with as a '.crash' file. Please follow these instructions to have apport report 
a new bug about your crash that can be dealt with by the automatic retracer. 
 
 If you are running the Ubuntu Stable Release you might need to enable apport 
in /etc/default/apport and restart. 
 
 If you are using Ubuntu with the Gnome desktop environment - launch nautilus 
and navigate to your /var/crash directory and double click on the crash report 
you wish to submit. 
 
 If you are using Kubuntu or Xubuntu you can file the crash using 
/usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a 
terminal - where _my_crash_report.crash is the crash you would like to report. 
 I'm closing this bug report since the process outlined above will 
automatically open a new bug report which can then dealt with more efficiently. 
Thanks in advance for your cooperation and understanding.

** Changed in: nautilus (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/2077757

Title:
  nautilus crashes when trying to open a folder

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


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

[Bug 2077633] Re: Partitions in left panel are not in order

2024-08-26 Thread Sebastien Bacher

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

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/3553
   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/2077633

Title:
  Partitions in left panel are not in order

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


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

[Bug 2073695] Re: Deadlock occurs while suspending md raid

2024-08-26 Thread Meir Elisha

Hi @philcox

much appreciated!
Thanks.

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

Title:
   Deadlock occurs while suspending md raid

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


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

[Bug 2077830] Re: libffi is installed but now compilers problem

2024-08-26 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions: 
 
 * Is this reproducible? 
 * If so, what specific steps should we take to recreate this bug? 
 
 This will help us to find and resolve the problem.

** Changed in: glib2.0 (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/2077830

Title:
  libffi is installed but now compilers problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2077830/+subscriptions


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

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

Yes quite a few people have reported similar problems this year with
Ubuntu's newer kernels. But I don't recall any of them being proven to
be obvious software bugs. Just a more conservative bandwidth
calculation, usually solved with a new cable.

If you want to go to maximum quality, I recommend the Apple Thunderbolt
4 Pro cables to avoid such issues. But that's a lot of money so probably
the option of last resort.

We do have a software option that might help too. In
~/.config/monitors.xml you can add maxbpc:

  
...
8
  

Choose 8 or 6 and then log in again. That should reduce the bandwidth
requirements, which might be enough.

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

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


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

[Bug 2077722] Re: [Ubuntu 24.04] MultiVM - L2 guest(s) running stress-ng getting stuck at booting after triggering crash

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

Title:
  [Ubuntu 24.04] MultiVM - L2 guest(s) running stress-ng getting stuck
  at booting after triggering crash

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


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

[Bug 2077825] Re: wrong screen resolution

2024-08-26 Thread Amnon Yekutieli

@ Daniel van Vugt (vanvugt):

Thanks, your solution worked to fix the screen magnification!

As for the slow motion of items on screen: I must have set the settings
-> general behavior -> animation speed to "slow", left end of slider.
Changing to the middle of the slider fixed it.

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

Title:
  wrong screen resolution

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


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

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

Though I wonder if the kernel has decided at boot time that the native
5K resolution is off the list. Please check with:

  sudo apt install drm-info
  sudo drm_info


** Changed in: linux (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/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


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

[Bug 2077858] [NEW] Fix ethernet performance on JSL and EHL

2024-08-26 Thread Kai-Heng Feng

Public bug reported:

[Impact]
Sub-optimal ethernet performance on Intel JSL and EHL platform with
Realtek PCIe NIC.

Iperf shows the network throughput can only reach around 75% of

[Fix]
The CPU idle state transition C1 -> C1E -> C0 overhead can be too high,
so disabling C1E to increase the IRQ latency and DMA speed.

[Test]
With the patch applied, iperf shows over 95% of network throughput
consistently.

[Where problems could occur]
Disabling C1E can theoretically increase power consumption slightly.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

** Affects: linux-oem-6.11 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.11 (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Oracular)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.11 (Ubuntu Oracular)
 Importance: Undecided
 Status: New


** Tags: jinju oem-priority originate-from-2071431

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.11 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: jinju oem-priority originate-from-2071431

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

Title:
  Fix ethernet performance on JSL and EHL

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2077858/+subscriptions


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

[Bug 2077858] Re: Fix ethernet performance on JSL and EHL

2024-08-26 Thread Stefan Bader

** Changed in: linux (Ubuntu Noble)
   Importance: Undecided => Medium

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

Title:
  Fix ethernet performance on JSL and EHL

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2077858/+subscriptions


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

[Bug 2077825] Re: wrong screen resolution

** Changed in: plasma-desktop (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  wrong screen resolution

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


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

[Bug 2077633] Re: Partitions in left panel are not in order

2024-08-26 Thread corrado venturini

Attaching today screenshot and lsblk
corrado@corrado-n13-oo-0823:~$ lsblk -e7 -o NAME,LABEL,SIZE,TYPE,MOUNTPOINT
NAMELABEL SIZE TYPE MOUNTPOINT
sda 465.8G disk 
├─sda1  a1-free32G part 
├─sda2  a2-free32G part 
└─sda3  dati401.8G part /media/corrado/dati
sdb 465.8G disk 
├─sdb1  efi recover   256M part 
├─sdb2  8G part 
├─sdb3 32G part /media/corrado/60234714-d5d6-4511-9142-e5ce2
├─sdb4  b4-free32G part 
└─sdb5  b5-dati 393.5G part 
sdc 931.5G disk 
├─sdc1  share1 32G part 
├─sdc2  share2 32G part 
├─sdc3  dati2 256G part 
├─sdc4  backup  579.5G part 
└─sdc5  c5-free32G part 
sdd 0B disk 
sde 0B disk 
sdf 0B disk 
sdg 0B disk 
sr0  1024M rom  
nvme1n1 232.9G disk 
├─nvme1n1p1   256M part /boot/efi
├─nvme1n1p2 n12-oo-071840G part 
├─nvme1n1p340G part /media/corrado/159c72c0-71cd-467f-8218-40a49
├─nvme1n1p4 n14-oo-080140G part 
├─nvme1n1p5 n15-oo-072140G part 
├─nvme1n1p6 n16-oo-081040G part 
└─nvme1n1p7 n17-oo-0702  32.6G part 
nvme0n1 238.5G disk 
├─nvme0n1p1 efi backup256M part 
├─nvme0n1p2 n02-noble  40G part 
├─nvme0n1p340G part /
└─nvme0n1p4 n04-dati158.2G part 
corrado@corrado-n13-oo-0823:~$ 


** Attachment added: "Screenshot From 2024-08-26 10-28-55.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2077633/+attachment/5809361/+files/Screenshot%20From%202024-08-26%2010-28-55.png

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

Title:
  Partitions in left panel are not in order

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


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

[Bug 2077860] [NEW] Black screen upon waking from suspend; keyboard mostly unresponsive; issue resolved by using previous kernel version.

Public bug reported:

Description: When I put my laptop into suspend and attempt to wake it,
the screen remains black. This issue does not occur when rebooting or
booting from a shutdown state. Additionally, the keyboard does not
respond as expected; for example, pressing Alt + F2/F3 or trying to
switch to an external screen using Super/Meta + P has no effect.
However, I can perform a soft reboot using Ctrl + Alt + PrntScr +
REISUB.

This issue occurs both with and without Wayland disabled. I attempted
the following modifications in the GRUB configuration without success:

GRUB_CMD_LINUX="nouveau.modeset=0"
GRUB_CMDLINE_LINUX="nouveau.blacklist=1"

The issue was temporarily resolved by booting into the previous kernel
version listed in Advanced Options for Ubuntu (6.5.0-45).

Steps to Reproduce:

Put the laptop into suspend mode.
Attempt to wake the laptop from suspend.

Expected Behavior: The screen should wake up normally, and the keyboard
should be fully functional.

Actual Behavior: The screen remains black, and the keyboard does not
respond as expected.

System Information:

Description: Ubuntu 22.04.4 LTS x86_64
Release: 22.04
GNOME Version: 42.9
CPU: 12th Gen Intel i7-1255U (12) @ 4.700GHz
GPU: Intel Device 46a8
Host: ThinkPad X1 Carbon Gen 10 (21CB009UGE)
Kernel Version: 6.8.0-40-generic

Additional Notes: The problem does not occur with the previous kernel
version (6.5.0-45). Please advise on further troubleshooting steps or
potential fixes.

** Affects: linux-hwe-6.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: suspend-resume

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

Title:
  Black screen upon waking from suspend; keyboard mostly unresponsive;
  issue resolved by using previous kernel version.

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


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

[Bug 2077860] Re: Black screen upon waking from suspend; keyboard mostly unresponsive; issue resolved by using previous kernel version.

** Tags added: suspend-resume

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

Title:
  Black screen upon waking from suspend; keyboard mostly unresponsive;
  issue resolved by using previous kernel version.

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


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

[Bug 2077860] Re: Black screen upon waking from suspend; keyboard mostly unresponsive; issue resolved by using previous kernel version.

2024-08-26 Thread Paul White

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 2077860

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: ubuntu => linux-hwe-6.8 (Ubuntu)

** Tags added: jammy

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

Title:
  Black screen upon waking from suspend; keyboard mostly unresponsive;
  issue resolved by using previous kernel version.

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


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

[Bug 2077186] Re: apply NVIDIA patches Aug 1-16, 2024

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  apply NVIDIA patches Aug 1-16, 2024

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


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

[Bug 2076922] Re: Jammy real-time patch set update: v5.15.163-rt78

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Jammy real-time patch set update: v5.15.163-rt78

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


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

[Bug 2076334] Re: jammy:linux bpf selftest do not build

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  jammy:linux bpf selftest do not build

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


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

[Bug 2074215] Re: [SRU] UBSAN warnings in bnx2x kernel driver

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  [SRU] UBSAN warnings in bnx2x kernel driver

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


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

[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Virtualbox Guru meditation on VM start caused by kernel commit in
  v6.9-rc4

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


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

[Bug 2073092] Re: net/sched: Fix conntrack use-after-free

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  net/sched: Fix conntrack use-after-free

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


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

[Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1028.28 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions


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

[Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)

** Description changed:

SRU Justification:

[ Impact ]

* The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be
maintained at runtime in addition to the dwarf unwinding information.

* This allows for simple backtrace implementations, but imposes a small
runtime overhead. For this to work, all code that might be part of
backtrace must be built with the -mbackchain GCC option.

* The -fno-omit-framepointer switch is neither necessary nor helpful in this
context.
Having a (soft/simulated) frame pointer does not improve backtraces at all
on IBM Z.

* However, forcing a frame pointer via the -fno-omit-frame-pointer
option negatively affects performance for multiple reasons: extra
prologue/epilogue overhead and fewer shrink-wrapping opportunities.

* Given -fno-omit-frame-pointer does not provide any improvements
(backtraces or otherwise) and only reduces performance, -fno-omit-frame-
pointers should not be used on IBM Z.

* So we are facing here a performance penalty without any gain - on
this particular platform.

* And sometimes (in rare cases like LP#2060108) frame pointers may even
lead to failed builds.

[ Test Plan ]

* Due to the above description of the impact and rationale,
this pragmatic approach for testing is given:

* Build the affected packages where frame-pointers should be reverted
using the updated dpkg package (that incl. the modified build defaults)
on (or for) this particular platform.

* Now frame-pointer usage be checked in the following different ways:

* 1) For the ease of use (and thanks to Julian Klode), there is this python
test script available that allows to verify a binary in regard to
frame pointers:
https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208
+
https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py

* 2) Another more manual way is to verify based on debug symbols like this:
- find and install the ddeb package
- maybe extract the file (e.g. unzstd)
- use 'readelf -wi'
- and grep for 'DW_AT_produce' (build options)
- look for entries regarding frame-pointer
The output may look similar to this:
readelf -wi
./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko
| grep DW_AT_produce
<23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS
2.42
<129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU
C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16
-mindirect-branch=thunk-extern -mfunction-return=thunk-extern
-mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g
-gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common
-fno-strict-aliasing -fno-asynchronous-unwind-tables
-fno-delete-null-pointer-checks -fno-allow-store-data-races
-fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection
-fzero-call-used-regs=used-gpr -fno-inline-functions-called-once
-falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow
-fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift
-fsanitize=bool -fsanitize=enum -fPIC

* 3) And maybe watching the build messages / log for the build options that
were used (but that is probably not sufficient - it's better to inspect
the output.)

[ Where problems could occur ]

* The dpkg modifications could have been done erroneously.
A dpkg test build and/or builds of other packages with the modified dpkg
version in place would show this.

* The settings in dpkg might be overwritten by other settings/packages.
Tests like above, would show this.

* One may think there could be issues in an environment where some packages
have frame-pointer enabled and other don't.
This is fine and was confirmed by IBM toolchain team and ours
(as well as by a longer running test system,
with FP disabled in kernel, that showed no issues - like expected).

[ Other Info ]

- * These changes were implemented during the opening of the oracular series.
-The very same changes are backported to 24.04 LTS.
+ * These changes were implemented during the opening of the oracular series.
+ The very same changes are backported to 24.04 LTS.

- * These only affect the ppc64el and s390x architectures,
-for other architectures it's a no-change upload.
+ * These only affect the ppc64el and s390x architectures,
+ for other architectures it's a no-change upload.

- * We didn't see any fallout for these changes during the development
-on the oracular series, and therefore don't expect any fallout or

[Bug 2077860] Re: Black screen upon waking from suspend; keyboard mostly unresponsive; issue resolved by using previous kernel version.

** Tags removed: jammy suspend-resume
** Tags added: black-screen kernel-bug regression-update

** Tags added: jammy

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

Title:
  Black screen upon waking from suspend; keyboard mostly unresponsive;
  issue resolved by using previous kernel version.

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


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

[Bug 2077583] Re: Wifi Bluetooth Modul for Realtek 8822ce is not working proper

2024-08-26 Thread Wolfgang

Der Fehler scheint im Kernel zu liegen. Somit ist als Paket "linux"
angegeben.

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

Title:
  Wifi Bluetooth Modul for Realtek 8822ce is not working proper

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


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

[Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)

** Description changed:

  SRU Justification:
  
  [ Impact ]
  
-  * Power's Linux ABIs all require an explicit call chain be stored on
+  * Power's Linux ABIs all require an explicit call chain be stored on
  the call stack frames which are all accessible via the stack pointer.
  
-  * Therefore, having a (soft/simulated) frame pointer does not improve
+  * Therefore, having a (soft/simulated) frame pointer does not improve
  backtraces at all on Power.
  
-  * However, forcing a frame pointer via the -fno-omit-frame-pointer
+  * However, forcing a frame pointer via the -fno-omit-frame-pointer
  option negatively affects performance for multiple reasons: extra
  prologue/epilogue overhead and fewer shrink-wrapping opportunities.
  
-  * Given -fno-omit-frame-pointer does not provide any improvements
+  * Given -fno-omit-frame-pointer does not provide any improvements
  (backtraces or otherwise) and only reduces performance, -fno-omit-frame-
  pointers should not be used on Power.
  
-  * So we are facing here a performance penalty without any gain - on
+  * So we are facing here a performance penalty without any gain - on
  this particular platform.
  
-  * And sometimes (in rare cases like LP#2060108) frame pointers may even
+  * And sometimes (in rare cases like LP#2060108) frame pointers may even
  lead to failed builds.
  
  [ Test Plan ]
  
-  * Due to the above description of the impact and rationale,
-this pragmatic approach for testing is given:
+  * Due to the above description of the impact and rationale,
+    this pragmatic approach for testing is given:
  
-  * Build the affected packages where frame-pointers should be reverted
-using the updated dpkg package (that incl. the modified build defaults)
-on (or for) this particular platform.
+  * Build the affected packages where frame-pointers should be reverted
+    using the updated dpkg package (that incl. the modified build defaults)
+    on (or for) this particular platform.
  
-  * Now frame-pointer usage be checked in the following different ways:
+  * Now frame-pointer usage be checked in the following different ways:
  
-  * 1) For the ease of use (and thanks to Julian Klode), there is this python
-   test script available that allows to verify a binary in regard to
-   frame pointers:
-   https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208
+  * 1) For the ease of use (and thanks to Julian Klode), there is this python
+   test script available that allows to verify a binary in regard to
+   frame pointers:
+   https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208
+   
https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py
+   requires python3-pyelftools
  
-  * 2) Another more manual way is to verify based on debug symbols like this:
-   - find and install the ddeb package
-   - maybe extract the  file (e.g. unzstd)
-   - use 'readelf -wi'
-   - and grep for 'DW_AT_produce' (build options)
-   - look for entries regarding frame-pointer
-   The output may look similar to this:
-   readelf -wi 
./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko
 | grep DW_AT_produce
-   <23>   DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 
2.42
-   <129>   DW_AT_producer: (indirect string, offset: 0x3eef): GNU 
C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 
-mindirect-branch=thunk-extern -mfunction-return=thunk-extern 
-mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g 
-gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common 
-fno-strict-aliasing -fno-asynchronous-unwind-tables 
-fno-delete-null-pointer-checks -fno-allow-store-data-races 
-fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection 
-fzero-call-used-regs=used-gpr -fno-inline-functions-called-once 
-falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow 
-fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift 
-fsanitize=bool -fsanitize=enum -fPIC
+  * 2) Another more manual way is to verify based on debug symbols like this:
+   - find and install the ddeb package
+   - maybe extract the  file (e.g. unzstd)
+   - use 'readelf -wi'
+   - and grep for 'DW_AT_produce' (build options)
+   - look for entries regarding frame-pointer
+   The output may look similar to this:
+   readelf -wi 
./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko
 | grep DW_AT_produce
+   <23>   DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 
2.42
+   <129>   DW_AT_producer: (indirect string, offset: 0x3eef): GNU 
C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 
-mindirect-branch=thunk-extern -mfunction-return=thunk-extern 
-mindirect-branch-t

[Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)

** Description changed:

  SRU Justification:
  
  [ Impact ]
  
   * The preferred way of doing stack unwinding on Linux on Z is via dwarf call 
frame information.
  In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be 
maintained at runtime in addition to the dwarf unwinding information.
  
   * This allows for simple backtrace implementations, but imposes a small
  runtime overhead. For this to work, all code that might be part of
  backtrace must be built with the -mbackchain GCC option.
  
   * The -fno-omit-framepointer switch is neither necessary nor helpful in this 
context.
    Having a (soft/simulated) frame pointer does not improve backtraces at all 
on IBM Z.
  
   * However, forcing a frame pointer via the -fno-omit-frame-pointer
  option negatively affects performance for multiple reasons: extra
  prologue/epilogue overhead and fewer shrink-wrapping opportunities.
  
   * Given -fno-omit-frame-pointer does not provide any improvements
  (backtraces or otherwise) and only reduces performance, -fno-omit-frame-
  pointers should not be used on IBM Z.
  
   * So we are facing here a performance penalty without any gain - on
  this particular platform.
  
   * And sometimes (in rare cases like LP#2060108) frame pointers may even
  lead to failed builds.
  
  [ Test Plan ]
  
   * Due to the above description of the impact and rationale,
     this pragmatic approach for testing is given:
  
   * Build the affected packages where frame-pointers should be reverted
     using the updated dpkg package (that incl. the modified build defaults)
     on (or for) this particular platform.
  
   * Now frame-pointer usage be checked in the following different ways:
  
   * 1) For the ease of use (and thanks to Julian Klode), there is this python
    test script available that allows to verify a binary in regard to
    frame pointers:
    https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208
-   
https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py
+   
https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py
+   requires python3-pyelftools
  
   * 2) Another more manual way is to verify based on debug symbols like this:
    - find and install the ddeb package
    - maybe extract the  file (e.g. unzstd)
    - use 'readelf -wi'
    - and grep for 'DW_AT_produce' (build options)
    - look for entries regarding frame-pointer
    The output may look similar to this:
    readelf -wi 
./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko
 | grep DW_AT_produce
    <23>   DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 
2.42
    <129>   DW_AT_producer: (indirect string, offset: 0x3eef): GNU 
C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 
-mindirect-branch=thunk-extern -mfunction-return=thunk-extern 
-mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g 
-gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common 
-fno-strict-aliasing -fno-asynchronous-unwind-tables 
-fno-delete-null-pointer-checks -fno-allow-store-data-races 
-fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection 
-fzero-call-used-regs=used-gpr -fno-inline-functions-called-once 
-falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow 
-fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift 
-fsanitize=bool -fsanitize=enum -fPIC
  
   * 3) And maybe watching the build messages / log for the build options that
    were used (but that is probably not sufficient - it's better to inspect
    the output.)
  
  [ Where problems could occur ]
  
   * The dpkg modifications could have been done erroneously.
     A dpkg test build and/or builds of other packages with the modified dpkg
     version in place would show this.
  
   * The settings in dpkg might be overwritten by other settings/packages.
     Tests like above, would show this.
  
   * One may think there could be issues in an environment where some packages
     have frame-pointer enabled and other don't.
     This is fine and was confirmed by IBM toolchain team and ours
     (as well as by a longer running  test system,
  with FP disabled in kernel, that showed no issues - like expected).
  
  [ Other Info ]
  
   * These changes were implemented during the opening of the oracular series.
     The very same changes are backported to 24.04 LTS.
  
   * These only affect the ppc64el and s390x architectures,
     for other architectures it's a no-change upload.
  
   * We didn't see any fallout for these changes during the development
     on the oracular series, and therefore don't expect any fallout or
     regressions in 24.04 LTS either.

-- 
You received this bug not

[Bug 2077860] Re: Black screen upon waking from suspend; keyboard mostly unresponsive; issue resolved by using previous kernel version.

I did, but i don't know if it worked, after authorizing it gave me a pop up 
window saying "no additional information gathered".
In the terminal it said: Package linux-hwe-6.8 not installed and no hook 
available, ignoring

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

Title:
  Black screen upon waking from suspend; keyboard mostly unresponsive;
  issue resolved by using previous kernel version.

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


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

[Bug 2051151] Re: Update to shim 15.8

This bug was fixed in the package shim - 15.8-0ubuntu1

---
shim (15.8-0ubuntu1) mantic; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
  * debian/rules: Update COMMIT_ID

 -- Mate Kukri   Thu, 25 Jan 2024 08:55:28
+

** Changed in: shim (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: shim-signed (Ubuntu Jammy)
   Status: Fix Committed => 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/2051151

Title:
  Update to shim 15.8

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


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

[Bug 2051151] Re: Update to shim 15.8

This bug was fixed in the package shim-signed - 1.51.4

---
shim-signed (1.51.4) jammy; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551

 -- Mate Kukri   Thu, 04 Apr 2024 13:54:55
+0100

** Changed in: shim (Ubuntu Focal)
   Status: Fix Committed => 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/2051151

Title:
  Update to shim 15.8

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


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

[Bug 2051151] Re: Update to shim 15.8

This bug was fixed in the package shim - 15.8-0ubuntu1

---
shim (15.8-0ubuntu1) mantic; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
  * debian/rules: Update COMMIT_ID

 -- Mate Kukri   Thu, 25 Jan 2024 08:55:28
+

** Changed in: shim-signed (Ubuntu Focal)
   Status: Fix Committed => 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/2051151

Title:
  Update to shim 15.8

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


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

[Bug 2051151] Re: Update to shim 15.8

This bug was fixed in the package shim-signed - 1.40.10

---
shim-signed (1.40.10) focal; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551

 -- Mate Kukri   Thu, 04 Apr 2024 13:56:01
+0100

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

Title:
  Update to shim 15.8

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


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

[Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64

This bug was fixed in the package shim - 15.8-0ubuntu1

---
shim (15.8-0ubuntu1) mantic; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
  * debian/rules: Update COMMIT_ID

 -- Mate Kukri   Thu, 25 Jan 2024 08:55:28
+

** Changed in: shim (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: shim-signed (Ubuntu Jammy)
   Status: Fix Committed => 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/2036604

Title:
  Synchronous Exception when booting VMs via qemu-efi-aarch64

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


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

[Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64

This bug was fixed in the package shim-signed - 1.51.4

---
shim-signed (1.51.4) jammy; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551

 -- Mate Kukri   Thu, 04 Apr 2024 13:54:55
+0100

** Changed in: shim (Ubuntu Focal)
   Status: Fix Committed => 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/2036604

Title:
  Synchronous Exception when booting VMs via qemu-efi-aarch64

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


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

[Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64

This bug was fixed in the package shim-signed - 1.40.10

---
shim-signed (1.40.10) focal; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551

 -- Mate Kukri   Thu, 04 Apr 2024 13:56:01
+0100

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

Title:
  Synchronous Exception when booting VMs via qemu-efi-aarch64

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


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

[Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64

This bug was fixed in the package shim - 15.8-0ubuntu1

---
shim (15.8-0ubuntu1) mantic; urgency=medium

  * New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
  - Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
  - Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
  - Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
  * SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
  * SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
  * SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
  * SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
  * debian/rules: Update COMMIT_ID

 -- Mate Kukri   Thu, 25 Jan 2024 08:55:28
+

** Changed in: shim-signed (Ubuntu Focal)
   Status: Fix Committed => 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/2036604

Title:
  Synchronous Exception when booting VMs via qemu-efi-aarch64

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


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

[Bug 2077583] Re: Wifi Bluetooth Modul for Realtek 8822ce is not working proper

2024-08-26 Thread Wolfgang

Nur nochmal zur Erinnerung : es handelt sich hier um eine PCIe WiFi-Karte von 
Realtek "RTL 8822CE".
Es gibt zwar verschiedene Ansätze im Netz doch hat hier keiner zu einer Lösung 
bzw. überhaupt zu einer Reaktion des BT-Moduls der Karte geführt.

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

Title:
  Wifi Bluetooth Modul for Realtek 8822ce is not working proper

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


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

[Bug 2077328] Re: microcode is not included when building initramfs for kernel 6.8

2024-08-26 Thread Benjamin Drung

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Yes, it is the same issue as
https://issues.redhat.com/browse/RHEL-17902.

The fix is commit
https://github.com/dracutdevs/dracut/commit/6c80408c8644a0add1907b0593eb83f90d6247b1
which is included since dracut 060. Ubuntu 24.04 comes with dracut 060.
So only Ubuntu 22.04 and older are affected.

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

** Changed in: dracut (Ubuntu)
   Status: New => Fix Released

** Changed in: dracut (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  microcode is not included when building initramfs for kernel 6.8

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


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

[Bug 1998754] Re: [MIR][jammy] oem-somerville-muk-meta

2024-08-26 Thread Kai-Chuan Hsieh

** Description changed:

  [Background]
  
  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
  
  [Impact]
  
   1. Upgrade path: Users will be upgrading from a package in the associated 
OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's 
impact.
  
  [Testing]
  
   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the 
relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive 
if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an 
upgrade to the OEM package is offered and that it completes successfully and 
the hardware works properly.
  
  [Regression Potential]
  
  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.
  
  [When switching kernel flavour] Check that the new kernel flavour works
  on the target platform.
  
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM 
that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-muk-meta for jammy:
  git clone -b muk-jammy-ubuntu 
https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Dell platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this 
package on some Dell platforms.
  oem-somerville-muk-meta will be upgraded to 22.04ubuntu1 or the later version 
from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of 
https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
- 
- https://ubuntu.com/certified/202302-31234
- https://ubuntu.com/certified/202302-31235
- https://ubuntu.com/certified/202302-31236
- https://ubuntu.com/certified/202302-31237
- https://ubuntu.com/certified/202303-31322
- https://ubuntu.com/certified/202303-31323

** Changed in: oem-priority
   Status: Fix Committed => In Progress

** Changed in: ubuntu
   Status: In Progress => Incomplete

** Changed in: oem-somerville-muk-meta (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  [MIR][jammy] oem-somerville-muk-meta

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998754/+subscriptions


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

[Bug 2077863] [NEW] package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to install/upgrade: el subproceso instalado paquete linux-headers-6.8.0-41-generic script post-installation devolvió el có

2024-08-26 Thread Daniel Carracedo Domínguez

Public bug reported:

just executed "sudo apt upgrade" and dpkg gave error when "--configure".

It didn't break my system (yet).

"lsb_release -rd" output:

No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-41-generic 6.8.0-41.41
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:petete 3706 F pipewire
 /dev/snd/controlC1:  petete 3711 F wireplumber
 /dev/snd/controlC0:  petete 3711 F wireplumber
CasperMD5CheckResult: pass
Date: Mon Aug 26 11:00:23 2024
ErrorMessage: el subproceso instalado paquete linux-headers-6.8.0-41-generic 
script post-installation devolvió el código de salida de error 11
InstallationDate: Installed on 2024-07-31 (26 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=80dc7680-ed0c-479f-bc85-767a16a7f611 ro quiet splash vt.handoff=7
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: /usr/bin/python3.12, Python 3.12.3, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc N/A
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to 
install/upgrade: el subproceso instalado paquete linux-headers-6.8.0-41-generic 
script post-installation devolvió el código de salida de error 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2020
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2002
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H310M-E R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2002:bd12/08/2020:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH310M-ER2.0:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package noble

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

Title:
  package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to
  install/upgrade: el subproceso instalado paquete linux-
  headers-6.8.0-41-generic script post-installation devolvió el código
  de salida de error 11

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


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

[Bug 2077862] [NEW] adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed

2024-08-26 Thread Hector CAO

Public bug reported:

ADT of adduser fails due to the merge of shadow to the version
1:4.15.3-3ubuntu2 in 24.10

Logs of the ADT :
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz

The failing tests:
- debian/tests/f/valid_username.t

Logs:

670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '82'
670s # expected: '0'
670s
670s #   Failed test 'user exists: \}'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
670s #  got: undef
670s # expected: anything else
670s
670s #   Failed test 'path exists: /home/\}'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
670s
670s #   Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 
'\}''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '12'
670s # expected: '0'
670s
670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/\}' '\}''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '82'
670s # expected: '0'
670s
670s #   Failed test 'user exists: \}'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
670s #  got: undef
670s # expected: anything else
670s
670s #   Failed test 'path exists: /home/\}'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
670s
670s #   Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 
'\}''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '12'
670s # expected: '0'
670s
670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/DOMAIN\user' 
--allow-all-names 'DOMAIN\user''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '82'
670s # expected: '0'
670s
670s #   Failed test 'user exists: DOMAIN\user'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
670s #  got: undef
670s # expected: anything else
670s
670s #   Failed test 'path exists: /home/DOMAIN\user'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
670s
670s #   Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 
'DOMAIN\user''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '12'
670s # expected: '0'
670s
670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '82'
670s # expected: '0'
670s
670s #   Failed test 'user exists: DOMAIN\user'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
670s #  got: undef
670s # expected: anything else
670s
670s #   Failed test 'path exists: /home/DOMAIN\user'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
670s
670s #   Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 
'DOMAIN\user''
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '12'
670s # expected: '0'
670s
670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" 
--allow-all-names "'c4\$h\\M0n3y\"'==>@"'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '82'
670s # expected: '0'
670s
670s #   Failed test 'user exists: 'c4$h\M0n3y"'==>@'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
670s #  got: undef
670s # expected: anything else
670s
670s #   Failed test 'path exists: /home/'c4$h\M0n3y"'==>@'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
670s
670s #   Failed test 'command success: /usr/sbin/deluser --quiet --remove-home 
"'c4\$h\\M0n3y\"'==>@"'
670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
670s #  got: '12'
670s # expected: '0'
670s # Looks like you failed 20 tests of 669.

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

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

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

** Description changed:

- ADT of adduser fails due to the merge of shadow on 24.10 to the version
+ ADT of adduser fails due to the merge of shadow to the version
  1:4.15.3-3ubuntu2 in 24.10
  
  Logs of the ADT :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz
  
  The failing tests:
  - debian/tests/f/valid_username.t
  
  Logs:

[Bug 2077464] Re: lscpu: Skip aarch64 decode path for rest of the architectures

2024-08-26 Thread Adrien Nader

I can confirm the issue:

BIOS Model name:  AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Unknown CPU @ 3.8GHz

It looks very minor however. As far as I'm concerned, it doesn't look
like it would be worth SRU'ing it, and considering we're past feature-
freeze for oracular, I'm not sure it would make it to oracular either.

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

Title:
  lscpu: Skip aarch64 decode path for rest of the architectures

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


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

[Bug 2076652] Re: Mouse cursor is oversized in GTK4 apps

This bug was fixed in the package gtk4 - 4.15.5+ds-2ubuntu1

---
gtk4 (4.15.5+ds-2ubuntu1) oracular; urgency=medium

  * Merge with Debian. Remaining change:
- Temporarily skip css tests on s390x to work around Debian 1079546

gtk4 (4.15.5+ds-2) experimental; urgency=medium

  * Replace disable vulkan patch with alternative fix pushed upstream
  * Update list of sysprof enabled architectures

 -- Jeremy Bícha   Sat, 24 Aug 2024 09:48:56 -0400

** Changed in: gtk4 (Ubuntu)
   Status: Fix Committed => 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/2076652

Title:
  Mouse cursor is oversized in GTK4 apps

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


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

[Bug 2069559] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box()

I have installed gnome-shell 46.0-0ubuntu6~24.04.4 on Noble and cannot
reproduce the crash using the test case described at the top of this
bug. However as mentioned in previous comments, this crash is refusing
to happen on demand, even without the fix.

Since we are still getting automated crash reports for this issue;

https://errors.ubuntu.com/problem/65513baf83b5ba140d09c2aa71b988097108cde0

I suggest we release the fix and the above page will provide the final
word in whether the crash is gone for good.


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

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from
  st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from
  st_theme_node_transition_get_paint_box() from
  st_widget_get_paint_volume()

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/2069559/+subscriptions


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

[Bug 2077864] [NEW] `data-ciphers-fallback` impossible for openvpn connection

2024-08-26 Thread Krister Swenson

Public bug reported:

My TPlink router is not very configurable.  I can connect to it using
`--data-ciphers-fallback AES-128-CBC`, but this seems to be impossible
to configure in the network manager.

This is similar to the bug here:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1993634
which states that --data-ciphers has been added upstream in debian 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012664), yet there is no 
mention of --data-ciphers-fallback.

If I try to manually edit the .yaml file in /etc/netplan/, by adding the
line `vpn.data-ciphers-fallback: "AES-128-CBC"` I get the following
error in /var/sys/syslog:

2024-08-26T11:27:38.979379+02:00 esperanza NetworkManager[1421097]:
  [1724664458.9792]
vpn[0x5859c6179920,f01dbf90-536f-4b22-8d5a-13e26b34993f,"TPlink_config"]:
connect: failed to connect interactively:
'GDBus.Error:org.freedesktop.NetworkManager.VPN.Error.BadArguments:
property “data-ciphers-fallback” invalid or not supported'


Without that line, I get this error:

2024-08-26T11:15:31.909947+02:00 esperanza nm-openvpn[1416267]: OPTIONS
ERROR: failed to negotiate cipher with server. Configure --data-ciphers-
fallback if you want to connect to this server.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: network-manager-openvpn 1.10.2-3
ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13
Uname: Linux 6.5.0-44-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 26 11:18:45 2024
InstallationDate: Installed on 2021-10-12 (1049 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  `data-ciphers-fallback` impossible for openvpn connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/2077864/+subscriptions


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

[Bug 2077866] [NEW] squid3 cc1 error and too smblib error on make compiling

2024-08-26 Thread Dorian Rosse

Public bug reported:

hello,


squid3 cc1 error and too smblib error on make compiling so i paste below the 
errors : 

```
smblib-util.c: In function 'SMB_Negotiate':
smblib-util.c:400:9: error: '__builtin_strncpy' output may be truncated copying 
79 bytes from a string of length 79 [-Werror=stringop-truncation]
  400 | strncpy(p, Con_Handle -> Svr_PDom, sizeof(Con_Handle -> 
Svr_PDom) - 1);
  | ^
smblib-util.c:423:9: error: '__builtin_strncpy' output may be truncated copying 
79 bytes from a string of length 79 [-Werror=stringop-truncation]
  423 | strncpy(p, Con_Handle -> Svr_PDom, sizeof(Con_Handle -> 
Svr_PDom) - 1);
  | ^
libtool: compile:  gcc -DHAVE_CONFIG_H -I../.. -I../../include -I../../lib 
-I../../src -I../../include -I../../lib -Wall -Wpointer-arith -Wwrite-strings 
-Wmissing-prototypes -Wmissing-declarations -Wcomments -Wshadow -Werror -pipe 
-D_REENTRANT -Wall -g -O2 -MT smbencrypt.lo -MD -MP -MF .deps/smbencrypt.Tpo -c 
smbencrypt.c -o smbencrypt.o >/dev/null 2>&1
smblib-util.c: In function 'SMB_TreeConnect':
smblib-util.c:537:5: error: '__builtin_strncpy' specified bound 129 equals 
destination size [-Werror=stringop-truncation]
  537 | strncpy(tree -> path, path, sizeof(tree -> path));
  | ^
smblib-util.c:538:5: error: '__builtin_strncpy' specified bound 20 equals 
destination size [-Werror=stringop-truncation]
  538 | strncpy(tree -> device_type, device, sizeof(tree -> device_type));
  | ^
cc1: all warnings being treated as errors
libtool: compile:  gcc -DHAVE_CONFIG_H -I../.. -I../../include -I../../lib 
-I../../src -I../../include -I../../lib -Wall -Wpointer-arith -Wwrite-strings 
-Wmissing-prototypes -Wmissing-declarations -Wcomments -Wshadow -Werror -pipe 
-D_REENTRANT -Wall -g -O2 -MT smbdes.lo -MD -MP -MF .deps/smbdes.Tpo -c 
smbdes.c -o smbdes.o >/dev/null 2>&1
make[2]: *** [Makefile:788: smblib-util.lo] Error 1
make[2]: *** Attente des tâches non terminées
make[2] : on quitte le répertoire « 
/home/dorian-rosse/programs/squid-3.5.27/lib/smblib »
make[1]: *** [Makefile:1067: all-recursive] Error 1
make[1] : on quitte le répertoire « 
/home/dorian-rosse/programs/squid-3.5.27/lib »
make: *** [Makefile:584: install-recursive] Error 1
```

```
lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04
apt-cache policy squid-3.5.27
N: Impossible de trouver le paquet squid-3.5.27
N: Impossible de trouver de paquet correspondant à l'expression rationnelle « 
squid-3.5.27 »
N: Impossible de trouver de paquet correspondant à l'expression rationnelle « 
squid-3.5.27 »
dorian-rosse@msi-torpedo-corsair:~/programs/squid-3.5.27$ apt-cache policy 
squid3
N: Impossible de trouver le paquet squid3
```

also i may be able to compile squid3 but your advice package look like
default squid so i paste the systemctl output about squid below :

```
sudo systemctl status squid
× squid.service - Squid Web Proxy Server
 Loaded: loaded (/usr/lib/systemd/system/squid.service; enabled; preset: 
enabled)
 Active: failed (Result: exit-code) since Sun 2024-08-25 18:16:11 CEST; 17h 
ago
   Duration: 4.499s
   Docs: man:squid(8)
   Main PID: 2152 (code=exited, status=1/FAILURE)
CPU: 457ms

août 25 18:16:11 msi-torpedo-corsair squid[2152]: Squid Parent: squid-1 process 
2506 will not be restarted for 3600 seconds due to repeated, frequent failures
août 25 18:16:11 msi-torpedo-corsair squid[2152]: Exiting due to repeated, 
frequent failures
août 25 18:16:11 msi-torpedo-corsair squid[2152]: Removing PID file 
(/run/squid.pid)
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Main process 
exited, code=exited, status=1/FAILURE
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Killing process 
2162 (pinger) with signal SIGKILL.
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Killing process 
2206 (pinger) with signal SIGKILL.
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Killing process 
2246 (pinger) with signal SIGKILL.
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Killing process 
2496 (pinger) with signal SIGKILL.
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Killing process 
2511 (pinger) with signal SIGKILL.
août 25 18:16:11 msi-torpedo-corsair systemd[1]: squid.service: Failed with 
result 'exit-code'.
dorian-rosse@msi-torpedo-corsair:~/programs/squid-3.5.27$ sudo systemctl stop 
squid
dorian-rosse@msi-torpedo-corsair:~/programs/squid-3.5.27$ sudo systemctl start 
squid
dorian-rosse@msi-torpedo-corsair:~/programs/squid-3.5.27$ sudo systemctl status 
squid
● squid.service - Squid Web Proxy Server
 Loaded: loaded (/usr/lib/systemd/system/squid.service; enabled; preset: 
enabled)
 Active: active (running) since Mon 2024-08-26 11:25:40 CEST; 2s ago
   Docs: man:squid(8)
Process: 92995 ExecStartPre=/usr/sbin/squid --foreground -z (code=exited, 
status=0/SUCCESS)
   Main PID: 92

[Bug 2077864] Re: `data-ciphers-fallback` impossible for openvpn connection

2024-08-26 Thread Krister Swenson

This might be solved by this upstream fix:
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/70

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

Title:
  `data-ciphers-fallback` impossible for openvpn connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/2077864/+subscriptions


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

[Bug 2077685] Re: python3-apt_2.7.7ubuntu2 uninstallable on armhf

This bug was fixed in the package python-apt - 2.7.7ubuntu3

---
python-apt (2.7.7ubuntu3) noble; urgency=medium

  * No-change rebuild without proposed (LP: #2077685)
  * Mirror list updates.

 -- Julian Andres Klode   Fri, 23 Aug 2024 09:52:34
+0200

** Changed in: python-apt (Ubuntu Noble)
   Status: Fix Committed => 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/2077685

Title:
  python3-apt_2.7.7ubuntu2 uninstallable on armhf

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


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

[Bug 2077685] Update Released

2024-08-26 Thread Łukasz Zemczak

The verification of the Stable Release Update for python-apt has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  python3-apt_2.7.7ubuntu2 uninstallable on armhf

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


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

[Bug 2076318] Re: [Asus Zenbook S 13] Heavy cursor stutter

** Description changed:

+ [ Impact ]
+ 
+ Heavy mouse cursor stutter is observed in Wayland sessions on some
+ machines, most visibly laptops with OLED panels when using the touchpad.
+ Using a high speed USB mouse can hide the issue.
+ 
+ [ Test Plan ]
+ 
+ 0. Find an affected machine.
+ 1. On the login screen move the cursor slowly from left to right. Expect no 
stuttery jumps.
+ 2. Still on the login screen, move the cursor rapidly in small circles. 
Expect almost perfectly even spacing between cursor sprites.
+ 
+ [ Where problems could occur ]
+ 
+ In scheduling of cursor movement or screen updates. If a mistake is made
+ then one could experience stuttering or freezes.
+ 
+ [ Original description ]
+ 
  On an Asus Zenbook S 13 I experience heavy cursor stutter, but not under
  all conditions...
  
  Wayland on battery: Heavy stutter
  Wayland on AC power: Light stutter
  Xorg on battery: Perfectly smooth
  Xorg on AC power: Perfectly smooth
  
  Mutter version: 46.4
  Display: 60.00Hz fixed frequency OLED
  Touchpad: 144Hz-145Hz

** Changed in: mutter (Ubuntu Noble)
   Status: Triaged => In Progress

** Summary changed:

- [Asus Zenbook S 13] Heavy cursor stutter
+ Heavy cursor stutter on OLED panels when using a touchpad

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

Title:
  Heavy cursor stutter on OLED panels when using a touchpad

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


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

[Bug 2025006] Re: Monitor colour profile is randomly not applied

** Tags added: fixed-in-mutter-46.5

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

Title:
  Monitor colour profile is randomly not applied

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


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

[Bug 2076917] Re: gnome-boxes missing dependency

2024-08-26 Thread Petros Schaffrath

I was able to narrow down the bug somewhat.

- Existing VMs can be started without the libvirt-system-daemon package
- you can also create and start a VM with the integrated download manager 
without the libvirt-system-daemon package

- However if you create a VM with the ISO file only you get the error
message "No KVM" if you have no libvirt-system-daemon package. This
seems to be a bug in the creation assistent in gnome-boxes.

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

Title:
  gnome-boxes missing dependency

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


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

[Bug 2077869] [NEW] systemd.postinst wants to restart masked systemd-binfmt.service

2024-08-26 Thread Kees Bakker

Public bug reported:

It is possible that the postinst is going to trigger a restart of
systemd-binfmt.service. Take a look at this section of systemd.postinst

_update_binfmt() {
_systemctl restart systemd-binfmt.service || true
}

# Update Message Catalogs database and binfmt registrations in response to dpkg 
triggers
if [ "$1" = "triggered" ]; then
shift
for trigger in $@; do
case $trigger in
/usr/lib/systemd/catalog)
_update_catalog an
;;
/usr/lib/binfmt.d)
_update_binfmt
;;
esac
done
exit 0
fi

It happened to me when I create a Incus Ubuntu noble container from an
older image (2024-05-30) and then simply did a "apt update" plus "apt
dist-upgrade" in the container.

I'm getting

Failed to restart systemd-binfmt.service: Unit systemd-binfmt.service is
masked.

I'm not getting that error when I launch from the latest Incus image. So
something might depend on other things.

Nevertheless, the postinst should not even try to restart a service that
is masked.

** Affects: systemd (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/2077869

Title:
  systemd.postinst wants to restart masked systemd-binfmt.service

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


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

[Bug 2077805] Re: "apt download" fails for ESM packages

2024-08-26 Thread Julian Andres Klode

The Pro client is responsible for setting the credentials, that said
this may be the correct behavior, it may also depend on the umask of
your root user.

As in, it makes sense to protect the credentials from non-root users,
you don't want e.g. some daemon to gain access to it and leak it.

** Package changed: apt (Ubuntu) => ubuntu-advantage-tools (Ubuntu)

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

Title:
  "apt download" fails for ESM packages

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


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

[Bug 2077805] Re: "apt download" fails for ESM packages

2024-08-26 Thread Renan Rodrigo

Julian is correct - this is not a bug, it is a feature (:

You need root privileges to run apt download / apt changelog.

** Changed in: ubuntu-advantage-tools (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/2077805

Title:
  "apt download" fails for ESM packages

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


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

[Bug 2077862] Re: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed

2024-08-26 Thread Hector CAO

** Description changed:

- ADT of adduser fails due to the merge of shadow to the version
+ ADT of adduser fails due to the merge of shadow on 24.10 to the version
  1:4.15.3-3ubuntu2 in 24.10
  
  Logs of the ADT :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz
  
  The failing tests:
- - debian/tests/f/valid_username.t
+ ---
+ 
+ 650s Test Summary Report
+ 650s ---
+ 650s debian/tests/f/valid_username.t (Wstat: 5120 (exited 20) Tests: 
669 Failed: 20)
+ 650s   Failed tests:  209-212, 214-217, 245-248, 250-253, 321-324
+ 650s   Non-zero exit status: 20
+ 650s Files=20, Tests=2631, 142 wallclock secs ( 0.44 usr  0.11 sys + 79.95 
cusr 41.69 csys = 122.19 CPU)
+ 650s Result: FAIL
  
  Logs:
+ ---
  
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: \}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/\}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/\}' '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: \}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/\}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/DOMAIN\user' 
--allow-all-names 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" 
--allow-all-names "'c4\$h\\M0n3y\"'==>@"'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: 'c4$h\M0n3y"'==>@'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/'c4$h\M0n3y"'==>@'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home "'c4\$h\\M0n3y\"'==>@"'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s # Looks like you failed 20 tests of 669.

-- 
You received this

[Bug 2055237] Re: Backport ps uart RS485 driver

This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1035.39 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-failed-jammy-linux-xilinx-zynqmp'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 
verification-needed-jammy-linux-xilinx-zynqmp

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

Title:
  Backport ps uart  RS485  driver

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


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

[Bug 1821352] Re: Default Applications cannot be set in System Settings

2024-08-26 Thread udippel

Fix released, at least as far as 20.04 onwards is concerned.

** Changed in: systemsettings (Ubuntu)
   Status: Incomplete => 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/1821352

Title:
  Default Applications cannot be set in System Settings

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


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

[Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)

Did the verification for the kernel (linux-generic) like above and based
on representative kernel modules (arch-specific and common):

noble:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 24.04 LTS
Release:24.04
Codename:   noble
$ uname -a
Linux testlpar1 6.8.0-35-generic #35-Ubuntu SMP Mon May 20 15:36:54 UTC 2024 
s390x s390x s390x GNU/Linux
$ sudo unzstd 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko.zst
 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko.zst:
 507329 bytes
$ readelf -wi 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko 
| grep DW_AT_produce | grep -c mbackchain
2
$ readelf -wi 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko 
| grep DW_AT_produce | grep -c no-omit-frame-pointer
0
$ sudo unzstd 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko.zst
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko.zst: 
17383593 bytes
$ readelf -wi 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko | grep 
DW_AT_produce | grep -c mbackchain
24
$ readelf -wi 
/usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko | grep 
DW_AT_produce | grep -c no-omit-frame-pointer
0

oracular:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Oracular Oriole (development branch)
Release:24.10
Codename:   oracular
$ uname -a
Linux s1lp14 6.11.0-4-generic #4-Ubuntu SMP Tue Aug 20 14:03:40 UTC 2024 s390x 
s390x s390x GNU/Linux
$ sudo unzstd 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko.zst
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko.zst:
 529441 bytes 
$ readelf -wi 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko 
| grep DW_AT_produce | grep -c mbackchain
2
$ readelf -wi 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko 
| grep DW_AT_produce | grep -c no-omit-frame-pointer
0
$ sudo unzstd 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko.zst
[sudo] password for ubuntu: 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko.zst: 
18990945 bytes
$ readelf -wi 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko  | grep 
DW_AT_produce | grep -c mbackchain
24
$ readelf -wi 
/usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko  | grep 
DW_AT_produce | grep -c no-omit-frame-pointer
0

Like one can see '-mbackchain' is set, but "-no-omit-frame-pointer" is
not set, hence successful verified.

Closing the affected 'linux (Ubuntu)' as 'Fix Released' - and with that
the project entry as well.


** Changed in: linux (Ubuntu Noble)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Oracular)
   Status: New => Fix Released

** Changed in: ubuntu-z-systems
   Status: New => 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/2064538

Title:
  Revert back frame pointers for s390x (remove -fno-omit-frame-pointer
  but use -mbackchain)

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


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

[Bug 2076044] Re: accerciser crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/accerciser/plugin/view.py: No module named 'imp'

2024-08-26 Thread Bug Watch Updater

** Changed in: accerciser (Debian)
   Status: New => 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/2076044

Title:
  accerciser crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/accerciser/plugin/view.py: No module named 'imp'

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


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

[Bug 2077729] Re: x86/vmware: Add TDX hypercall support

2024-08-26 Thread Philip Cox

** Changed in: linux-intel (Ubuntu Noble)
 Assignee: (unassigned) => Thibf (thibf)

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

Title:
  x86/vmware: Add TDX hypercall support

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


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

[Bug 2063973] Re: network-online.target is reached before netplan-configured interfaces are online

Waiting for all (non-optional) interfaces to be ready on a link-local
level ("degraded") and one interface having a global IP ("routable") is
now implemented in Netplan v1.1.

This is according to the "Definition of an online system" [spec]. And is
implemented via a /run/systemd/system/systemd-networkd-wait-
online.service.d/10-netplan.conf drop-in configuration generated by
Netplan.

[spec] https://discourse.ubuntu.com/t/spec-definition-of-an-online-
system/27838

** Changed in: netplan.io (Ubuntu)
   Status: Triaged => 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/2063973

Title:
  network-online.target is reached before netplan-configured interfaces
  are online

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2063973/+subscriptions


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

[Bug 2077465] Re: FFe: enable sysprof integration for folks, gtk3, pango

2024-08-26 Thread Jeremy Bícha

** Description changed:

  Impact
  ==
  The Ubuntu Desktop plans to install the sysprof app by default (LP: #2077465) 
Some libraries have a build option to enable better integration with sysprof, 
so we should enable that option.
  
  This is not believed to otherwise have an impact on apps using those
  libraries.
  
  Why wasn't this done sooner?
  
  libsysprof-capture-4-dev was promoted to main August 14, the day before 
Ubuntu 24.10 Feature Freeze. There wasn't time to make these changes then with 
everything else that needed to be done that week.
  
  Testing done
  
- The changes have been applied in Debian Unstable where the builds completed 
successfully and the autopkgtests have completed successfully.
- 
- (dogtail's autopkgtest triggered by gtk+3.0 failed but that's because of
- a known at-spi2-core issue unrelated to this change)
+ The changes have been applied in Debian Unstable where the builds completed 
successfully and the autopkgtests have completed successfully. All 3 have 
successfully migrated to Debian Testing.
  
  Other Info
  ==
  folks and pango1.0 are syncs. gtk+3.0 will be a merge.

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

Title:
  FFe: enable sysprof integration for folks, gtk3, pango

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


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

[Bug 2077872] [NEW] Kernel 5.15.0-118, 119 causes suspend to fail, works fine with 5.15.0-117

2024-08-26 Thread Lukas Fichtner

Public bug reported:

System:
Env: Desktop
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Kernel: 5.15.0-118(119)-generic
secure boot enabled

Log files:
kern.log -> https://pastebin.ubuntu.com/p/KGN9QcQV9F/
lspci-vnvn.log -> https://pastebin.ubuntu.com/p/fXQYDTPVvr/
version.log -> https://pastebin.ubuntu.com/p/TZzhRshmVJ/

Description:
After updating to Kernel version 5.15.0-118(and 119), the system fails to 
suspend correctly. The system remains turned on and continues to throw errors.
The issue is evident in the logs, which show repeated failures related to task 
freezing during the suspend process. This problem does not occur with Kernel 
version 5.15.0-117, where the system suspends and resumes as expected.

visable Errors:
Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Freezing remaining freezable tasks ...
Freezing of tasks failed after 20.007 seconds (9 tasks refusing to freeze, 
wq_busy=0):
task:lockd   state:I stack:0 pid: 2511 ppid: 2 flags:0x4000
Call Trace:

__schedule+0x24e/0x590
schedule+0x69/0x110
schedule_timeout+0x105/0x140
? srso_return_thunk+0x5/0x10
? srso_return_thunk+0x5/0x10
svc_get_next_xprt+0xf1/0x190 [sunrpc]
svc_recv+0x1a9/0x330 [sunrpc]
lockd+0xa9/0x1c0 [lockd]
? set_grace_period+0xa0/0xa0 [lockd]
kthread+0x12a/0x150
? set_kthread_struct+0x50/0x50
ret_from_fork+0x22/0x30

task:nfsdstate:I stack:0 pid: 2653 ppid: 2 flags:0x4000

Solution/Workaround:
systemctl stop rpcbind nfs-server.service

Package versions:
nfs-kernel-server 1:2.6.1-1ubuntu1.2
rpcbind 1.2.6-2build1

** Affects: linux (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/2077872

Title:
  Kernel 5.15.0-118,119 causes suspend to fail, works fine with
  5.15.0-117

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


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

[Bug 2077749] Re: Regression in Ubuntu 22.04 kernel 6.8.0 for module ath9k

Please post the full kernel log showing the error. You can run 'apport-
collect 2077749' on the affected machine.

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

Title:
  Regression in Ubuntu 22.04 kernel 6.8.0 for module ath9k

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


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

[Bug 2077694] Re: package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to install/upgrade: installed linux-headers-6.8.0-41-generic package post-installation script subprocess returned error exit

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 2068107
   package linux-headers-  failed to install/upgrade: 
installed linux-headers- package post-installation script subprocess 
returned error exit status

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

Title:
  package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to
  install/upgrade: installed linux-headers-6.8.0-41-generic package
  post-installation script subprocess returned error exit status 11

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


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

[Bug 2077712] Re: lastlog does not capture all logins

2024-08-26 Thread Ravi Kant Sharma

** Tags added: rls-nn-incoming

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

Title:
  lastlog does not capture all logins

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


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

[Bug 2077760] Re: Error message after applying updates

Can you please post /var/log/apt/term.log?

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

Title:
  Error message after applying updates

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


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

[Bug 1999178] Re: netplan generator causes deadlock during systemd daemon-reload

"generate" is not calling "udevadm control --reload" anymore, as
discussed in https://github.com/canonical/netplan/pull/488

Fixed in the 1.0.1-1ubuntu2~24.04.1 SRU for Noble (LP: #2074197)

** Changed in: netplan.io (Ubuntu Noble)
   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/1999178

Title:
  netplan generator causes deadlock during systemd daemon-reload

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


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

[Bug 1987679] Re: os-prober leaves filesystems (lvm-thin, lvm snap) mounted

2024-08-26 Thread Ravi Kant Sharma

** Tags added: rls-jj-incoming

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

Title:
  os-prober leaves filesystems (lvm-thin, lvm snap) mounted

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


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

[Bug 2077784] Re: package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to install/upgrade: installed linux-headers-6.8.0-41-generic package post-installation script 서브프로세스가 오류 종료 상태 11를 반환했습니다

Can you attached the logfile
/var/lib/dkms/nvidia/535.183.01/build/make.log?

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

Title:
  package linux-headers-6.8.0-41-generic 6.8.0-41.41 failed to
  install/upgrade: installed linux-headers-6.8.0-41-generic package
  post-installation script 서브프로세스가 오류 종료 상태 11를 반환했습니다

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


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

[Bug 2077092] Re: Setting an invalid bond primary via NetworkManager will break the YAML configuration

** Tags added: foundations-todo

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

Title:
  Setting an invalid bond primary via NetworkManager will break the YAML
  configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077092/+subscriptions


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

[Bug 2069262] Re: DKMS build failures are not filed correctly

** Description changed:

  When kernel header packages (linux*-headers) are installed/upgraded, all
  installed DKMS modules are rebuilt. Currently, if any of that rebuild
  fails, a bug if filed for the kernel header package which is incorrect.
  
  There are two different scenarios, both of which are not kernel
  problems:
  
  1) An official DKMS package from the Ubuntu archive fails to build -> A
- bug should be raised for that DKMS package.
+ bug should be raised for that DKMS package and the build log should be
+ attached.
  
  2) An unsupported DKMS package fails to build -> No bug should be filed,
  but ideally the user should be made aware of the situation.
  
  An example invalid bug is bug 2067015.

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

Title:
  DKMS build failures are not filed correctly

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


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

[Bug 2077829] Re: Missing CS35L56 sof firmware for Dell Bolan platform

** Tags added: kern-11541

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

Title:
  Missing CS35L56 sof firmware for Dell Bolan platform

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


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

[Bug 2077799] Re: Ubuntu 24.04: usb 1-7: "device descriptor read/64, error -110" error during boot with USB Bluetooth Stick

Please post the full kernel log showing the errors, not just part of it.

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

Title:
  Ubuntu 24.04: usb 1-7: "device descriptor read/64, error -110" error
  during boot with USB Bluetooth Stick

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


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

[Bug 2077780] Re: package linux-image-5.15.0-119-generic 5.15.0-119.129~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-119-generic package pre-removal script subprocess returned error

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

You chose to abort the removal of the running kernel which incorrectly
triggers a bug report.

** This bug has been marked a duplicate of bug 2073399
   Aborting the removal of the running kernel triggers apport

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

Title:
  package linux-image-5.15.0-119-generic 5.15.0-119.129~20.04.1 failed
  to install/upgrade: installed linux-image-5.15.0-119-generic package
  pre-removal script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2077780/+subscriptions


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

[Bug 2077823] Re: AX88179_178a USB-ethernet adapter not always initializes properly with the kernel 6.8

This commit is in Ubuntu 6.8.0-40.40. Which kernel are you running?

** Changed in: linux-hwe-6.8 (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/2077823

Title:
  AX88179_178a USB-ethernet adapter not always initializes properly with
  the kernel 6.8

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


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

[Bug 2077571] Re: GVE stuck TX queues

2024-08-26 Thread Magali Lemes do Sacramento

** Description changed:

  [Impact]
  Request from Google to backport a set of patches to address issues in the GVE 
driver.
  
  [Fix]
  36e3b949e35964e22b9a57f960660fc599038dd4 (gve: Fix an edge case for TSO skb 
validity check)
  1b9f756344416e02b41439bf2324b26aa25e141c (gve: ignore nonrelevant GSO type 
bits when processing TSO headers)
  
  [Test]
  Compile and boot tested.
  
  [Where problems could occur]
  Changes are limited to the GVE driver.
+ 
+ [Other info]
+ #SF 00389911

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

Title:
  GVE stuck TX queues

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


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

[Bug 2077742] Re: Advanced mouse scrolling

2024-08-26 Thread Amin Bandali

Hello,

Please open a feature request for this on upstream's issue tracker at
https://bugzilla.mozilla.org and provide a link to that issue so I could
link the two together.  Thanks.

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

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: firefox (Ubuntu)
   Status: Opinion => New

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

** Changed in: firefox (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/2077742

Title:
  Advanced mouse scrolling

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


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

[Bug 2077516] Re: [FFe] libreoffice 24.8.0 for oracular

2024-08-26 Thread Rico Tzschichholz

** Description changed:

+ The testsuite had some issues in early builds which needed sorting.
+ Unfortunately this made it miss the deadline for feature-freeze.
+ 
+ We really want 24.8.x releases in oracular since the 24.2.x series will
+ be EOL by end of November.
+ 
  [Impact]
  
   * LibreOffice 24.8.0 is in its first release of the 24.8 line:
   https://wiki.documentfoundation.org/ReleasePlan/24.8#24.8.0_release
  
   24.8.0 RC3 is identical to the 24.8.0 release
  
   * This release will introduce new binary packages and add support for
  KDE6/Plasma6
  
  [Testing]
  
   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_248/594/
  
    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/16355797/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-libreoffice-libreoffice-prereleases/oracular/amd64/libr/libreoffice/20240821_041655_c1182@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-libreoffice-libreoffice-prereleases/oracular/arm64/libr/libreoffice/20240821_194039_753bf@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-libreoffice-libreoffice-prereleases/oracular/armhf/libr/libreoffice/20240821_003826_dc703@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-libreoffice-libreoffice-prereleases/oracular/ppc64el/libr/libreoffice/20240821_012605_1a707@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-libreoffice-libreoffice-prereleases/oracular/s390x/libr/libreoffice/20240821_29_c63a5@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
   * Packaging changes are staged at
  
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/oracular-24.8
  
  [Regression Potential]
  
   * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

** Changed in: libreoffice (Ubuntu)
   Importance: High => Critical

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

Title:
  [FFe] libreoffice 24.8.0 for oracular

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


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

[Bug 2077398] Re: build-depends on python3-nose or uses it for autopkgtest

2024-08-26 Thread Bug Watch Updater

** Changed in: sosreport
   Status: Unknown => Fix Released

** Changed in: sosreport
   Importance: High => Unknown

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

Title:
  build-depends on python3-nose or uses it for autopkgtest

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


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

[Bug 2077264] Re: Stuck at splash screen while shutting down due to clamd/clamav

2024-08-26 Thread Douglas Moura

Hey Mitchel, the file was generated automatically, that's the file I
have under the /var/crash folder, it's the same file as the link.

doug@bolado:/var/crash$ ll
total 675676
drwxrwsrwt  2 root whoopsie  4096 Aug 26 09:04 ./
drwxr-xr-x 14 root root  4096 Jul 17 08:55 ../
-rw-r-  1 doug whoopsie 679363927 Aug 20 09:40 
_usr_bin_clamscan.1000.crash

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

Title:
  Stuck at splash screen while shutting down due to clamd/clamav

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


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

[Bug 2077798] Re: Incomplete fix for bug 2077617 causes FTBFS

2024-08-26 Thread Pushkar Kulkarni

** Tags added: update-excuse

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

Title:
  Incomplete fix for bug 2077617 causes FTBFS

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


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

[Bug 2077809] Re: package firefox 129.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2024-08-26 Thread Amin Bandali

Hello,

Per the dpkg terminal log, the script downloading and installing the
Firefox snap encountered an unexpected EOF (end-of-file marker) while
downloading the file from the snap store. Are you able to reproduce this
issue? It may have been a temporary failure on the snap store side that
may have since been fixed. If you're still able to reproduce this issue
please add a comment with detailed steps on how to do so, otherwise
there may not be much to do here and could close the issue. Thanks.


** Changed in: firefox (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/2077809

Title:
  package firefox 129.0.2+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

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


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

[Bug 1786013] Autopkgtest regression report (linux-meta-intel-iotg-5.15/5.15.0.1064.70~20.04.1)

2024-08-26 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-intel-iotg-5.15 
(5.15.0.1064.70~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.23 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-intel-iotg-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

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

Title:
  Packaging resync

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


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

[Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)