🤦 . you are totally right. using the private key just works fine.
** Changed in: openssh (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.
Public bug reported:
I upgraded recenty from Noble to Oracular and since then, I can no
longer add my ssh key to the ssh-agent with ssh-add. The error is:
$ ssh-add ~/.ssh/x.pub
Error loading key "/home/x/.ssh/.xpub": error in libcrypto
Adding other keys works fine.
ProblemType: Bug
DistroRe
Ok. Thanks for clarification. With that I think we can continue to get
https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-
rootfs-1/+merge/452352 merged.
But I still find this behavior confusing/buggy. I can still use
"debconf-show openssh-server" and see the password-authentication ent
looks like there's no db_input/db_go call in the openssh-server.config
file. Is that by intention?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-recon
Public bug reported:
openssh-server does provide a couple of configuration options:
[~]$ sudo debconf-get-selections |grep openssh-server
openssh-server openssh-server/listenstream-may-failerror
openssh-server openssh-server/password-authentication boolean true
openssh-server openssh-s
This is not a systemd or tomcat bug. As I explained in
https://bugs.launchpad.net/cloud-images/+bug/1988498 , a broken systemd package
got removed from the archive but the broken version got included into the
docker image.
We'll release a new docker image soon to fix the problem. Let's track tha
SRU verification for hirsute:
I did a testbuild with repo-stamp enabled against the livecd-rootfs version
from proposed (2.719.3). See
- https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/308173
-
https://launchpadlibrarian.net/567803112/buildlog_ubuntu_hirsute_amd64_amd64-tar
I did a testbuild with repo-stamp enabled against the livecd-rootfs version
from proposed (2.664.33). See
-
https://launchpadlibrarian.net/566970666/buildlog_ubuntu_focal_amd64_amd64-tarball_proposed_BUILDING.txt.gz
- https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/307101
Tha
Bionic is not affected
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => Invalid
--
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/1917920
Title:
magic-pro
** Changed in: livecd-rootfs (Ubuntu Hirsute)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
** Changed in: livecd-rootfs (Ubuntu Focal)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
** Changed in: livecd-rootfs (Ubuntu Bionic)
Assignee: (unassigned) => Thomas
** Description changed:
- [Why SRU?]
+ [Impact]
The fixes for this bug (including the fixes for LP:#1944906) need to be
backported to hirsute, focal and bionic) to be able to re-enable the
"repo-snapshot-stamp" feature for image builds. That feature is important to
get consistent image build
** Description changed:
+ [Why SRU?]
+ The fixes for this bug (including the fixes for LP:#1944906) need to be
backported to hirsute, focal and bionic) to be able to re-enable the
"repo-snapshot-stamp" feature for image builds. That feature is important to
get consistent image builds (means th
Public bug reported:
I updated network-manger on hirsute:
network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over
(1.30.0-1ubuntu2)
During the postinst run, I get:
Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ...
Failed to restart network-manager.service: Un
Public bug reported:
Currently running 21.04, apport version is 2.20.11-0ubuntu62 .
When I try to fill a bug, I see:
$ ubuntu-bug network-manager
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/repor
I also have this problem (with a LUKS & LVM). As a workaround, I did:
1) boot into live CD, start a terminal and do everything as root (sudo -i)
2) open the encrypted LUKS partition: cryptsetup luksOpen /dev/nvme0n1p3
nvme0n1p3_crypt
Note that the name (in my case "nvme0n1p3_crypt") must match t
15 matches
Mail list logo
