[Bug 1889342] Re: Thunderbolt Dock Loses Monitors

[koba]

@rhpot1991,
would you please try 5.10-oem-1025 to check if the issue is gone?
Thanks

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

Title:
  Thunderbolt Dock Loses Monitors

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

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

[Bug 1928045] [NEW] I dont know

[Sebby K X]

Public bug reported:

I literally dont know

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
Uname: Linux 4.15.0-143-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue May 11 11:51:02 2021
InstallationDate: Installed on 2021-04-20 (20 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-05-11 (0 days ago)
mtime.conffile..etc.update-manager.release-upgrades: 2021-05-11T11:48:31.257537

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


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

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

Title:
  I dont know

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

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

Re: [Bug 1827442] Re: [MIR] libheif

[Christian Ehrhardt ]

> @paelzer I updated the 'All open unclaimed MIR bugs' link on the MIR
> wiki page to show both NEW and CONFIRMED bugs, and I think we should be
> sure to include 'CONFIRMED' state bugs in our weekly review, not just
> 'NEW' state bugs.

Yeah I've got a notification about it.
I agree and thank you Dan!
I have shortened the link (same function, but omitting the defaults)
and updated also the link that we use in the weekly meeting (also on
that page, but in a different place).
Finally I have updated the state-machine info on the page to reflect
that we now also consider "Confirmed" tasks in our incoming queue.

We'll have to re-review all these cases that pop up by that, they are
all a bit fallen through the cracks by this.
Once discussed we will update each of one either assigning a
(re-)reviewer or whatever else seems to be the appropriate next step.

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

Title:
  [MIR] libheif

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

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

[Bug 1923347] Re: Selecting an area on the desktop is broken on multi-monitor setups in X11

[Daniel van Vugt]

** Description changed:

+ [Impact]
+ 
  This is a new bug as of yesterday or the day before. If I select an area
  on the desktop on my rightmost monitor, the origin point of the
  selection is placed correctly at the cursor position, but other point is
  offset by the width of the leftmost monitor (see attached screenshot).
  
  Basically, the origin point is correctly at (cursor X, cursor Y), but
  the other point is at (cursor X + monitor offset X, cursor Y + monitor
  offset Y).
+ 
+ [Test Plan]
+ 
+ Set up two monitors side-by-side and log into 'Ubuntu on Xorg'. Now on
+ the rightmost monitor select an area of the desktop. Ensure the corner
+ of the selection always matches the current cursor position.
+ 
+ [Where problems could occur]
+ 
+ Anywhere in the desktop icons selection behaviour. Unlikely given all
+ that is changing is the removal of an optional optimization.
+ 
+ [Other Info]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 11 14:04:05 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-14 (574 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-01-07 (93 days ago)

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

Title:
  Selecting an area on the desktop is broken on multi-monitor setups in
  X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1923347/+subscriptions

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

[Bug 1925095] Re: GNOME Desktop selection is misaligned with the mouse on 21.04-dev

[Daniel van Vugt]

** Description changed:

+ [Impact]
+ 
  When dragging the mouse while selected on the Desktop, the selection box
  is misaligned with the mouse pointer. The issue only started happening
  on 21.04 after upgrading from 20.04 to the dev version of the OS.
+ 
+ [Test Plan]
+ 
+ Drag the mouse on the desktop and ensure the corner of the selection box
+ matches the mouse pointer position.
+ 
+ [Where problems could occur]
+ 
+ Anywhere in the desktop icons selection behaviour. Unlikely given all
+ that is changing is the removal of an optional optimization.
+ 
+ [Other Info]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 22:00:22 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-12-28 (112 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
-  LANG=pt_BR.UTF-8
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago)

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

Title:
  GNOME Desktop selection is misaligned with the mouse on 21.04-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1925095/+subscriptions

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

[Bug 1926573] Re: TGL-H USB DWC3 ID complement

[AceLan Kao]

Currently we don't have 0x9a15 pci device to verify, so will not SRU
patches.

** Description changed:

  [Impact]
  There is a new USB DWC3 ID which is required by TGL-H platform.
  
  [Fix]
  Cherry pick below series of patches from v5.12-rc2
  
https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/
  f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P
  73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU
  e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform 
device
  e68d0119e328 software node: Introduce device_add_software_node()
  
  [Test]
- Verified on Dell TGL-H gaming platform
  
  [Where problems could occur]

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

Title:
  TGL-H USB DWC3 ID complement

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

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

[Bug 1928040] Re: GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set

[Steve Langasek]

** Package changed: grub2 (Ubuntu) => grub2-signed (Ubuntu)

** Changed in: grub2-signed (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is
  set

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

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

[Bug 1927911] Re: Update intel-microcode to latest upstream release 20210216 for CVE fixes for xeon platforms

[Alex Murray]

** Also affects: intel-microcode (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Xenial)
   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/1927911

Title:
  Update intel-microcode to latest upstream release 20210216 for CVE
  fixes for xeon platforms

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

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

[Bug 1923347] Re: Selecting an area on the desktop is broken on multi-monitor setups in X11

[Daniel van Vugt]

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
   Status: Triaged => In Progress

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

Title:
  Selecting an area on the desktop is broken on multi-monitor setups in
  X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1923347/+subscriptions

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

[Bug 1925095] Re: GNOME Desktop selection is misaligned with the mouse on 21.04-dev

[Daniel van Vugt]

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
   Status: Triaged => In Progress

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

Title:
  GNOME Desktop selection is misaligned with the mouse on 21.04-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1925095/+subscriptions

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

[Bug 1927288] Re: Please enable php8.0 in Ubuntu 21.10

[Matthias Klose]

php8.0 removed from the blacklist

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

Title:
  Please enable php8.0 in Ubuntu 21.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.4/+bug/1927288/+subscriptions

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

[Bug 1907686] Re: ovn: instance unable to retrieve metadata

[Hemanth Nakkina]

Another customer hit this bug - waiting for release on uca ussuri

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

Title:
  ovn: instance unable to retrieve metadata

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1907686/+subscriptions

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

Re: [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

[koba]

@Henrik,
Thanks.
here's another test kernel that disable d3cold_allowed for nvme with hmb.
https://drive.google.com/drive/folders/1gK67OYm6-jeKLj7GIQNZLCaHuaOwVTr1?usp=sharing

Please check the status of d3cold_allowed(it must be 0) before
s2idle&resume.
sudo cat /sys/bus/pci/devices/\:58\:00.0/d3cold_allowed

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

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

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

[Bug 1921475] Re: [2.9.2] Commissioning does not collect correct storage information

[Sandor Zeestraten]

1. The disks are not SCSI (Model: ST16000NM001G, see 
https://www.seagate.com/gb/en/enterprise-storage/exos-drives/exos-x-drives/exos-x16/),
 but I suspect they are identified as such due to the HBA?
2. The bug watcher has wrongly identified that LXD has releases a fix. Please 
remove that.
2. It sounds like MAAS needs to fix the way it identifies and determines the 
type of disk.

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

Title:
  [2.9.2] Commissioning does not collect correct storage information

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

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

[Bug 1928040] Re: GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set

[Matthew Ruffell]

** Description changed:

  [Impact]
  
  GCE cloud instances started with images released prior to 2020-11-11
  will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
  packages are installed from -updates.
  
  Upon reboot, the instance drops down to a grub prompt, and ceases to
  boot any further.
  
  The output displayed is:
  
  BdsDxe: loading Boot0003 "debian" from 
HD(15,GPT,,0x2800,0x35000)/\EFI\debian\shimx64.efi
  BdsDxe: starting Boot0003 "debian" from 
HD(15,GPT,,0x2800,0x35000)/\EFI\debian\shimx64.efi
  
  UEFI: Attempting to start image.
  Description: debian
  FilePath: 
HD(15,GPT,36903981-58D9-4718-A4EC-3D3E6CF6AF42,0x2800,0x35000)/\EFI\debian\shimx64.efi
  OptionNumber: 3.
  
  GNU GRUB version 2.04
  grub>
  
  Now, on GCE cloud images prior to 2020-11-11, /etc/default/grub.d/50
  -cloudimg-settings.cfg contained this line:
  
  GRUB_DISTRIBUTOR=Debian
  
  In images after 2020-11-11, this line was REMOVED from
  /etc/default/grub.d/50-cloudimg-settings.cfg and instead, images fell
  back to the below line in /etc/default/grub
  
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
  
  The above line always returns "Ubuntu".
  
  The new grub2 version 2.02~beta2-36ubuntu3.32 now places the EFI
  executables in the /EFI/Ubuntu directory, while the grub config points
  to /EFI/Debian, and the grub config cannot be found, and hence we drop
  to a grub shell.
  
  [Testcase]
  
  You can start an instance up on Google Cloud with an affected image with
  the below command:
  
  gcloud compute instances create test-xenial-1
  --image=ubuntu-1604-xenial-v20200429 --image-project=ubuntu-os-cloud
  
  From there:
  
  $ sudo apt update
  $ sudo apt install grub-common grub-efi-amd64 grub-efi-amd64-bin 
grub-efi-amd64-signed grub-pc-bin grub2-common
  $ sudo reboot
  
  The instance will not come back up, and you will see a grub shell in the
  logs on GCP.
  
  You can also reproduce in KVM. Simply add:
  
  GRUB_DISTRIBUTOR=Debian
  
  to a file in /etc/default/grub.d/50-cloudimg-settings.cfg then:
  
  $ sudo update-grub
  $ sudo reboot
  
+ Test packages are available in the following ppa:
+ 
+ https://launchpad.net/~mruffell/+archive/ubuntu/lp1928040-test
+ 
+ If you install these test packages, you should be able to upgrade grub
+ and reboot without issue.
+ 
  [Where problems could occur]
  
  We will be changing the grub configuration for every Google cloud
  instance started with an image produced before 2020-11-11, and there is
  risk that we could make a change which prevents instances from booting.
  We should proceed with caution and make sure to test older and newer
  images.
  
  The fix will be targeted to the /etc/default/grub.d/50-cloudimg-
  settings.cfg file only, so only cloud instances would get the change,
  and only if the grub versions match particular versions.
  
  [Other info]
  
  A workaround is to remove the below line from /etc/default/grub.d/50
  -cloudimg-settings.cfg before installing the new grub packages.
  
  GRUB_DISTRIBUTOR=Debian

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

Title:
  GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is
  set

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

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

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

On Tue, May 11, 2021 at 1:35 AM Francisco Menchaca
<1921...@bugs.launchpad.net> wrote:
>
> Hi Christian,
>
> Thanks for your response.
>
> Do you mean disabling and enabling autostart to the old guests?
>
> In our dev lab worked straight away after installing the first PPA you
> bundled together, I didn't have to disable and enable  autostart.

I didn't have to do it in any of my tests either, all I was saying was
"whatever it is maybe it helps there".
As I said I'm lost on options a bit, I could get the fix prepared to
get into Ubuntu as-is, but since you seem to have a more complex issue
underneath in your prod environment we need to find if there the fix
a) doesn't help at all
b) only helps after guest autostart off/on
c) only helps after (b) plus service or even system restart
d) ??? something else ???

Since only your environment is affected by this new special behavior I
can't really debug/help much until we know what the difference is :-/

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

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

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

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

[Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04

[Jean-Baptiste Lallement]

** Tags added: rls-ii-incoming

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

Title:
  Overview sometimes fails to appear or disappear in 21.04

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

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

[Bug 1879339] Re: test_310_config_security_perf_events_restrict / test_400_refcount_config in ubuntu_qrt_kernel_security failed on F-OEM-5.6

[Steve Beattie]

Sorry for the lag on this issue.

Timo, while the added hooks are useful, they don't for the time being
obviate the need for the larger hammer of the sysctl, so we'd still like
to keep the referred to patch available, until we are forced to make a
choice if and when upstream drops the sysctl entirely.

Po-Hsu, if it's easier for tracking for it to be a separate bug report,
that's fine. Am hoping ot have more time soon to focus on qa-r-t issues
when they come up.

Thanks.

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

Title:
  test_310_config_security_perf_events_restrict /
  test_400_refcount_config in ubuntu_qrt_kernel_security failed on
  F-OEM-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1879339/+subscriptions

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

[Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[JIlani]

Hey, Touchpad is still not working on any kernels.
I did the fresh 20.04 install and seems be touchpad issue again.

Tried kernels:5.4,5.6,5.8.14,5.9,5.12

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

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

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

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

[Bug 1926673] Re: Null pointer of fig2dev of gensvg.c in function svg_arrows

[xiao huang]

Can you apply for cve for me

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

Title:
  Null pointer of fig2dev of gensvg.c in function svg_arrows

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

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

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Chris Chiu]

The dmesg log looks OK to me at least the snd_hda_codec_realtek has the
chance to configure. The weird part is why still dummy output. Can you
give me the output of the commands "pactl list sinks`, `pactl list
sources`, `aplay -l` and `arecord -l`?


Could you also try to boot the kernel with the parameter 
"snd_intel_dspcfg.dsp_driver=2" per 
https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb in "Kernel 
modules" section to see if it makes any difference? Thanks

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

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

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

[Bug 1879341] Re: test_350_retpolined_modules from ubuntu_qrt_kernel_security failed on F-OEM-5.6

[Steve Beattie]

Hi, this looks like a legit issue with the linux-oem-5.6 da903x-
regulator module, which appears to have been addressed in f16861b12fa0
("regulator: rename da903x to da903x-regulator") (v5.8-rc6), which
points out that kmod gets confused before that commit.

You can verify this with e.g.:

  $ modinfo -k 5.6.0-1055-oem 
/lib/modules/5.6.0-1055-oem/kernel/drivers/regulator/da903x.ko
  filename:   /lib/modules/5.6.0-1055-oem/kernel/drivers/regulator/da903x.ko
  license:GPL v2
  file:   drivers/mfd/da903x
  author: Mike Rapoport 
  author: Eric Miao 
  description:PMIC Driver for Dialog Semiconductor DA9034

versus the da903x backlight driver:

  $ modinfo -k 5.6.0-1055-oem 
/lib/modules/5.6.0-1055-oem/kernel/drivers/video/backlight/da903x_bl.ko
  filename:   
/lib/modules/5.6.0-1055-oem/kernel/drivers/video/backlight/da903x_bl.ko
  alias:  platform:da903x-backlight
  license:GPL
  author: Mike Rapoport 
  author: Eric Miao 
  description:Backlight Driver for Dialog Semiconductor DA9030/DA9034
  srcversion: 5FEF8A3329A530B5C1874A5
  depends:
  retpoline:  Y
  intree: Y
  name:   da903x_bl
  vermagic:   5.6.0-1055-oem SMP mod_unload modversions 
  sig_id: PKCS#7
  signer: Build time autogenerated kernel key
  sig_key:5B:09:65:9C:C7:55:2E:3D:11:79:28:EA:EE:F1:AD:DB:18:F9:34:F7
  sig_hashalgo:   sha512
  signature:  8E:0D:4A:F9:F1:F8:D3:AC:84:0F:D0:77:91:AA:62:1B:C0:65:81:AE:
  39:19:77:92:9A:99:E2:6A:A5:3A:C1:30:71:2A:89:AB:AD:24:95:06:
  F5:7D:AD:3D:A2:E6:25:66:8C:E1:44:07:37:39:0F:9F:B4:50:E1:6B:
  6A:8E:2C:1E:57:A8:76:65:88:46:12:B4:30:A1:3C:B7:96:17:1E:D7:
  C1:9A:C7:8A:48:05:0A:BF:3E:E3:D6:1B:14:50:EE:E2:FC:00:10:AE:
  18:7E:04:72:22:A0:61:31:9A:F2:8A:F5:0B:5C:87:F1:E3:63:58:6B:
  CE:AF:57:6B:EA:B7:E2:ED:17:17:E6:40:C7:92:0B:05:22:E6:06:3B:
  3B:C5:14:5F:A8:46:C3:20:A6:CB:B6:B9:9D:C9:39:A0:A1:34:90:3F:
  5B:1A:D2:EC:C4:C5:F5:84:DF:2F:16:B2:E1:92:C0:C0:A1:5F:1B:A6:
  45:69:6A:4D:16:85:9A:44:2C:13:58:5F:47:33:F3:4D:A6:E0:77:A2:
  2B:DA:76:C5:5C:17:6C:47:6A:E9:C8:A4:00:DB:F7:AA:27:5E:87:A3:
  63:BC:1B:C9:75:99:AC:5F:B1:77:18:21:6E:90:D6:70:D8:E9:8E:EE:
  59:68:44:73:CC:6E:30:FF:9D:A8:41:E2:32:1E:F7:8B:E6:97:F6:3F:
  D4:70:69:AA:02:9E:AA:C6:D6:5A:F2:64:9F:DA:E5:7F:41:2B:E5:D4:
  24:DD:20:72:4E:42:F4:5A:D4:73:46:12:61:66:99:0B:D7:35:47:2B:
  73:A2:9A:1E:4D:18:49:8D:AB:18:82:D7:A3:6C:4E:95:A4:98:7F:88:
  9E:22:74:F6:20:46:50:E1:E1:32:12:3C:32:C9:89:85:FB:F1:DC:C0:
  F1:C7:EB:45:89:E9:B5:A0:89:C3:0B:FD:FE:2D:07:28:14:AD:E9:1E:
  C1:5D:35:79:B0:53:0D:31:15:CB:74:F6:7F:E4:FE:BF:01:D4:35:34:
  4C:28:86:0A:8D:66:F5:7C:39:D3:7D:FC:69:B4:CD:6D:3A:84:8D:45:
  87:77:64:C4:A5:AD:7A:11:7C:EF:B8:EC:97:E5:EC:F4:F2:99:3D:54:
  A0:E4:08:97:28:A0:39:CE:2C:23:0C:0F:D6:28:5D:D2:AB:21:40:B7:
  F9:8E:67:50:85:62:1C:1B:4B:7E:1E:81:06:91:8B:05:B2:A4:E7:33:
  18:0E:11:D5:36:7C:00:DA:47:2C:FD:12:5A:E0:55:45:65:2A:65:9D:
  A3:32:24:44:B9:BA:E0:58:3C:D1:74:D4:98:A5:43:9C:DB:6A:B6:7C:
  27:43:EE:74:3B:BA:B2:B6:6D:F3:42:52

(It's not clear whether this is just modinfo not being able to report
correct results or that the module is actually built without retpoline
and is also unsigned.)

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

Title:
  test_350_retpolined_modules from ubuntu_qrt_kernel_security failed on
  F-OEM-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1879341/+subscriptions

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

[Bug 1928040] [NEW] GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set

[Matthew Ruffell]

Public bug reported:

[Impact]

GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.

Upon reboot, the instance drops down to a grub prompt, and ceases to
boot any further.

The output displayed is:

BdsDxe: loading Boot0003 "debian" from 
HD(15,GPT,,0x2800,0x35000)/\EFI\debian\shimx64.efi
BdsDxe: starting Boot0003 "debian" from 
HD(15,GPT,,0x2800,0x35000)/\EFI\debian\shimx64.efi

UEFI: Attempting to start image.
Description: debian
FilePath: 
HD(15,GPT,36903981-58D9-4718-A4EC-3D3E6CF6AF42,0x2800,0x35000)/\EFI\debian\shimx64.efi
OptionNumber: 3.

GNU GRUB version 2.04
grub>

Now, on GCE cloud images prior to 2020-11-11, /etc/default/grub.d/50
-cloudimg-settings.cfg contained this line:

GRUB_DISTRIBUTOR=Debian

In images after 2020-11-11, this line was REMOVED from
/etc/default/grub.d/50-cloudimg-settings.cfg and instead, images fell
back to the below line in /etc/default/grub

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

The above line always returns "Ubuntu".

The new grub2 version 2.02~beta2-36ubuntu3.32 now places the EFI
executables in the /EFI/Ubuntu directory, while the grub config points
to /EFI/Debian, and the grub config cannot be found, and hence we drop
to a grub shell.

[Testcase]

You can start an instance up on Google Cloud with an affected image with
the below command:

gcloud compute instances create test-xenial-1
--image=ubuntu-1604-xenial-v20200429 --image-project=ubuntu-os-cloud

>From there:

$ sudo apt update
$ sudo apt install grub-common grub-efi-amd64 grub-efi-amd64-bin 
grub-efi-amd64-signed grub-pc-bin grub2-common
$ sudo reboot

The instance will not come back up, and you will see a grub shell in the
logs on GCP.

You can also reproduce in KVM. Simply add:

GRUB_DISTRIBUTOR=Debian

to a file in /etc/default/grub.d/50-cloudimg-settings.cfg then:

$ sudo update-grub
$ sudo reboot

[Where problems could occur]

We will be changing the grub configuration for every Google cloud
instance started with an image produced before 2020-11-11, and there is
risk that we could make a change which prevents instances from booting.
We should proceed with caution and make sure to test older and newer
images.

The fix will be targeted to the /etc/default/grub.d/50-cloudimg-
settings.cfg file only, so only cloud instances would get the change,
and only if the grub versions match particular versions.

[Other info]

A workaround is to remove the below line from /etc/default/grub.d/50
-cloudimg-settings.cfg before installing the new grub packages.

GRUB_DISTRIBUTOR=Debian

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: grub2 (Ubuntu Xenial)
 Importance: Critical
 Status: In Progress


** Tags: sts xenial

** Also affects: grub2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: grub2 (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: grub2 (Ubuntu Xenial)
   Status: New => In Progress

** Tags added: sts xenial

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

Title:
  GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is
  set

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

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

[Bug 1928039] [NEW] Release Upgrade crashes when trying to upgrade to 20.04.2 LTS

[Aiden]

Public bug reported:

The machine says Could not calculate the upgrade and then says "An
unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to investigate this yourself the log files in
'/var/log/dist-upgrade' will contain details about the upgrade.
Specifically, look at 'main.log' and 'apt.log'."

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 5.4.0-1047.49~18.04.1-azure 5.4.106
Uname: Linux 5.4.0-1047-azure x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
Date: Tue May 11 04:56:37 2021
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-05-11 (0 days ago)
VarLogDistupgradeLspcitxt:
 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) [8086:7192] (rev 03)
 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA 
[8086:7110] (rev 01)
 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE 
[8086:7111] (rev 01)
 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] 
(rev 02)
 00:08.0 VGA compatible controller [0300]: Microsoft Corporation Hyper-V 
virtual VGA [1414:5353]

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


** Tags: amd64 apport-bug bionic dist-upgrade uec-images

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

Title:
  Release Upgrade crashes when trying to upgrade to 20.04.2 LTS

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

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

[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs

[Thomas Bechtold]

** Changed in: livecd-rootfs (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: livecd-rootfs (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: livecd-rootfs (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Changed in: livecd-rootfs (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => In Progress

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

Title:
  Add ubuntu-oci project for building OCI-ready tarballs with livecd-
  rootfs

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

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

[Bug 1928026] Re: Cannot suspend after the first suspend

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1928026/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

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

Title:
  Cannot suspend after the first suspend

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

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

[Bug 1892475] Re: /usr/bin/ld: utils.o:(.data.rel.local+0x0): multiple definition of `xprintf'; xs_tdb_dump.o:(.bss+0x0): first defined here collect2: error: ld returned 1 exit status

[Launchpad Bug Tracker]

[Expired for xen (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xen (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  /usr/bin/ld: utils.o:(.data.rel.local+0x0): multiple definition of
  `xprintf'; xs_tdb_dump.o:(.bss+0x0): first defined here collect2:
  error: ld returned 1 exit status

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

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

[Bug 1877618] Re: 20.04 fails to boot via PXE (amd64) - "hidden .disk not found, and hard to discover"

[Launchpad Bug Tracker]

[Expired for casper (Ubuntu) because there has been no activity for 60
days.]

** Changed in: casper (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  20.04 fails to boot via PXE (amd64) - "hidden .disk not found, and
  hard to discover"

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

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

[Bug 1892205] Re: tcgbios.c:1519:33: error: taking address of packed member of ‘struct ’ may result in an unaligned pointer value [-Werror=address-of-packed-member]

[Launchpad Bug Tracker]

[Expired for xen (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xen (Ubuntu)
   Status: Incomplete => Expired

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

Title:
   tcgbios.c:1519:33: error: taking address of packed member of ‘struct
  ’ may result in an unaligned pointer value [-Werror=address-of-packed-
  member]

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

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

[Bug 1908930] Re: libwebkit2gtk-4.0-37 missing files break epiphany

[Launchpad Bug Tracker]

[Expired for webkit2gtk (Ubuntu) because there has been no activity for
60 days.]

** Changed in: webkit2gtk (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  libwebkit2gtk-4.0-37 missing files break epiphany

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

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

[Bug 1917298] Re: dbus-daemon not started after reboot

[Launchpad Bug Tracker]

[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: dbus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  dbus-daemon not started after reboot

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

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

[Bug 1917298] Re: dbus-daemon not started after reboot

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  dbus-daemon not started after reboot

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

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

[Bug 1917298] Re: dbus-daemon not started after reboot

[Launchpad Bug Tracker]

[Expired for dbus (Ubuntu Focal) because there has been no activity for
60 days.]

** Changed in: dbus (Ubuntu Focal)
   Status: Incomplete => Expired

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

Title:
  dbus-daemon not started after reboot

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

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

[Bug 1917298] Re: dbus-daemon not started after reboot

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu Focal) because there has been no activity
for 60 days.]

** Changed in: systemd (Ubuntu Focal)
   Status: Incomplete => Expired

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

Title:
  dbus-daemon not started after reboot

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

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

[Bug 1918497] Re: connect to one shared folder error package

[Launchpad Bug Tracker]

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  connect to one shared folder error package

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

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

[Bug 1918586] Re: File system becomes read only during upgrade

[Launchpad Bug Tracker]

[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  File system becomes read only during upgrade

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

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

[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs

[Thomas Bechtold]

** Description changed:

  [Impact]
  
  Currently the ubuntu-base livecd-rootfs project is used to build tarballs 
that are the base for building docker/OCI images.
  The tarballs produced with the ubuntu-base project are modified externally 
(see https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh ) 
to create the "official" ubuntu images on dockerhub.
  
  When including the ubuntu-oci project into livecd-rootfs, we can build
  tarballs that already contain the changes that are currently done
  externally. This has multiple advantages:
  
  1) a Dockerfile using that tarball would no longer have to modify anything 
(means less layers)
  2) publishing new OCI images no longer depends on the external dockerhub 
image creation. Currently eg. the AWS ECR ubuntu containers depend on the 
containers from dockerhub. That would be no longer the case with this change
  3) Possible faster reaction on CVEs. no longer depending on external 
processes.
  
  [Test Plan]
  
- 1) Build a test ubuntu-oci tarball with ubuntu-old-fashioned:
+ 1) build ubuntu-oci project
+ a) Build a test ubuntu-oci tarball with ubuntu-old-fashioned:
  
  ./scripts/ubuntu-bartender/ubuntu-bartender --no-cleanup --  --series
  impish --image-format plain --project ubuntu-oci --subproject minimized
  
- 2) create a Dockerfile using the tarball created in step 1):
+ b) create a Dockerfile using the tarball created in step 1):
  
  cat << EOF > Dockerfile
  FROM scratch
  ADD ubuntu-impish-oci-cloudimg-amd64-root.tar.gz /
  CMD ["/bin/bash"]
  EOF
  
- 3) build the container
+ c) build the container
  
  docker build .
  
- 4) run something in the container:
+ d) run something in the container:
  
  docker run -it $container-id uname -a
  
- 5) check the size of the docker image and compare with the image for the
+ e) check the size of the docker image and compare with the image for the
  same series available on dockerhub
  
+ 2) build another project (ubuntu-base minimized)
+ TODO: describe test steps
  
  [Where problems could occur]
  
  This change could break other livecd-rootfs projects which might lead to
  failed builds. But beside that, there is nothing I can think of that
  would be affected by this change.
  
  [Other Info]
  
  When this is accepted, there will be livefs builds available at
  https://launchpad.net/~cloud-images-release-
  managers/+livefs/ubuntu/$SERIES/ubuntu-oci

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

Title:
  Add ubuntu-oci project for building OCI-ready tarballs with livecd-
  rootfs

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

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

[Bug 1928038] [NEW] Multiple memory leaks in libgdiplus

[Chintan Shah]

Public bug reported:

Multiple memory leaks have been identified in libgdiplus library when
the test code provided ibgdiplus/tests/testgdi.c is compiled with ASAN
enabled. Memory leaks have been found in multiple components of the
library as below :

0x7fce7e31a3d0 in GdipCreatePen1 /home/targets/libgdiplus/src/pen.c:258

0x7fce7e36d4da in GdipCreateSolidFill
/home/targets/libgdiplus/src/solidbrush.c:138

Following is the output of the testgdi.c when it is compiled with ASAN.

jpg drawn 
tif drawn 
gif drawn 
png drawn 
bmp drawn 
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
  after 127 requests (127 known processed) with 0 events remaining.

=
==61628==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 504 byte(s) in 3 object(s) allocated from:
#0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7fce7e31a3d0 in gdip_pen_new /home/targets/libgdiplus/src/pen.c:66
#2 0x7fce7e31a3d0 in GdipCreatePen1 /home/targets/libgdiplus/src/pen.c:258

Direct leak of 256 byte(s) in 1 object(s) allocated from:
#0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7fce7bb720b9  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1d0b9)

Direct leak of 168 byte(s) in 3 object(s) allocated from:
#0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7fce7e36d4da in gdip_solidfill_new 
/home/targets/libgdiplus/src/solidbrush.c:55
#2 0x7fce7e36d4da in GdipCreateSolidFill 
/home/targets/libgdiplus/src/solidbrush.c:138

Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x7fce7e6a2961 in realloc 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98961)
#1 0x7fce7dbf325c  (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x5025c)

Indirect leak of 168 byte(s) in 3 object(s) allocated from:
#0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7fce7e36d4da in gdip_solidfill_new 
/home/targets/libgdiplus/src/solidbrush.c:55
#2 0x7fce7e36d4da in GdipCreateSolidFill 
/home/targets/libgdiplus/src/solidbrush.c:138

Indirect leak of 160 byte(s) in 2 object(s) allocated from:
#0 0x7fce7e6a279a in __interceptor_calloc 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a)
#1 0x7fce7dbf322e  (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x5022e)

Indirect leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x7fce7e6a279a in __interceptor_calloc 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a)
#1 0x7fce7bb727c8  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1d7c8)

Indirect leak of 16 byte(s) in 2 object(s) allocated from:
#0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7fce7dbf3cb5  (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x50cb5)

SUMMARY: AddressSanitizer: 1320 byte(s) leaked in 16 allocation(s)


Information requested: 

# lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

#apt-cache policy libgdiplus
libgdiplus:
  Installed: 4.2-1ubuntu1
  Candidate: 4.2-1ubuntu1
  Version table:
 *** 4.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

Expected : No memory leaks while running the test code
What happened : Couple of memory leaks in libgdiplus component as indicated in 
the output.

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

** Attachment added: "This is the ASAN compiled version of testgdi.c"
   
https://bugs.launchpad.net/bugs/1928038/+attachment/5496252/+files/compiled_testgdi

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

Title:
  Multiple memory leaks in libgdiplus

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

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

[Bug 1927841] Re: Video Driver bug

[Stephan Foley]

This was very helpful. On ubuntuforums, it was suggested that I check
the "Optimus" setting under the "Video" menu in the BIOS. That solved
half the problem. Then following your suggestion and changing the
Multimedia engine in SMPlayer to /usr/bin/mpv solved the other half.

Nvidia currently works and CPU usage is now around 10%, which I am
pretty amazed about. Thanks!

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

Title:
  Video Driver bug

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

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

[Bug 1875459] Re: System hangs when loading google maps on chrome with navi AMD GPU

[Kai-Heng Feng]

I think the desktop should use HWE kernel (5.8) by now. Can you please
give it a try?

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

Title:
  System hangs when loading google maps on chrome with navi AMD GPU

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

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

[Bug 1928030] [NEW] s3ql 3.7.0 crash, version bump requested

[Henry Wertz]

Public bug reported:

I "backported" s3ql (built .debs for python3-pyfuse3_3.2.0-2build1,
python3-trio_0.18.0-1, and s3ql_3.7.0+dfsg-2build1-local1 to use in
Ubuntu 20.04), and encountered a fairly quick crash (like under a
minute) when I started writing data to the s3ql filesystem.  The log
ends with several "During handling of the above exception, another
exception occurred:" python tracebacks, ending with
"s3ql.block_cache.NoWorkerThreads: no upload threads".  Per the bug
referenced, this won't result in data loss, a umount + fsck.s3ql cleans
it up fine.  But still.

https://github.com/s3ql/s3ql/issues/234

Bug fixed in 3.7.1, I built 3.7.2 and it works a treat.  No crashes
under very heavy usage; it's a bit faster than 3.3.4 that 20.04 focal
ships with in general usage and much faster to unmount.

3.7.0 is current version in hirsute and impish, so should be bumped to
3.7.2.

** Affects: s3ql (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/1928030

Title:
  s3ql 3.7.0 crash, version bump requested

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

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

[Bug 1879339] Re: test_310_config_security_perf_events_restrict / test_400_refcount_config in ubuntu_qrt_kernel_security failed on F-OEM-5.6

[Kelsey Skunberg]

** Tags added: 5.6 oem oem-5.6 sru-20210412

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

Title:
  test_310_config_security_perf_events_restrict /
  test_400_refcount_config in ubuntu_qrt_kernel_security failed on
  F-OEM-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1879339/+subscriptions

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

[Bug 1879341] Re: test_350_retpolined_modules from ubuntu_qrt_kernel_security failed on F-OEM-5.6

[Kelsey Skunberg]

** Tags added: 5.6 oem oem-5.6 sru-20210412

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

Title:
  test_350_retpolined_modules from ubuntu_qrt_kernel_security failed on
  F-OEM-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1879341/+subscriptions

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

[Bug 1887487] Re: range bound deduction test in test_verifier from ubuntu_bpf failed on F-oem-5.6

[Kelsey Skunberg]

** Tags added: oem-5.6 sru-20210412

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

Title:
  range bound deduction test in test_verifier from ubuntu_bpf failed on
  F-oem-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887487/+subscriptions

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

[Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

[Kelsey Skunberg]

** Tags added: oem oem-5.6

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

Title:
  btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions

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

[Bug 1880631] Re: l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable

[Kelsey Skunberg]

** Tags added: oem-5.6 sru-20210412

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

Title:
  l2tp.sh from net in ubuntu_kernel_selftests failed with test not
  executable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880631/+subscriptions

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

[Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H

[Kelsey Skunberg]

** Tags added: oem-5.6

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

Title:
  icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
  F-OEM-5.6 / G / H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880645/+subscriptions

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

[Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux

[Kelsey Skunberg]

** Tags added: oem oem-5.6

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

Title:
  psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892213/+subscriptions

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

[Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite

[Kelsey Skunberg]

** Tags added: oem oem-5.6 sru-20210412

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

Title:
  xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in
  ubuntu_kernel_selftests will fail if running the whole suite

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions

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

[Bug 1879345] Re: probe event parser error log check in ftrace from ubuntu_kernel_selftests failed on F-OEM-5.6

[Kelsey Skunberg]

** Tags added: oem oem-5.6 sru-20210412

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

Title:
  probe event parser error log check in ftrace from
  ubuntu_kernel_selftests failed on F-OEM-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879345/+subscriptions

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

[Bug 1928026] [NEW] Cannot suspend after the first suspend

[ahiung lim]

Public bug reported:

The suspend fail, it wakes up after 4 or 5 seconds from suspending. This
issue is very similar to Elementary OS's problem which I discovered. The
only difference is that in Ubuntu, it can suspend for the first time
after the restart or turned on, after waking up, it wont be able to
suspend again until restart.

Ubuntu 20.04.2 LTS
Macbook Air 13" Mid 2013

** Affects: 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/1928026

Title:
  Cannot suspend after the first suspend

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

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

[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

[Daniel van Vugt]

This bug probably should not have been recycled for gnome-shell users.
This bug is from 2014 and relates to Compiz/Unity. If you are using
gnome-shell then please subscribe to bug 1927948 instead.

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

Title:
  Windows change Monitor/Desktop after screen lock

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

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

[Bug 1927948] Re: Windows switch monitor after resuming from sleep

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1419
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1419
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2092
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092
   Importance: Unknown
   Status: Unknown

** Tags added: multimonitor

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

Title:
  Windows switch monitor after resuming from sleep

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

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

[Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so)

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
apport-cli YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

** Changed in: xserver-xorg-video-ati (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/1926050

Title:
  [radeon] Web benchmark freezing and crashing the system (Xorg crashes
  in Mesa's r600_dri.so)

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

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

[Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system

[Daniel van Vugt]

Thanks for that. Your system log shows it was Xorg crashing in the
radeon driver:

mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: radeon: The kernel rejected 
CS, see dmesg for more information (-16).
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE)
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Backtrace:
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 0: /usr/bin/Xwayland 
(OsLookupColor+0x13c) [0x563171f8122c]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fd7d0f9547f]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 2: 
/lib/x86_64-linux-gnu/libc.so.6 (__nss_database_lookup+0x44c4) [0x7fd7d0ef52e4]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x74483) 
[0x7fd7cf85bde3]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x7a00b) 
[0x7fd7cf866c8b]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x128cc) 
[0x7fd7cf7982fc]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x13efe) 
[0x7fd7cf79b1fe]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x19952) 
[0x7fd7cf7a6592]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (nouveau_drm_screen_create+0x214793) 
[0x7fd7cfd68943]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (nouveau_drm_screen_create+0x21489a) 
[0x7fd7cfd68c5a]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x5e6cd) 
[0x7fd7cf8301dd]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 11: 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so 
(__driDriverGetExtensions_zink+0x3b139) [0x7fd7cf1266c9]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 12: /usr/bin/Xwayland 
(glamor_get_modifiers+0x76d) [0x563171e27e3d]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 13: /usr/bin/Xwayland 
(XkbDDXTerminateServer+0x102) [0x563171f325c2]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 14: /usr/bin/Xwayland 
(XkbDDXTerminateServer+0x12cb) [0x563171f3496b]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 15: /usr/bin/Xwayland 
(XkbDDXTerminateServer+0x683) [0x563171f33013]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 16: /usr/bin/Xwayland 
(XkbDDXTerminateServer+0xc16) [0x563171f33b46]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 17: /usr/bin/Xwayland 
(XkbDDXTerminateServer+0x1f90) [0x563171f362b0]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 18: /usr/bin/Xwayland 
(SendErrorToClient+0x354) [0x563171f4a5c4]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 19: /usr/bin/Xwayland 
(InitFonts+0x3b4) [0x563171f4e654]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 20: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fd7d0daf0b3]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 21: /usr/bin/Xwayland 
(_start+0x2e) [0x563171e1c5be]
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE)
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Bus error at address 
0x7fd7d07c4000
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE)
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: Fatal server error:
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Caught signal 7 (Bus 
error). Server aborting

** Summary changed:

- [radeon] Web benchmark freezing and crashing the system
+ [radeon] Web benchmark freezing and crashing the system (Xorg crashes in 
Mesa's r600_dri.so)

** Package changed: linux-hwe-5.8 (Ubuntu) => mesa (Ubuntu)

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [radeon] Web benchmark freezing and crashing the system (Xorg crashes
  in Mesa's r600_dri.so)

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

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

[Bug 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login

[Daniel van Vugt]

Thanks. I can see lots of crashes and errors from your gnome-shell
extensions. Please remove them by:

  cd /home/grizzlysmit/.local/share/gnome-shell/
  rm -rf extensions

then log out and in again. And if you experience any problems again
after that then just follow the instructions in comment #5 again.

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

Title:
  on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins
  after login

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

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

[Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

[Daniel van Vugt]

** No longer affects: sddm (Ubuntu)

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

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

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

[Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction

[Daniel van Vugt]

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

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 1922353, 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. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 1922353
   Overview sometimes fails to appear or disappear in 21.04

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

Title:
  Gnome Activities Overview Unresponsive to Mouse or Touchscreen
  Interaction

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

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

[Bug 1925139] Re: efi: Failed to lookup EFI memory descriptor

[Steve Langasek]

Verified for hirsute.

** Description changed:

  efi: Failed to lookup EFI memory descriptor
  
  is an error message generated by the kernel.
  
  Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
  
  [Test case]
- Verify that 'sudo journalctl -b -1 | grep 'efi: Failed to lookup' returns no 
results.
+ Verify that 'sudo journalctl -b 0 | grep 'efi: Failed to lookup' returns no 
results.

** Description changed:

  efi: Failed to lookup EFI memory descriptor
  
  is an error message generated by the kernel.
  
  Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
  
  [Test case]
- Verify that 'sudo journalctl -b 0 | grep 'efi: Failed to lookup' returns no 
results.
+ Verify that 'sudo journalctl -b | grep 'efi: Failed to lookup' returns no 
results.

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

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

Title:
  efi: Failed to lookup EFI memory descriptor

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

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

[Bug 1928017] Re: The Restriced Codecs article recommends an application that was recently discontinued

[Gunnar Hjalmarsson]

Thanks for calling our attention to this. It affects both ubuntu-docs
and gnome-user-docs, so I submitted an upstream issue as well.

** Also affects: gnome-user-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-user-docs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-docs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-docs (Ubuntu)
   Status: New => Confirmed

** Bug watch added: gitlab.gnome.org/GNOME/gnome-user-docs/-/issues #123
   https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/123

** Also affects: gnome-user-docs via
   https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/123
   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/1928017

Title:
  The Restriced Codecs article recommends an application that was
  recently discontinued

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1928017/+subscriptions

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

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[MikeMecanic]

Fresh installed HH final ISO alongside Windows 10 secure boot enabled.
Proposed must be enabled in Hirsute (9 packages):

sudo apt install shim-signed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  shim-signed
1 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 447 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://mirrors.edge.kernel.org/ubuntu hirsute-proposed/main amd64 
shim-signed amd64 1.47+15.4-0ubuntu2 [447 kB]
Fetched 447 kB in 1s (865 kB/s)
Preconfiguring packages ...
(Reading database ... 159131 files and directories currently installed.)
Preparing to unpack .../shim-signed_1.47+15.4-0ubuntu2_amd64.deb ...
Unpacking shim-signed (1.47+15.4-0ubuntu2) over (1.46+15.4-0ubuntu1) ...
Setting up shim-signed (1.47+15.4-0ubuntu2) ...
Trying to migrate /boot/efi into esp config
Installing grub to /boot/efi.
Installing for x86_64-efi platform.
Installation finished. No error reported.

mokutil --sb
SecureBoot enabled
SecureBoot validation is disabled in shim

uname -r
5.13.0-051300rc1-generic

sda   232.9G
├─sda1 vfat 100M /boot/efi  
├─sda2   16M
├─sda3 ntfs   150.1G
└─sda4 ext482.6G /

All good!

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

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

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

[Bug 1925139] Re: efi: Failed to lookup EFI memory descriptor

[Steve Langasek]

** Description changed:

  efi: Failed to lookup EFI memory descriptor
  
  is an error message generated by the kernel.
  
  Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
+ 
+ [Test case]
+ Verify that 'sudo journalctl -b -1 | grep 'efi: Failed to lookup' returns no 
results.

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

Title:
  efi: Failed to lookup EFI memory descriptor

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

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

[Bug 1880211] Re: Logwatch package points to wrong location for zfs utils

[Bryce Harrington]

On all target releases, I've reproduced the bug with the old logwatch
version, and verified the issue is resolved with the new logwatch
version.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-groovy verification-needed-xenial
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-groovy verification-done-xenial

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

Title:
  Logwatch package points to wrong location for zfs utils

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

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

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

Hi Christian,

Thanks for your response.

Do you mean disabling and enabling autostart to the old guests?

In our dev lab worked straight away after installing the first PPA you
bundled together, I didn't have to disable and enable  autostart.

Kind Regards,
FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483

  


On Mon, 10 May 2021 at 22:31, Christian Ehrhardt  <
1921...@bugs.launchpad.net> wrote:

> Hi Francisco,
> I have re-checked but I don't see any other related code for your issue.
> The PPA contains the one fix we know about.
>
> I could think of old guests (that existed and were configured autostart
> before the upgrade) to maybe stay in their odd state. But disabling and
> enabling autostart for them should make it work.
> Is at least that working for you?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921325
>
> Title:
>   VM will not auto-start automatically when server is rebooted after
>   virsh domrename
>
> Status in libvirt package in Ubuntu:
>   Fix Released
> Status in libvirt source package in Bionic:
>   Triaged
> Status in libvirt source package in Focal:
>   Fix Released
>
> Bug description:
>
>   OS: Ubuntu 18.04.5
>   uname -r
>   4.15.0-118-generic
>
>
>   /usr/bin/qemu-system-x86_64 --version
>   QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>
>
>   $ virsh version
>   Compiled against library: libvirt 4.0.0
>   Using library: libvirt 4.0.0
>   Using API: QEMU 4.0.0
>   Running hypervisor: QEMU 2.11.1
>
>   VM running on KVM on different servers won't start automatically when
>   the server is rebooted after changing the VM domain name.
>
>   Issue Replication:
>
>   1. Set the VM to autostart
>   2. Reboot the server
>   3. VM will start automatically
>   4. Changed the VM domain name virsh domrename VM.old VM.new
>   5. Set the VM.new domain to autostart
>   6. Reboot the server
>   7. VM.new won't start automatically.
>
>   Can you please assist?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions
>

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

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

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

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

[Bug 1928021] [NEW] ubuntu_sysdig_smoke_test: "test_060_nx" fails on focal/linux-oracle

[Khaled El Mously]

Public bug reported:

Example failure:

http://10.246.72.9/5.4.0-1045.49-oracle/focal-linux-oracle-oracle-
amd64-5.4.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
security.py.DEBUG.html


Failure output: 

585.FAIL: test_060_nx (__main__.KernelSecurityTest)
586.NX bit is working
587.--
588.Traceback (most recent call last):
589.File "./test-kernel-security.py", line 554, in test_060_nx
590.self.assertShellExitEquals(rie_expected, ["./nx-test-rie", "data"])
591.File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1166, in assertShellExitEquals
592.self.assertEqual(expected, rc, msg + result + report)
593.AssertionError: Got exit code -11, expected 0
594.Command: './nx-test-rie', 'data'
595.Output:
596.rodata:0x559730ee5008
597.data: 0x559730ee7010
598.bss: 0x559730ef7040
599.brk: 0x5597313a62b0
600.rw: 0x7fa963894000
601.rwx: 0x7fa963867000
602.stack: 0x7ffe099e9eb0
603.Dump of /proc/self/maps:
604.559730ee3000-559730ee4000 r--p  08:01 1562993 
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
605.559730ee4000-559730ee5000 r-xp 1000 08:01 1562993 
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
606.559730ee5000-559730ee6000 r--p 2000 08:01 1562993 
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
607.559730ee6000-559730ee7000 r--p 2000 08:01 1562993 
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
608.559730ee7000-559730ee8000 rw-p 3000 08:01 1562993 
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
609.559730ee8000-559730ef8000 rw-p  00:00 0
610.5597313a5000-5597313c6000 rw-p  00:00 0 [heap]
611.7fa96366b000-7fa96369 r--p  08:01 45790 
/usr/lib/x86_64-linux-gnu/libc-2.31.so
612.7fa96369-7fa963808000 r-xp 00025000 08:01 45790 
/usr/lib/x86_64-linux-gnu/libc-2.31.so
613.7fa963808000-7fa963852000 r--p 0019d000 08:01 45790 
/usr/lib/x86_64-linux-gnu/libc-2.31.so
614.7fa963852000-7fa963853000 ---p 001e7000 08:01 45790 
/usr/lib/x86_64-linux-gnu/libc-2.31.so
615.7fa963853000-7fa963856000 r--p 001e7000 08:01 45790 
/usr/lib/x86_64-linux-gnu/libc-2.31.so
616.7fa963856000-7fa963859000 rw-p 001ea000 08:01 45790 
/usr/lib/x86_64-linux-gnu/libc-2.31.so
617.7fa963859000-7fa96385f000 rw-p  00:00 0
618.7fa963867000-7fa963868000 rwxp  00:00 0
619.7fa963868000-7fa963869000 r--p  08:01 45783 
/usr/lib/x86_64-linux-gnu/ld-2.31.so
620.7fa963869000-7fa96388c000 r-xp 1000 08:01 45783 
/usr/lib/x86_64-linux-gnu/ld-2.31.so
621.7fa96388c000-7fa963894000 r--p 00024000 08:01 45783 
/usr/lib/x86_64-linux-gnu/ld-2.31.so
622.7fa963894000-7fa963895000 rw-p  00:00 0
623.7fa963895000-7fa963896000 r--p 0002c000 08:01 45783 
/usr/lib/x86_64-linux-gnu/ld-2.31.so
624.7fa963896000-7fa963897000 rw-p 0002d000 08:01 45783 
/usr/lib/x86_64-linux-gnu/ld-2.31.so
625.7fa963897000-7fa963898000 rw-p  00:00 0
626.7ffe099cb000-7ffe099ec000 rwxp  00:00 0 [stack]
627.7ffe099ee000-7ffe099f1000 r--p  00:00 0 [vvar]
628.7ffe099f1000-7ffe099f2000 r-xp  00:00 0 [vdso]
629.ff60-ff601000 --xp  00:00 0 [vsyscall]
630.Attempting to execute function at 0x559730ee7010
631.If this program seg-faults, the region was enforced as non-executable...
632.
633.
634.--
635.Ran 125 tests in 73.445s
636.
637.FAILED (failures=1)



This failure is expected on the 5.4 oracle kernel, since it no longer assumes 
READ_IMPLIES_EXEC personality by default, as per this change: 

https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
oracle/+git/focal/commit/?id=0e74912698dc008056759c501e7de3c551daedf1


So this test will fail from now on on f/oracle.

The test should treat f/oracle as it treats the 5.8 kernels - it should
expect a return output of -11 not 0.

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

** No longer affects: linux-oracle (Ubuntu)

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

[Bug 1909171] Re: sddm-greeter segfault

[Remy]

Dude... I wish you posted that before I started all of these on my side !!
See ?? We both posted nearly at the same time !

I tried to downgrade first but I don't know why it started to throw me
huge dependency problems (Qt5 and tons of unknown packages)... I gave
up...

Feeling as surprised as you are when I fired up your "mesa downgrading
command"... No dependency warnings... Well since it's now working for
me, I was not going to play again with those nasty things and going to a
possibly new nightmare by pressing "Y" but yeah ! no dependency
warning...

rcornet solution seems to be the best/safest one provided there is no
dependency warnings.

Cheers

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

Title:
  sddm-greeter segfault

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

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

[Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49

[Ted L]

Thank you Po-Hsu.  The 5.8.0-52.59 kernel appears to be working fine on
Focal.

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

Title:
  IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49

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

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

[Bug 1928019] Re: package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade: installed plymouth-theme-ubuntustudio package post-removal script subprocess returned error exit status 1

[Erich Eickmeyer ]

This will happen if you try it. Never add the ubuntustudio-* packages
directly. If you wish to use the Ubuntu Studio packages on a regular
Ubuntu install, install "ubuntustudio-installer" first as this is the
supported method. The method you tried is unsupported, so I'm closing
this bug.

** Changed in: ubuntustudio-look (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/1928019

Title:
  package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade:
  installed plymouth-theme-ubuntustudio package post-removal script
  subprocess returned error exit status 1

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

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

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

[Congelli501]

I tested the pre-built binary of the latest version of runc (by just replacing 
/usr/sbin/runc) and I was able to go to 400 pods on a single test node.
This new version was released today.

```
root@node0:~# runc -v
runc version 1.0.0-rc94
spec: 1.0.2-dev
go: go1.14.15
libseccomp: 2.5.1
```
https://github.com/opencontainers/runc/releases

 
I tried the pre-built binary of runc 1.0.0-rc93, and I was stuck to 164 pods 
again with "code = DeadlineExceeded desc = context deadline exceeded" error:
```
root@node0:~# runc -v
runc version 1.0.0-rc93
spec: 1.0.2-dev
go: go1.14.14
libseccomp: 2.5.1
```

The changelog for 1.0.0-rc94 contains this line that could match:
runc init: fix a hang caused by deadlock in seccomp/ebpf loading code
(regression in rc93, #2871)


The version 1.0.0-rc92 was working fine too.
```
root@node0:~# runc -v
runc version 1.0.0-rc92
spec: 1.0.2-dev
```

Please upgrade to version 1.0.0-rc94 or downgrade to 1.0.0-rc92.

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

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

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

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

[Bug 1923268] Re: grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac} before /grub/grub.cfg

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402538

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

Title:
  grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
  before /grub/grub.cfg

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

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

[Bug 1921915] Re: Bluetooth controller not detected on CM4

[William Wilson]

** Changed in: pi-bluetooth (Ubuntu Focal)
   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/1921915

Title:
  Bluetooth controller not detected on CM4

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

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

[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy

[William Wilson]

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

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

Title:
  SRU bluetooth fixes and CVEs to focal and groovy

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

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

[Bug 1928019] Re: package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade: installed plymouth-theme-ubuntustudio package post-removal script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade:
  installed plymouth-theme-ubuntustudio package post-removal script
  subprocess returned error exit status 1

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

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

[Bug 1928019] [NEW] package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade: installed plymouth-theme-ubuntustudio package post-removal script subprocess returned error exit status 1

[Christopher Wilson]

Public bug reported:

Unfortunately, I made the mistake of trying to add ubuntustudio packages
to a base install of Ubuntu 20.04 and there has been a problem.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: plymouth-theme-ubuntustudio 20.04.1
ProcVersionSignature: Ubuntu 5.6.0-1055.59-oem 5.6.19
Uname: Linux 5.6.0-1055-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May  5 11:42:18 2021
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
ErrorMessage: installed plymouth-theme-ubuntustudio package post-removal script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-10-30 (192 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201030-14:39
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: ubuntustudio-look
Title: package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade: 
installed plymouth-theme-ubuntustudio package post-removal script subprocess 
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntustudio-look (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade:
  installed plymouth-theme-ubuntustudio package post-removal script
  subprocess returned error exit status 1

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

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

[Bug 1921915] Re: Bluetooth controller not detected on CM4

[William Wilson]

The verification passed for Groovy.

*** On Pi 400 **

ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available
[bluetooth]#

ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1.1~20.10.1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 *** 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 *** 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:F6:84:4E Pairable: yes
[bluetooth]# devices
[bluetooth]# list
Controller DC:A6:32:F6:84:4E ubuntu [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:F6:84:4E Discovering: yes
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade
[NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0
[bluetooth]#

* On CM4 **
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available
[bluetooth]#

ubuntu@ubuntu:~$ !apt
apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1.1~20.10.1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 *** 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 *** 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:FE:BA:B2 Pairable: yes
[bluetooth]# devices
[bluetooth]# list
Controller DC:A6:32:FE:BA:B2 ubuntu [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:FE:BA:B2 Discovering: yes
[NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[bluetooth]#

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

-- 
You received this bug notification because you are a member of 

[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy

[William Wilson]

The verification passed for Groovy.

*** On Pi 400 **

ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available
[bluetooth]#

ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1.1~20.10.1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 *** 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 *** 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:F6:84:4E Pairable: yes
[bluetooth]# devices
[bluetooth]# list
Controller DC:A6:32:F6:84:4E ubuntu [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:F6:84:4E Discovering: yes
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade
[NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0
[bluetooth]#


* On CM4 **
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
 *** 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available
[bluetooth]#

ubuntu@ubuntu:~$ !apt
apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1.1~20.10.1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 *** 0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 0.1.15ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 *** 4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted 
arm64 Packages
100 /var/lib/dpkg/status
 3-0ubuntu2~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted 
arm64 Packages
 2-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 
Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:FE:BA:B2 Pairable: yes
[bluetooth]# devices
[bluetooth]# list
Controller DC:A6:32:FE:BA:B2 ubuntu [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:FE:BA:B2 Discovering: yes
[NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[bluetooth]#

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

Title:
  SRU bluetooth fixes and CVEs

[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x

[Michael Hudson-Doyle]

So the initramfs-tools with the fix has migrated now, the next impish
daily should have it (serial 20210511 or later). Would you be able to
test to see if that helps?

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

Title:
  Getting error "ipconfig: no devices to configure" while trying to
  autoinstall in a VLAN env on s390x

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

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

[Bug 1927029] Re: ua attach command fails

[Alex Trepca]

I uploaded it to this Gist:
https://gist.githubusercontent.com/atrepca/dede1e2f4b894a444d6ac0f0abeaf5dd/raw/e5877b08940773e01e5ef93596f31ede49cb69e0
/ubuntu-advantage.log

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

Title:
  ua attach command fails

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

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

[Bug 1927029] Re: ua attach command fails

[Alex Trepca]

Trying again...

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

Title:
  ua attach command fails

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

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

[Bug 1927029] Re: ua attach command fails

[Alex Trepca]

I can't seem to be able to attach, ok to post the full log here? It's
1342 lines.

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

Title:
  ua attach command fails

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

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

[Bug 1909171] Re: sddm-greeter segfault

[rcornet]

Remy (remyzerems) solution seems better if the PPA author can be trusted.
Part of the security in Linux, comes from not installing random  stuff  on the 
Internet.
PPAs are individual repos that anyone can set up without Ubuntu responsability 
or oversight.

I know nothing about the PPA author, maybe the greatest guy ever.
I just want to remind people of performing due diligence on adding repos from
 unknown/un-trusted sources.

I will stay with the downgraded mesa, since the platform I use is a laptop 
where everything
I need works right now. Is older hardware, so there is no need for the newest 
and the
 greatest video card drivers.

I'll wait for the official mesa from ubuntu.

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

Title:
  sddm-greeter segfault

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

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

[Bug 1926437] Autopkgtest regression report (python-apt/1.6.5ubuntu0.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-apt (1.6.5ubuntu0.6) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

botch/unknown (arm64)
update-manager/unknown (arm64)
apt/1.6.13 (amd64)
ubiquity/unknown (arm64)
isenkram/unknown (arm64)
python-apt/unknown (arm64)
chromium-browser/unknown (arm64)
livecd-rootfs/unknown (arm64)
aptdaemon/1.1.1+bzr982-0ubuntu19.5 (i386)
breezy-debian/unknown (arm64)
bzr-builddeb/unknown (arm64)
apport/2.20.9-0ubuntu7.23 (amd64)
software-properties/0.96.24.32.14 (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/bionic/update_excuses.html#python-apt

[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/1926437

Title:
  [SRU] Backport zstd support, fix bug in python-apt

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

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

[Bug 1921134] Re: SBAT shim 15.4 release

[Steve Langasek]

This is a false-positive for the SRU due to the binary copy of shim 1.47
from impish to hirsute-proposed.  It has already been fixed in hirsute
release, there is no change here and no need for an SRU verification.

** Changed in: shim-signed (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

** Tags removed: verification-needed

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

Title:
  SBAT shim 15.4 release

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

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

[Bug 1925673] Re: Please set binary package compression to xz

[Steve Langasek]

This was not necessary to include in the SRU of shim-signed to hirsute
(and in fact I specifically omitted the change from the upload I did to
hirsute-proposed, which got clobbered).  But it also doesn't have any
impact for hirsute since -Zxz is already the default, so given that the
package has successfully been installed by users I consider this
verified and not a blocker for the SRU.

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

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

Title:
  Please set binary package compression to xz

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

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

[Bug 1928011] Re: grub-efi-amd64-signed: Depends: grub2-common (>= 2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

[Daniel Hollocher]

*within a release.  I've also updated the information above.  Let me
know what further info is needed.

** Changed in: grub2-signed (Ubuntu)
   Status: Incomplete => New

** Changed in: update-manager (Ubuntu)
   Status: Incomplete => New

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

Title:
  grub-efi-amd64-signed: Depends: grub2-common (>=
  2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

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

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

[Bug 1928011] Re: grub-efi-amd64-signed: Depends: grub2-common (>= 2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

[Daniel Hollocher]

This is package upgrades with a release.

** Description changed:

- I think this might be an issue with softare-updater, honestly.  But it won't 
upgrade grub, giving this as an explanation: 
+ EDIT:I'm using the software update tool to do a regular package upgrade
+ on Xubuntu 20.04.
+ 
+ I think this might be an issue with softare-updater, honestly.  But it won't 
upgrade grub, giving this as an explanation:
  ***
  PACKAGE DEPENDENCIES CANNOT BE RESOLVED
  This error could be caused by required additional software packages which are 
missing or not installable. Furthermore there could be a conflict between 
software packages which are not allowed to be installed at the same time.
  Transaction failed: Package dependencies cannot be resolved
-  The following packages have unmet dependencies:
+  The following packages have unmet dependencies:
  
  grub-efi-amd64-signed: Depends: grub2-common (>= 2.02~beta2-36ubuntu3.31) but 
2.04-1ubuntu26.11 is to be installed
  ***
- 
  
  Isn't 2.04 > than 2.02?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon May 10 16:32:05 2021
  InstallationDate: Installed on 2020-04-01 (404 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: grub2-signed
  UpgradeStatus: Upgraded to focal on 2020-09-29 (223 days ago)

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

Title:
  grub-efi-amd64-signed: Depends: grub2-common (>=
  2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

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

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

[Bug 1883089] Fix included in openstack/neutron 16.3.2

[OpenStack Infra]

This issue was fixed in the openstack/neutron 16.3.2 release.

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

Title:
  [L3] floating IP failed to bind due to no agent gateway port(fip-ns)

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

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

[Bug 1925768] Re: Losing Wifi connection when USB-C Hub was plugged-in

[Miroslav Andjelkovic]

Yes, when I just plug in my hub (also without any connections), my wifi
connection get lost.

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

Title:
  Losing Wifi connection when USB-C Hub was plugged-in

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

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

[Bug 1928011] Re: grub-efi-amd64-signed: Depends: grub2-common (>= 2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

[Steve Langasek]

> Isn't 2.04 > than 2.02?

Yes, it is:

$ dpkg --compare-versions 2.04-1ubuntu26.11 gt 2.02~beta2-36ubuntu3.31; echo $?
0
$

So I don't see what the problem here is based on the information
available.

Did this error happen as part of a release upgrade between two releases,
or package upgrades within a release?  We will need more logs in order
to diagnose but the answer to the previous question establishes which
logs we need.

** Changed in: grub2-signed (Ubuntu)
   Status: New => Incomplete

** Changed in: update-manager (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/1928011

Title:
  grub-efi-amd64-signed: Depends: grub2-common (>=
  2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

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

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

[Bug 1928017] [NEW] The Restriced Codecs article recommends an application that was recently discontinued

[Media Physics]

Public bug reported:

https://help.ubuntu.com/stable/ubuntu-help/video-dvd-restricted.html
https://help.ubuntu.com/stable/ubuntu-help/video-dvd.html.en

These two help articles both recommend the Fluendo DVD Player for
legally playing DVDs. However, Fluendo announced that they would be
discontinuing their product as of April 11, 2021, and new licenses don't
appear to be available anymore (https://fluendo.com/en/blog/post
/oneplay-dvd-player-product-discontinuation/). As such, these
instructions are no longer accurate.

The AskUbuntu community is currently searching for alternatives
(https://askubuntu.com/questions/1337426/legally-playing-dvds-post-
april-2021), but, in the mean-time, at least a note saying that the
software was discontinued will be helpful.

** Affects: ubuntu-docs (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/1928017

Title:
  The Restriced Codecs article recommends an application that was
  recently discontinued

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

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

[Bug 1884723] Fix included in openstack/neutron 17.1.2

[OpenStack Infra]

This issue was fixed in the openstack/neutron 17.1.2 release.

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

Title:
  [OVS] multicast between VM instances on different compute nodes is
  broken with IGMP snooping enabled

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

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

[Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

[Mark Cunningham]

** Description changed:

  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).
  
- There are already two customer cases from the US Army complaining about
- this behavior
- 
(https://canonical.lightning.force.com/lightning/r/Case/5004K03vkq4QAA/view
- and
- 
https://canonical.lightning.force.com/lightning/r/Case/5004K03tkbmQAA/view).
+ There are already two customer cases from Canonical clients complaining
+ about this behavior (00297697 and 00303806).
  
  Also, potentially, this will cause further problems in the future, since
  both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock
  accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead to
  the busy node environment.
  
  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there is
  no plan to fix this issue!
  
  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.
  
  Note that we don't propose to remove pam_tally2, since not every user of
  this module is affected.
  
  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.
  
  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it with
  pam_tally2), we could not reproduce the conditions to test pam_faillock
  with.
  
  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

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

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

[Bug 1863608] Re: version 80 does not start using remote display (X11)

[Benjamin Cahill]

Thanks for the heads up. I upgraded Chromium to
90.0.4430.72-0ubuntu0.16.04.1 and it's working fine here as well.

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

Title:
  version 80 does not start using remote display (X11)

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

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

[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[William Wilson]

The verification passed for focal.

* On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
  Installed: 5.53-0ubuntu3
  Candidate: 5.53-0ubuntu3.1
  Version table:
 5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
Packages
 *** 5.53-0ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages
100 /var/lib/dpkg/status
pi-bluetooth:
  Installed: 0.1.10ubuntu6
  Candidate: 0.1.15ubuntu0~20.04.1
  Version table:
 0.1.15ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse 
arm64 Packages
 *** 0.1.10ubuntu6 500
500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.04.1
  Candidate: 4-0ubuntu0~20.04.1
  Version table:
 4-0ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse 
arm64 Packages
 *** 3-0ubuntu2~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 
Packages
100 /var/lib/dpkg/status
 1.20200212-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl devices
No default controller available

ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
  Installed: 5.53-0ubuntu3.1
  Candidate: 5.53-0ubuntu3.1
  Version table:
 *** 5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 5.53-0ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages
pi-bluetooth:
  Installed: 0.1.15ubuntu0~20.04.1
  Candidate: 0.1.15ubuntu0~20.04.1
  Version table:
 *** 0.1.15ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse 
arm64 Packages
100 /var/lib/dpkg/status
 0.1.10ubuntu6 500
500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.04.1
  Candidate: 4-0ubuntu0~20.04.1
  Version table:
 *** 4-0ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse 
arm64 Packages
100 /var/lib/dpkg/status
 3-0ubuntu2~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 
Packages
 1.20200212-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:F6:84:4E Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:F6:84:4E Discovering: yes
[NEW] Device 28:11:A5:D5:AC:98 28-11-A5-D5-AC-98
[NEW] Device 68:27:37:05:F4:ED [TV] Samsung 6 Series (55)
[NEW] Device 5B:1B:6F:46:F3:00 5B-1B-6F-46-F3-00
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[NEW] Device 42:25:C8:1B:5F:D2 42-25-C8-1B-5F-D2
[NEW] Device 64:FF:0A:21:B1:70 64-FF-0A-21-B1-70
[CHG] Device 28:11:A5:D5:AC:98 RSSI: -62
[CHG] Device 28:11:A5:D5:AC:98 TxPower: 8
[CHG] Device 28:11:A5:D5:AC:98 Name: LE-Lemonade
[CHG] Device 28:11:A5:D5:AC:98 Alias: LE-Lemonade
[NEW] Device 4B:04:19:F1:60:90 4B-04-19-F1-60-90
[bluetooth]#

** On CM4 **

apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
  Installed: 5.53-0ubuntu3
  Candidate: 5.53-0ubuntu3.1
  Version table:
 5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
Packages
 *** 5.53-0ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages
100 /var/lib/dpkg/status
pi-bluetooth:
  Installed: 0.1.10ubuntu6
  Candidate: 0.1.15ubuntu0~20.04.1
  Version table:
 0.1.15ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse 
arm64 Packages
 *** 0.1.10ubuntu6 500
500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.04.1
  Candidate: 4-0ubuntu0~20.04.1
  Version table:
 4-0ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse 
arm64 Packages
 *** 3-0ubuntu2~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 
Packages
100 /var/lib/dpkg/status
 1.20200212-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl devices
No default controller available

ubuntu@ubuntu:~$ apt-cache policy bluez linux-firmware-raspi2 pi-bluetooth
bluez:
  Installed: 5.53-0ubuntu3.1
  Candidate: 5.53-0ubuntu3.1
  Version table:
 *** 5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 5.53-0ubuntu3 500
500 h

[Bug 1909171] Re: sddm-greeter segfault

[Remy]

Hi guys !

I managed to get it working by upgrading the mesa driver to the latest version 
using the Kisak-mesa PPA as described there :
https://itsfoss.com/install-mesa-ubuntu/
I followed the paragraph : "Install the latest stable version of Mesa driver in 
Ubuntu [Latest point release]"

Note that the command "sudo apt install mesa" did not work, so I just
did "sudo apt upgrade" instead which installed all the required stuff
from the kisak PPA.

It installed the mesa 21.1.0 which is working great on my config. I got
the sddm back working (still flickering if I move the mouse to another
account, but still working !!).

Seems like the Firefox tabs crash is no longer occurring now (I'm using
FF 88.0).

Hope this helps !

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

Title:
  sddm-greeter segfault

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

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

[Bug 1909171] Re: sddm-greeter segfault

[rcornet]

I have another workaround, which actually makes sddm-greeter work again.
I had my doubts so I went to confirm my assumptions. You can skip my
detective work and rambling by going under the asterisk line.

And it is true that both programs which JohnDoe_71Rus (johndoe99)
mentions have similar issues. I haven't looked at glxinfo till now and
just now found that pages at unix.stackexchange.com cause tabs crashes
with the RIP CODE message in dmesg. But only if I reach to the end of
the web page. Strange behavior. Disabling hardware acceleration does not
solve the problem.

I mentioned previously that viewing video files was no problem and I tried 
'mpv' from the terminal and it uses the gpu driver and works fine, except that 
it crashes when the video ends with a seg fault. Which is probably why I did 
not notice the problem when using SMPlayer as the GUI.
Using the vo=xv driver causes no error when finishing the 

I suppose that I was just lucky that most webs I visits don't require
the magic 3d that makes certain pages crash firefox tabs.

Still sddm-greeter should not fail so catastrophically when it does
nothing so complex that requires the gpu's shadow magic. Without
terminal-fu level skills most users wont be able to maneuver through the
issue. And blindly will blame it on Linux being "unusable".

Some level of fault tolerance is needed but hardware issues are
difficult to plan around.

But again: Why sddm-greeter uses gpu's magic?

Dependencies perhaps? Is it Qt5 indirect fault?

Running gdb on sddm on runlevel 2 with no X and the segfault appeared in  :
QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5

There is no RIP Code message in dmesg. So I was not convinced.

strace was not helpfull either.

So I gave up on finding the exact culprit. Short of recompiling sddm,
qt5 and mesa and debugging them in tandem. Unfortunately I don't have
the time.

*

First: I'm using Lubuntu 20.04, newer *buntu versions I have no idea of
their status/compatibility/versioning/etc. This only applies to 20.04.

So I tracked down the main mesa libraries and downgraded them all to the
previous version.

#apt install libglapi-mesa=20.0.4-2ubuntu1 libglx-mesa0=20.0.4-2ubuntu1
libgl1-mesa-dri=20.0.4-2ubuntu1 libegl-mesa0=20.0.4-2ubuntu1
libgbm1=20.0.4-2ubuntu1

So then with dpkg-reconfigure sddm-greeter I selected it again as the
display manager.

Went to runlevel 5 and presto IT WORKS. Firefox tabs do not crash
anymore on unix.stackexchange.com and mpv on the command line using the
gpu driver does not segfaults anymore on exit.

So I can confirm without doubt that the main culprit as JohnDoe_71Rus
said, is in the mesa libraries upgrade. But I can't confirm the exact
code/library where the problem is located.

Surprisingly i did not have any dependencies issues when downgrading
this libraries. Other people experience might differ due to the
uniqueness of their systems.

To prevent apt from upgrading this packages again;

#apt-mark hold libglapi-mesa=20.0.4-2ubuntu1 libglx-
mesa0=20.0.4-2ubuntu1 libgl1-mesa-dri=20.0.4-2ubuntu1 libegl-
mesa0=20.0.4-2ubuntu1 libgbm1=20.0.4-2ubuntu1

When the patched update to the mesa bug comes just use "apt-mark unhold"
with the same list.

This workaround/solution by downgrading might break some stuff and might not be 
future proof.
So far on my own testing everything works.

The changelog for mesa: 
https://launchpad.net/ubuntu/focal/+source/mesa/+changelog
does not seem that impressive, so unless there is a change in your hardware 
there should be no impact on your system. But I can't give any guaranties. 


Most of the changelog is ppc64 fixes and the big upgrade: 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699


I hope this helps others.

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

Title:
  sddm-greeter segfault

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

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

[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy

[William Wilson]

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

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

Title:
  SRU bluetooth fixes and CVEs to focal and groovy

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

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

[Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pam (Ubuntu)
   Status: New => Confirmed

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

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

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

[Bug 1928011] Re: grub-efi-amd64-signed: Depends: grub2-common (>= 2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

[Daniel Hollocher]

Tj, from irc #ubuntu, says "I can see the problem. it's the onegrub
builds for i386 going back to 16.04 ... the updater is picking the FIRST
in the list which is for Version: 1.167+2.04-1ubuntu44"

I think this is in reference to a change in grub2: grub2-unsigned
(2.04-1ubuntu44) hirsute; urgency=medium

  * Compile grub-efi-amd64 installable i386 platform on hirsute, to make
it available in bionic and earlier as part of onegrub builds.

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

Title:
  grub-efi-amd64-signed: Depends: grub2-common (>=
  2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed

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

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

[Bug 1926057] Re: nextcloud crashes with SIGSEV

[monochromec]

Still causing SIGSEV with  3.1.1-1ubuntu1.1.

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

Title:
  nextcloud crashes with SIGSEV

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

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