Hi Timo,
When we can expect that to be part of 'focal-updates' ?
--
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/1956915
Title:
New bugfix release 21.2.6
Status in mesa
Getting the same issue using Qualcomm Atheros modem on WPA university
WLAN network. Confirmed that same settings and hardware work fine with
Ubuntu 21.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** No longer affects: systemd (Ubuntu)
** No longer affects: ubuntu-meta (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
All autopkgtests for the newly accepted rsync (3.1.3-8ubuntu0.2) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
dgit/9.10 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as
** Changed in: gdm3 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1960226
Title:
Ubuntu Jammy Desktop fails to boot after
Thanks for the bug report. Please run these commands:
lspci -k > lspci.txt
lsusb > lsusb.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Summary changed:
- Bluetooth headset not detected by bluetoth
+ Sony WF-XB700 Bluetooth headset not detected
** Also
I was thinking gdm3 needed some investigation but this update was
published an hour ago:
https://launchpad.net/ubuntu/+source/gdm3/41.3-1ubuntu2
Fingers crossed.
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
Thanks for the bug report.
It seems unlikely the flicker is caused by the new CPU. To prove that
you could maybe reinstall the old one?
I think more likely this is a connection problem with the analog VGA
cable. Try unplugging and replugging both ends of the VGA cable. And if
you can then please
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1960460
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Fresh install using 20220202 Daily ISO with ZFS + Encryption selected
from the installer
The system ends up in busybox after entering the unlock key.
Here is a part of the logs captured from the screen, the complete log
can be found as an attachement:
find: /dev/zvol/: No
I fixed gspell and am uploading it now.
If you see this issue, you can add NO_AT_BRIDGE=1 to a dh_auto_test
override
https://salsa.debian.org/gnome-team/gspell/-/commit/9951fca4b
** Changed in: at-spi2-core (Ubuntu)
Status: New => Fix Released
** Tags added: ftbfs jammy
--
You
All autopkgtests for the newly accepted rsync (3.1.2-2.1ubuntu1.3) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el)
s3ql/2.26+dfsg-4 (armhf)
Please visit the excuses page listed below and
Public bug reported:
With this patch applied gspell is FTBFS with the following errors:
Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus:
Failed to connect to socket debian/home/.cache/at-spi/bus: No such file
or directory
I removed the patch and rebuilt this package in a
** Changed in: binutils
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only
Fixed mainline and 2.38 branch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
Status in
(We technically had the same issue with the previous upload as 4.0.6 was
higher than what hirsute shipped at the time, though in that case the
EOL for hirsute was just a month or so away making the case for skipping
that SRU even stronger :))
--
You received this bug notification because you are
In general, it's indeed a problem for such cases, though there are a few
mitigating factors here:
- This would only be a problem for those who upgrade from focal to
impish. My understanding is that there is no direct upgrade path to
achieve this, you'd need to go throughgroovy and hirsute, both
Sorry about the delay in replying to this bug.
>From the bug description, it seems to me that this issue happened while
using Ubuntu Xenial (16.04); is that correct? I know it has been a
while, but can you still reproduce the issue? If yes, are you able to
describe the steps necessary to
Hello David, or anyone else affected,
Accepted rsync into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsync/3.1.2-2.1ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello David, or anyone else affected,
Accepted rsync into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/rsync/3.1.3-8ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
this bug is "fix committed" for both focal and impish, meaning the
update is in the respective -proposed pocket.
see comment #5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/rsync/+git/rsync/+merge/415253
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
** Package changed: libxcb (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1960372
Title:
DPMS ignores attempts to DISABLE IT
Status in Ubuntu:
New
Public bug reported:
Fresh install; NM is greyed out upon resume from suspend. Everything
works, but NM is not accessible.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.3
Uname: Linux 5.15.15-76051515-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Public bug reported:
Not sure - submitting crash record
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion:
Yes, but this bug is about focal (+ impish), and I'm missing 21.2.x (or
21.3.x) on focal updates.
--
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/1956915
Title:
New bugfix
Upstream 3.2.0 includes the identified upstream fix and Jammy has
3.2.3-8ubuntu2 so this is Fix Released for the development release.
Impish is also > 3.2.0 so only Focal and older are affected.
** Changed in: rsync (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug
Is there a risk here that on other desktop environments on Ubuntu, there
will be a duplicate event that will not be debounced, and therefore
regress users? I'm not sure if this is what you're already stating in
"Where problems could occur". If this is a risk, then could you include
it in your Test
Thank you for the detailed SRU information! You anticipated most of the
obvious questions and saved us a bunch of round trips.
> Should someone do an upgrade to impish, we've confirmed that the
upgrade is resolvable and that they'll just be left with a more recent
version of LXC than that in the
Public bug reported:
hello
Ihave issue with xorgs after i change my processor from i5 to i7 , my desktop
spec is Hp elite 8200 , please help . regards
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
** Tags added: fr-2035
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1960404
Title:
merge python-debian 0.1.43 from Debian sid
Status in python-debian package in
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1960404
Title:
merge python-debian 0.1.43 from Debian sid
Status in python-debian package in
Attached is a patch against the latest Debian version. The delta has
also been pushed here : https://salsa.debian.org/schopin/python-
debian/-/commits/external-zstd
and will be posted in a MR if athos doesn't pick it up in his own at
https://salsa.debian.org/python-debian-team/python-
Just faced this bug on 20.04.3 with service apache2 restart.
As noted earlier 'systemctl daemon-reload' did fix it, but this workaround is
rather not an obvious solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Please merge the latest Debian version of this package.
** Affects: python-debian (Ubuntu)
Importance: Wishlist
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in
2022-02-09 Fails
Ran 2 tests -
http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244128/testcases/1300/results
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1960226
Seems the problem is not ubiquity. Downgrading to 22.04.4 before
installing made no improvement.
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
the jammy queue has had 21.3.x for weeks now
--
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/1956915
Title:
New bugfix release 21.2.6
Status in mesa package in Ubuntu:
Fix
41 matches
Mail list logo
