This bug was fixed in the package glance - 2:20.2.0-0ubuntu1
---
glance (2:20.2.0-0ubuntu1) focal; urgency=medium
* New stable point release for OpenStack Ussuri (LP: #1948914).
-- Chris MacNaughton Thu, 28 Oct 2021
07:01:56 +
** Changed in: glance (Ubuntu Focal)
The verification of the Stable Release Update for nova 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 nova - 2:21.2.3-0ubuntu1
---
nova (2:21.2.3-0ubuntu1) focal; urgency=medium
* New stable point release for OpenStack Ussuri (LP: #1948914).
-- Chris MacNaughton Thu, 28 Oct 2021
07:01:58 +
** Changed in: nova (Ubuntu Focal)
Status:
@ayanamist - When you say 'roll back to 5.4.0-89', do you mean you
interrupt the grub timeout and select a kernel to boot ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952094
Title:
CIFS mount
Seems ok in Ubuntu 21.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672013
Title:
Installation on VirtualBox with a new 18GB btrfs partition fails
because of insufficient disk space
To
@seb128, please tell us what information is missing when you mark a bug
as "incomplete" because without doing so it looks like you're just
trying to trigger the automatic closure because you don't want to bother
fixing a bug.
--
You received this bug notification because you are a member of
This bug was fixed in the package nova - 3:23.1.0-0ubuntu1
---
nova (3:23.1.0-0ubuntu1) hirsute; urgency=medium
* New stable point release for OpenStack Wallaby (LP: #1948912).
-- Chris MacNaughton Wed, 27 Oct 2021
10:16:25 +
** Changed in: nova (Ubuntu Hirsute)
The verification of the Stable Release Update for glance 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
With my SRU hat on: it's always a bit of a tricky situation whether we
accept a completely new upstream version backport for a stable LTS
series. In case of mdadm it's especially tricky, considering that 4.1
has been tagged (released) 3 years ago, meaning 4.2 has 3+ years of
changes bundled up.
This bug was fixed in the package glance - 2:22.1.0-0ubuntu1
---
glance (2:22.1.0-0ubuntu1) hirsute; urgency=medium
[ Corey Bryant ]
* d/gbp.conf: Create stable/wallaby branch.
[ Chris MacNaughton ]
* New stable point release for OpenStack Wallaby (LP: #1948912).
-- Chris
I have upgraded to 20.04.3 from Bionic Beaver. I kind of screwed up the
install. I forgot something about my computer. I installed an extra hard
drive inside of the case. I unplugged my external drives but forgot about
the extra one inside. If I had remembered I would have unpluged it it to.
Thank
Hello,
I have given up on the Nvidia-driver, moving on the Kubuntu 21.10 and
consequently Nouveau...
Thanks again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872950
Title:
Nvidia 340.108 fails
So snapd doesn't support running inside privileged containers, so any
setup requiring snapd to do things in privileged containers is an
unsupported setup.
We have historically supported nesting however recently numerous things
changed there, 1) there was a lxd regression which broke nested
I ran autopkgtest using squid.internal and the test failed with these
errors:
=== short test summary info
FAILED tests/test_content.py::TestContentFromStream::test_content_bad_endpoint
FAILED
** Also affects: vdpau-video (Ubuntu)
Importance: Undecided
Status: New
** Tags added: hirsute 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/1890815
Title:
vainfo requires a
Here is the new log for the updated issue:
JS ERROR: TypeError: firstButton.icon is undefined
_adjustIconSize@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:630:38
_redisplay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:882:14
^^^
I can confirm that after a update to Ubuntu 21.10 the buggy behavior is back
again :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880570
Title:
Dock - running applications are not/delayed
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
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
** Changed in: linux (Ubuntu Bionic)
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/1928679
Title:
Support importing mokx keys into revocation list from the mok
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
** Changed in: linux (Ubuntu Bionic)
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/1932029
Title:
Support builtin revoked certificates
To manage notifications
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
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
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
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
I was waiting for a review / acknowledge from the upstream maintainer,
before applying this fix and unfortunately I didn't receive that in time
to push this fix in 5.13.0-22.
But now I got the ok from the maintainer, so I just sent the SRU fix to
the ubuntu kernel team mailing list:
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
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
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
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
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
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
** 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).
+
+
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
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
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
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
** 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
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
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
> 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.
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
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"
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
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
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-
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
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.
*** 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.
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:
***
** 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
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
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
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.
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
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.
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
|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
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
> 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
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
** 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
** 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.
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
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.
** 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
** 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.
** 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
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.
** 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.
** 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:
** 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
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
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]
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
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
** 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:
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
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
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
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
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
201 - 300 of 427 matches
Mail list logo
