** No longer affects: systemd (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu Core 18
To manage notifications
@vanvugt: Thanks for having a look. Have you tried firefox from flatpak or any
other flatpak application?
Also is the "pipewire-media-session" package installed by default? It didn't
seem to be the case for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Hardware Info:
1th Gen Intel(R) Core(TM) i9-11900K
MSI MEG Z590 ACE
GeForce RTX 3090
Operating System Version:
Ubuntu 20.04.3 LTS
intel-microcode version:
3.20210608.0ubuntu0.20.04.1
Symptom:
Unexpected random reboots often happen during periods
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 1950239
and then change the status of the bug to 'Confirmed'.
If, due to the
Oh and surely only going forward in tomcat9 or maybe even tomcat10 once
it is real.
And only together with Debian as we do not want to regularly need to merge a
universe package.
Debian itself does not benefit, for them it is a no-op as they do not have
apport.
Maybe prep/test and submit it to
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950239
Title:
creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-raspi (Ubuntu Groovy)
Status: Confirmed => Invalid
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Groovy)
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/1896950
FYI there is a chance that this will be handled indirectly via Postgresql-14
See bug 1949579
Furthermore on Postgresql-13 there is soon an upcoming v13.5 which will
include the reported commits.
We need to try-build both against the PPA at
The following PPA contains cross-platform (s390x, ppc64el, arm64 and amd64)
test builds for kernels 5.13/impish, 5.11/hirsute and 5.4/focal:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1950144/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Our delta is trivial (FTBFS)
https://git.launchpad.net/ubuntu/+source/open-isns/commit/?id=7e9bfa4f7d79b465b8e441ccb6a140fcf2b51b80
Since then all are just no change rebuilds.
This now is also visible in Debian (due to libc upgrade)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994672
We
** Changed in: qemu (Ubuntu Impish)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
Title:
qemu-arm-static swallows the program
** Changed in: chromium-browser (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/1950040
Title:
Wayland Screensharing broken in Ubuntu 21.10
To manage
Aha! Launchpad was OOPSing when I tried to upload the gzipped tarball,
but I've successfully uploaded the files as a zstd-compressed tarball.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940485
** Attachment added: "thermald debug script output"
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+attachment/5539066/+files/try-again.tar.zstd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just tested 21.10 and can reproduce the bug in Firefox there. It
appears the cause is Firefox version 93 in Ubuntu 21.10, whereas Ubuntu
22.04 has Firefox 94. So here's how to fix it in Ubuntu 21.10:
snap remove firefox
snap install firefox --candidate
Chrome/Chromium will need a
Public bug reported:
Caja is part of the Ubuntu MATE package but apparently unsupported.
Caja after the latest update takes minutes to open a menu and it takes 3
times to open files with Eye of MATE.
Nautilus has similar problems but is not as slow. But then it crashes.
How do I get Caja
@Chris, could you upload the log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940485
Title:
thermald often limits CPU frequency while on AC
To manage notifications about this bug go to:
This bug was fixed in the package net-tools -
1.60+git20181103.0eebece-1ubuntu4
---
net-tools (1.60+git20181103.0eebece-1ubuntu4) jammy; urgency=low
* Add new DEP8 tests for hostname and ifconfig (LP: #1679346):
- d/t/control: add hostname-set-get and ifconfig-lo-info
-
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with
error
I installed 21.10 with ZFS+encryption before this was fixed. Do I need
to reformat and reinstall? Or is there a way to check for corruption on
each zpool?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1507
This ID is included in upstream.
[Impact]
- * Devices have goodix [27c6:639c] fingerprint component will get
-supported.
+ * Devices have
** Description changed:
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1505
This ID is included in upstream.
[Impact]
* Devices have goodix [27c6:639c] fingerprint component will get
supported.
* This sru
Public bug reported:
Update to focal failed and error occurred
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: rabbitmq-server 3.6.10-1
ProcVersionSignature: Ubuntu 4.15.0-161.169-generic 4.15.18
Uname: Linux 4.15.0-161-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
** Tags added: oem-priority originate-from-1950246 somerville
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Andy Chi (andch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Update to focal failed and error occurred
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: rabbitmq-server 3.6.10-1
ProcVersionSignature: Ubuntu 4.15.0-161.169-generic 4.15.18
Uname: Linux 4.15.0-161-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
[Expired for nvidia-graphics-drivers-470 (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Update to focal went wrong and rospkg doesnt install since then
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python-rospkg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-161.169-generic 4.15.18
Uname: Linux 4.15.0-161-generic x86_64
ApportVersion:
** Changed in: consul (Debian)
Status: New => 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/1940152
Title:
TLS related test failure with go1.16
To manage notifications about
Public bug reported:
[Impact]
* Fingerprint cannot enrolled successfully on goodix fingerprint
device.
[Test Plan]
* Enroll fingerprints on laptop and login without problem at first time
(no fingerprint stored in goodix device).
* Re-install Focal directly without deleting stored
Testing on Ubuntu 22.04. Screen sharing in Wayland sessions is *working*
for the Firefox snap but not the Chromium snap and not the Chrome deb
either.
Actually that's expected for Chrome/Chromium because they used Xwayland
by default so can't access the screen. The weird thing is that running
Thanks.
Something I should note (here, because I don't know where else to put
it) is that both my and this original poster's graphics cards use the
GCN 1.0 architecture (according to
https://en.wikipedia.org/wiki/Radeon_Rx_200_series#Mobile_models).
This is the arch that only has pseudo support
Yes it appears to be a kernel issue. I don't know if downgrading (or
upgrading) will fix it but that's definitely worth a try.
See also
https://gitlab.freedesktop.org/drm/amd/-/issues?scope=all=opened=%22ring+gfx+timeout%22
--
You received this bug notification because you are a member of
As comment in https://github.com/home-sweet-gnome/dash-to-
panel/issues/1500#issuecomment-962511964, this problem is caused by
dash-to-dock not release the hooks of nautilus.
This issue could be fixed by disable-enable the dash-to-panel after
editing the /usr/share/gnome-shell/extensions/ubuntu-
This guide describes how to make a copy of gnupg files in order to
create a duplicate card:
https://zach.codes/ultimate-yubikey-setup-guide/
It would be nice if such a guide weren't necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Do we know if this is kernel issue? Will downgrading the kernel fix it
in the short term?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949497
Title:
[amdgpu] Screen freezes
Hi,
The riscv port project has been approved by the OpenJDK community [1],
and we have switched to project-specific repo for future development
[2]. Please also switch to use the new repo.
[1] https://openjdk.java.net/projects/riscv-port
[2] https://github.com/openjdk/riscv-port/tree/riscv-port
This bug is still present on 20.10. You'd think after 10 years ... it
would get fixed??? Glad I found this thread. Very pleased to have this
working with a *very* simple symlink.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring gfx timeout)
+ [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1949497 ***
https://bugs.launchpad.net/bugs/1949497
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1949497, so it is being marked as such. Please
Thanks for the bug report. Next time the problem happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New =>
** Tags removed: bugnameltc-194783 severity-medium
** Tags added: bugnameltc-192677 severity-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927076
Title:
IPv6 TCP in reuseport_bpf_cpu from
Hmm actually the problem appears to be fixed in the new version in
Ubuntu 22.04 already.
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That apparent corruption is actually encoded information used by the
desktop-icons-ng extension. It's not pretty and ideally nobody should
see it.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
desktop-icons-ng (Ubuntu)
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061
Thanks. That confirms it is bug 1945061.
** This bug has been marked a duplicate of bug 1945061
gdm3 crashed with SIGSEGV in ensure_display_for_seat()
--
You received this bug notification because you
** Summary changed:
- IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node
entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
+ IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node
entei (Oops: Exception in kernel mode, sig: 4 [#1])
Hello Matthias, or anyone else affected,
Accepted gcc-9-cross-ports into focal-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/gcc-9-cross-ports/18ubuntu5 in a
few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Matthias, or anyone else affected,
Accepted gcc-9-cross-mipsen into focal-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/gcc-9-cross-mipsen/4+c2ubuntu2.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Matthias, or anyone else affected,
Accepted gcc-9-cross into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/gcc-9-cross/21ubuntu5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Grant Orndorff,
This is happening when I try to upgrade with apt upgrade
I already reported in another post but was doubled and I posted here, I
reported on this:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927905
I tried to run command: env
InterpreterPath: /usr/bin/python3.9
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211108)
PackageArchitecture: all
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /usr/bin/python3 /usr/bin/cloud-init status --wait
ProcEnviron:
LA
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950204
Title:
stuck while booting since 20.04.3 LTS upgrade
To manage notifications
This bug was fixed in the package distro-info - 1.1
---
distro-info (1.1) unstable; urgency=medium
* Man pages and help: Clarify that --supported includes development releases
(Closes: #902167, LP: #1727751)
* Update Python module to satisfy pylint 2.11 (Closes: #998598)
*
Public bug reported:
When you go to create a new folder on the desktop, the dialog box that
asks you for the folder name has a corrupted title bar. It says "New
Folder@!HTD" instead of "New Folder".
This is occuring on Ubuntu 21.10
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package:
The verification of the Stable Release Update for gdebi has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package gdebi - 0.9.5.7+nmu5ubuntu2
---
gdebi (0.9.5.7+nmu5ubuntu2) impish; urgency=medium
* Drop Ubuntu-specific patches - no-longer needed
(LP: #1756238, #1946499)
-- Dani Llewellyn Thu, 14 Oct 2021 18:30:02
+0100
** Changed in: gdebi (Ubuntu
FYI: SolidRun Honeycomb/ClearFog LX2K users depend upon this feature as
well (ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT=n); despite this original issue
being filed for Cavium boards, it's still true for more recent hardware
as well.
Thus, please don't remove it without compatibility testing. Thanks!
--
Exactly the same trouble here!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950101
Title:
Cannot wakeup from sleep from keyboard
To manage notifications about this bug go to:
Public bug reported:
When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish
image and nothing new installed to it, update-initramfs fails like so:
Setting up linux-firmware (1.201.1) ...
Edit -- it transpires that, despite what I said, the magic <0 to <=0
change hasn't been made on the main branch of mesa's git repo yet. I've
successfully compiled a local copy (with meson & ninja) and am running
it in a separate root to avoid clobbering the system libraries using
LD_LIBRARY_PATH
(In reply to V Stuart Foote from comment #14)
> Complex stuff, and requires major refactoring of Calc needing some UX
> envisioning.
What exactly? The requirement is clear (and requested repeatedly in the
recent survey [1]). It's expected to scroll per pixel even when the cell
exceeds the window
** Changed in: exim4 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946857
Title:
Merge exim4 from Debian unstable for 22.04
To manage notifications
Hello,
I could find out that there is a sound driver for the laptop. The issue is in
the zero volume when installer is enabled, so a user can change it only if he
has a braille display. Please fix the zero volume issue in the installer, I
believe it was already reported.
--
You received this
Fails for me too 5.15.1 on Penryn, Ivybridge, Haswell and guest VMs on
Zen3.
I had to rebuild the kernel from kernel.org using the config from Ubuntu
Mainline but disabling the debian pem certs and "CONFIG_UBSAN_TRAP".
After that it worked on all the above architectures.
--
You received this
** Changed in: makedumpfile (Ubuntu)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This change was made by a bot.
** Changed in: linux (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/1950205
Title:
Some shaders can crash the amdgpu kernel
Public bug reported:
Hi there,
I am experiencing, at random, the AMD-GPU "fences timed out!" bug
reported previously as being either a kernel issue
(https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa
(https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The
later was
Public bug reported:
After the upgrade to 20.04.3 LTS booting doesn't work.
In the booting process (using the latest kernel) the computer stuck,
showing a purple screen:
UBUNTU 20.04
. . . . .
(sometimes the dots indicating
** Description changed:
- Gnugpg does not offer the option to store the private and public keys
- on two different keycards.
+ Gnugpg does not offer the option to store the private and public keys on
+ two different keycards.
I have followed the official yubikey guide as follows, but it
This bug was fixed in the package linux-bluefield - 5.4.0-1021.24
---
linux-bluefield (5.4.0-1021.24) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1021.24 -proposed tracker (LP:
#1947236)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
* Add
This bug was fixed in the package linux-bluefield - 5.4.0-1021.24
---
linux-bluefield (5.4.0-1021.24) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1021.24 -proposed tracker (LP:
#1947236)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
* Add
This bug was fixed in the package linux-bluefield - 5.4.0-1021.24
---
linux-bluefield (5.4.0-1021.24) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1021.24 -proposed tracker (LP:
#1947236)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
* Add
Public bug reported:
Gnugpg does not offer the option to store the private and public keys
on two different keycards.
I have followed the official yubikey guide as follows, but it might
apply to similar smart cards and USB tokens:
To import the key on your YubiKey:
Insert the YubiKey into
Public bug reported:
Upgrading from 18.04 to 20.04 on Azure using apt
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd 3.0.3-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-1063.66~18.04.1-azure 5.4.148
Uname: Linux 5.4.0-1063-azure x86_64
NonfreeKernelModules: nvidia_modeset
Seems Ubuntu Mainline Kernel team doesn't hear us as 5.15.1 still fails
to boot but they're don't care about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14
5.15.1 still fails to boot on my desktop. Nothing is changed.
** Summary changed:
- Linux 5.14/4.13.14 fails to boot
+ Linux 5.15/5.14/4.13.14 fails to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: impish jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923253
Title:
Unable to on or off the orca screenreader on arctica-greeter lightdm
greeter using ++
To manage
I am originating from a Ubuntu 21.10 system to a Debian Bullet system,
but now I can't get X-forwarding to work from any site I connect to when
originating from Ubuntu 21.10.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet
Performing the verification for Bionic:
First, reproducing the bug with the current version:
# apt policy rsync
rsync:
Installed: 3.1.2-2.1ubuntu1.1
Candidate: 3.1.2-2.1ubuntu1.1
Version table:
*** 3.1.2-2.1ubuntu1.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.82.00-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1948025):
- Fixed a bug that can cause a kernel crash in SLI Mosaic
1 - 100 of 402 matches
Mail list logo
