Kenneth, raising bug reports against the Ubuntu project will seldom
attract the attention of an Ubuntu developer that can assist in helping
with the issue that you are experiencing. To ensure that the right
people see a bug report, *every* report should identify the software
package related to the
Please close as I am no longer on 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792652
Title:
18.04.1 LTS undefined reference to `CRYPTO_get_lock_name'
To manage notifications about this bug
I just had a look and next version of Ubuntu uses ModemMamager 1.18.2 as
of now, so it does not have the handling for FCC unlock procedure.
** Also affects: modemmanager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
** Changed in: caja (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/1950295
Title:
Caja version 1.26.0-0ubuntu2~hirsute1.1 with Linux 5.13.0-20-generic
x86
Public bug reported:
As a prerequisite for the wireguard MIR (#1950317), we should add some
build-time tests to the package.
To start with, we can generate a pair of keys using the built wg tool.
** Affects: wireguard (Ubuntu)
Importance: High
Assignee: Andreas Hasenack (ahasenack)
Public bug reported:
This bug has been persisting since I've bought an external monitor for
my laptop and started using Wayland (first on Ubuntu 20.04) until today
(Ubuntu 21.10).
It isn't consistent, but it occurs about 90% of the time when I'm on
Wayland. On Xorg, this has never occurred.
When
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Public bug reported:
On startup the system reported there had been an error with this
package. I am new to Ubuntu and had a problem with an update to Ubuntu
20.04.3 initially due to badly mounted /efi/boot that I corrected in
fstab. I then did the partial upgrade as prompted and then could only
re
Did a successful hirsute testbuild for amd64 and arm64 with repo-snapshot-stamp
enabled. See:
- amd64:
https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/312995
- arm64:
https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/312996
** Tags removed: verification
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667911
Title:
upgrade to 15 to 16
To manage notifi
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
This bug was fixed in the package golang-defaults - 2:1.17~1
---
golang-defaults (2:1.17~1) unstable; urgency=medium
* Update to Go 1.17.
* Update man pages to Go 1.17
* Convert golang-src "Architecture: all" and marked "Multi-Arch: foreign"
as recommended by the Multiarch h
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
** Summary changed:
- libmbim cannot make use of Quectel EM120
+ modemmanager/libmbim cannot make use of Quectel EM120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949621
Title:
modemmanager/libm
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
** Changed in: jinja2-time (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885305
Title:
jinja2-time: FTBFS in unstable
To manage notifications abou
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Taking care of these:
- build time test:
https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1952767
- dep8 test: https://bugs.launchpad.net/bugs/1952102
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Released to focal-backports, thanks!
** Changed in: libreoffice (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950467
Title:
[BPO] libreo
Did a successful hirsute testbuild for amd64 and arm64 with repo-snapshot-stamp
enabled. See:
- amd64:
https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/313001
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-foca
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Impish)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a m
** Tags removed: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947600
Title:
Default browser changed from firefox to chrome
To manage notifications about this bug go to:
https://bu
** Changed in: firefox (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: firefox (Ubuntu Impish)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Same issue here, with the same workaround for me:
Edit /etc/default/grub.d/kdump-tools.cfg
Change the crashkernel part to read
crashkernel=512M-:256M
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: amd
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/1944382
Title:
Enable runtime power management for yellow carp XHCI
To manage notificat
** Changed in: libayatana-indicator (Ubuntu Impish)
Status: New => Incomplete
** Changed in: libayatana-indicator (Ubuntu Impish)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Re comment #2, thanks for your feedback.
Sorry for the delay in acknowledging.
Belatedly closing this issue.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: amd
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/1932577
Title:
[Cezanne/Renoir] Adjust uPEP for different _HID behavior
To manage notif
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Confirmed => Won't Fix
** Changed in: amd
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/1930719
** Changed in: deja-dup (Ubuntu Bionic)
Status: Triaged => 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/918489
Title:
duplicity allows a new, different passphrase if an archive
After more experience with different settings it seems that the behavior
of vfs_cache_pressure was changed a lot between linux kernel version 5.3
and 5.4.
For cases where vfs_cache_pressure=1 did work nicely with version 5.3
you need something in range 30-90 for linux kernel version 5.4 to get
the
> Assigning back to ddstreet - what would be the right assignee now,
~ubuntu-backporters, no-one, ... ?
I added a discussion item for the next backporters meeting for this:
https://wiki.ubuntu.com/UbuntuBackports/Agenda#Discussion
> And out of curiosity - would that now show up in [1] or does foc
What is the plan for 5.13 though? Will it stay for a while, or will
there be a migration to 5.14? The new firmware needs to be in place no
matter the kernel version or project. So for safety the suggestion
would be to take that patch to all kernels so that you can put the new
firmware back in pl
|Thank you for reporting this bug to Ubuntu. We are sorry that we do
not always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the updat
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
This seems to be a 'master' bug, with several duplicates. for issues
without an adequate description of the issues(s) the reporters were
seeing.
Ubunt
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Groovy is EOL. Can you reproduce this bug in newer Ubuntu MATE release?
** Tags removed: groovy
** Changed in: ubiquity (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.
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
** Changed in: subiquity (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952545
Title:
Subsiquity Installer fails during verification of pre-partitioned MBR
Public bug reported:
Ubuntu version:
Description:Ubuntu 20.04.3 LTS
Release:20.04
Package version:
samba-vfs-modules:
Installed: 2:4.13.14+dfsg-0ubuntu0.20.04.2
Candidate: 2:4.13.14+dfsg-0ubuntu0.20.04.2
Version table:
*** 2:4.13.14+dfsg-0ubuntu0.20
*** This bug is a duplicate of bug 1717796 ***
https://bugs.launchpad.net/bugs/1717796
The same bug occurs on Raspberry Pi and Mac OS, I think it is an open-
source bluetooth bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Reporter no longer uses Launchpad
Both releases referred to are long time EOL
So closing as "Invalid"
** Changed in: xorg (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.ne
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
In case it helps to reproduce the problem, or if its useful to anyone
else affected by this, we downgraded (and have also pinned) the
following packages:
apt-get install samba=2:4.13.14+dfsg-0ubuntu0.20.04.1 samba-
common=2:4.13.14+dfsg-0ubuntu0.20.04.1 samba-common-
bin=2:4.13.14+dfsg-0ubuntu0.20
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Public bug reported:
Hi,
Please remove libdigidoc from Jammy, as it fails to build against
OpenSSL 3.0, which hinders the transition.
https://launchpad.net/ubuntu/+source/libdigidoc/3.10.5-2build1
Fixing the failure is non-trivial, and without upstream involvement (see below)
I'd much rather ha
switched the log for a slightly more anonymized one
** Attachment removed: "samba_audit.log"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1952774/+attachment/5544382/+files/samba_audit.log
** Attachment added: "(anonymized) syslog"
https://bugs.launchpad.net/ubuntu/+source/samba/+
> what's the best way to save those logs?
What you've done is just fine, thanks. The 'Send to canonical' prompt
works well also but this is great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195254
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
** Changed in: lasagne (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888735
Title:
lasagne: autopkgtest fails with newer python-mock
To manage not
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
** Description changed:
+ [Impact]
+
+ On some thinkpads we may get a kernel panic at boot, because the
+ elantech driver (trakcpad) can trigger out-of-bounds access in the
+ stack.
+
+ [Test case]
+
+ Simply boot the kernel on one of the affected systems (e.g., Thinkpad
+ E14 Gen2).
+
+ [Fix]
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
No usable information attached
Further information requested from reporter on other bug reports
Closing this one as "Invalid"
** Tags added: xenial
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner. You reported this bug some time ago and there have been many
changes in Ubuntu since that time. Your problem may have been fixed with
some of the update
101 - 200 of 427 matches
Mail list logo
