This bug was fixed in the package openssh - 1:8.4p1-5ubuntu2
---
openssh (1:8.4p1-5ubuntu2) impish; urgency=medium
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
ensure parallel processes will not disrupt one another when halting
(LP: #1905285)
Hi Wayne! Thanks for commenting.
> It's only the 128-bit hash that depends on 0.8.0.
> The 0.7 version works fine with rsync, giving it
> the 64-bit and 32-bit hashes.
Yes. Except it seems that if you switch the libxxhash0 from 0.8 to 0.7,
you get different behaviour.
rsync doesn't check what
Please fix it asap.
We have the same issue. We have migrated our Nagios to Ubuntu 20.04. Now we
have flapping hosts, because of this issue!
Is there a timeline when you will able to fix it ?
Thanks
Silvan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Hui Wang,
Just ran these commands, still no sound out of the speakers on my side.
Best Regards,
Thibaut Soubrié
Le ven. 9 juil. 2021 à 09:25, Hui Wang <1918...@bugs.launchpad.net> a
écrit :
> Please test this command:
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x10
> sudo
Next possible culprit: binutils
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1934995
Title:
Broken on ppc64el (toolchain bug?)
Status in umockdev package in Ubuntu:
Upgraded to systemd 245.4-4ubuntu3.8 on ThinkPad P17, but this issue is
still exist.
--
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/1928200
Title:
Prompt error message
Public bug reported:
Fuse3 is a requirement for qemu 6 (LP: #1934510). Since we don't want
to support two versions of fuse in main, we'd like reverse-dependencies
of fuse to switch to fuse3.
e2fsprogs FTBFS in a test rebuild changing the build-dependency on
libfuse-dev to libfuse3-dev.
Excerpt
Hello Walter,
Thanks for filling the bug and helping in making the Ubuntu server
better.
However, if I get everything right, I think you're mistaken about how it
works and I am sorry but what you're trying to do is not correct! You
cannot just decide to take one of the package from another
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
Here is the file:
pa-info > pa-info.txt
On Fri, Jul 9, 2021 at 10:18 AM Rabi Sah wrote:
> Hi ,
>
> i do not see the anything after i run pa-info > pa-info.txt command. I did
> not understand what to do with your command.
>
> On Thu, Jul 8, 2021 at 11:50 PM Hui Wang <1935...@bugs.launchpad.net>
@ddstreet, unfortunately, even with 245.4-4ubuntu3.8 on Focal, the mtime
keeps changing as RAs are received :/
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The gdb-11-branch branch has been updated by Simon Marchi
:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=ff32938d4471ebf6dce462934de8ab47f9fd5d66
commit ff32938d4471ebf6dce462934de8ab47f9fd5d66
Author: Simon Marchi
Date: Thu Jul 8 10:05:16 2021 -0400
gdb: don't set
Fixed by that commit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1934505
Title:
gdb 11 doesn't work on impish/s390x: internal-error:
displaced_step_prepare_status
The master branch has been updated by Simon Marchi
:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=74b10a3219e44ba2585e3f7226a6455d41e92c1b
commit 74b10a3219e44ba2585e3f7226a6455d41e92c1b
Author: Simon Marchi
Date: Wed Jul 7 08:57:36 2021 -0400
gdb: don't set Linux-specific
Verification for Focal (245.4-4ubuntu3.8)
# Initial repro on focal:
root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf
/etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844292 1625844273
1625844273 0 4096
root@focal:~# ip
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
Verification for Groovy (246.6-1ubuntu1.5)
# Initial repro on groovy:
root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf
/etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844827 1625844823
1625844823 0 4096
root@groovy:~#
Sorry, the use cases you describe are not supported by Ubuntu.
You're welcome to hack your system as you wish, but that doesn't mean
that we will necessarily make changes in Ubuntu to accommodate that. We
do try to be helpful, of course. And in this case I agree that it is a
bug that rsync
python3.5 has stopped passing its testsuite due to expried test certs.
Thus upload of openssl has triggered regression in python3.5
I've cherrypicked updated test certs and keys, but to cherry-pick those
cleanly, I also had to cherrypick an earlier bug fix. All of these are
unmodified from 3.5.10
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
> that was the atime
yep, really no way around updating the atime, as systemd of course needs
to access the file to check if the content is the same or not
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
A user still might have written a script or a service which calls
/usr/lib/libmbim/mbim-proxy and by moving the binary we would end up
introducing a regression and that's a scenario we should consider.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I think the patch in comment #1 looks reasonable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1928989
Title:
expiring trust anchor compatibility issue
Status in
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
Thanks Robert, I saw that you uploaded to bionic and focal now, any
reason to not merge to impish? If technically the feature doesn't apply
to the current serie maybe we should just merge with a default setting
to false so we just need to turn the option on for the next LTS if
needed?
--
You
How about this case:
- I make a hypothetical package that depends on libxxhash < 0.8 because
I want the "broken/old" xxh128 support;
- I have libxxhash 0.7.3 (that came with Focal);
- I have rsync 3.1.x (that came with Focal);
- Now I release-upgrade my system from Focal to Groovy;
- I get
[machine]
HP ProBook
[OS]
Groovy
[systemd version]
246.6-1ubuntu1.5
[test result]
mic mute key works fine.
** 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
[machine]
HP ProBook
[OS]
Hirsute
[systemd version]
247.3-3ubuntu3.2
[test result]
mic mute key works fine.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
[machine]
HP ProBook
[OS]
Focal
[systemd version]
245.4-4ubuntu3.8
[test result]
mic mute key works fine.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of
I've found that other people with RX 5600 XT had problems with this
version of mesa.
https://bugs.archlinux.org/task/70554
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4691
There is a new release of mesa (21.0.3-2) that fixes the problem for
those users.
Hope that you upload it to
> Unfortunately the ppc maas seems down right now
product engineering has access to PPC systems in maas?!? sigh...that
sure would be nice for sustaining engineering to have access to also :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
= Verification =
Before:
14: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8:f1:ae:10 brd ff:ff:ff:ff:ff:ff
altname `�lժ�
altname ��lժ�
After:
15: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether
Sorry about the noise, I had a problem in my reproducing steps, the
previous comment should be ignored. I got confused by stat's output
changing but that was the atime, not the mtime that was changing.
** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal
--
You
PPA with these changes available from https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/4594
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1928989
Title:
ADT results at https://bileto.ubuntu.com/excuses/4594/xenial.html
** Description changed:
[Impact]
* openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.
[Test Plan]
* Import staging cert equivalent to ISRG Root
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
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.
Confirmed fixed on lxd02 and client site, running Focal. No reboot was
done.
Thank you.
--
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/1891215
Title:
systemd-resolved
What package / application were you reporting a bug about? IIRC most
apport hooks won't ask for dmesg information.
If you remove the crash files in /var/crash/ and lock your screen do you
get another jackd crash in there? It could be that the crash reporting
process for jackd actually is asking
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
Hi ,
i do not see the anything after i run pa-info > pa-info.txt command. I did
not understand what to do with your command.
On Thu, Jul 8, 2021 at 11:50 PM Hui Wang <1935...@bugs.launchpad.net>
wrote:
> Please plug the mic in, and run pa-info > pa-info.txt, then upload the
> pa-info.txt
>
> --
Please test this command:
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x10
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0e20
//please test if speaker works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
My Repro-tests indeed seem to indicate that really qemu 6.0 is the trigger for
this,
but as I said HW is rather unavailable at the moment. I was told that the MAAS
is serviced but should be back soon - so I'll have a look later when this one
is available again.
--
You received this bug
Hey there. Thanks for your time on this. I'll try to supply positive
confirmation over the weekend.
--
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/1853164
Title:
systemd:
I find Usage: clevis COMMAND [OPTIONS]
clevis decrypt Decrypts using the policy defined at encryption time
clevis decrypt tpm2plus Encrypts using a TPM2.0 chip binding policy
clevis encrypt sss Encrypts using a Shamir's Secret Sharing policy
clevis encrypt tang Encrypts
root@lp1894622-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.7 amd64system and service manager
root@lp1894622-f:~# man systemd-resolve
No manual entry for systemd-resolve
root@lp1894622-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.8 amd64
root@lp1894622-g:~# dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.4 amd64system and service manager
root@lp1894622-g:~# man systemd-resolve | head -1
No manual entry for systemd-resolve
root@lp1894622-g:~# dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.5
ubuntu@lp1928200-f:~$ cat /etc/binfmt.d/TestFormat.conf
:TestFormat:M::XX::/bin/true:F
ubuntu@lp1928200-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.6 amd64system and service manager
reboot to pick up change...
reboot again to show issue...
[ OK ] Reached
> Upgraded to systemd 245.4-4ubuntu3.8 on ThinkPad P17, but this issue
is still exist.
you may be seeing some other problem, you should open a new bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
root@lp1894622-h:~# dpkg -l systemd| grep systemd
ii systemd247.3-3ubuntu3.1 amd64system and service manager
root@lp1894622-h:~# man systemd-resolve | head -1
No manual entry for systemd-resolve
root@lp1894622-h:~# dpkg -l systemd| grep systemd
ii systemd247.3-3ubuntu3.2
root@lp1858210-g:~# dpkg -l systemd | grep systemd
ii systemd246.6-1ubuntu1.4 amd64system and service manager
root@lp1858210-g:~# timedatectl list-timezones | grep Eastern
root@lp1858210-g:~#
root@lp1858210-g:~# dpkg -l systemd | grep systemd
ii systemd246.6-1ubuntu1.5
root@lp1858210-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.7 amd64system and service manager
root@lp1858210-f:~# timedatectl list-timezones | grep Eastern
root@lp1858210-f:~#
root@lp1858210-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.8
root@lp1858210-h:~# dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.1 amd64system and service manager
root@lp1858210-h:~# timedatectl list-timezones | grep Eastern
root@lp1858210-h:~#
root@lp1858210-h:~# dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.2
I am sorry. I did not understand for the first time. I did understand on
second time but I was not sure if I turned on the microphone because I have
a hyper-x headphone which needs to bring it down to turn on the headphones
so I am attaching this file after I turn on the headphone.
I would like
This change disallows floating point and hexadecimal representations of
numbers as well as purely numeric, which should be a good compromise.
For example, 0x0 is now invalid, as well as 0x123456789 and 0.0, while
0x0x0x0x is considered valid. It also adds these new restrictions to the
man page.
The reason I mentioned jackd is the bug description shows a listing of
crashes in /var/crash and there is one from July 8th:
CrashReports:
644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08
04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
600:118:124:37:2021-07-08
Please try a boot parameter: snd_hda_intel.model=alc221-hp-mic
After booting with this parameter, when you plug a mic to the audio
jack, a popup dialogue will sho to let you select what audio device you
plugged.
Let us see if there is that pop-up dialogue first.
--
You received this bug
Also affected:
Ubuntu version: 21.04
Linux kernel: 5.11.0-22-generic x86_64
CPU model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
GPU: 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4)
Laptop model:
Please collect a log while the system is playing the sound via speaker:
check the speaker is the active output device
play the music via youtu or sth else
run 'sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef'
run 'alsa-info --no-upload' to get the alsa-info.txt.
upload
On Fri 9. Jul 2021 at 16:55, Brian Murray <1935...@bugs.launchpad.net>
wrote:
> What package / application were you reporting a bug about? IIRC most
> apport hooks won't ask for dmesg information.
>
Besides automatic crash reports which i haven’t seen happening for
quite some time,
I only used
Did you mean to run this command?
On Fri, Jul 9, 2021, 9:25 PM Hui Wang <1935...@bugs.launchpad.net>
wrote:
> Please try a boot parameter: snd_hda_intel.model=alc221-hp-mic
>
> After booting with this parameter, when you plug a mic to the audio
> jack, a popup dialogue will sho to let you select
A similar bug: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1935570
--
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/1935570
Title:
[HP Compaq Pro 6300
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
80 matches
Mail list logo
