not working
** Attachment added: "software updater fails Peek 2021-06-08 09-27.gif"
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5503022/+files/software%20updater%20fails%20Peek%202021-06-08%2009-27.gif
--
You received this bug notification because you are
Is this a regression from an older release? We can fix it, but if it's
not a regression, I'd just skip it, as running apt-key is the wrong
approach anyway.
They should just pmrum cp some-repo-key.gpg /etc/apt/trusted.gpg.d.
optimally drop the keyring elsewhere and use signed-by in sources.list
sni
There is another fix in master that belongs to
https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 - I've bumped my
PPA build to include both as it is worth a try if this fixes the current
ppc64 issues in v3.66.
Build of 3.66-1ubuntu1~impishppa2 started, later on I'll let the
autopkgtests run.
*
I'm guessing this is related to bug 108, even if you only have one
keyboard. It sounds related.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: i18n
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xor
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => linux-hwe-5.8 (Ubuntu)
** Tags added: regression-update
--
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/1930976
Titl
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460
(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/1930903
Title:
Frequent kernel
** Summary changed:
- Ubuntu 20.04 doesn't work with moidern KVMs
+ Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: kvm
** Summary changed:
- Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Rec
I was able to verify that a merge of 3.66 would on Ubuntu trigger the
very same bug that Debian has blocking the dogtag-pki test on powerpc64.
=> https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-
ppa-service-4577/impish/ppc64el/d/dogtag-
pki/20210608_031158_a9d4a@/log.gz
--
You
Public bug reported:
apt-key fails when the POSIXLY_CORRECT environmental variable is set.
This is due to chmod acting differently with POSIXLY_CORRECT set: chmod tries
to use `--` as a parameter with this variable.
This prevents some third-party utilities, like pmrun, from using apt-
key.
---
Ideally, I'd wish it not to stop sshd when /boot/efi becomes
unavailable. Or at least bring back the services it stopped when the
emergency shell is canceled.
More practically, and more on topic to the original reason for this bug
report, I'd like it if stopping the emergency shell would print a
Thanks for reporting the issue!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1930917
Title:
Latest isc-dhcp-server rejects proper dhcpd.conf
Status in isc-dhcp package
Tested and confirmed that 4.4.1-2.2ubuntu6.2 corrects this. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1930917
Title:
Latest isc-dhcp-server rejects proper
So to summarize:
-your drive failed
-you ssh'ed into the machine and started a service that required the drive
-systemd put the system into emergency target
-you switched to the backup partition and systemd exited the emergency target
-the emergency shell is now inactive, but of course its output
I'm currently treating this as an upstream kernel regression reported
here
https://lore.kernel.org/regressions/20210607142245.eikvyeacqwwu6dn3@wittgenstein
We should wait whether a simple revert will be acceptable or whether
anything else is needed from LXC specifically.
--
You received this bu
** Description changed:
[Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html
(proprietary
This bug was fixed in the package isc-dhcp - 4.4.1-2.2ubuntu6.2
---
isc-dhcp (4.4.1-2.2ubuntu6.2) hirsute-security; urgency=medium
* Fix regression caused by rebuild with newer toolchain (LP: #1930917)
- debian/rules: build with -fno-strict-aliasing.
-- Marc Deslauriers Mon,
A little more information, after some investigation.
The issue affects xdm logins at the console, as well as remote ssh
logins. This also means that audio at the console fails to work, as ACLs
for the console's user are not added to the audio devices.
It seem that it can be solved by putting in /
debdiff to go over the ESM process by security team.
Thanks
- Eric
** Patch added: "xenial_lp1930286.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+attachment/5502934/+files/xenial_lp1930286.debdiff
--
You received this bug notification because you are a member of
While we wait for 3.67 and maybe (Thanks Timo) for [1] I have ensured that we
have a 3.66 test build.
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4577/+packages
The check of it's delta also showed that we can drop a bit of it nowadays.
=>
https://code.launchpad.net/~paelzer/ub
For what it's worth, I commented out the `mystatedir statedir ifindex
interface` line, and changed the three `return` lines to be `exit 0` and
now I no longer get the angry red FAILED line during boot, `systemctl
status networking.service` looks okay, and my internet continues to
function just fine
** Changed in: openssh (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
+ [Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
https://www.synop
FYI by tjaaltonen - there's another crasher in 3.66 on ppc64el..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
So 3.66 won't be the "take this and it works" solution.
** Bug watch added: Debian Bug tracker #989410
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
--
You re
UA customer test pkg outcome:
"
We ran the Defensics test suite before and after installing the test packages.
We could observe two core dumps before the test package installation.
But after test package installation, core dumps were not generated.
Can you provide this package as the fix?
"
This
I can confirm the update introduced a regression on Hirsute (and Impish
I presume). Focal and Groovy work properly. Unfortunately, it's not
related to the security patch, but it stems from the package being
rebuilt with the newer toolchain in Hirsute, so removing the patch won't
fix the issue.
I a
Public bug reported:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Con
workaround: sudo apt purge libtss2-esys0 libsrt1-gnutls manpages-de
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1539689
Title:
package lvm2 2.02.133-1ubuntu4 failed to ins
As I said I tried to recreate this, but it worked.
It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container.
Upgrading the host to impish it Impish/5.11.0-16-generic still works fine.
It seems it only fails in autopkgtest infrastructure, not sure why yet
:-/
--
You received
On Mon, Jun 07, 2021 at 05:14:50AM -, Andrea Righi wrote:
> Public bug reported:
>
> The lxc autotest is failing with the following error(s) on the latest
> kernel linux-unstable 5.13:
>
> FAIL: lxc-tests: lxc-test-apparmor (1s)
> ---
> failed - opened /sys/kernel/uevent_helper
> ---
> PASS:
Please disregard my last comment (#5). The problem I had was not this
one but related to using other connector agents in addition to
NetworkManager, in my case the openvpn3 command line.
(Automatic connection to the VPN is not there, but that is probably
safest.)
--
You received this bug notifi
Public bug reported:
Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
before now slipping into a bad mode.
Now it seems all tests failed in boot-and-services by hanging until killed by
VirtSubproc.Timeout of autokgtest.
The last [1] test log has a bit more, it shows a py
I was adding a few of the blocked packages as incomplete tasks to have
this bug update-excuse show up in excuses. Right now until we know
better I'd consider this a systemd issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Looking at the journal, I think the sequence of events is:
- SSD fails last Friday
- I log in today over ssh, start messing around
- I notice that collectd is not running (since Friday), try to `sudo systemctl
start collectd`
- systemd tries to bring up collectd's dependency local-fs.target, whic
Public bug reported:
An SSD that held my /boot/efi partition failed, took down local-fs.target,
which brought up emergency.target. I ended up with no ssh access, and a
message on the local console telling me
to press Enter to get a root shell, or press Ctrl-D to continue booting
normally. The
33 matches
Mail list logo
