Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (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.
@Daniel could you try out the bluez package from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ?
Should be as simple as doing:
sudo add-apt-repository ppa:waveform/pi-bluetooth
sudo apt update
sudo apt upgrade
The version in that PPA contains
I'm not an expert at all but I noticed these lines in my logs:
When sound works:
Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
[...]
Pin-ctls: 0xc0: OUT HP
When it doesn't work:
Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
[...]
Pin-ctls: 0x00:
OP has the first form.
When upgrading a system with this file altered, it is important to keep
it unchanged or the system will not resolve DNS on reboot.
No need to ask. Just don't overwrite the file if it has been changed.
Because if it has been changed, there is a reason, and pushing the
package's default config is
** Changed in: systemd
Status: Unknown => Fix Released
--
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/1903300
Title:
systemd-networkd silently fails to set vxlan
OK, I'm attaching the logs since I could reproduce the bug again.
When upgrading from alsa-utils 1.2.2-1ubuntu1 to alsa-utils
1.2.2-1ubuntu2 with speakers plugged in the 3.5mm jack, I could clearly
hear a "thump" sound when the 3.5mm jack stopped working. Neither a
reboot or a cold boot solved
** Attachment added: "Using alsa-utils 1.2.2-1ubuntu1. Sound works on all
outputs."
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+attachment/5432035/+files/pa-info_01_alsa-utils-ubuntu1.txt
--
You received this bug notification because you are a member of Ubuntu
Touch
weisswilly1985 THANK YOU - your workaround is a lifesaver on my rpi4,
Raspberry Pi OS (stock kernel).
Here's my tested script to get it installed locally:
# add a workaround script to rememdy eth0 losing it's IP lease randomly
wget
*** This bug is a duplicate of bug 1890394 ***
https://bugs.launchpad.net/bugs/1890394
Sounds right, thanks! I was morally certain it would have been reported
previously, but I couldn't find it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
when you say "tries to replace" do you mean this:
Configuration file '/etc/systemd/resolved.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the
*** This bug is a duplicate of bug 1890394 ***
https://bugs.launchpad.net/bugs/1890394
pretty sure this is a dup of bug 1902871 (which is itself a dup of older
bug 1890394), but if you disagree feel free to un-dup.
** This bug has been marked a duplicate of bug 1890394
Lightdm-gtk-greeter
> systemd-udev-trigger service didn't correctly run at the proper time
to generate uevents for existing devices
note: as systemd-networkd did correctly associate the .network file at
first, my guess would be during boot the .network file was different
than it is when boot is finished, which is
This problem is somehow created only on the first boot, most likely by
some magic being performed by cloud-init. If the created instance is
rebooted, there is no problem and systemd-networkd can be restarted with
no problems.
Marking this as invalid for system as this isn't a systemd issue, this
This isn't a problem with 3.2 to 3.3 upgrade, this is a problem where on
first boot of the azure instance any restart of networkd fails to
associate the .network file with the interface, e.g.:
root@lp1902960-3:~# networkctl status eth0
● 2: eth0
** Bug watch added: github.com/systemd/systemd/issues #15391
https://github.com/systemd/systemd/issues/15391
** Also affects: systemd via
https://github.com/systemd/systemd/issues/15391
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Tags added: fr-901
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
New
Bug
*** This bug is a duplicate of bug 1902960 ***
https://bugs.launchpad.net/bugs/1902960
I'm pretty sure this is a dup of bug 1902960; feel free to un-dup if
there is reason to think i'm wrong.
** This bug has been marked a duplicate of bug 1902960
Upgrade from 245.4-4ubuntu3.3 to
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1897965
Title:
pulseaudio: Failed to load
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: procps (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
@Hui Wang
I installed everything and it seems work now properly as well on my T14.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1901157
Title:
Thank you for the bug report!
Olivier, assigning to you since you usually do the librsvg updates,
would be great if you could SRU this one
** Changed in: librsvg (Ubuntu)
Importance: Undecided => High
** Changed in: librsvg (Ubuntu)
Status: New => Confirmed
** Changed in: librsvg
The attachment "groovy 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
"patch" tag, and if
Attaching debdiff for groovy. Same changes should work for focal
built via pbuilder-dist and tested
root@659bc6500a59:/# dpkg -i
/home/vfazio/pbuilder/groovy_result/procps_3.3.16-5ubuntu3_amd64.deb
(Reading database ... 4259 files and directories currently installed.)
Preparing to unpack
Public bug reported:
Crash installing gnome-boxes on the terminal.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
Public bug reported:
The patches used to ignore errors in containers no longer work as of
3.3.16 due to upstream commit https://gitlab.com/procps-
ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932
The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not
WriteSetting
Current status of this bug:
The gnome-terminal fix for groovy has been pushed to the VCS repo. I'm
waiting for a sponsor to upload it.
As regards hirsute: We have identified three upstream pango commits
which together with the gtk fix in hirsute-proposed fix the issue the
'right' way. The pango
Here's the full strace for the /bin/cat test case.
** Attachment added: "gdb-bin-cat.trace"
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+attachment/5431989/+files/gdb-bin-cat.trace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Oh and using either of '/tmp/dbgsym' or /tmp/dbgsym/usr/lib/debug' for
the debug-file-directory works.
--
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/1818918
Title:
gdb
I've come up with a simpler test case on an Ubuntu 20.10 system which
follows:
1) Execute 'gdb --args cat'
2) in gdb type 'run'
3) press Ctrl-Z
4) in gdb type 'generate-core-file /tmp/cat.core'
5) download the dbgsym for coreutils
6) Extract them 'dbg-deb -x
** Changed in: apport (Ubuntu)
Importance: High => Low
--
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/1787480
Title:
bugpattern checking not working for a ubiquity bug
** Description changed:
[Impact]
When you want to select a monospace font in gnome-terminal's profile
editor, it does not always show the regular font but rather an
- arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
- upstream commit which fixes it.
+ arbitrarily
Public bug reported:
* Impact
That's the current GNOME stable update, which fixes a number of issues,
including a regression[1] since librsvg 2.40.x which was shipped in
Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between
Ubuntu 20.04's current librsvg 2.48.7 (that version was
Well hirsute does not exist in that ppa. This is not a bug in Ubuntu
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
While generating the logs I found out that maybe it's not alsa-utils
version.
It could also be a combination of the following:
- Booting up with earphones plugged in makes the sound come out from the
internal speakers (and not the earphones).
- Changing the sound output device in the settings
Public bug reported:
when I try the sudo apt-get update command to fix apps not showing in
the gnome-software center it produces the following error
E: The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu
hirsute Release' does not have a Release file.
** Affects: apt (Ubuntu)
The attachment "lp1903048.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
"patch" tag, and if
@henry-sprog yup, that looks like the same
Attached a patch to fix this in hirsute; once landed will SRU this to
groovy and earlier.
** Patch added: "lp1903048.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5431962/+files/lp1903048.debdiff
--
You received
Is this the same as: #1903286?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
Dziękuję za zainteresowanie. Aktualnie mój HP 8760 nie działa, więc
jak dla mnie problem z Ubuntu 20.04 stał się nieistotny.
Jeszcze raz dziękuję i pozdrawiam ekipę Ubuntu.
Tomek P.
2020-11-06 12:18 GMT+01:00, archi02 <1835...@bugs.launchpad.net>:
> Same issue here and no workaround works :
Public bug reported:
Fixed upstream, please include [1].
Thank you.
[1] https://github.com/systemd/systemd/pull/15397
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.3
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
The version of gtk+3.0 in the proposed pocket of Groovy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you
The version of gtk+3.0 in the proposed pocket of Groovy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you
The testing package of libasound2 built by @hui.wang has resolved the
issue for me as well. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1901922
Title:
I can confirm all of the above. Also looking at the Pi OS the in which
the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the
soft block has no effect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1902407
Title:
package python3-pexpect 4.2.1-1 failed to install/upgrade:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Same issue here and no workaround works : neither switching from lz4 to
gzip nor keeping lz4 and only update initramfs. I also tried to launch
with another kernel, without success.
The computer is now blocked (Xubuntu 20.04, fresh install). I really
don't want to reinstall 18.04.
What can I do ?
@Hui Wang
I installed your package and rebooted. It seems to fix the issue, audio
is working as expected again.
One thing I noticed is that when I mute the speakers or microphone via
their media keys (F1 and F4) the LEDs on the keys don't light up. It may
not be related to this issue though
The issue seems so far resolved by the testing package. After two full
power cycles (power off, disconnect power, power on, reconnect power)
the audio still works!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
Public bug reported:
Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10
desktop,to save using a USB port. The mouse does not get recognised,
double clicking either Bluetooth Adaptors or Bluetooth Manager has no
effect. Full update run this morning.
ProblemType: Bug
I already tested the testing package with 20.04, it worked.
And this is the testing package for 20.10, I don't know if this could fix the
issue for 20.10 or maybe 20.10 needs more patches.
I built a testing package of libasound2 for 20.10, please install and
test it:
sudo add-apt-repository
I built a testing package of libasound2 for 20.10, please install and
test it:
sudo add-apt-repository ppa:hui.wang/pa-testing
sudo apt install libasound2
This will install the alsa-lib 1.2.3.2-1ubuntu3+testamd
reboot.
--
You received this bug notification because you are a member of
This is to confirm that the package in 'proposed' works. I installed
tracker 2.3.6-0-ubuntu1 from 'focal-proposed' and when running 'tracker
search something' I get actual search results (and no more Glib
warnings).
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Changed in: netplan
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Łukasz Zemczak (sil2100)
--
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/1664844
Title:
No
@Hui Wang
I get this
$ sudo add-apt-repository ppa:hui.wang/pa-testing
$ sudo apt install libasound2
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have
I looked into the apt history and I actually updated the following sound
related updates (these are the old version numbers that seemed to work)
- libasound2:amd64=1.2.2-2.1ubuntu2
- libasound2:i386=1.2.2-2.1ubuntu2
- libasound2-data:all=1.2.2-2.1ubuntu2
- alsa-utils:amd64=1.2.2-1ubuntu1
I could
** Changed in: apt (Ubuntu Focal)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1872200
Title:
apt does not accept globs and regexes in
The version of apt in the proposed pocket of Focal that was purported to
fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Touch
The version of apt in the proposed pocket of Focal that was purported to
fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Touch
The version of apt in the proposed pocket of Focal that was purported to
fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: apt (Ubuntu Focal)
Status: Fix Committed => Won't Fix
--
You
I have verified the fixed package, see attached terminal output.
Steps taken:
- check package version
- verify nf_tables is used
- check default chains have not been created yet
- run test case
- check if default chain has been created
After that I upgraded the iptables packages on my neutron
@Thore,
Please try this libasound2 (ubuntu 20.04):
sudo add-apt-repository ppa:hui.wang/pa-testing
sudo apt install libasound2
This will install the testing kernel 1.2.2-2.1ubuntu2.1+testamd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
@Thore,
Please try this libasound2 (ubuntu 20.04):
sudo add-apt-repository ppa:hui.wang/pa-testing
sudo apt install libasound2
This will install the testing version 1.2.2-2.1ubuntu2.1+testamd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The fix (upgrading to HWE) doesn't change the Mesa lib version, so while
it could be caused by a newer Mesa interacting badly with the older
kernel or xorg, I feel like it seems more like to be kernel or xorg.
18.04 is LTS, and this is somewhat of a trap for those doing CI testing
of desktop
@Marcus,
could you please upload the log of pa-info (pa-info > pa-info.txt) both
with alsa-utils 1.2.2-1ubuntu1 and ubuntu2?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1903271
Title:
package perl 5.30.0-9ubuntu0.2 failed to install/upgrade: package is
in
> I suspect libasound2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1)
beeing responsible, since this is the only sound related update that I
installed today.
Could you try to install back the old version (the deb files are on
https://launchpad.net/ubuntu/+source/alsa-
@Gunnar, if you want to go with a revert it shouldn't need to block on
hirsute since we aren't going to go that way in the new serie but rather
cherrypick the new pango fix (we could do that now in Debian and sync
over, let know if you need help with an upload)
--
You received this bug
Public bug reported:
reports of dependancies not installed
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: perl 5.30.0-9ubuntu0.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
If that that would be a regression from bug #1899745
Hui could you investigate if that's correct?
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
@Marcu, do you mean if you go back to 1.2.2-1ubuntu1 the issue resolves
itself?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1901926
Title:
[HDA-Intel - HDA Intel
Sorry for doubler post, I forgot to add attachment.
** Attachment added: "/dev after command"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901922/+attachment/5431794/+files/tree.after.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
*** This bug is a duplicate of bug 1415128 ***
https://bugs.launchpad.net/bugs/1415128
** This bug has been marked a duplicate of bug 1415128
Update-manager not launching
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Another thing that brings the soundcard correctly up is running the
following sequence of commands:
udevadm control --reload-rules && udevadm trigger
I took a snapshot of the /dev tree before and after the command. There
are no significant differences.
** Attachment added: "/dev before
Fixed by https://launchpad.net/ubuntu/+source/python-apt/2.1.3ubuntu3
migrating after some work on dependencies.
Note cloud and lxd images do not yet contain this, so you'll need to
update before add-apt-repository or wait another day or two.
Thanks everyone.
** Changed in: python-apt (Ubuntu)
77 matches
Mail list logo
