[Bug 1455818] Re: [SRU] mysql-server-5.6.postrm fails when /usr/share/mysql-common/configure-symlinks doesn't exist

[Christian Ehrhardt ]

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

** This bug has been marked a duplicate of bug 1771630
   package mysql-server-5.7 (not installed) failed to install/upgrade: 
installed mysql-server-5.7 package post-installation script subprocess returned 
error exit status 127

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

Title:
  [SRU] mysql-server-5.6.postrm fails when /usr/share/mysql-common
  /configure-symlinks doesn't exist

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

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

[Bug 1771630] Re: package mysql-server-5.7 (not installed) failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127

[Christian Ehrhardt ]

I've just marked another bug report a dup.
For the sake of collecting all different-but-same causes in one place I wanted 
to quote the issue.
In the new case it is - again - a mysql from a 3rd party that is interfering 
with what is provided by Ubuntu.

In this case due to leftovers of mysql-community-* packages from
https://dev.mysql.com/downloads/mysql/

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

Title:
  package mysql-server-5.7 (not installed) failed to install/upgrade:
  installed mysql-server-5.7 package post-installation script subprocess
  returned error exit status 127

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

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

[Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child

[Christian Ehrhardt ]

+1 to Timo to not go for "system nssdb" for the cause of this case here.
Also system-wide-trust would be bug 1647285 and is quite a different scope.

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

Title:
  Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for
  p11_child

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

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

[Bug 1906612] Re: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127

[Christian Ehrhardt ]

Hi Ankit,
I'll mark this as a dup of bug 1771630 and comment there for you.
Because this is "another, but still similar case" to that other bug.
Please read there for what this is about and how to resolve.

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

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

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

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

[Bug 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

[lizhiyuan]

gnome-session-binary[6932]: GnomeDesktop-WARNING: Could not create
transient scope for PID 7153:
GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process
with ID 7153 does not exist.

** Package changed: meta-gnome3 (Ubuntu) => gnome-session (Ubuntu)

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

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

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

[Bug 1906727] Re: focal iscsiadm and blockdev location is wrongly mention in apparmor profi; le

[James Page]

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

** Changed in: charm-nova-compute
   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/1906727

Title:
  focal iscsiadm and blockdev location is wrongly mention in apparmor
  profi;le

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1906727/+subscriptions

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

[Bug 1906642] Re: Xorg crashes with abort in iris_dri.so

[Timo Aaltonen]

Any reason why you haven't installed updates? Your mesa is old, there's
20.0.8-0ubuntu1~20.04.1 available since July.

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

Title:
  Xorg crashes with abort in iris_dri.so

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

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

[Bug 1906770] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1906770

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Kernel 5.4.0-56 Wi-Fi does not connect

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

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

[Bug 1906774] [NEW] Crashed during INstall on the new PI 400 Keyboard PC.

[michael robert zubas jr]

Public bug reported:

I tried to INstall the new Ubuntu MATE onto the new Raspberry Pi 400
Keyboard PC that was recently Released, and gave me an Error.

Tehre is the BUg Report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-1015.15-raspi 5.4.44
Uname: Linux 5.4.0-1015-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: arm64
CasperMD5CheckResult: skip
Date: Fri Dec  4 01:49:55 2020
ImageMediaBuild: 20200812
SourcePackage: ubiquity
UbiquityDebug:
 
UbiquitySyslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 focal oem-config 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/1906774

Title:
  Crashed during INstall on the new PI 400 Keyboard PC.

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

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

[Bug 1906774] Re: Crashed during INstall on the new PI 400 Keyboard PC.

[michael robert zubas jr]

Please look into this so others who buy this new Product can have Ease
Of Use.

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

Title:
  Crashed during INstall on the new PI 400 Keyboard PC.

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

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

[Bug 1899180] Re: autopkgtest fails Bionic@amd64 (service) and Hirsute@arm64 (racy)

[Christian Ehrhardt ]

Recent Hirsute stats:
  arm64
smoke-lxc  (F 22% f  0% S  0% B 15% => P 62%/) 
..FF.F...BF..F...BF.FB.F...BBB.F

All seem to be like:
+ check_domain
+ grep+  -qs sl[[:space:]]\+running
virsh list
+ virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls
error: Requested operation is not valid: Init pid is not yet available

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

Title:
  autopkgtest fails Bionic@amd64 (service) and Hirsute@arm64 (racy)

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

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

[Bug 1899180] Re: autopkgtest almost always fails in Bionic on amd64

[Christian Ehrhardt ]

On Hirsute this now also became (from a yet unknown change in a different 
component) flaky.
Essentially having timing issues between "start" and "lxc-enter-namespace".
Since we like the test, but not actually care too much about libvirt-lxc (we 
favor LXD by orders of magnitude for that use case) I think what I'll implement 
is:

1. make the test skippable
2. skip if the restart of libvirtd failed (we still want to test the 
consequence of guests being alive if it worked, but if the restart itself 
failed we should skip)
3. on check_domain since we seem to have races between start and being ready 
add a retry mechanism

I'll test that in hirsute where the current arm64 issues happen and if
working well there that can be what we backport along the next SRUs.

** Summary changed:

- autopkgtest almost always fails in Bionic on amd64
+ autopkgtest fails Bionic@amd64 (service) and Hirsute@arm64 (racy)

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

Title:
  autopkgtest fails Bionic@amd64 (service) and Hirsute@arm64 (racy)

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

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

[Bug 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

[lizhiyuan]

This problem not only affects the display of the tray, but also affects the 
work of some boot-up programs, including but not limited to nextcloud and qvray.
Qvray’s main interface display will be misaligned, and the work is not very 
normal. Restart after kill -9 is no problem.

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

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

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

[Bug 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])

[Timo Aaltonen]

Right, it still needs amdgpu.exp_hw_support=1 on 5.4.

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

Title:
  FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is
  AMD/ATI Renoir [1002:1636])

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

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

[Bug 684982]

[Me-x6]

sorry to revive a dead thread, but is this expected to work on Firefox
83.0 (build id 20201112153044) + Gnome 3.38 + Wayland/DRM?

when restoring my session, all Firefox windows are created on the first
workspace.

does a setting or feature flag need to be enabled to take advantage of
this?

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

Title:
  Firefox windows don't restore on correct workspaces

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

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

[Bug 1906739] Re: default sssd pam config breaks local user logins if sssd isn't running

[Timo Aaltonen]

Do you have pam_localuser in there? Should be above pam_sss.

If not, then fix your config.

https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/860488

** Changed in: sssd (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/1906739

Title:
  default sssd pam config breaks local user logins if sssd isn't running

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

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

[Bug 1906770] [NEW] Kernel 5.4.0-56 Wi-Fi does not connect

[Ted R Marcus]

Public bug reported:

After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot complete
connection to network with Netgear A6210 USB adapter (Mediatek MT7612U
chipset). Network manager can see available networks, but attempting to
connect to a network stalls on "connecting" and does not complete
connection. Reverting to 5.4.0-54 solves problem. I did not see this
problem after updating to 5.4.0-56 on a 10-year-old Toshiba Satellite
laptop (also Mint 19.3), so it appears related to the Netgear/Mediatek
hardware.

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

** Attachment added: "Running under kernel 5.4.0-54"
   
https://bugs.launchpad.net/bugs/1906770/+attachment/5440850/+files/lspci-vnvn.log

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

Title:
  Kernel 5.4.0-56 Wi-Fi does not connect

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

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

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

[Christian Ehrhardt ]

r10-6819 had 22 good runs.
r10-6829 will be the next to try.

Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18 (signature different)
r10-6080 good 0 of 10
r10-6586 good 0 of 27
r10-6760 good 0 of 20
r10-6799 good 0 of 20
r10-6819 good 0 of 22
r10-6829 next
r10-6839 bad 2 of 9
r10-7093 bad 2 of 19
20200507 bad 3 of 7

Signatures:
r10-4054 arm_legitimate_address_p (nonimmediate)
r10-6839 add_regs_to_insn_regno_info (lra)
r10-7093 add_regs_to_insn_regno_info (lra)
r10-7093 add_regs_to_insn_regno_info (lra)
20200507 add_regs_to_insn_regno_info (lra)
20200507 avoid_constant_pool_reference (lra)
20200507 extract_plus_operands (lra)
ubu-10.2 add_regs_to_insn_regno_info (lra)
ubu-10.2 add_regs_to_insn_regno_info (lra)
ubu-10.2 avoid_constant_pool_reference (lra)
ubu-10.2 thumb2_legitimate_address_p (lra)

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

Title:
  gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation
  fault

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

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

[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

[Daniel van Vugt]

https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/-/merge_requests/193

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

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

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

[Bug 1906107] Re: "unexpectedly disconnected from host boot status daemon" under high memory load

[Kai-Heng Feng]

Would it be possible for you to do a reverse kernel bisection?

First, find the first -rc kernel works and the last -rc kernel doesn’t
work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect new $(the working version you found)
$ git bisect old $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it doesn’t work,
$ git bisect old
Otherwise,
$ git bisect new
Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the issue.

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

Title:
  "unexpectedly disconnected from host boot status daemon" under high
  memory load

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

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

[Bug 1901572] Re: snapd vulnerable to Library Injection from CWD

[Alex Murray]

Deleted PoC etc before marking this public.

** Attachment removed: "snap-escape-POC.tar.gz"
   
https://bugs.launchpad.net/snapcraft/+bug/1901572/+attachment/5427455/+files/snap-escape-POC.tar.gz

** Attachment removed: "make_libc.py"
   
https://bugs.launchpad.net/snapcraft/+bug/1901572/+attachment/5427456/+files/make_libc.py

** Information type changed from Private Security to Public Security

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

Title:
  snapd vulnerable to Library Injection from CWD

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

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

[Bug 1906767] [NEW] while updating an unspecific fault

[Oliver Dicklhuber]

Public bug reported:

while updating on ubuntu 20.04 an error message is created

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.41
ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18
Uname: Linux 4.15.0-126-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Fri Dec  4 06:56:41 2020
InstallationDate: Installed on 2015-10-06 (1885 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-12-04 (0 days ago)
VarLogDistupgradeTermlog:

** 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/1906767

Title:
  while updating an unspecific fault

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

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

[Bug 1905620] Re: please promote modules from extra to modules for HiFive Unleashed

[Dimitri John Ledkov]

and it looks like that is failing to reboot over telnet connection =/
i'll build a brand new image with 5.8.0-11 kernel directly and will try
that.

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

Title:
  please promote modules from extra to modules for HiFive Unleashed

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

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

[Bug 1905620] Re: please promote modules from extra to modules for HiFive Unleashed

[Dimitri John Ledkov]

Deployed focal image.

And checked where currently loaded modules are coming from

$ cat /proc/modules |cut -f1 -d\ | xargs -L1 modinfo | sed -n 's/filename: 
*//p' | xargs dpkg -S
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/uio/uio_pdrv_genirq.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/uio/uio.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/gpu/drm/drm.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/net/sched/sch_fq_codel.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/gpu/drm/drm_panel_orientation_quirks.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/net/ipv4/netfilter/ip_tables.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/net/netfilter/x_tables.ko
linux-modules-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/fs/autofs/autofs4.ko
linux-modules-extra-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko
linux-modules-extra-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/cadence/macb.ko
linux-modules-extra-5.4.0-24-generic: 
/lib/modules/5.4.0-24-generic/kernel/drivers/i2c/busses/i2c-ocores.ko


Enabled groovy, groovy-updates, groovy-proposed.

Performed

$ sudo apt install linux-virtual linux-generic-

such that 5.8.0-11 kernel is installed from groovy-proposed, *without*
modules-extra.

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

Title:
  please promote modules from extra to modules for HiFive Unleashed

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

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

[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

[Daniel van Vugt]

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   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/1898462

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

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

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

[Bug 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)

[You-Sheng Yang]

** Changed in: linux-firmware (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Groovy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: Incomplete => In Progress

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Hirsute)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Hirsute)
   Status: Incomplete => In Progress

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Invalid => Won't Fix

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

Title:
  Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)

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

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

[Bug 1905620] Re: please promote modules from extra to modules for HiFive Unleashed

[Dimitri John Ledkov]

starting verification of the groovy's build. It will take a bit of time
=)

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

Title:
  please promote modules from extra to modules for HiFive Unleashed

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

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

[Bug 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]

[You-Sheng Yang]

** Changed in: linux-firmware (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Groovy)
   Status: Confirmed => In Progress

** Changed in: linux-firmware (Ubuntu Groovy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]

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

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

[Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

Yes, when --use-ldaps is specified, adcli will make a TLS connection to
the domain controller, and speak LDAPS. This works, and is the reason
why this bug slipped through our regression testing. I should have
tested without the --use-ldaps flag as well.

Regardless, this bug seems to be caused by the GSS-SPNEGO implementation
in the cyrus-sasl2 package being broken. adcli links to libsasl2
-modules-gssapi-mit, which is a part of cyrus-sasl2, since adcli does
not implement GSS-SPNEGO itself, and relies on cyrus-sasl libraries.

I downloaded the source package of cyrus-sasl2 2.1.27+dfsg-2 from Focal,
and I built it on Bionic, and installed it. I then tried a adcli join,
and it worked:

https://paste.ubuntu.com/p/R8PyHJMNtT/

Looking at the cyrus-sasl2 source repo, it seems the Bionic version is
missing a lot of commits related to GSS-SPNEGO support.

Commit 816e529043de08f3f9dcc4097380de39478b0b16
From: Simo Sorce 
Date: Thu, 16 Feb 2017 15:25:56 -0500
Subject: Fix GSS-SPNEGO mechanism's incompatible behavior
Link: 
https://github.com/cyrusimap/cyrus-sasl/commit/816e529043de08f3f9dcc4097380de39478b0b16

Commit 4b0306dcd76031460246b2dabcb7db766d6b04d8
From: Simo Sorce 
Date: Mon, 10 Apr 2017 19:54:19 -0400
Subject: Add support for retrieving the mech_ssf
Link: 
https://github.com/cyrusimap/cyrus-sasl/commit/4b0306dcd76031460246b2dabcb7db766d6b04d8

Commit 31b68a9438c24fc9e3e52f626462bf514de31757
From: Ryan Tandy 
Date: Mon, 24 Dec 2018 15:07:02 -0800
Subject: Restore LIBS after checking gss_inquire_sec_context_by_oid
Link: 
https://github.com/cyrusimap/cyrus-sasl/commit/31b68a9438c24fc9e3e52f626462bf514de31757

This doesn't even seem to be a complete list either, and if we backport
these patches to the Bionic cyrus-sasl2 package, it fails to build for
numerous reasons.

I also found a similar bug report in Debian, which features the above third 
commit: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917129

>From what I can tell, GSS-SPNEGO in cyrus-sasl2 for Bionic has never
worked, and changing it to the default was a bad idea.

So, we have a decision to make. If supporting the new Active Directory
requirements in ADV190023 [1][2] which adds --use-ldaps for adcli, as a
part of bug 1868703 is important, and something the community wants, we
need to fix up cyrus-sasl2 to have a working GSS-SPNEGO implementation.

[1] https://msrc.microsoft.com/update-guide/en-us/vulnerability/ADV190023
[2] 
https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows

If we don't want --use-ldaps for adcli, then we can revert the patches
for adcli on Bionic, and go back to what was working previously, with
GSS-API.

** Bug watch added: Debian Bug tracker #917129
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917129

** Also affects: cyrus-sasl2 (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/1906627

Title:
  adcli fails, can't contact LDAP server

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

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

[Bug 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]

[You-Sheng Yang]

Verified with bug 1890105 (AX210 bluetooth) in
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1890130
/support-intel-bluetooth-typhoon-peak/unstable. Will submit SRU patches
later.

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

Title:
  Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]

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

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

[Bug 1905274] Re: enable u-boot spl for riscv64

[Dimitri John Ledkov]

Groovy will not receive these changes. There will not be a point release
of groovy to make a new image. Focal images will be provided at next
point release which will only be supported to upgrade to hirsute or next
LTS.

** Description changed:

- enable u-boot spl for riscv64
+ [Impact]
  
- 1) backport opensbi 0.8 to focal
- https://bugs.launchpad.net/ubuntu/focal/+source/opensbi/+bug/1905456
+  * To build bootable uboot-sifive package, it must be built with
+ opensbi. Currently those are missbuilt and not packaged.
  
- 2) build u-boot with opensbi specified
+ [Test Case]
  
- 3) ship uboot-spl in the cloud image
+  * Download u-boot buildlog for riscv64
+ 
+ and Look for:
+ 
+ /<>/"arch/riscv/lib/mkimage_fit_opensbi.sh" \
+ arch/riscv/dts/hifive-unleashed-a00.dtb > u-boot.its
+ WARNING: OpenSBI binary "fw_dynamic.bin" not found, resulting binary is not 
functional.
+ 
+ 
+ * A missbuilt package will have the Warning emitted by 
mkimage_fit_opensbi.sh, whereas fixed u-boot package will not.
+ 
+ * Check that uboot-sifive riscv64 .deb provides
+ 
+ ./usr/lib/u-boot/sifive_fu540/u-boot-spl.bin
+ ./usr/lib/u-boot/sifive_fu540/u-boot.bin
+ ./usr/lib/u-boot/sifive_fu540/u-boot.itb
+ ./usr/lib/u-boot/sifive_fu540/uboot.elf
+ 
+ As those will be consumed by livecd-rootfs when building bootable
+ preinstalled images.
+ 
+ [Where problems could occur]
+ 
+  * u-boot build embedds FU540 dtb and OpenSBI at a particular interface
+ versions. It is unknown if these components will be compatible with
+ future board revisions or may require changes and rebuilds. Specifically
+ kernel interfaces with opensbi and uboot and hardware and has certain
+ dtb expectation. Currently it has been verified that the dtb vendored in
+ opensbi u-boot and kernel are all identical. But hardware issues may
+ arise when these will change out of sync - for example opensbi installed
+ shutdown/reboot handler resulting in a reboot hang.
+ 
+ I expect all of these components needing changes and rebuilds to support
+ FU740.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance

** Also affects: livecd-rootfs (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: u-boot (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: u-boot (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu Groovy)
   Status: New => Won't Fix

** Changed in: u-boot (Ubuntu Groovy)
   Status: New => Won't Fix

** Description changed:

  [Impact]
  
-  * To build bootable uboot-sifive package, it must be built with
+  * To build bootable uboot-sifive package, it must be built with
  opensbi. Currently those are missbuilt and not packaged.
  
  [Test Case]
  
-  * Download u-boot buildlog for riscv64
+  * Download u-boot buildlog for riscv64
  
  and Look for:
  
  /<>/"arch/riscv/lib/mkimage_fit_opensbi.sh" \
  arch/riscv/dts/hifive-unleashed-a00.dtb > u-boot.its
  WARNING: OpenSBI binary "fw_dynamic.bin" not found, resulting binary is not 
functional.
  
- 
- * A missbuilt package will have the Warning emitted by 
mkimage_fit_opensbi.sh, whereas fixed u-boot package will not.
+ * A missbuilt package will have the Warning emitted by
+ mkimage_fit_opensbi.sh, whereas fixed u-boot package will not.
  
  * Check that uboot-sifive riscv64 .deb provides
  
  ./usr/lib/u-boot/sifive_fu540/u-boot-spl.bin
  ./usr/lib/u-boot/sifive_fu540/u-boot.bin
  ./usr/lib/u-boot/sifive_fu540/u-boot.itb
  ./usr/lib/u-boot/sifive_fu540/uboot.elf
  
  As those will be consumed by livecd-rootfs when building bootable
  preinstalled images.
  
  [Where problems could occur]
  
-  * u-boot build embedds FU540 dtb and OpenSBI at a particular interface
+  * u-boot build embedds FU540 dtb and OpenSBI at a particular interface
  versions. It is unknown if these components will be compatible with
  future board revisions or may require changes and rebuilds. Specifically
  kernel interfaces with opensbi and uboot and hardware and has certain
  dtb expectation. Currently it has been verified that the dtb vendored in
  opensbi u-boot and kernel are all identical. But hardware issues may
  arise when these will change out of sync - for example opensbi installed
  shutdown/reboot handler resulting in a reboot hang.
  
  I expect all of these components needing changes and rebuilds to support
  FU740.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Groovy will not receive these changes. There will not be a point
+ release of groovy to make a new image. Focal images will be provided at
+ 

[Bug 1897460] Re: VLC Snap Incompatible With Thunderbird

[Launchpad Bug Tracker]

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

** Changed in: gnome-software (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/1897460

Title:
  VLC Snap Incompatible With Thunderbird

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

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

[Bug 1898204] Re: [Gigabyte Z170-HD3P] No sound

[Launchpad Bug Tracker]

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

** Changed in: pulseaudio (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/1898204

Title:
  [Gigabyte Z170-HD3P] No sound

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

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

[Bug 1898382] Re: can not install any of iso on my laptop, HDD and RAM are OK

[Launchpad Bug Tracker]

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

** Changed in: ubiquity (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/1898382

Title:
  can not install any of iso on my laptop, HDD and RAM are OK

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

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

[Bug 341347] Re: konqueror crashed with SIGSEGV in QMetaObject::activate()

[Bug Watch Updater]

** Changed in: kdelibs
   Status: Confirmed => Incomplete

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

Title:
  konqueror crashed with SIGSEGV in QMetaObject::activate()

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

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

[Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM

[Po-Hsu Lin]

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

** No longer affects: linux-signed-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/1872401

Title:
  vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
  B-oracle-4.15 / X-KVM / B-KVM

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

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

[Bug 1872212] Re: grub-install: Operation not permitted

[Jack Christensen]

I just installed the following updates. Seems to have fixed the issue
for me; grub-install now runs without error. Thanks very much!

Upgraded the following packages:
libefiboot1 (37-2ubuntu2.1) to 37-2ubuntu2.2
libefivar1 (37-2ubuntu2.1) to 37-2ubuntu2.2

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

Title:
  grub-install: Operation not permitted

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

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

[Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

[Wayne Schroeder]

I also just installed on a pi 4 and had the same issue -- devices worked but 
would not persist across reboots, and then successive re-adds were... strange, 
unreliable, etc.  Lots of "it appears to work but doesn't."  Tried the PPA 
packages and it worked at first, but was seriously inconsistent at adding and 
removing devices.  I downgraded the PPA packages back to originals and still 
couldn't reliably add devices.  I re-upgraded to PPA packages and the bluetooth 
was essentially working less than ever.  Since it felt like a software issue, 
like configurations and "sessions" were being munged, I killed BT, searched 
around and wiped out /var/lib/bluetooth/* (which appeared to have multiple base 
addresses???) and then I was able to clean out gnome's ui and re-add and things 
now persist across reboots.  
  
To me, this seems like the PPA fixes the issue, but the original packages 
created a state where there were multiple stale / conflicting states in 
/var/lib/bluetooth that you must disabled bt, clean, then re-enable / reboot 
and things work.  It almost feels like the original packages had the BT adapter 
changing addresses each boot or similar.

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

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

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

[Bug 1906748] [NEW] 3.7+4565-7 FTBFS on s390x due to symbol changes

[Robert Ancell]

Public bug reported:

3.7+4565-7 FTBFS on s390x due to symbol changes

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


** Tags: update-excuse

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

Title:
  3.7+4565-7 FTBFS on s390x due to symbol changes

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

[Kai-Chuan Hsieh]

@seb128

Thanks for reviewing it carefully and the explicit explanation.

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906745] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

[Scott Stensland]

lspci | grep -i network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 
802.11a/b/g/n Wireless LAN Controller (rev 01)


SOLUTION

sudo apt-get purge bcmwl-kernel-source


sudo apt-get install   broadcom-sta-source  broadcom-sta-dkms   
broadcom-sta-common

reboot

now wifi is OK

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
  failed to build

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

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

[Bug 1906746] [NEW] 3.5-3.1 FTBFS on armhf/ppc64el/riscv64/s390x due to symbol changes

[Robert Ancell]

Public bug reported:

3.5-3.1 FTBFS on armhf/ppc64el/riscv64/s390x due to symbol changes

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


** Tags: update-excuse

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

Title:
  3.5-3.1 FTBFS on armhf/ppc64el/riscv64/s390x due to symbol changes

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

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

[Bug 330222] Re: kopete crashed with SIGSEGV in Kopete::Transfer::slotProcessed()

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=181416.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-01-20T18:22:54+00:00 Florian Reinhard wrote:

Version:   0.60.82 (using Devel)
OS:Linux
Installed from:Compiled sources

plugins: 
* KopeteTeX
* statistics
* history
* otr (quit the otr session since file transfer doesn't work with otr)

howto reproduce:
1) send a file to a jabber-contact
2) you get a progress window in systray, this one contains a stop-button, hit it

don't know if it matters whether the jabber-contact accepted the
filetransfer or not

backtrace:
Anwendung: Kopete (kopete), Signal SIGSEGV
[Current thread is 0 (LWP 11246)]

Thread 3 (Thread 0xb2454b90 (LWP 11335)):
#0  0xb5d5d54a in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0xb6ea30ab in ?? () from /usr/lib/libQtCore.so.4
#2  0xb6ea3281 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb6ea4e3c in ?? () from /usr/lib/libQtCore.so.4
#4  0xb6ea165a in ?? () from /usr/lib/libQtCore.so.4
#5  0xb5cde602 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#6  0xb5cdea8a in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb5cdef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#8  0xb6ea1497 in QEventDispatcherGlib::processEvents () from 
/usr/lib/libQtCore.so.4
#9  0xb6e7552a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#10 0xb6e756ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#11 0xb2f01e59 in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#12 0xb6d866ae in ?? () from /usr/lib/libQtCore.so.4
#13 0xb5e7550f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#14 0xb623e7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb2c55b90 (LWP 11336)):
#0  0xb806b430 in __kernel_vsyscall ()
#1  0xb5e79075 in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib/tls/i686/cmov/libpthread.so.0
#2  0xb624c9ed in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib/tls/i686/cmov/libc.so.6
#3  0xb6d876f2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7636532 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb6d866ae in ?? () from /usr/lib/libQtCore.so.4
#6  0xb5e7550f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb623e7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb58196c0 (LWP 11246)):
[KCrash Handler]
#6  0xb70a205c in KJob::setError (this=0xaffb950, errorCode=123) at 
/build/buildd/kde4libs-4.1.96/kdecore/jobs/kjob.cpp:234
#7  0xb7dbe121 in Kopete::Transfer::slotError (this=0xaffb950, error=123, 
errorText=@0xbfa6ac94) at 
/build/buildd/kdenetwork-4.1.96/kopete/libkopete/kopetetransfermanager.cpp:257
#8  0xb30812d1 in JabberFileTransfer::slotTransferError (this=0xaffbbe8, 
errorCode=2) at 
/build/buildd/kdenetwork-4.1.96/kopete/protocols/jabber/jabberfiletransfer.cpp:282
#9  0xb308508c in JabberFileTransfer::qt_metacall (this=0xaffbbe8, 
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfa6addc)
at 
/build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/jabberfiletransfer.moc:80
#10 0xb6e8ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb6e8c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb2dce803 in XMPP::FileTransfer::error (this=0xb0fea38, _t1=2) at 
/build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/libiris/moc_filetransfer.cpp:131
#13 0xb2de4ce8 in XMPP::FileTransfer::s5b_error (this=0xb0fea38, x=1) at 
/build/buildd/kdenetwork-4.1.96/kopete/protocols/jabber/libiris/iris/jabber/filetransfer.cpp:326
#14 0xb2dd2957 in XMPP::FileTransfer::qt_metacall (this=0xb0fea38, 
_c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfa6aefc)
at 
/build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/libiris/moc_filetransfer.cpp:93
#15 0xb6e8ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb6e8c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb2dce9b3 in ByteStream::error (this=0xb0fd6f0, _t1=1) at 
/build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/libiris/moc_bytestream.cpp:111
#18 0xb2df8260 in XMPP::S5BConnection::man_failed (this=0xb0fd6f0, x=1) at 
/build/buildd/kdenetwork-4.1.96/kopete/protocols/jabber/libiris/iris/jabber/s5b.cpp:453
#19 0xb2df82bf in XMPP::S5BManager::item_error (this=0x9cbf178, x=1) at 
/build/buildd/kdenetwork-4.1.96/kopete/protocols/jabber/libiris/iris/jabber/s5b.cpp:1000
#20 0xb2dd21c4 in XMPP::S5BManager::qt_metacall (this=0x9cbf178, 
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfa6b03c)
at 
/build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/libiris/moc_s5b.cpp:241
#21 0xb6e8ba60 in QMetaObject::activate () 

[Bug 427914] Re: kopete crashed with SIGSEGV in QString()

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=207094.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-09-11T17:10:22+00:00 Jonathan Thomas wrote:

Version:(using KDE 4.3.1)
OS:Linux
Installed from:Ubuntu Packages

Originally reported at https://launchpad.net/bugs/427914

The user reported a crash while editing a contact's alias. This looks
similar to bug 194155, but the situation is somewhat different, and that
one is supposed to be fixed.

Here's the backtrace:

.
Thread 2 (Thread 31810):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
No locals.
#1  0x7f9dfb2e24db in QWaitConditionPrivate::wait (
this=, mutex=0x2818e88, time=18446744073709551615)
at thread/qwaitcondition_unix.cpp:87
code = -422875088
#2  QWaitCondition::wait (this=, mutex=0x2818e88, 
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
returnValue = 
#3  0x7f9df86d977c in QHostInfoAgent::run (this=0x2818e70)
at kernel/qhostinfo.cpp:260
locker = {{mtx = 0x2818e89, val = 42045065}}
info = {d = 0x7f9ddc000ee0}
id = 42929920
#4  0x7f9dfb2e1425 in QThreadPrivate::start (arg=0x2818e70)
at thread/qthread_unix.cpp:188
data = 0x2819230
#5  0x7f9df594ca04 in start_thread (arg=)
at pthread_create.c:300
__res = 
pd = 0x7f9de6cb7910
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140316158687504, 
3107188231428688504, 140734926485280, 140316158687504, 0, 3, 
-3160050650747450760, -3160093096012625288}, 
  mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, 
data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
robust = 
#6  0x7f9dfa12f64d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#7  0x in ?? ()
No symbol table info available.
.
Thread 1 (Thread 31808):
#0  QString (this=0x1) at /usr/include/qt4/QtCore/qstring.h:711
No locals.
#1  Kopete::Contact::contactId (this=0x1)
at ../../../kopete/libkopete/kopetecontact.cpp:451
No locals.
#2  0x7f9dfd1ca5bf in Kopete::XmlContactStorage::storeMetaContact (
this=, metaContact=0x255d860, 
minimal=)
at ../../../kopete/libkopete/contactlist/xmlcontactstorage.cpp:684
contactNameSource = { = {
impl = 0x35b9a40}, }
displayName = { = {impl = 0x35b4320}, }
propertySources = { = {impl = 0x3605920}, }
_nameSource = { = {impl = 0x36aece0}, }
_photoSource = { = {impl = 0x35baf40}, }
metaContactDoc = { = {impl = 0x35b41b0}, }
photo = { = {impl = 0x35b4240}, }
#3  0x7f9dfd1cd811 in Kopete::XmlContactStorage::save (this=0x35f7e70)
at ../../../kopete/libkopete/contactlist/xmlcontactstorage.cpp:269
node = {impl = 0x35b4410}
metaContact = 
_container_ = {c = {{p = {static shared_null = {ref = {_q_value = 1}, 
  alloc = 0, begin = 0, end = 0, sharable = 1, array = {
0x0}}, d = 0x33e4530}, d = 0x33e4530}}, brk = 0, i = {
i = 0x33e4588}, e = {i = 0x33e4e50}}
groupList = {{p = {static shared_null = {ref = {_q_value = 1}, 
alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, 
  d = 0x230c190}, d = 0x230c190}}
metaContactList = {{p = {static shared_null = {ref = {_q_value = 1}, 
alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, 
  d = 0x33e4530}, d = 0x33e4530}}
stream = {_vptr.QTextStream = 0x0, d_ptr = 0x156013d}
filename = {static null = {}, static shared_null = {
ref = {_q_value = 1}, alloc = 0, size = 0, data = 0x63a77a, 
clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, 
capacity = 0, reserved = 0, array = {0}}, static shared_empty = {
ref = {_q_value = 202}, alloc = 0, size = 0, 
data = 0x7f9dfb6b885a, clean = 0, simpletext = 0, 
righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, 
array = {0}}, d = 0x361c6b0, static codecForCStrings = 0x0}
contactListFile = { = { = { = {
_vptr.QObject = 0x7f9dfbda6550, static staticMetaObject = {
  d = {superdata = 0x0, 
stringdata = 0x7f9dfb45c580 "QObject", 
data = 0x7f9dfb45c620, extradata = 0x7f9dfb6b0040}}, 
d_ptr = 0x361c9e0, static staticQtMetaObject = {d = {
superdata = 0x0, stringdata = 0x7f9dfb465e00 "Qt", 
data = 

[Bug 1906738] Re: alsa/sdw: add support for tgl_3_in_1_sdca soundwire machine

[Hui Wang]

** Description changed:

- this bug is for tracking.
+ [Impact]
+ We need to enable a Dell soundwire machine in the OEM project, but
+ the soundwire design is different from previous generation, it follows
+ soundwire sdca spec. both ubuntu kernel and upstream kernel don't have
+ driver for soundwire sdca yet, so the audio device on this machine
+ can't be detected.
+ 
+ [Fix]
+ backport 20 patches from the kernel git tree of intel sof/project
+ 
+ [Test]
+ After booting up, we could see the sound card by running
+ pacmd list-cards, and there is speaker, headphone, dmic and headset-mic
+ on this sound card, test playback and record, all worked well.
+ 
+ [Where problems could occur]
+ The patches change some soundwire bus driver and alsa intel asoc
+ machine driver, it could make the sound stop working on old
+ soundwire machines. But this possibility is very low since we
+ tested these patches on Dell soundwire machines.

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

Title:
  alsa/sdw: add support for tgl_3_in_1_sdca soundwire machine

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

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

[Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

[Marcelo Pires]

Uninstalling pulseaudio and working only with alsa, the same problem continues.
I was playing the audio with the specifications of aplay -l

 Lista de Dispositivos PLAYBACK Hardware 
placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog]
  Dispositivo secundário: 0/1
  Dispositivo secundário #0: subdevice #0
placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital]
  Dispositivo secundário: 1/1
  Dispositivo secundário #0: subdevice #0


when the audio stopped and I ran aplay -l and returned:

 Lista de Dispositivos PLAYBACK Hardware 
placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog]
  Dispositivo secundário: 1/1
  Dispositivo secundário #0: subdevice #0
placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital]
  Dispositivo secundário: 1/1
  Dispositivo secundário #0: subdevice #0



Does anyone know what can it be?

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

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

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

[Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

[Marcelo Pires]

Uninstalling pulseaudio and working only with alsa, the same problem continues.
I was playing the audio with the specifications of aplay -l

 Lista de Dispositivos PLAYBACK Hardware 
placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog]
  Dispositivo secundário: 0/1
  Dispositivo secundário #0: subdevice #0
placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital]
  Dispositivo secundário: 1/1
  Dispositivo secundário #0: subdevice #0


when the audio stopped and I ran aplay -l and returned:

 Lista de Dispositivos PLAYBACK Hardware 
placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog]
  Dispositivo secundário: 1/1
  Dispositivo secundário #0: subdevice #0
placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital]
  Dispositivo secundário: 1/1
  Dispositivo secundário #0: subdevice #0



Does anyone know what can it be?

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

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

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

[Bug 1906745] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

[Scott Stensland]

Public bug reported:

apt-get upgrade  caused crash of  wireless bcmwl

afterwards my wifi fails to work


before updates had

x86_64
5.4.0-57-generic
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"


apt-get upgrade

The following NEW packages will be installed:
  linux-headers-5.8.0-32-generic linux-hwe-5.8-headers-5.8.0-32 
linux-image-5.8.0-32-generic linux-modules-5.8.0-32-generic
  linux-modules-extra-5.8.0-32-generic
The following packages will be upgraded:
  linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 
linux-image-generic-hwe-20.04 wireless-regdb


Setting up linux-modules-5.8.0-32-generic (5.8.0-32.34~20.04.1) ...
Setting up linux-hwe-5.8-headers-5.8.0-32 (5.8.0-32.34~20.04.1) ...
Setting up linux-headers-5.8.0-32-generic (5.8.0-32.34~20.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.8.0-32-generic

Kernel preparation unnecessary for this kernel.  Skipping...
applying patch 0002-Makefile.patch...patching file Makefile
Hunk #1 succeeded at 113 with fuzz 1.
Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line).

applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines).

applying patch 
0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 221 (offset -14 lines).

applying patch 0013-gcc.patch...patching file Makefile

applying patch 
0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 2169 (offset 12 lines).

applying patch 0020-add-support-for-linux-4.3.patch...patching file
src/shared/linux_osl.c

applying patch 0021-add-support-for-Linux-4.7.patch...patching file
src/wl/sys/wl_cfg80211_hybrid.c

applying patch 0022-add-support-for-Linux-4.8.patch...patching file 
src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 2391 (offset 3 lines).
Hunk #2 succeeded at 2501 (offset 3 lines).
Hunk #3 succeeded at 2933 (offset 9 lines).

applying patch 0023-add-support-for-Linux-4.11.patch...patching file 
src/include/linuxver.h
patching file src/wl/sys/wl_linux.c
Hunk #1 succeeded at 2919 (offset 4 lines).

applying patch 0024-add-support-for-Linux-4.12.patch...patching file 
src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 55 (offset 5 lines).
Hunk #2 succeeded at 472 (offset 5 lines).
Hunk #3 succeeded at 2371 (offset 5 lines).
Hunk #4 succeeded at 2388 (offset 5 lines).

applying patch 0025-add-support-for-Linux-4.14.patch...patching file 
src/shared/linux_osl.c
Hunk #1 succeeded at 1080 (offset 4 lines).

applying patch 0026-add-support-for-Linux-4.15.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #2 succeeded at 2306 (offset 4 lines).
Hunk #3 succeeded at 2368 (offset 4 lines).

applying patch 0027-add-support-for-linux-5.1.patch...patching file 
src/include/linuxver.h
Hunk #1 succeeded at 595 (offset 4 lines).


Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-32-generic -C /lib/modules/5.8.0-32-generic/build 
M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.
   ...done.
Setting up linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-57-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-57-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-32-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-32-generic
Setting up linux-headers-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ...
Setting up linux-modules-extra-5.8.0-32-generic (5.8.0-32.34~20.04.1) ...
Setting up linux-image-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ...
Setting up linux-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.8.0-32-generic

Kernel preparation unnecessary for this kernel.  Skipping...
applying patch 0002-Makefile.patch...patching file Makefile
Hunk #1 succeeded at 113 with fuzz 1.
Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line).

applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines).

applying patch 
0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 221 (offset -14 lines).

applying patch 0013-gcc.patch...patching file Makefile

applying patch 
0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 2169 (offset 12 lines).

applying patch 

[Bug 1906741] [NEW] Firefox sometimes causes garbled audio

[Dave Evans]

Public bug reported:

Opening certain applications/websites at the same time as Firefox causes
the audio to become garbled.

The audio sounds distorted with an echo.

Certain actions are guaranteed to cause this, but it can also happening
when only running instances of Firefox.

I've been able to consistently cause this by launching Zoom from a link within 
Firefox. 
This does not occur when using Chrome. 

The only way to fix the issue is to shut down all audio-related
programs.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 83.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  rdevans   55475 F pulseaudio
 /dev/snd/controlC0:  rdevans   55475 F pulseaudio
 /dev/snd/controlC3:  rdevans   55475 F pulseaudio
 /dev/snd/controlC1:  rdevans   55475 F pulseaudio
BuildID: 20201112153044
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec  3 16:55:36 2020
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-10-20 (1140 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 
 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 
 169.254.0.0/16 dev enp7s0 scope link metric 1000
Locales: extensions.sqlite corrupt or missing
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago)
dmi.bios.date: 02/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: H67M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal

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

Title:
  Firefox sometimes causes garbled audio

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

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

[Bug 1906744] [NEW] xdg-document-portal creates a mountpoint which produces an error report from df

[Gordon Lack]

Public bug reported:

If I run "df" it starts with an error message:

[parent]: df
df: /run/user/4410/doc: Operation not permitted
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs1630320 1604   1628716   1% /run
.

The /run/user/4410/doc (mode r-x--) has been created by:

/usr/libexec/xdg-document-portal

started by:

/lib/systemd/systemd --user

using:

/usr/lib/systemd/user/xdg-document-portal.service


I'm not sure why this is there, but i appear to have no control over it.

It should not result in simple tools such as df producing error messages
just because it exists.

/proc/mounts shows it as:

portal /run/user/4410/doc fuse.portal
rw,nosuid,nodev,relatime,user_id=4410,group_id=1001 0 0

If it is a required mount then perhaps df should be made to ignore
portal mounts by default?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xdg-desktop-portal 1.8.0-1
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Dec  4 02:09:11 2020
InstallationDate: Installed on 2020-05-03 (214 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: xdg-desktop-portal
UpgradeStatus: Upgraded to groovy on 2020-10-26 (39 days ago)

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

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

Title:
  xdg-document-portal creates a mountpoint which produces an error
  report from df

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

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

[Bug 1906743] [NEW] package ukui-wallpapers (not installed) failed to install/upgrade: prøver å skrive over «/usr/share/backgrounds/calla.png» som også finnes i pakken ubuntukylin-wallpapers-focal 20.

[ketthors]

Public bug reported:

I don't know why this happened

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: ukui-wallpapers (not installed)
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Dec  4 02:06:14 2020
DuplicateSignature:
 package:ukui-wallpapers:(not installed)
 Unpacking ukui-wallpapers (20.04.3-1.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Mvp9iE/133-ukui-wallpapers_20.04.3-1.1_all.deb (--unpack):
  prøver å skrive over «/usr/share/backgrounds/calla.png» som også finnes i 
pakken ubuntukylin-wallpapers-focal 20.10.1
ErrorMessage: prøver å skrive over «/usr/share/backgrounds/calla.png» som også 
finnes i pakken ubuntukylin-wallpapers-focal 20.10.1
InstallationDate: Installed on 2020-12-03 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: gnome-shell
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: ukui-wallpapers
Title: package ukui-wallpapers (not installed) failed to install/upgrade: 
prøver å skrive over «/usr/share/backgrounds/calla.png» som også finnes i 
pakken ubuntukylin-wallpapers-focal 20.10.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ukui-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package groovy

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

Title:
  package ukui-wallpapers (not installed) failed to install/upgrade:
  prøver å skrive over «/usr/share/backgrounds/calla.png» som også
  finnes i pakken ubuntukylin-wallpapers-focal 20.10.1

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

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

[Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Daniel van Vugt]

This bug has been closed for 4 years. If you experience any crashes in
18.04 or 20.04 then please open a new bug.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

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

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

[Bug 1906449] Re: [nvidia] [amdgpu] Xorg randomly freezes

[Daniel van Vugt]

Thanks. Good news at least that I don't see any kernel driver crashes
there.

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => New

** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-440
(Ubuntu)

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xfce4 (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/1906449

Title:
  [nvidia] [amdgpu] Xorg randomly freezes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1906449/+subscriptions

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

[Bug 1906686] Re: Xorg freeze

[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:
ubuntu-bug 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.

** Tags added: radeon

** Summary changed:

- Xorg freeze
+ [radeon] Xorg freeze

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Package changed: ubuntu => xorg-server (Ubuntu)

** Package changed: xorg-server (Ubuntu) => ubuntu

** Summary changed:

- [radeon] Xorg freeze
+ [radeon] Display freeze

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

Title:
  [radeon] Display freeze

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

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

[Bug 1906642] Re: Xorg crash

[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:
ubuntu-bug 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.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Xorg crash
+ Xorg crashes with abort in iris_dri.so

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

** Changed in: mesa (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/1906642

Title:
  Xorg crashes with abort in iris_dri.so

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

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

[Bug 1906473] Re: package linux-image-5.4.0-56-generic 5.4.0-56.62 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (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/1906473

Title:
  package linux-image-5.4.0-56-generic 5.4.0-56.62 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

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

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

[Bug 1906642] Re: Xorg crash

[Daniel van Vugt]

The one crash I can see here is incomplete due to missing/incorrect
debug symbols:

[   701.646] (EE) Backtrace:
[   701.648] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55cdba58a52c]
[   701.649] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f214374541f]
[   701.650] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f214358218b]
[   701.651] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7f2143561859]
[   701.653] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   701.653] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) 
[0x7f214177d3a7]
[   701.654] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(nouveau_drm_screen_create+0x2036b7) [0x7f214236fb97]
[   701.654] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x24ee8) [0x7f21417cd608]
[   701.655] (EE) 7: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_destroy_pixmap+0x150) [0x7f2142ee7480]
[   701.656] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   701.656] (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) 
[0x7f2142f208f0]
[   701.656] (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x55cdba42d995]
[   701.656] (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) 
[0x55cdba583ba2]
[   701.656] (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) 
[0x55cdba428cf7]
[   701.657] (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55cdba42cfc4]
[   701.657] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f21435630b3]
[   701.658] (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x55cdba416a2e]

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

Title:
  Xorg crashes with abort in iris_dri.so

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

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

[Bug 1906736] Re: Please update package to 3.38.2

[Daniel van Vugt]

** Tags added: groovy

** Tags added: hirsute

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

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

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

Title:
  Please update package to 3.38.2

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

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

[Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously

[zespri]

Also reported here: https://askubuntu.com/questions/1296506/ubuntu-20-04
-why-does-turning-off-wi-fi-can-be-turned-off-to-save-power-turn

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

Title:
  Bluetooth and Wi-Fi items in Power are worded ambiguously

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

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

[Bug 1906250] Re: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=27008.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-12-03T22:32:05+00:00 Florian Weimer wrote:

With qemu-user, it's common that a process of the wrong endianness tries
to parse ld.so.cache. For performance reasons, the consistency checks
are somewhat limited, so crashes can be the result.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1906250/comments/1


On 2020-12-03T22:35:12+00:00 Florian Weimer wrote:

Patch: https://sourceware.org/pipermail/libc-
alpha/2020-November/119447.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1906250/comments/2


** Changed in: glibc
   Status: Unknown => In Progress

** Changed in: glibc
   Importance: Unknown => Low

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

Title:
  Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
  qemu-s390x on x86_64.

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

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

[Bug 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])

[Daniel van Vugt]

Timo,

The release notes incorrectly(?) suggest Renoir support is in kernel 5.4:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes

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

Title:
  FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is
  AMD/ATI Renoir [1002:1636])

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

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

[Bug 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])

[Daniel van Vugt]

It's a little bit cryptic but at the top of this page:

linux (Ubuntu) Fix Released refers to the fix being in Ubuntu 20.10.

linux-meta-hwe-5.8 (Ubuntu) Fix Released refers to the fix being
optional in Ubuntu 20.04. Only if you were using 20.04 would you need to
install linux-generic-hwe-20.04-edge.

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

Title:
  FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is
  AMD/ATI Renoir [1002:1636])

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

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

[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset

[Russell Morris]

> The one obvious next test would be to shut down the macOS guest and
try an ubuntu guest with the same forwards. That will allow us to see if
it is "virtualization-components" or actually "guest OS" that we need to
think about.

Good idea. OK, so I shut down all VM's, added this same USB device to a
Windows 10 VM I also had defined (on the same host OS). Started it up
(same way, virsh start) => booted up, and ... USB device works!

So it seems to be guest OS related, agreed? And actually, not even that
I'd say, as I can't even use it in the bootloader / UEFI, so not really
even the OS, but the bootloader / UEFI? And that sort of aligns with the
watchdog reset, as then it works, but still hasn't gotten to the OS
(boot). Agreed?

Thanks!

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

Title:
  USB Passthrough Fails on Start, Needs domain Reset

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

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

[Bug 1418279] Re: Automount NFSv4 doesn't work

[Erik Lönroth]

I get the same issue. I've created systemd unit files for both mount and
automount:


$ cat /etc/systemd/system/share-apps.automount 
[Unit]
Description=Automount Scratch

[Automount]
Where=/share/apps/

[Install]
WantedBy=multi-user.target


$ cat /etc/systemd/system/share-apps.mount 
[Unit]
Description=Scratch

[Mount]
What=192.168.2.241:/mnt/nfs_share
Where=/share/apps
Type=nfs

[Install]
WantedBy=multi-user.target


Mounting works fine (HELLO is a file on the remote NFS server):

$ systemctl start share-apps.mount 
$ ls /share/apps/
HELLO

However, automount fails:

$ systemctl stop share-apps.mount 
$ ls /share/apps/
$ systemctl start share-apps.automount 
Operation on or unit type of share-apps.automount not supported on this system.

$ systemd-detect-virt 
lxc


The nfs client container is privilegued.

The nfs client container has these apparmor settings and is restarted
with those settings:

lxc config get iceberg:juju-ee5ee4-0 raw.apparmor
mount fstype=rpc_pipefs, mount fstype=nfsd, mount fstype=nfs, mount 
fstype=nfsv4, mount fstype=autofs,

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

Title:
  Automount NFSv4 doesn't work

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

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

[Bug 1906743] Re: package ukui-wallpapers (not installed) failed to install/upgrade: prøver å skrive over «/usr/share/backgrounds/calla.png» som også finnes i pakken ubuntukylin-wallpapers-focal 20.10

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

Title:
  package ukui-wallpapers (not installed) failed to install/upgrade:
  prøver å skrive over «/usr/share/backgrounds/calla.png» som også
  finnes i pakken ubuntukylin-wallpapers-focal 20.10.1

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

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

[Bug 1906739] [NEW] default sssd pam config breaks local user logins if sssd isn't running

[Jason Alavaliant]

Public bug reported:

If you install sssd on a machine and then stop the service.   Logins as
local users fail (until sssd is started back up).

e.g. When trying to login using the correct password for 'localadmin', the 
login fails with the auth logs recording messages like;
pam_sss(login:auth): Request to sssd failed. Connection refused
FAILED LOGIN (1) on '/dev/tty1' FOR 'localadmin', Authentication failure
pam_sss(login:account): Request to sssd failed. Connection refused
login[31397]: Authentication service cannot retrieve authentication info

>From what I've found in testing. The problem comes from 
>/etc/pam.d/common-account
which by default specifies;

account [default=bad success=ok user_unknown=ignore]pam_sss.so

If that is changed to

account [default=ignore success=ok user_unknown=ignore]pam_sss.so

The pam stack doesn't exit out straight away when sssd can't be
connected to,  and instead pam_unix.so is still used.

So far in my testing I've not found any problems from the change,
network logins with bad passwords are still rejected etc. As is
understand it the change is making pam skip over pam_sss.so if it
returns a result other than successful login.   So I'm not seeing how it
could cause problems.

Can the default pam configuration set by the sssd package please be
updated to change the default=bad to default=ignore   so that a broken
sssd daemon doesn't stop all local account logins from working as well?

Thanks
-J

** Affects: sssd (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/1906739

Title:
  default sssd pam config breaks local user logins if sssd isn't running

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

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

[Bug 1906738] [NEW] alsa/sdw: add support for tgl_3_in_1_sdca soundwire machine

[Hui Wang]

Public bug reported:

this bug is for tracking.

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

** Affects: linux-oem-5.10 (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: In Progress


** Tags: oem-priority originate-from-1902170 somerville

** Changed in: linux-oem-5.10 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-oem-5.10 (Ubuntu)
   Status: New => In Progress

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Tags added: oem-priority originate-from-1902170 somerville

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

Title:
  alsa/sdw: add support for tgl_3_in_1_sdca soundwire machine

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

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

[Bug 1906740] [NEW] Set Colormap gives "invalid parameter name 'num colors'"

[Damian Yerrick]

Public bug reported:

I'm using GIMP 2.10.18-1 on Xubuntu 20.04.1. In Colors > Map > Set
Colormap, when I click the Palette: Default button to set the
replacement palette, I'm supposed to see a list of palettes from which
to choose. Instead, I get the following error:

Plug-in "script-fu"
(/usr/lib/gimp/2.0/plug-ins/script-fu/script-fu)
attempted to install procedure "temp-procedure-number-6" with invalid parameter 
name "num colors".

These forum references claim that this error is specific to versions
2.10.16 and 2.10.18 and was fixed in 2.10.20:

https://www.reddit.com/r/GIMP/comments/gb5zih/error_when_running_set_colormap_script/
http://gimpchat.com/viewtopic.php?f=9=18293

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gimp 2.10.18-1
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Dec  3 19:36:12 2020
InstallationDate: Installed on 2018-06-10 (907 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gimp
UpgradeStatus: Upgraded to focal on 2020-11-04 (29 days ago)

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


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

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

Title:
  Set Colormap gives "invalid parameter name 'num colors'"

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

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

[Bug 1828434] Re: Unable to print after libgs 9.26 installed

[rtimai]

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

Attempted the following suggested procedures, without success.

/var/log/apt/history.log
sudo apt reinstall libgs9-common
  Reinstall: libgs9-common:amd64 (9.27~dfsg-2+deb10u4)
sudo apt reinstall hpijs-ppds printer-driver-hpijs
  Reinstall: hpijs-ppds:amd64 (3.18.12+dfsg0-2), printer-driver-hpijs:amd64 
(3.18.12+dfsg0-2)

On the chance that the "Filters failed" issue involved the PDF viewer
Evince, I installed the PDF Viewer browser extension in Chromium,
enabled local file access per instructions, and I am now able to print
selected PDF pages without error. Interestingly, Evince continues to
fail filtered print jobs, but now without returning an error message.
The cups error log appears to mark the failed jobs as "completed" now.

My point here is that a potential workaround for this complex issue may
be to try using an alternate PDF viewer.

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

Title:
  Unable to print after libgs 9.26 installed

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

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

[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor

[Ubuntu Foundations Team Bug Bot]

The attachment "Test fix to work around grub-probe failure" seems to be
a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  ubuntu 20.04.1 installed with zfs root fails to boot after installing
  xen-hypervisor

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

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

[Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

I built the current upstream master branch of adcli, and it too fails on
Bionic:

https://paste.ubuntu.com/p/vsgfxyb9X7/

This must be why the exact same patches work on Focal. The problem
probably isn't adcli itself, but more likely a library it depends on.

# apt depends adcli
adcli
  Depends: libsasl2-modules-gssapi-mit
  Depends: libc6 (>= 2.14)
  Depends: libgssapi-krb5-2 (>= 1.6.dfsg.2)
  Depends: libk5crypto3 (>= 1.7+dfsg)
  Depends: libkrb5-3 (>= 1.10+dfsg~alpha1)
  Depends: libldap-2.4-2 (>= 2.4.7)
  
I will try upgrading each of these one at a time to see if it improves the 
situation.

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

Title:
  adcli fails, can't contact LDAP server

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

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

[Bug 1906627] Re: adcli fails, can't contact LDAP server

[Jason Alavaliant]

I hit this bug as well.  In my testing though  if --use-ldaps is
specified, the join no longer hangs.

So I'm wondering if possibly the GSS-SPENGO support is somehow relying
on something from --use-ldaps code  or should be set to only be active
if --use-ldaps is set?

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

Title:
  adcli fails, can't contact LDAP server

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

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

[Bug 1906642] Re: Xorg crash

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Xorg crash

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

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

[Bug 1906734] Re: le programme d'installation a planté

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => ubiquity (Ubuntu)

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

Title:
  le programme d'installation a planté

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

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

[Bug 150399] Re: "Create new >Link to > Hard disk device" doesn't work with UUIDs/LABELs in fstab

[Bug Watch Updater]

** Changed in: kde-baseapps
   Status: New => Unknown

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

Title:
  "Create new >Link to > Hard disk device" doesn't work with
  UUIDs/LABELs in fstab

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/150399/+subscriptions

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

[Bug 150399]

[A-samirh78]

"Hard disk device" entry in the "create new" menu hasn't been offered
for some time.

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

Title:
  "Create new >Link to > Hard disk device" doesn't work with
  UUIDs/LABELs in fstab

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/150399/+subscriptions

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

[Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

Hi Rolf,

I sincerely apologise for causing this regression, it seems my testing
was not good enough during the recent SRU.

I recently made a change to adcli in bug 1868703 to add the --use-ldaps flag, 
so adcli can communicate with a domain controller over LDAPS.
It also introduced a change where it will use GSS-SPENGO by default, and 
enforce channel signing, over doing everything in cleartext, which was the old 
default.

The good news is that it seems to be limited to Bionic only, and even
though Focal got the exact same patches, Focal seems unaffected.

For anyone experiencing this bug, you can downgrade to a working adcli
with:

$ sudo apt install adcli=0.8.2-1

I am working to fix this now.

Comparison of logging and packet traces from various versions:

Bionic adcli 0.8.2-1
https://paste.ubuntu.com/p/NWHGQn746D/

Bionic adcli 0.8.2-1ubuntu1
https://paste.ubuntu.com/p/WRnnRMGBPm/

Focal adcli 0.9.0-1ubuntu0.20.04.1
https://paste.ubuntu.com/p/8668pJrr2m/

We can see that Bionic 0.8.2-1ubuntu1 stops at Couldn't lookup computer
account: BIONIC$: Can't contact LDAP server

Starting debugging now. Will update soon.

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

** Changed in: adcli (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: adcli (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: adcli (Ubuntu Bionic)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

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

Title:
  adcli fails, can't contact LDAP server

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

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

[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor

[Todd]

The best solution may involve fixing grub-probe so it knows a ZFS filesystem.
The attached patch is a simple workaround that worked on my 3 test systems.

For example if the patch is downloaded to /tmp/grub2.patch

You can install the patch like this:

cd /etc/grub.d; sudo patch < /tmp/grub2.patch



** Patch added: "Test fix to work around grub-probe failure"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+attachment/5440778/+files/grub2.patch

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

Title:
  ubuntu 20.04.1 installed with zfs root fails to boot after installing
  xen-hypervisor

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

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

[Bug 1901812] Re: Error in do-release-upgrade, invalid start byte

[Retromingent]

Does anyone know if the issue is script incompatibility with python3.8?
I have python2.7, python3.8 and python3.9 installed and do-release-
upgrade fails exactly as described in this report.  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/1901812

Title:
  Error in do-release-upgrade, invalid start byte

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

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

[Bug 1906725] Re: [SRU] ceph 15.2.7

[Billy Olsen]

** Description changed:

  [Impact]
- This release fixes a serious bug in RGW that can cause data loss and also 
fixes CVE 2020-25660. We would like to make sure all of our supported customers 
have access to these improvements.
+ This release fixes a serious bug in RGW that can cause data loss and also 
fixes CVE 2020-25660. We would like to make sure all of our users have access 
to these improvements.
  
  The update contains the following package updates:
  
-* ceph 15.2.7
+    * ceph 15.2.7
  
  [Test Case]
  The following SRU process was followed:
  
  https://wiki.ubuntu.com/OpenStackUpdates
  
- In order to avoid regression of existing consumers, the OpenStack team
- will run their continuous integration test against the packages that are
- in -proposed. A successful run of all available tests will be required
+ In order to avoid regression of existing users, the OpenStack team will
+ run their continuous integration test against the packages that are in
+ -proposed. A successful run of all available tests will be required
  before the proposed packages can be let into -updates.
  
  The OpenStack team will be in charge of attaching the output summary of
  the executed tests. The OpenStack team members will not mark
  ‘verification-done’ until this has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.

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

Title:
  [SRU] ceph 15.2.7

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

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

[Bug 1906736] [NEW] Please update package to 3.38.2

[Timo Witte]

Public bug reported:

The latest version in the debian repo fixes this bug, where CSGO can´t be 
played in fullscreen mode:
https://github.com/ValveSoftware/csgo-osx-linux/issues/2551

It´s part of debian SID already:
https://packages.debian.org/sid/main/libmutter-7-0

** Affects: mutter (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/1906736

Title:
  Please update package to 3.38.2

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

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

[Bug 1906642] Re: Xorg crash

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  Xorg crash

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

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

[Bug 1897378] Re: [SRU] liblzf backport to focal

[Gianfranco Costamagna]

moving into main
https://bugs.launchpad.net/ubuntu/groovy/+source/liblzf/+bug/1901904

** Changed in: liblzf (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/1897378

Title:
  [SRU] liblzf backport to focal

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

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

[Bug 1906700] Re: Xenial update: v4.4.246 upstream stable release

[Ian]

** Changed in: linux (Ubuntu Xenial)
   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/1906700

Title:
  Xenial update: v4.4.246 upstream stable release

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

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

[Bug 1906703] Re: Xenial update: v4.4.247 upstream stable release

[Ian]

** Changed in: linux (Ubuntu Xenial)
   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/1906703

Title:
  Xenial update: v4.4.247 upstream stable release

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

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

[Bug 1905205] Re: ubuntu_stress_smoke_test Segmentation fault in linux from Groovy/linux 5.8.0-30.32 ADT test failure

[Launchpad Bug Tracker]

This bug was fixed in the package stress-ng - 0.12.00-1

---
stress-ng (0.12.00-1) unstable; urgency=medium

  * Makefile: bump version
  * stress-epoll: fix sanity check for an unexpected epoll_ctl success
  * stress-funccall: disable ALWAYS_INLINE for PCC
  * stress-inotify: add void argument, fixes pcc build warning
  * stress-epoll: fix pcc build warning
  * stress-close: add invalid flags call to close_range
  * core-shim: add flags field to close_range shim to match 5.10
system call
  * stress-utime: voidify return using assignment and voidification
  * stress-stack: reduce scope of variable ret
  * stress-sock: clean up some cppcheck warnings
  * stress-mlock: put HAVE_MLOCKALL into a statement block
  * stress-affinity: add in missing voidification of ret
  * stress-brk: remove redundant return 0 statement
  * stress-pkey: limit pkey system call warning to just instance 0
  * core-helper: don't use getpwent for static stress-ng builds:
  * stress-stack: rename sz to mlock_sz to avoid variable shadowing
  * stress-pthread: remove duplicate declaration of ret to clean up
build warning
  * stress-msg: rename variable i to j to avoid name shadowing warning
  * stress-prctl: remove redundant declaration of environ
  * stress-msg: clean up variable shadowing
  * stress-yield: workaround FreeBSD usleep bug
  * stress-timer: workaround duplicated timer_delete segfault in FreeBSD
  * stress-ng.h: make shim_unconstify_ptr a static inline helper
  * stress-link: cast getpid() return to int for %d format specifier
  * stress-open: only declare obsolete_futimesat when it is required
  * stress-mmap: voidify page_size if HAVE_MPROTECT is not defined
  * stress-access: declare variable j only if HAVE_FACCESSAT is defined
  * stress-sem-sysv: silently ignore failures on semctl commands
  * stress-sem-sysv: ensure 4th arg of semctl is zero when not used
  * stress-sem-sysv: fix zero semaphores case in GETALL semctl
  * stress-brk: don't exercise mlockall with MCL_FUTURE if it is not
defined
  * Fix clobbering of errno by error message logging before reading errno
  * stress-sem-sysv: move scope of array sems
  * stress-poll: make tv_nsec out of range value a 32 bit value
  * stress-mmap: only use PROT_GROWSUP and PROT_GROWSDOWN if supported
  * Fix ~0ULL cast to void * build warnings on 32 bit builds
  * kernel-coverage: add --pathological for sysinval stress
  * syscalls: update work to do and recent changes
  * stress-vm-splice: add pipe to memory vmsplicing
  * stress-utime: exercise utime family of calls with invalid filenames
  * stress-sysinfo: fix build issues introduced by previous commit
  * stress-sysinfo: exercise ustat with invalid major/minor
  * stress-userfaultfd: exercise UFFDIO_WAKE
  * stress-ramfs: exercise umount with some invalid pathnames
  * stress-binderfs: exercise invalid umount calls
  * stress-hdd: exercise invalid ftruncate/truncate fd/filename
  * stress-hdd: exercise invalid ftruncate/truncate size
  * stress-timer: exercise duplicated timer_delete
  * stress-pthread: add tkill to shim and exercise it
  * stress-pthread: add tgkill to shim and exercise it
  * stress-sync-file: exercise 0 nbytes sync, it has special semantics
  * stress-swap: exercise swapon with invalid path
  * stress-sysinfo: exercise invalid statfs path
  * stress-fstat: exercise stat, lstat on invalid path
  * stress-splice: exercise splice with some more invalid or untested
arguments
  * stress-bad-altstack: exercise sigaltstack with various stack settings
  * core-helper: fix comment, min stack size can be MINSIGSTKSZ
  * stress-sysinval: only allow with --pathological option (LP: #1906447)
  * stress-shm-sysv: exercise duplicated shmdt on unmapped addresses
  * stress-shm-sysv: define MPOL_* only if required, add one more
shmctl call
  * stress-xattr: exercise invalid setxattr arguments
  * stress-set: add timezone argument to get more kernel coverage
  * stress-nice: fix priority ranges, use correct offset in priority
  * stress-set: exercise invalid pid and pgid in setpgid call
  * stress-clone: exercise setns with invalid nstype and fd
  * stress-set: exercise sethostname with illegal length host
  * stress-set: exercise a range of setgroups calls
  * stress-set: exercise setdomainname with invalid name length
  * stress-pthread: exercise set_tid_address with NULL address
  * stress-pthread: exercise set_robust_list with invalid length
  * stress-numa: add in a mix of various set_mempolicy calls
  * stress-sendfile: add more kernel coverage tests
  * stress-sendfile: periodically exercise sendfile with invalid arguments
  * core-helper: find bad_fd in reverse fd order if RLIMIT not supported
  * stress-sem-sysv: disable SETALL and exercise long run of semops
  * stress-sem-sysv: exercise semctl with various invalid arguments
  * stress-sem-sysv: add SIGCHLD handler to ensure pause() gets
interrupted
  * stress-schedpolicy: exercise sched_setscheduler with invalid 

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

[Launchpad Bug Tracker]

This bug was fixed in the package libinput - 1.16.4-1ubuntu1

---
libinput (1.16.4-1ubuntu1) hirsute; urgency=medium

  * quirks: Unset INPUT_PROP_BUTTONPAD for Dell Precision 7550/7750.
(LP: #1906341)
  * Update control build-dep libevdev-dev (>= 1.10.0) for
libevdev_disable_property API

 -- Sebastien Bacher   Thu, 03 Dec 2020 16:32:27
+0100

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

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906447] Re: init_module may pin a lot of memory if given a bogus size

[Launchpad Bug Tracker]

This bug was fixed in the package stress-ng - 0.12.00-1

---
stress-ng (0.12.00-1) unstable; urgency=medium

  * Makefile: bump version
  * stress-epoll: fix sanity check for an unexpected epoll_ctl success
  * stress-funccall: disable ALWAYS_INLINE for PCC
  * stress-inotify: add void argument, fixes pcc build warning
  * stress-epoll: fix pcc build warning
  * stress-close: add invalid flags call to close_range
  * core-shim: add flags field to close_range shim to match 5.10
system call
  * stress-utime: voidify return using assignment and voidification
  * stress-stack: reduce scope of variable ret
  * stress-sock: clean up some cppcheck warnings
  * stress-mlock: put HAVE_MLOCKALL into a statement block
  * stress-affinity: add in missing voidification of ret
  * stress-brk: remove redundant return 0 statement
  * stress-pkey: limit pkey system call warning to just instance 0
  * core-helper: don't use getpwent for static stress-ng builds:
  * stress-stack: rename sz to mlock_sz to avoid variable shadowing
  * stress-pthread: remove duplicate declaration of ret to clean up
build warning
  * stress-msg: rename variable i to j to avoid name shadowing warning
  * stress-prctl: remove redundant declaration of environ
  * stress-msg: clean up variable shadowing
  * stress-yield: workaround FreeBSD usleep bug
  * stress-timer: workaround duplicated timer_delete segfault in FreeBSD
  * stress-ng.h: make shim_unconstify_ptr a static inline helper
  * stress-link: cast getpid() return to int for %d format specifier
  * stress-open: only declare obsolete_futimesat when it is required
  * stress-mmap: voidify page_size if HAVE_MPROTECT is not defined
  * stress-access: declare variable j only if HAVE_FACCESSAT is defined
  * stress-sem-sysv: silently ignore failures on semctl commands
  * stress-sem-sysv: ensure 4th arg of semctl is zero when not used
  * stress-sem-sysv: fix zero semaphores case in GETALL semctl
  * stress-brk: don't exercise mlockall with MCL_FUTURE if it is not
defined
  * Fix clobbering of errno by error message logging before reading errno
  * stress-sem-sysv: move scope of array sems
  * stress-poll: make tv_nsec out of range value a 32 bit value
  * stress-mmap: only use PROT_GROWSUP and PROT_GROWSDOWN if supported
  * Fix ~0ULL cast to void * build warnings on 32 bit builds
  * kernel-coverage: add --pathological for sysinval stress
  * syscalls: update work to do and recent changes
  * stress-vm-splice: add pipe to memory vmsplicing
  * stress-utime: exercise utime family of calls with invalid filenames
  * stress-sysinfo: fix build issues introduced by previous commit
  * stress-sysinfo: exercise ustat with invalid major/minor
  * stress-userfaultfd: exercise UFFDIO_WAKE
  * stress-ramfs: exercise umount with some invalid pathnames
  * stress-binderfs: exercise invalid umount calls
  * stress-hdd: exercise invalid ftruncate/truncate fd/filename
  * stress-hdd: exercise invalid ftruncate/truncate size
  * stress-timer: exercise duplicated timer_delete
  * stress-pthread: add tkill to shim and exercise it
  * stress-pthread: add tgkill to shim and exercise it
  * stress-sync-file: exercise 0 nbytes sync, it has special semantics
  * stress-swap: exercise swapon with invalid path
  * stress-sysinfo: exercise invalid statfs path
  * stress-fstat: exercise stat, lstat on invalid path
  * stress-splice: exercise splice with some more invalid or untested
arguments
  * stress-bad-altstack: exercise sigaltstack with various stack settings
  * core-helper: fix comment, min stack size can be MINSIGSTKSZ
  * stress-sysinval: only allow with --pathological option (LP: #1906447)
  * stress-shm-sysv: exercise duplicated shmdt on unmapped addresses
  * stress-shm-sysv: define MPOL_* only if required, add one more
shmctl call
  * stress-xattr: exercise invalid setxattr arguments
  * stress-set: add timezone argument to get more kernel coverage
  * stress-nice: fix priority ranges, use correct offset in priority
  * stress-set: exercise invalid pid and pgid in setpgid call
  * stress-clone: exercise setns with invalid nstype and fd
  * stress-set: exercise sethostname with illegal length host
  * stress-set: exercise a range of setgroups calls
  * stress-set: exercise setdomainname with invalid name length
  * stress-pthread: exercise set_tid_address with NULL address
  * stress-pthread: exercise set_robust_list with invalid length
  * stress-numa: add in a mix of various set_mempolicy calls
  * stress-sendfile: add more kernel coverage tests
  * stress-sendfile: periodically exercise sendfile with invalid arguments
  * core-helper: find bad_fd in reverse fd order if RLIMIT not supported
  * stress-sem-sysv: disable SETALL and exercise long run of semops
  * stress-sem-sysv: exercise semctl with various invalid arguments
  * stress-sem-sysv: add SIGCHLD handler to ensure pause() gets
interrupted
  * stress-schedpolicy: exercise sched_setscheduler with invalid 

[Bug 1906698] Re: Xenial update: v4.4.245 upstream stable release

[Ian]

** Changed in: linux (Ubuntu Xenial)
   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/1906698

Title:
  Xenial update: v4.4.245 upstream stable release

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

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

[Bug 1906609] Re: Mozilla Thunderbird SMTP Server Stack-Based Buffer Overflow Vulnerability

[Seth Arnold]

** Information type changed from Private Security to Public Security

** Changed in: thunderbird (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/1906609

Title:
  Mozilla Thunderbird SMTP Server Stack-Based Buffer Overflow
  Vulnerability

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

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

[Bug 1906734] [NEW] le programme d'installation a planté

[chouaid]

Public bug reported:

Message d'erreur après une tentative d'installation : "nous sommes
désolés, le programme d'installation a planté.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec  3 23:45:13 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu

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

Title:
  le programme d'installation a planté

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

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

[Bug 1906449] Re: [nvidia] [amdgpu] Xorg randomly freezes

[Kuroš Taheri-Golværzi]

I apologize. I'd misread your instructions as "-b-l" (as in, L, instead
of the number one) and I got an error, so I assumed that I was supposed
to pass "-b -l". When I realized my mistake, I reproduced the error
again, and then rebooted again, and this time, I passed "-b-1" (with the
number one). Here's the correct file with the correct output.

** Attachment added: "actual journalctl result output file (the right one this 
time)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1906449/+attachment/5440770/+files/prevboot.txt

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

Title:
  [nvidia] [amdgpu] Xorg randomly freezes

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

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

[Bug 1906609] [NEW] Mozilla Thunderbird SMTP Server Stack-Based Buffer Overflow Vulnerability

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug by Seth Arnold (seth-arnold):

A vulnerability has been reported in Mozilla Thunderbird, which can be
exploited by malicious people to compromise a vulnerable system.


An error when parsing SMTP server status codes can be exploited to cause a 
stack-based buffer overflow.

Successful exploitation may allow execution of arbitrary code.

The vulnerability is reported in versions prior to 78.5.1.

Affected Software

The following software is affected by the described vulnerability.
Please check the vendor links below to see if exactly your version is
affected.

Mozilla Thunderbird 78.x

Solution

Update to version 78.5.1.

References

1. https://www.mozilla.org/en-US/security/advisories/mfsa2020-53/


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

-- 
Mozilla Thunderbird SMTP Server Stack-Based Buffer Overflow Vulnerability
https://bugs.launchpad.net/bugs/1906609
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to the bug report.

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

[Bug 1901904] Re: [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1

[Gianfranco Costamagna]

Before accepting focal we need to unblock this
https://bugs.launchpad.net/ubuntu/+source/liblzf/+bug/1897378

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

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

** Description changed:

  [SRU Justification]
  
  Impact: The build of virtualbox-dkms modules fails in 20.04/Focal when the 
5.8 based HWE kernel is installed.
   * Rename of mm->mmap_sem into mmap_lock
   * Modified API to read/write CR4
   * Modified API to access virtual memory areas
  
  Fix: Picking 2 patches from a later version of virtualbox and adjusting
  the 3rd to match what upstream virtualbox settled in the end with (that
  enables some code only for kernels between 2.6.23 and 5.8, the compile
  of virtualbox-dkms succeeds on 5.8.
  
  Testcase: dkms install -m virtualbox -v 6.1.10 -k 5.8.0-*-generic
  
  [ Other info ]
  * for groovy, other than fixing this issue, we finally sync 6.1.16 everywhere 
(due to late upload before release, this change was suitable to a 0 day SRU but 
I didn't proceed, so now its a good timing to fix it)
  * for focal, it needs liblzf, in the system, I removed the embedded version 
now that the archive has a packaged one
  
  [ Regression Potential ]
  This could show runtime issues when used on the 5.8 kernel but that did not 
work at all with the Focal version of virtualbox. The code generated for older 
kernels is unchanged.
  
  ---
  
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/v/virtualbox/20201016_103035_8da78@/log.gz
+ 
+ 
+ LIBLZF
+ [ Impact ]
+ * Needed to SRU newer virtualbox versions
+ 
+ [Regression Potential]
+ * none, leaf package
+ 
+ [ Other info ]
+ Please, this is a bundled library in virtualbox, now packaged as system 
library.
+ Unfortunately this is missing in focal, but we need to backport virtualbox 
from time to time (due to kernel changes).
+ 
+ In order to avoid having a special bundled version in virtualbox again
+ (the library is now stripped from sources), and to introduce bugs in
+ packaging, I would really like to add this library (leaf) to focal

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

Title:
  [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with
  linux-hwe-5.8 5.8.0-25.26~20.04.1

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

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

[Bug 1901904] Re: [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1

[Gianfranco Costamagna]

thanks sil2100, I reuploaded and also added a virtualbox-hwe for groovy
to sync versions together.

G.

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

Title:
  [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with
  linux-hwe-5.8 5.8.0-25.26~20.04.1

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

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

[Bug 1836475] Re: [SRU] update-notifier-common weekly cron job runs at the same time for all computers across the globe

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~chad.smith/ubuntu/+source/update-notifier/+git/update-notifier/+merge/394160

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

Title:
  [SRU] update-notifier-common weekly cron job runs at the same time for
  all computers across the globe

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

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

[Bug 1906731] [NEW] impossible to upgrade from 18.04 to 20

[Tasson]

Public bug reported:

Impossible to upgrade from ubuntu 18.04 to 20.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.41
ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18
Uname: Linux 4.15.0-126-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec  3 23:37:17 2020
InstallationDate: Installed on 2016-12-22 (1442 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-12-03 (0 days ago)

** 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/1906731

Title:
  impossible to upgrade from 18.04 to 20

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

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

[Bug 1906250] Re: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.

[Florian Weimer]

** Bug watch added: Sourceware.org Bugzilla #27008
   https://sourceware.org/bugzilla/show_bug.cgi?id=27008

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=27008
   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/1906250

Title:
  Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
  qemu-s390x on x86_64.

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

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

[Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

** Tags added: regression-update

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

Title:
  adcli fails, can't contact LDAP server

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

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

[Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

** Also affects: adcli (Ubuntu Bionic)
   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/1906627

Title:
  adcli fails, can't contact LDAP server

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

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