This bug was fixed in the package pam - 1.4.0-10ubuntu1
---
pam (1.4.0-10ubuntu1) jammy; urgency=medium
* Merge from Debian unstable (LP: #1916509). Remaining changes:
- debian/control: have libpam-modules recommend update-motd package
- debian/libpam-modules.postinst: Add P
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1952083
Title:
Add support for Beige Goby
Status in a
This bug was fixed in the package logrotate - 3.18.1-2ubuntu1
---
logrotate (3.18.1-2ubuntu1) jammy; urgency=low
* Merge from Debian unstable (LP: #1952602). Remaining changes:
- debian/control: Drop mailx to Suggests for Ubuntu; it's only used
on request, and we don't con
** Tags removed: update-excuses
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1953200
Title:
[jammy] FTBFS with boost
Status in mir package in U
** Changed in: pam
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1953201
Title:
pam_env doesn't accept /etc/environment files that don'
FWIW, the problem happens because of this new check on
modules/pam_env/pam_env.c:
https://github.com/linux-pam/linux-
pam/blob/master/modules/pam_env/pam_env.c#L317-L320
if (p[strlen(p)-1] != '\n' && !feof(f)) {
D(("_assemble_line: line too long"));
return -1;
FWIW I'm going to mark this bug 'low' instead of high, on the basis that
Debian has shipped pam 1.4.0 in a stable release and there hasn't even
been a single bug report about this issue, it was only caught because of
a bug in the Ubuntu autopkgtest-cloud implementation that was writing
entries to /
Public bug reported:
Since PAM 1.4.x, pam_env's behaviour has silently changed and now it
fails to parse/doesn't accept /etc/environment files that don't end with
a newline.
It's easy to reproduce:
$ lxc launch ubuntu-daily:jammy pam-env-test --vm
$ lxc shell pam-env-test
# # Note that pam-1.4.x
Public bug reported:
https://launchpad.net/ubuntu/+source/mir/2.4.1-0ubuntu3
[ 38%] Building CXX object
src/client/CMakeFiles/mirclientobjects.dir/event_printer.cpp.o
cd /<>/build-amd64/src/client && /usr/bin/c++
-DCLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" -DEGL_NO_X11 -DLOG_NDEBUG=1
-
This bug was fixed in the package qtbase-opensource-src -
5.15.2+dfsg-14ubuntu1
---
qtbase-opensource-src (5.15.2+dfsg-14ubuntu1) jammy; urgency=medium
* Rebuild against openssl 1.1.1 in release pocket. (LP: #1952977)
-- Rik Mills Thu, 02 Dec 2021 07:25:25 +
** Changed in:
** Changed in: tzdata (nUbuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1484367
Title:
package tzdata 2015f-0ubuntu0.15.04 faile
I modified the debian/changelog file so that this bug is referenced in
it, this way the Launchpad janitor will close the bug report.
$ dput logrotate_3.18.1-2ubuntu1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/jammy/logrotate_3.18.1-2ubuntu1_so
The attachment "skel.bashrc.patch" 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-murr
I'm pretty much with @ddstreet here, introducing another hack to handle
Ubuntu Core quirks is not nice, as those hacks will make our systemd
more unstable over time and will break regularly after merging upstream
changes.
As stated before, we already carry such hacks since 2014 and I just want
to
Public bug reported:
While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi aarch64
Frankly I didn't remember this bug :) it's a machine in not using much
anymore but I think at some point the problem stopped happening.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
The upstream report moved to:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/149
but has not seen any activity for more than five years now.
As this issue has sat incomplete for nearly six years without any
response I
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Description changed:
+ Patch attached below.
+
[Description]
Separating the first part of a list and the `alert` part with && (or any
of the doubled control operators) will result the second character to be
printed in the body of a message, for example with:
sleep 5s && alert
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
(and in Impish in 1.16.6-2ubuntu1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1946096
Title:
Support manual firmware upgrading for Foxconn and Quectel modems.
St
Fixed in Jammy in 1.18.2-0ubuntu1.
** Changed in: modemmanager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1946096
Title
Hello Jerry, or anyone else affected,
Accepted modemmanager into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.16.6-2~20.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I think all concerns raised have now been addressed so I'm accepting the
upload into Hirsute and Focal.
** Changed in: modemmanager (Ubuntu Hirsute)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-hirsute
--
You received this bug notification because y
Hello Jerry, or anyone else affected,
Accepted modemmanager into hirsute-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.16.6-2~21.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. S
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Pavlos, thank you for your report and helping make Ubuntu better.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
I'm belatedly closing this as "Invalid" as you successfully upgraded
to Ubuntu 18.04 and there is nothing for us to do here.
** Changed in: xorg (Ubuntu)
Status:
** Description changed:
[Impact]
The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.
The modem manufacture vendors (Foxconn and Quectel) provided u
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Other bug reports found and responded to but no reply received.
No point in again asking if there still related outstanding issues.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification becaus
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Other reports found and responded to but no reply received.
No point in again asking for information from reporter.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
** Summary changed:
- Problems with Ubuntu Nome persist
+ Pr
Several other reports found and responded to but no reply received.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Closing this as "Invalid" as no point asking again if there is still
an issue with a currently supported release of Ubuntu.
** Changed in: xorg (Ubuntu)
Status:
*** This bug is a duplicate of bug 1659991 ***
https://bugs.launchpad.net/bugs/1659991
** This bug has been marked a duplicate of bug 1659991
no sound
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
htt
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1690528
Title:
screen corruption at startup
Status in xorg package
Further to comment #3, I'm closing this bug report as it was resolved
some time ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1690528
Title:
screen corruption at startu
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
I'm closing this as "Invalid" as no useful information was provided in
this and another bug report which was raised at about the same t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Description changed:
Separating the first part of a list and the `alert` part with && (or any
of the doubled control operators) will result the second character to be
printed in the body of a message, for example:
sleep 5s && alert
+
+ will display the following message:
+
+ sleep
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Patch added: "skel.bashrc.patch"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1953151/+attachment/5545229/+files/skel.bashrc.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.laun
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Changed in: bash (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1953151
Title:
Doubled control operators before `alert` will have
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Description changed:
Separating the first part of a list and the `alert` part with && (or any
of the doubled control operators) will result the second character to be
- printed in the body of a message. Adding the asterisk after the [;&|]
- bracket expression fixes it:
+ printed in the body
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Separating the first part of a list and the `alert` part with && (or any
of the doubled control operators) will result the second character to be
printed in the body of the message. Adding the asterisk after the [;&|]
bracket expression fixes it.
alias alert='notify-send --urgency=low -i "$([ $? =
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Public bug reported:
Separating the first part of a list and the `alert` part with && (or any
of the doubled control operators) will result the second character to be
printed in the body of a message. Adding the asterisk after the [;&|]
bracket expression fixes it:
alias alert='notify-send --urge
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review 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.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
1 - 100 of 104 matches
Mail list logo
