All autopkgtests for the newly accepted alsa-lib (1.2.3.2-1ubuntu3.1) for
groovy have finished running.
The following regressions have been reported in tests triggered by the package:
openjdk-8/8u275-b01-0ubuntu1~20.10 (armhf)
Please visit the excuses page listed below and investigate the
All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2.2) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
openjdk-8/8u275-b01-0ubuntu1~20.04 (armhf)
Please visit the excuses page listed below and investigate the
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1901922
Title:
[SRU][Lenovo ThinkPad
Oh, as mentioned elsewhere, the microphone light on the keyboard doesn't
seem to turn off/on as expected, but this may be an issue elsewhere
(FWIW it works as expected under a current Fedora install on this
system)
--
You received this bug notification because you are a member of Ubuntu
Touch
Did a fresh install of Groovy on an affected machine and updated it to
the latest release packages first, and confirmed the audio issue still
existed.
I then installed the packages above and rebooted, and audio seems to be
working as expected on that system now.
I think that did the trick!
--
bugzilla.gnome.org is being shut down in favor of a GitLab instance.
We are closing all old bug reports and feature requests in GNOME Bugzilla which
have not seen updates for a long time.
If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported
** Changed in: network-manager
Status: Confirmed => Expired
--
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/942856
Title:
NetworkManager does not support
[Expired for base-files (Ubuntu) because there has been no activity for
60 days.]
** Changed in: base-files (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
So the issue is: if there is a .gnu_debugaltlink GDB will try to load
that file and throw an error if it can't. That path is absolute and GDB
does _not_ look for that path/file anywhere else, not even inside
'debug-file-directory'.
GDB seems to only look at section .gnu_debugaltlink in
g-s-d p11-kit backend ready at https://gitlab.gnome.org/GNOME/gnome-
settings-daemon/-/merge_requests/208
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Medium
** Changed in:
On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it
I was able to reproduce what Brian is reporting here.
If the -dbgsym for the package is installed, gdb works and reports that it is
reading from the /tmp/dbgsym path. When -dbgsym package is not installed then
it fails with the
'could not find '.gnu_debugaltlink' file for ...' message
--
You
This is still an issue with hirsute afaict.
(hirsute-amd64)root@impulse:/tmp# gdb --ex 'set debug-file-directory
/tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'cor
e-file /tmp/cat.core'
GNU gdb (Ubuntu 10.1-0ubuntu1) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
I tried the testcase from comment #12 in Focal and Hirsute and it worked
just fine:
$ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
Type "apropos word" to search for commands related to "word".
Reading symbols
Ah, thanks for pointing that out but there is still an issue with the
test case in comment #12 as the .gnu_debugaltlink file is still not
loaded.
Reading symbols from /bin/cat...
Reading symbols from
/tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug...
could not
Public bug reported:
iputils-ping:
Installato: 3:20190709-3
Candidato: 3:20190709-3
Tabella versione:
*** 3:20190709-3 500
500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
lsb_release -rd:
Description:Ubuntu 20.04.1 LTS
additional behaviour I've noticed:
on first boot, when the sound device isn't in use for a while, it stops
sending bitstream data to the receiver, until there's a new audio event.
it seems to be some sort of device sleep mode.
on 20.04, after resuming from sleep, this device sleep mode wouldn't
I face a similar issue that I posted on ubuntu forum:
https://ubuntuforums.org/showthread.php?t=2452881
PPA solves my issue and interestingly changes the Bluetooth controller
address
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1904230
Title:
System freeze after logging onto desktop session
Status in xorg
You have been subscribed to a public bug:
After performing a recent update, I am encountering a complete system
freeze shortly after logging on to a graphical session but only for a
single user (which may suggest a corrupted configuration file
somewhere). This is repeatable - happens every time I
Hello Johan, or anyone else affected,
Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
For what it's worth, I created a Focal lxd container, followed the
instructions listed in the description, but could not reproduce the
issue. I was able to successfully build wireshark without problems
here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Johan, or anyone else affected,
Accepted alsa-ucm-conf into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu5.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Johan, or anyone else affected,
Accepted alsa-lib into groovy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.2.3.2-1ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
> 7) Execute "gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
--ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug'"
Try setting the debug-file-directory first, it should work.
gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex
Hello Johan, or anyone else affected,
Accepted alsa-lib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.2.2-2.1ubuntu2.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent
Yes, but that's really something for dpkg upstream to look at, and not
something we should patch out downstream.
** No longer affects: apt (Ubuntu)
** Changed in: dpkg (Ubuntu)
Importance: Undecided => Low
** Changed in: dpkg (Ubuntu)
Status: New => Triaged
--
You received this bug
@tmolloy, thank you for circling back around. I'm glad the patches worked for
you :-)
Note that there are other (unrelated) packages in @waveform's PPA that may get
installed with an apt upgrade. I don't know what the state of those packages
are. I disabled the PPA after installing bluez, just
This doesn't seem to be related to the previous bugs.
I tried to reproduce this on 18.04.4 (I don't have 20.04) and a fresh
build of GDB master, and I couldn't.
(gdb) disass _start
Dump of assembler code for function _start:
0x00010074 <+0>: mov r7, #4
0x00010078 <+4>: mov
You're right btw that it's a dpkg bug, but it's a bit more subtle. The
cleanup that dpkg performs after installation is meant to preserve the
hold state for non-installed packages. This is handled by the
pkg_is_informative function, which classifies everything with "pkg->want
!= PKG_WANT_UNKNOWN"
Public bug reported:
After installing current 20.04 release on ThinkBook 13s IML with Intel
audio card built-in microphone is not working - I'm unable to record
anything.
I could confirm that it was working in Windows 10 (previously installed
on that laptop), and when I'm using headphones their
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: iptables (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
Reported upstream here:
https://bugzilla.netfilter.org/show_bug.cgi?id=1481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1904192
Title:
ebtables can not rename just
I recharged the mouse, but:
$ solaar show
Unifying Receiver
Device path : /dev/hidraw0
USB id : 046d:c52b
Serial : 23FF9429
Firmware : 12.10.B0032
Bootloader : 02.15
Other : AA.AA
Has 3 paired device(s) out of a maximum of 6.
Notifications: wireless
** Bug watch added: bugzilla.netfilter.org/ #1481
http://bugzilla.netfilter.org/show_bug.cgi?id=1481
** Also affects: iptables via
http://bugzilla.netfilter.org/show_bug.cgi?id=1481
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Unsubscribing sponsors for now, Alex are you still working on that?
Please subscribe the team back if you get something ready for upload
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
There is no intend here to block any fix for stable serie but in case
that was not clear enough or if the SRU team didn't feel comfortable
with hirsute lacking behind and I uploaded back the patches but I'm
tagging the bug as 'block-proposed' instead which should be enough
incensitive to sort out
Whether it's a bug in apt or in something used by apt doesn't really
make a difference from an end user perspective. Can this bug be reopened
as a dpkg bug, then, or should I report that as a new bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
This is not a bug in apt. dpkg cleans up its database and removes hold
states for non-installed packages following an operation.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
When a package is not installed and apt dist-upgrade offers to install
it, if this is not desired, it is possible to hold the package using
multiple tools, which puts it in a state documented in dpkg.1 as:
hold
A package marked to be on hold is kept on the
Hi,
Debian maintainer here. I'll take care of the issue during the weekend.
Thanks,
Gregor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1903966
Title:
Loading
Public bug reported:
Hi,
I have an issue with ebtables that affects libvirt.
While initially found in hirsute I had to realize this is broken in
Groovy and even Bionic (might be a different reason back then) as well right
now.
But working in Focal (witch matches my memory of it being good before
Just to close the loop, I've just made fresh SD and USB boot disks from
the latest current Mate 20.10 image and both don't have working
Bluetooth, Ive updated both with the ppa and now both do work and I can
use mouse and headphones with no problems. I have no idea why my
original USB boot of Mate
The solution is to provide a dedicated pam configuration for chpasswd
without the ask_oldauthtok option.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1904166
Title:
To reproduce:
apt install libpam-passwdqc
sed -i -e 's/\(pam_passwdqc.so\)/\1 ask_oldauthtok/'
/etc/pam.d/common-password
echo 'root:hearth=mirth-Double' | chpasswd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Closing since it's fixed in the current version, a bionic SRU has been
uploaded now so that serie is going to be added as a target to the bug
when it gets reviewed and accepted
** Changed in: wpa (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because
It may be due to the libpam-passwdqc configuration using ask_oldauthtok
and similar=deny.
It was working fine on Bionic but fails with Focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
@Matthieu, @Dave, thanks for the comments and details.
I'm not blocking work to land, the 20.10 SRU could be accepted now and I didn't
revert in that serie.
The SRU team tries to ensure the fix is in the new serie so it doesn't get
forgotten/regress when next version is out but I think it's
Public bug reported:
Hello.
We are unable to change user password using chpasswd with libpam-
passwdqc, it seems to miss detect old password:
root@server:~# echo 'root:hearth=mirth-Double' | chpasswd
[…]
Weak password: is the same as the old one.
Try again.
root@server:~#
** Changed in: v4l-utils (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1823650
Title:
v4l-utils ftbfs in cosmic
Status in
Thank you for your bug report, the package is coming directly from
Debian, could you report the issue to them on
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=v4l-
utils ?
** Changed in: v4l-utils (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification
52 matches
Mail list logo
