Before going any further please upgrade the Motherboard firmware to the
latest release and re-test. By my count there have been 13 upgrades
since:
DMI: ASUS System Product Name/ROG STRIX Z590-E GAMING WIFI, BIOS 0232
01/06/2021
with the latest being 2203 2024/04/17 according to
Recent kernels: 6.8.0-25 from Noble and the mainline kernel builds from
e.g:
https://kernel.ubuntu.com/mainline/v6.8/amd64/
Used for ensuring support for recent hardware.
If these will be rebuilt without module compression for LTS/HWE kernel
releases then this issue isn't so vital, but it will
Public bug reported:
This is the same cause as the Mantic bug "cryptsetup autopkgtest fails
with zstd compressed kernel modules"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120
where hooks/cryptroot::add_modules() needs postfix wildcards after
$glob.ko on 2 lines.
It affects
This also affects LTS releases with HWE, and/or locally built kernels. I
hit it today building v6.8.0 with CONFIG_MODULES_COMPRESS_XZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2035120
Title:
Remaining problem could be with SeaBIOS. Copying here my question to
OFTC #virt
Doing some GRUB bios-mode boot testing with qemu/x86_64. Attached 2 IDE
devices, a small HDD (file with mbr and 2 partitions) and a CDROM (iso
file). If SeaBIOS boots the CD GRUB can see both devices ("(cd) (hd0)")
After reserching the NFS lock issue it seems I found the solution on the
Debian 11 Bullseye server:
$ sudo systemctl enable rpc-statd
Created symlink /etc/systemd/system/nfs-server.service.wants/rpc-statd.service
→ /lib/systemd/system/rpc-statd.service.
$ sudo systemctl start rpc-statd
Now, the
One issue is that when the libvirt cache mode is set to "none" what is
passed to qemu is "write-cache=on". If I set libvirt cache mode to
"writethrough" qemu gets "write-cache=off" !
The remaining problem is solving the lock issue on NFS. Came back to
this issue again today and its again blocked
ons of apt and is focused on the URL
encoding only it has minimal potential for causing regressions.
[1] https://github.com/linux-surface/linux-surface/issues/625
[2] https://launchpad.net/~tj/+archive/ubuntu/bugfixes
[3] https://salsa.debian.org/apt-
team/apt/-/commit/06ec0067057e0578f3bc515f6a97d6
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/5538304/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574341
Title:
Although most other issues are solved there is still no multitouch for
this device with kernel v5.15 and xserver-xorg 1.20.13-1ubuntu1 using
Kubuntu 21.10.
# xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4
Here's the reproducer that shows that dummy0 is being created in the
host network namespace. This is an upstream bug (oversight) so far as I
can tell from its purpose.
# what the host sees initially
root@t300chi:~# nmcli con
NAME UUID TYPE DEVICE
USB3hub
Public bug reported:
Ubuntu 20.04 amd64. Originally thought this was virt-manager but tested
via virsh and found it appears to be caused by libvirt.
$ apt-cache policy libvirt-daemon virt-manager | grep -E '(^[^ ]|Installed)'
libvirt-daemon:
Installed: 6.0.0-0ubuntu8.14
virt-manager:
** Attachment added: "Screenshot from virt-manager"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+attachment/5535410/+files/Screenshot_2021-10-23_11-17-02.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm currently working on getting my optimisation patches into the
mainline kernel and to Debian's initramfs-tools. After that I'll
investigate dracut.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On LVM systems where an LV is fronted by a dm-writecache LV grub-probe
fails to identify the filesystem type:
root@sunny:~# grub-probe -d /dev/mapper/SUNNY-usr_local -t fs
error: invalid segment.
error: invalid segment.
grub-probe: error: disk
Update: Lennart's AF_SOCKET solution was added to systemd v248 in:
commit e2c2f868b28f1445e061bf7eb475b0c49efe3ac2
Author: Lennart Poettering
Date: Wed Nov 4 17:24:53 2020 +0100
cryptsetup: port cryptsetup's main key file logic over to
read_full_file_full()
Previously, we'd load
This really should not be marked Invalid since it represents a very real
regression on recommended and documented functionality that many
installs using LUKS rely upon. Workarounds of varying security quality
abound as a result instead of a single, well designed and integrated
solution.
Indeed,
Public bug reported:
scroll bar was so small as to be almost invisible even when I hovered
over where it should be - it did work once or twice but I had to get
lucky in where I clicked to move the info in the window up or down.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: qterminal
Public bug reported:
no scrollbar on the software selection window. (arrow keys did work)
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: discover (not installed)
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion:
I suspect these may be related:
https://github.com/electron/electron/pull/30893 "fix: crash when
launching app with systemd v249"
https://github.com/microsoft/vscode/issues/132609 "Electron 14+
required? Potential systemd 249 / nVidia issue"
Electron patch backported from Chromium:
This was just brought to my attention so I took a look at the source-
code. Thanks to oldfred's comment #20 showing part of the installer log
that helps isolate the source-code responsible.
It looks like this is a result of this code - written in 206 - assuming
a debconf entry that is empty and
I've cherry-picked the upstream patches and built the package in my bug-
fixes PPA:
https://launchpad.net/~tj/+archive/ubuntu/bugfixes
Verified it solves the issue even in the face of a 1000ms delay being
imposed by the router using:
## example traffic control to slow down UDP port 53 traffic
The local systemd-resolved fails to resolve the name so client
applications return failures. Most notably it shows up in web browsers
but also for apt package updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248)
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server
** Description changed:
+ Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248)
+
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server
Public bug reported:
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server answers and then
resolved sends an ICMP Destination Unreachable (Port
User is long-gone after workaround solved their issue. This report is
FYI in case other users hit the same error messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940332
Title:
hci0: Failed
** Description changed:
Despite the fix in 2012 (bug #991360) the default configuration shipped
- with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the
- DHCPv6 hostname option by default. All it needs is:
+ with isb-dhcp-client /etc/dhcp/dhclient.conf in 2021 still does not
Public bug reported:
Despite the fix in 2012 (bug #991360) the default configuration shipped
with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the
DHCPv6 hostname option by default. All it needs is:
# send host-name with DHCPv6 not just DHCPv4
send fqdn.fqdn = gethostname();
** Description changed:
This report is related to a problem reported in IRC #ubuntu whereby
(Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot
time but can later.
Appears to be a race condition between the wifi chipset setting up the
device and enabling the
Public bug reported:
This report is related to a problem reported in IRC #ubuntu whereby
(Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot
time but can later.
Appears to be a race condition between the wifi chipset setting up the
device and enabling the attached USB
I've built a package with this fix applied in my PPA at:
https://launchpad.net/~tj/+archive/ubuntu/bugfixes/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879923
Title:
Update Scan Data
** Attachment added: "Screenshot of Scantable Update success"
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/+attachment/5517930/+files/kaffeine-scantable-success.png
** Changed in: kaffeine (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug
Attached patch cherry-picked from upstream and confirmed working
** Patch added: "Update for focal 20.04"
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/+attachment/5517929/+files/kaffeine_2.0.18-1ubuntu1.debdiff
--
You received this bug notification because you are a
** Changed in: kaffeine (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Description changed:
- Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop. Update Scan
- Data Over Internet fails with message: Scan data update failed
+ Workaround from Tj; 3 commands (ignore word-wrapp
Confirming this is still an issue on 20.04 with
$ apt-cache policy kaffeine
kaffeine:
Installed: 2.0.18-1build1
Candidate: 2.0.18-1build1
Version table:
*** 2.0.18-1build1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
The file is a sequence of
** Description changed:
The packaging nor man-pages do not make clear that these tools only
support a very old "legacy" tuner format (DVBv3) and as such fail to
work using various instruction sources.
The tuner files are installed via the dependency on 'dtv-scan-tables'
and are
Public bug reported:
The packaging nor man-pages do not make clear that these tools only
support a very old "legacy" tuner format (DVBv3) and as such fail to
work using various instruction sources.
The tuner files are installed via the dependency on 'dtv-scan-tables'
and are predominantly DVBv5
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Sourceware.org Bugzilla #12398
https://sourceware.org/bugzilla/show_bug.cgi?id=12398
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=12398
Importance: Unknown
Public bug reported:
Possible vulnerability with an active proof of concept that may well
become a CVE.
ssh-agent Shielded Private Key Extraction
https://security.humanativaspa.it/openssh-ssh-agent-shielded-private-
key-extraction-x86_64-linux/
** Affects: openssh (Ubuntu)
Importance:
@Cyan - is that on 21.10 (Impish) because your report has changed the
status for the 20.04 (Focal) report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906479
Title:
qemu:handle_cpu_signal
Public bug reported:
I've been working with a user for the last 2 days on a failure to even
start the kernel when installing 20.04 or 21.04 (possibly other
releases) with a UEFI boot.
System is Dell XPS 9550 amd64 with Ubuntu Budgie.
The symptom is that after GRUB successfully loads the kernel
We've installed 5.12.0 on Callum's PC and the latest qemu-user-static
(5.2+dfsg-9ubuntu3) from 21.04 and so far it also appears to be working.
We're not sure what has been happening but we'll chalk this one down to
user-error for now unless it re-occurs!
--
You received this bug notification
Before I forget and in case others find it useful I wrote a simple
Python tool to check binfmt magic bytes registered with the kernel with
particular files.
It can be found here:
https://iam.tj/projects/misc/binfmt-check
--
You received this bug notification because you are a member of Ubuntu
Testing by trying to execute /sbin/ldconfig within the aarch64 Debian
bullseye chroot on 20.04 amd64 host for all installed kernels is
working, including 5.12.0, the version booted to by default !
That is: 5.4.0-73-lowlatency 5.8.0-41-lowlatency 5.10.2 5.11.0+
5.12.0-elloe+
This is extremely
All tests using chroot's on my host are with kernel v5.12.0 with the
ubuntu kernel .config as base + 'make olddefconfig'.
I'll try the standard Ubuntu 20.04 kernel, and HWE, just in case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I stepped back to the chroot and tried qemu-aarch64-static from 21.04's
qemu-user-static (5.2+dfsg-9ubuntu2) but *debootstrap* fails in the same
way as previously reported.
HOWEVER, this works:
$ sudo chroot bullseye-arm64 /usr/bin/qemu-aarch64-static /sbin/ldconfig -v
/sbin/ldconfig: Can't stat
Ok, that was an easy solve:
$ sudo chown 0:0 bullseye-arm64
And with that installation runs to completion. This is inside a 21.04
amd64 desktop KVM virtual machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In a 21.04 amd64 desktop virtual machine it fails but with a different
error apparently related to bullseye systemd package, not sure if I can
untangle this mix of problems:
$ sudo apt install qemu-user-static debootstrap
$ sudo qemu-debootstrap --arch=arm64 bullseye bullseye-arm64/
First simple test with 21.04 amd64 LXD host with kernel 5.12.0 results
in the same issue.
I'll need to repeat in a virtual machine next.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928075
Title:
Another data point.
We tried installing qemu-aarch64-static from Debian's qemu-user-static
amd64 packages from testing (1:5.2+dfsg-10) (bullseye) and experimental
(6.0+dfsg-1~exp0) into the chroot. Both result in the same error.
On my PC I have kernel 5.12.0-elloe+ and Callum has 5.10.0. We both
Looking closer we've just noticed the bullseye's ldconfig claims to be
dynamically linked but buster's is statically linked.
This reminds of bug #1908331 we solved earlier this year in qemu itself
due to the build flag -static-pie
$ file bullseye-arm64/sbin/ldconfig
bullseye-arm64/sbin/ldconfig:
Will do - I run builds of the mainline kernel tracking upstream so that
part isn't a problem. We are operating on bare-metal on the host.
I suspect it is glibc and/or compilation options since trying to
manually call, for example, /bin/dash or other executables hits the same
issue.
--
You
URL:http://ftp.debian.org/debian/pool/main/u/util-linux/mount_2.36.1-7_arm64.deb
[181404/181404] ->
"/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/mount_2.36.1-7_arm64.deb"
[1]
2021-05-11 11:42:20
URL:http://ftp.debian.org/debian/pool/main/u/util-linux/util
** Description changed:
+ SRU justification (created by Tj)
+
+ [Impact]
+
+ Without this patch `speedtest-cli` is unable to download the list of
+ servers it needs to fetch each time it is invoked and causes a Python
+ exception and terminates, rendering the tool unusable.
+
+ Applying
No, this is incorrect. called as 'cal' the intention is to be bit
compatible with the original 'cal'. 'ncal' added the highlight option
and as the man-page shows '-h' is only valid when it is called as
'ncal'.
Secondly highlighting when called as 'cal' was a (Debian) bug #9848389
which is
** Patch added: "Upstream fix applied"
https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1923628/+attachment/5493343/+files/speedtest-cli_2.1.2ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Debdiff provided by Reiner"
https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1916767/+attachment/5488486/+files/firejail-cve.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
CPU: 0 PID: 1 Comm: systemd Tainted: G OE 5.4.0-66-generic
#74~18.04.2-Ubuntu
The stand-out info in the log fragments is the kernel is tainted with
GPL (G) unsigned (E) out-of-tree (O) modules:
openvswitch(OE)
mlx5_core(OE)
mlxfw(OE)
mlx4_en(OE)
mlx4_ib(OE)
mlx4_core(OE)
Public bug reported:
All attempts to build non disk-image targets 'directory' 'tar'
'subvolume' (lightweight containers) fail with the same error. The only
fix appears to be to upgrade to latest mainline code (mkosi version 9).
Example:
root@elloe000:~# mkosi -t directory
DISTRIBUTION:
** Description changed:
version 5-1 does not support Ubuntu correctly in that it tries to use
the version number rather than version codename in arguments to
debootstrap.
+
+ $ sudo mkosi
+ ...
+ Traceback (most recent call last):
This applies for 21.04, 21.10 and 20.04
** Patch added: "Debdiff from 5-1"
https://bugs.launchpad.net/ubuntu/+source/mkosi/+bug/1923145/+attachment/5485893/+files/mkosi_5-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
version 5-1 does not support Ubuntu correctly in that it tries to use
the version number rather than version codename in arguments to
debootstrap.
** Affects: mkosi (Ubuntu)
Importance: Undecided
Status: In Progress
** Changed in: mkosi (Ubuntu)
Status:
Had my techie test the SRU for 20.04 on the affected E495 and can
confirm this works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block staircase display with
Public bug reported:
Froze twice on me.
1) Started up OK, selected preferences fine, then froze when I chose
which streaming service and category to listen to.
2) Started up OK, chose one streaming service and station (played fine),
then chose another music category and froze (had to kill -9 it
Public bug reported:
There is no menu item for installed Jupyter-console under "Programming"
or under "Accessories".
Similarly, installed GNU PSPP only has a menu item under "Other" but not
also under "Education".
Finally, installed R (statistical software) only has a menu item under
** Summary changed:
- Octave GUI command line editing display problems in Lubuntu 21.04 alpha
+ Octave GUI command line editing display problems in Lubuntu 21.04 daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Command line editing is all messed up: sometimes there is excess space
between characters, sometimes characters disappear when editing. It
seems like the cursor is often in the wrong place (too much space behind
it, especially as a longer command is typed out).
ProblemType:
** Description changed:
$ apt-cache policy k3b
k3b:
Installed: 19.12.3-0ubuntu1
On Xubuntu 20.04 we've discovered a very strange issue. All but the
first copy of a CD-audio burn result in tracks with complete silence.
This happens whether we do one burn operation with "Copies"
** Description changed:
$ apt-cache policy k3b
k3b:
- Installed: 19.12.3-0ubuntu1
+ Installed: 19.12.3-0ubuntu1
On Xubuntu 20.04 we've discovered a very strange issue. All but the
first copy of a CD-audio burn result in tracks with complete silence.
This happens whether we do
Public bug reported:
$ apt-cache policy k3b
k3b:
Installed: 19.12.3-0ubuntu1
On Xubuntu 20.04 we've discovered a very strange issue. All but the
first copy of a CD-audio burn result in tracks with complete silence.
This happens whether we do one burn operation with "Copies" set greater
than
** Changed in: isc-dhcp (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/1905800
Title:
Apparmor denies pid file creation for dhclient when started by
** Summary changed:
- package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to install/upgrade:
installed mysql-server-5.7 package post-installation script subprocess returned
error exit status 1
+ Live/overlayfs apparmor DENIED open "upper/etc/mysql/conf.d" mysql-server-5.7
package
Public bug reported:
With the current package in 21.04 dev (4.4-1) manually downloaded via
dget an initial build fails due to artifacts (symlinks to system-
installed fonts) of the build process. Comparing to the builder logs I
see that a 'clean' is required to remove them. I've never hit this
Erich, looks like that code wasn't reached or if it was the object
(list) "auto_removable" was empty.
Maybe the problem is outside this code. Does apt think those packages
are still installed?
apt list --installed 'linux-image*'
Also, what is the actual content of /boot/ ("ls -latr /boot/") ?
I haven't been able to test this since the systems I have here don't
have any kernel images lying around, but wondering if this patch could
help narrow down the cause?
Apply to a (copy) of /usr/bin/unattended-upgrade - possibly put in
/usr/local/bin/ so it is called before the package-installed
I'm also wondering if these are laptops or desktops, and if laptops, are
they mainly on battery whilst not sleeping/charging? I ask since apt-
daily-upgrade.service has:
ConditionACPower=true
and so may be reporting:
Condition check resulted in Daily apt upgrade and clean activities being
|& tee /tmp/build.log
make[1]: Entering directory '/media/tj/SourceCode/builds/arm-beagle'
GEN ./Makefile
scripts/kconfig/conf --syncconfig Kconfig
You are building kernel with non-retpoline compiler.
Please update your compiler.
make[1]: *** [arch/x86/Makefile:317: checkbin] Error 1
ma
Looking at the Debian changelog looks like both Ubuntu 18.04 and 20.04
needs at least 6.01-2 whereas it has 6.01-1. Ubuntu 20.10 has 6.12-1:
libhttp-daemon-perl (6.01-2) unstable; urgency=medium
...
[ Fabian Grünbichler ]
* switch to IO::Socket::IP to add IPv6 support (Closes: #667738)
[
Public bug reported:
iputils-ping includes ping6 which can send Node Information requests,
e.g:
ping6 -N name ipv6:addr::ess
but there is no system daemon to listen and respond.
iputils package contains ninfod which performs that function but it
isn't built or packaged.
For IPv6 networks Node
Another follow-up. Had the same problem with 20.04 amd64. My solution
detailed above would not work when using the GUI where the Blueman
bluetooth applet was in the notification area.
Eventually I found it worked from a real tty console (switched from GUI
to tty2 with Ctrl+Alt+F2) and running the
Hi Christian, sorry I missed your updates on this one. I've only just
come back to the issue yesterday and apparently I've hit another issue:
bug #1908331 "Regression: qemu-user-static binaries are dynamically
linked"
That side-tracked me whilst trying to do the git-bisect and I've still
not
I've posted a question to the qemu-devel mailing list with subject "Are
user static builds really dynamically linked ?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression:
To be sure I built upstream v4.2.1 and it reports the expected and
required linkage. Build needs some additional tweaking to avoid libssh
deprecated functions causing -Werror to trigger:
$ sudo apt install liblzma-dev
$ ../../qemu/configure --target-list=aarch64-linux-user --static
** Description changed:
On 20.04 (qemu 4.2) the binaries built for qemu-user-static -
specifically in the case I've hit /usr/bin/qemu-aarch64-static - are
completely static executables.
The same binaries from a qemu 5.x build are not. Although they don't
link to other shared
Public bug reported:
On 20.04 (qemu 4.2) the binaries built for qemu-user-static -
specifically in the case I've hit /usr/bin/qemu-aarch64-static - are
completely static executables.
The same binaries from a qemu 5.x build are not. Although they don't
link to other shared libraries they are
** Description changed:
On 20.04 amd64 trying to run 'aptitude full-upgrade' inside a Debian
buster chroot:
mkdir debian-buster-aarch64
sudo debootstrap --arch=arm64 --foreign buster debian-buster-aarch64
http://deb.debian.org/debian
sudo cp -a /usr/bin/qemu-aarch64-static
Public bug reported:
On 20.04 amd64 trying to run 'aptitude full-upgrade' inside a Debian
buster chroot:
mkdir debian-buster-aarch64
sudo debootstrap --arch=arm64 --foreign buster debian-buster-aarch64
http://deb.debian.org/debian
sudo cp -a /usr/bin/qemu-aarch64-static
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906131
Title:
No rule to make target 'scripts/module.lds' while building
Public bug reported:
kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
module linker script" ) that affects where and how scripts/module.lds is
used and causes external modules to fail to build since that linker
script is not shipped in the linux-{image,header} packages.
Similar issues with Logitech wireless keyboard and mouse after updating
Hirsute. Mouse freezes intermittently but is mostly usable. Keyboard is
essentially unusable (this is posted via onscreen keyboard). All
hardware fully functional on Hirsute with 5.8.0-25 and 5.8.0-26 before
updates on 11/27
** Project changed: launchpad => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905993
Title:
Actual kernel don't want to make more than 64 cpus available
To manage notifications
Public bug reported:
??
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpam-systemd:amd64 204-5ubuntu20.31
ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
Uname: Linux 3.13.0-19-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.29
AptdaemonVersion: 1.1.1-1ubuntu5.2
So far when this affects me (20.04) it is when I've opened the media
from a file manager or started VLC via the menu.In both cases it uses
"vlc --start-from-file ..." - if I start vlc on the command-line
without that option it seems to quit/terminate correctly and not hang
about.
--
You
*** This bug is a duplicate of bug 1876989 ***
https://bugs.launchpad.net/bugs/1876989
Public bug reported:
20.04.1 Encrypted LVM install, sda4 > LUKSv2 > VG > LVs
cryptsetup creates LUKSv2 containers. GRUB can only understand LUKSv1
and therefore cannot access its root device making the
Public bug reported:
20.04.1, when applying updates, 'full log' is reporting for every
package install:
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such
device)
This should either be corrected (by mounting devpts into the /target/ or
redirecting the error to /dev/null to
Public bug reported:
20.04.1, Custom storage layout
This view does not refresh when underlying changes have occurred,
whether using the "Reset" option, or using 'Back' to move back through
the pages.
Specific scenario is related to "Unable to add a GPT partition with
400+GB free space" bug
Public bug reported:
20.04.1 installer, Custom storage layout
On a device with 400+ GB free space and 4 existing GPT partitions the
option to add a GPT partition is disabled.
Apparently the logic cannot code with dis-contiguous partitions!
root@ubuntu-server:/# gdisk -l /dev/sda
GPT fdisk
May be fixed by upstream commits:
7b7d897e8898 2020-07-24 12:34:42 +0200 N shirley her mmc: sdhci-pci-o2micro:
Add HW tuning for SDR104 mode
cdd2b769789a 2020-07-24 12:30:36 +0200 N shirley her mmc: sdhci-pci-o2micro:
Bug fix for O2 host controller Seabird1
--
You received this bug
Public bug reported:
I've been working with a colleague with an ubuntu-server install in a
Xen virtual machine. The install doesn't use an external
kernel/initrd.img but due to having package ubuntu-server installed also
installs cloud-initramfs-copymods.
The initial report was the system
1 - 100 of 2963 matches
Mail list logo
