We haven't had any bug reports like this that weren't hardware-specific.
Maybe to avoid confusion here we should choose just one Bluetooth chip.
Either the USB dongle (Broadcom Corp. BCM20702A0) or the internal chip
(Intel AX210/AX211/AX411).
--
You received this bug notification because you are
For the USB dongle there are kernel messages:
[ 34.065571] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 34.065744] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21e8.hcd'
[ 34.065757] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21e8.hcd'
** Package changed: bluez (Ubuntu) => linux
I just installed the -proposed package and still no dice. Could someone
post (here or elsewhere) a instructions for getting this working from
scratch as of today?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
The attachment "8df79f60d616e183257ae1a2c2b48beaf29e5eec.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
Public bug reported:
While using debian-installer to install Ubuntu Focal, I get the
following error:
May 16 22:02:41 base-installer: Certificate verification failed:
The certificate is NOT trusted. The certificate chain uses expired
certificate. Could not handshake: Error in the
Just to add a voice to this: we see the same things migrating from 18.04
to 22.04 while controlling some embedded ARM/Debian devices running
dropbear. The key are indeed appearing in the wrong place as stated
above and the log in does not proceed as expected. We can work around
this for
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1973642
Title:
[REGRESSION] Unable to
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
[Expired for wpa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: wpa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
I believe this is caused by debootstrap - it only uses packages from the
release pocket (and this is frozen from the time Ubuntu 20.04 LTS was
originally released). This is a known issue
https://askubuntu.com/questions/744684/latest-security-updates-with-
debootstrap but I am not sure if there is
the missing firmware warning is not the reason, it's erroring because of
klibc-utils
** Package changed: linux-firmware (Ubuntu) => klibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
@eurbah hi, also for the service in question, can you attach the output
of `systemctl list-dependencies --after snap..service`
AFAICT, all services are to be started after snapd.apparmor.d, which in
turn is started after apparmor.service, which should ensure that
apparmor profiles are loaded
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Hi Etienne, can you be a bit more explicit about what is the issue that
you are seeing? What are the services which are not starting?
Also please attach the SVG file generated by "sudo systemd-analyze
plot", it might help us.
--
You received this bug notification because you are a member of
** Summary changed:
- Screen Blank: External screen is not turned off
+ [nvidia] Screen Blank: External screen is not turned off
** Tags added: nvidia nvidia-wayland wayland
** Tags added: hybrid multimonitor
--
You received this bug notification because you are a member of Ubuntu
Touch
You have been subscribed to a public bug:
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module
r8169
Errors were encountered while processing:
klibc-utils
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
The sound is not comming and when I try to turn up the volume,it is
saying 'dummy output' instead of volume.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
Uname: Linux
Does the same bug occur if you choose a Xorg session (or just non-
Wayland) on the login screen?
--
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/1973467
Title:
[nvidia]
*** This bug is a duplicate of bug 1972809 ***
https://bugs.launchpad.net/bugs/1972809
Thank you for your bug report, that's already reported as bug #1972809
which has a candidate fix available for testing
** This bug has been marked a duplicate of bug 1972809
Cant enable ua from GUI,
Public bug reported:
When using PathExistsGlob in a path unit, systemd starts the
corresponding service unit in an infinite loop. We have observed this
problem only under Jammy.
--
[Unit]
Description=Test
[Path]
PathExistsGlob=/home/www-data/test/*.so
Unit=test.service
[Install]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
After update to 4.15.0-177 I have a frequent issues with detecting my
Wi-Fi card on boot (Ubuntu 18.04, Lenovo P51), have to switch back to
4.15.0-176 for work.
description: Wireless interface
product: Wireless 8265 / 8275
vendor: Intel Corporation
physical id: 0
Thank you for your bug report. Could you edit
/lib/systemd/system/wpa_supplicant.service to add a '-d' to the
ExecStart cmd, restart, try to connect and share the 'journalctl -b 0'
log from the system?
It would also be worth trying if
https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 makes
Thank you for your bug report. The string was translated after the
current language packs were generated so is missing from the curent
version
https://translations.launchpad.net/ubuntu/jammy/+source/gnome-
session/+pots/gnome-session-42/fr/29/+translate
it should be fixed in the next langpacks
--- Comment From i...@de.ibm.com 2022-05-16 06:17 EDT---
With the new combination, bedtools testsuite is green and zlib passes all of my
tests too. So it looks good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: wpa (Ubuntu Jammy)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1962541
Title:
PEAP wifi can't connect (ubuntu
the update on https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1
which allows legacy renegociation by default might fix some of the
issues reported on this bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
Packages patched for CVE-2020-35522, CVE-2022-0561, CVE-2022-0562,
CVE-2022-0865 and CVE-2022-0891 are now released and available.
(https://ubuntu.com/security/notices/USN-5421-1).
Jammy is currently at version 4.3.0-6 which includes the patch for
CVE-2022-0865 as it was introduced in 4.3.0-5.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pcsc-lite (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
We're seeing this same issue. The postinst script in the 22.04 package
seems to be missing a few lines that were still there in 21.10, one of
which would be the one that executes systemctl enable pcscd.socket.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Lenovo Legion S7 15IMH5
Has anyone managed to get their sound working on it? Would appreciate a
tutorial or some tips (the more specific, the better, as this thread is
full of other devices as well and it'd take a long time to try
everything)
--
You received this bug notification because you
Looking at the model number, there's a chance it's compatible with the
verbs of the 15IMHG05, or another model from around that time.
Do you know how to build and run your own kernel?
Also, please provide a URL to your alsa-info.
On 5/15/2022 12:12 PM, bugzilla-dae...@kernel.org wrote:
>
Public bug reported:
Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
** Affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The package FTBFS against -proposed but builds successfully against the
-release pocket.
Based on the error, it seems related to recent changes in how apt
determines kernels that can be autoremoved.
apt (2.0.7) focal; urgency=medium
* Revert "Protect currently running kernel at run-time"
*
Thanks you for you bug report, does that cmd work for you?
$ xdg-open http://www.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1973470
Title:
Ubuntu-bug
Public bug reported:
Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as
an external usb dongle will not work. Bluetooth starts as off, and
cannot be turned on. If I use systemctl to turn it on, it is on but
doesn't find any devices through bluez. Blueman finds devices but
We haven't got new reports since the fix landed nor visible regression
so let's say the fix is working as intended.
** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish
--
You received this bug notification because you are a
This became a sync, after debian accepted my DEP8 tests.
https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thank you Seb, I had the issue reported in this bug in a WeWork today
(first time connecting since updating to Jammy) and the package in
-proposed resolved the issue for me as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Trying to validate this upload but unattended-upgrades failed to build
with:
Applying pinning: PkgFilePin(id=0, priority=-32768)
Applying pin -32768 to package_file: >/test/root.unused-deps/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages'
Sent new dep8 tests to debian, and then synced the package back into ubuntu:
https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
Please find attached the debdiff between debian package and the ubuntu
one.
** Patch added: "debdiff_debian_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590044/+files/debdiff_debian_ubuntu.debdiff
** Tags added: fr-2388
--
You received this
Please find attached the debdiff between old ubuntu version and the new
one.
** Patch added: "debdiff_oldubuntu_newubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590043/+files/debdiff_oldubuntu_newubuntu.debdiff
--
You received this bug
Public bug reported:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my
Thank you for your bug report, could you include the output of
$ ubuntu-drivers debug
?
** Changed in: software-properties (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Promotion from -proposed sure would be nice. I see verification has
been done but a update excuses shows an netplan.io regression[1]. I'm
not sure if the test is flaky but I see that seb retried it a few
times[2] last week and it failed consistently, so maybe not.
I'm just curious if there's
You have been subscribed to a public bug:
The desktop entry for Startup Applications is untranslated under Ubuntu
22.04 in my native french language.
** Affects: language-pack-gnome-fr (Ubuntu)
Importance: Low
Status: Fix Committed
** Tags: i18n jammy l10n
--
Startup
** Changed in: wpa (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1962541
Title:
PEAP wifi can't connect (ubuntu
All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.6) for bionic have
finished running.
The following regressions have been reported in tests triggered by the package:
docker.io/20.10.7-0ubuntu5~18.04.3 (i386, amd64, s390x, arm64, ppc64el)
sbd/1.3.1-2 (amd64)
On 5/16/22 09:42, Lena Voytek wrote:
> You noted that this may be due to update-manager having two instances
> running. Were you able to try again with one running to get it updated?
> If not, does updating with:
>
> sudo apt update
> sudo apt upgrade
>
> cause any errors?
Yes, errors persist:
Good news for Belgians who connect tot the government site with there id
card.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
pcscd 1.9.5-3 do not start
see also https://sourceware.org/bugzilla/show_bug.cgi?id=29045#c3 where
the gdb list recommends updating to a stable version of gdb
** Bug watch added: Sourceware.org Bugzilla #29045
https://sourceware.org/bugzilla/show_bug.cgi?id=29045
--
You received this bug notification because you are a
I attempted to reproduce by running the command through localhost over
ssh and it succeeded using a 3GB file. This may be due to the transfer
between Ubuntu and Debian then. Here is my test case:
# lxc launch images:ubuntu/jammy test-rsync
# lxc exec test-rsync bash
# apt update && apt
** Description changed:
When using PathExistsGlob in a path unit, systemd starts the
corresponding service unit in an infinite loop. We have observed this
problem only under Jammy.
--
[Unit]
Description=Test
[Path]
PathExistsGlob=/home/www-data/test/*.so
Hello Thomas,
Since the issue can't be reproduced in impish or jammy, is this an error
you found in Focal, or has this been fixed for you? If it's an error in
an earlier supported version then we can backport the fix to it.
Thanks!
--
You received this bug notification because you are a member
Thanks, but I am not sure if that can still be helpful for the
analysis, because in the meantime I got the nvidia drivers running
properly.
What finally got me there was these commands:
ubuntu-drivers devices
ubuntu-drivers autoinstall
apt install nvidia-dkms-510
update-initramfs -k all -u
and a
The attachment "debdiff_oldubuntu_newubuntu.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
This was a deliberate change in systemd [1] to address the kernel's
bind/unbind uevent issue [2]. In short, it is an intentional change in
udev's behavior, and unfortunately breaks the assumptions that your
custom udev rules rely on.
[1]
** Changed in: gudhi (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1968074
Title:
moc fails to parse include inside
Hi @Sebastien, no problem at all.
I will create a new bug report once I'm sure I've tried everything on my
side.
Have a lovely day.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
Hello Frank,
You noted that this may be due to update-manager having two instances
running. Were you able to try again with one running to get it updated?
If not, does updating with:
sudo apt update
sudo apt upgrade
cause any errors?
Thanks!
** Changed in: openssh (Ubuntu)
Status: New
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdb (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
Hello Sebastian,
Thank you for taking the time to make this bug report. The error you are
encountering shows up through openldap, so marking the bug under
openldap is fine. It may be due to multiple sources attempting to free a
request. Does this error show up every time you attempt to log in?
Hi Lena,
i found the Problem after some time:
I dont know why but Ubuntu 22.04 needs longer to take the LDAP Request.
This is also the answer, why ldap without HAPROXY is working.
Now i have set HAPROXY timeout to 5sec and it is working now. With
Ubuntu 20.04 (same configuration) ldap Login
In accordance with Debian Policy, the unversioned .so is available in
the liborc-0.4-dev package.
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#development-
files
** Changed in: orc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Public bug reported:
Fresh install of Xubuntu 22.04, currently with network-manager
1.36.4-2ubuntu1
Attempting to connect to an EAP-TLS network fails with:
NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation:
(wifi) connection 'AP' has security, and secrets exist. No new
here is the result of the journalctl
** Attachment added: "result of the journalctl command"
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+attachment/5590157/+files/journalctl.odt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I already tried to apply
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834
but this doesn't help.
I also tried
https://ubuntuforums.org/showthread.php?t=2474436
but doesn't help neither
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
for https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1
i'm a bit lost! What do I have to do with the 3 available files?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
70 matches
Mail list logo
