Uploading to ssh-ubuntu (via sftp to upload.ubuntu.com):
Uploading base-files_13.6ubuntu2.dsc: 1.34 KB / 1.34 KB (100.00%) - done.
Uploading base-files_13.6ubuntu2.tar.xz: 94.16 KB / 94.16 KB (100.00%) - done.
Uploading base-files_13.6ubuntu2_source.buildinfo: 6.04 KB / 6.04 KB
(100.00%) - d
Sounds very similar to what was done here:
apparmor (4.1.0~beta5-0ubuntu12) plucky; urgency=medium
[ Ryan Lee ]
* Add patch to fix lsblk denials on Hyper-V systems (LP: #2103524):
- d/p/u/lsblk_hyper_v_fixup.patch
[...]
-- Ryan Lee Mon, 24 Mar 2025 10:14:46 -0700
** Changed in: ap
Thanks Maxime. What's the plan for landing the fix in Plucky? Will you
cherry-pick it, cut a new upstream snapshot, or something like that?
Note that there are just 5 working days before Plucky final freeze.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch
For posterity: I discussed this FFe with Skia and approved it in a side
channel, before sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/2103526
Title:
[FFe] Al
The status of the lightdm task is unclear to me, so I'm moving it back
to Incomplete.
Also: unsubscribing ubuntu-release as I think there is nothing left for
us to do here. Please re-subscribe if you think this is wrong. Thanks.
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Incomple
Unsubscribing ubuntu-release as I think there is nothing left for us to
do here. Please re-subscribe if you think this is wrong. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpa
Unsubscribing ubuntu-release as I think there is nothing left for us to
do here. Please re-subscribe if you think this is wrong. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bu
I also stumbled on this and tried the aa-notify way mentioned in comment
6, but that didn't work for me. I get the notification prompt on
allowing access to the key stored under my home directory, but by the
time I click on "Allow" openvpn already failed and gave up trying. The
"allow" setting (i.e
I think autopkgtest is working as expected. You asked to pin
src:nftables from -proposed, autopkgtest did that, even if this causes
dependency resolution issues. In the specific case you also need to add
src:libnftnl to the pinned packages.
Normally when this problem happens, autopkgtest re-tries
t; Paride Legovini (paride)
** Changed in: shadow (Ubuntu Noble)
Assignee: Paride Legovini (paride) => Tim Andersson (andersson123)
** Changed in: shadow (Ubuntu Noble)
Milestone: None => noble-updates
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-25.04-beta
--
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/2084089
Title:
ZFS with disk encryption missing cry
This is Fix Released, see e.g.
https://autopkgtest.ubuntu.com/results/autopkgtest-
oracular/oracular/amd64/p/perl/20240913_092937_6936a@/log.gz
** Changed in: perl (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Thanks!
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1.dsc
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1.debian.tar.xz
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1_source.buildinfo
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1_source.changes
** Changed in: libdmapsharing (Ubuntu Nobl
That versions string probably works, but I believe we want something
like:
3.9.13-2ubuntu1~22.04.1
which is not at work of being ambiguous.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdmapsharing in Ubuntu.
https://
Hello, I think the versions string in the debdiff is not OK for an SRU,
since 3.9.13-2ubuntu1 is already used in Oracular.
On this SRU in general, I share the concerns I expressed in [1].
[1] https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2084460
--
You received this bug notification becau
I am not sure the Impact is relevant enough to grant an SRU, and I
believe that the issue mentioned under "Where problems could occur":
> The packaging fixes have enabled other security hardening flags.
> This could have unintended effects.
is not negligible at all. Given that the diff is technic
** Changed in: libcanberra (Ubuntu Oracular)
Milestone: ubuntu-24.10-beta => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/2060693
Title:
No welcome/
** Changed in: totem (Ubuntu Oracular)
Milestone: ubuntu-24.10-beta => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/2060730
Title:
totem cannot insta
** Changed in: auto-package-testing
Status: New => Incomplete
--
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/2069834
Title:
systemd defaulting to tmpfs for /tmp cau
I reproduced this issue by:
1. Starting a Jammy LXD container
2. Stop+disable systemd-resolved, install dnsmasq
3. Verify that dnsmasq is healthy
4. Upgraded to Noble
5. systemd-resolved is running again, dnsmasq is broken
I started looking into this bug because it has a dnsmasq task (so it's
par
Hopefully worked around in autopkgtest by:
https://salsa.debian.org/ci-
team/autopkgtest/-/commit/2344e8197ed29ed1d94c33270207252574bb743c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launch
ppa-purge 0.2.8+bzr63-0ubuntu2 is currently in mantic-proposed,
sponsored by halves. Unsubscribing ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs
This also affects src:adduser, which has this delta:
+if ($action eq "adduser") {
+# Mute the command
+system('sh' => ( '-c' => '"$@" >/dev/null 2>&1', '--',
'/usr/sbin/zsysctl', 'userdata', 'create', $new_name, $home_dir,));
+}
causing it to fail in minim
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading software-properties_0.99.47.dsc: done.
Uploading software-properties_0.99.47.tar.xz: done.
Uploading software-properties_0.99.47_source.buildinfo: done.
Uploading software-properties_0.99.47_source.changes: done.
Successful
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: software-properties (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Hello Nathan,
the diff LGTM, I just have two questions:
1. The bug description has a "test case", but that's more of a
reproducer than of a test case, right? The "expected result" is not
explicitly stated. In particular, looking at this step:
- After Authentication, nothing happens.
what shoul
I believe this is fixed in:
openssh (1:9.6p1-3ubuntu3) noble; urgency=medium
* Add sshd-socket-generator to generate ssh.socket drop-in configuration
[...]
>From README.Debian:
The provided ssh.socket unit file sets ListenStream=22. A systemd generator,
sshd-socket-generator, parses the ssh
** Tags added: server-todo
--
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/2060150
Title:
openssh sets PAM_RHOST to UNKNOWN causing slow logins
Status in openssh package i
With 0b4c5056925e7358374874c8bf4767290157e903 (in autopkgtest 5.33) lxc-
start-ephemeral is not called anymore.
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: autopkgtest (Ubuntu)
Status: Triaged => Fix Committed
-
I am not sure I fully understand the latest comment. Does it mean that
8.0p1-19.0.1 just works? What about 8.0p1-19.0.1.2, mentioned in [1]?
[1] https://linux.oracle.com/errata/ELSA-2024-12164.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
** Changed in: auto-package-testing
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: auto-package-testing
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
** Also affects: heimdal (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: heimdal (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: heimdal (Ubuntu Focal)
Status: New => Fix Released
** Changed in: heimdal (Ubuntu Jammy)
Status: Ne
Uploaded and accepted:
==
OK: lvm2_2.03.16.orig.tar.xz
OK: lvm2_2.03.16-3ubuntu1.debian.tar.xz
OK: lvm2_2.03.16-3ubuntu1.dsc
-> Component: main Section: admin
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because
I just sponsored lvm2 2.03.16-3ubuntu1 which should fix the FTBFS.
On including libdm-propagate-ioctl-errors-back-to-caller.patch: I am not
sure this bug is important enough to grant that. The patch may apply
cleanly to 2.03.16, but still it comes from 2.03.23, which is not a
trivial change in the
** Changed in: lvm2 (Ubuntu)
Status: New => In Progress
--
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/2054683
Title:
Please merge lvm2 2.03.16-3 from Debian unstable.
** Changed in: policykit-1 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2054716
Title:
package polkitd 124-1 failed to inst
klibc (2.0.13-4) unstable; urgency=medium
[ Sven Joachim ]
* debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
(Closes: #1055694).
[ Salvatore Bonaccorso ]
* debian/control: Add myself to Uploaders
Date: 2024-02-21 22:32:43.744541+00:00
Signed-By: Parid
** Changed in: klibc (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/2054823
Title:
Sync klibc 2.0.1
Thanks for the additional information. By reading the pages Sergio
linked to I found one user writing:
Downgrading openssh-server to version 8.0p1-19.el8_8 will
revert the update and SSH will work again, although this
probably not advisable.
That's definitely not advisable, but I think it's
Looks like the experiment worked: having
e /tmp 1777 root root 30d
deleted a test directory which has mtime and atime >30d old (done via:
touch -d '29 days ago', and then left to age over the weekend).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
AIUI he suggests keeping the boot time cleanup, and that it could be
nice to have the 30d behavior back. In any case that's what I'd prefer.
I know we're speaking of file age; certainly not of blindly deleting
everything every month or so :-)
--
You received this bug notification because you are
FWIW I agree with Nick's preference (clean at boot && clean files older
than 30d). Maybe we could make that 40d, as 30d is likely to be a time
interval at which a lot of periodic things happen (e.g. an off-site
backup). A retention period >30d is less likely be synchronized with it
in an unlucky wa
Hello and thanks for this bug report. The analysis looks sensible to me,
but I'm not really familiar with gss. To better understand the situation
I have a couple of questions:
- Does this mean that gss is unusable in Jammy at the moment? AFAICT
this is the only bug report about it, so I would be s
This is a duplicate of LP: #1922130, marking it as such.
--
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/2052618
Title:
Missing sftp-server argument -m force_file_perms
St
Hi and thanks for working at this SRU. I have some comments on the
debdiff:
- Please specify the patch Author in the DEP-3 headers. See [1] for more
info on the header format.
- The patch description should not be "apply upstream patch", because
the patch is just the patch, it contains no informa
Hi, adding a couple of extra pointers here (I'm the Debian irqbalance
maintainer). This the Debian bug where the discussion on removing
irqbalance from the kernel Recommends happened:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926967
In Debian irqbalance is not installed anymore by default
** Changed in: pld-linux
Status: New => Incomplete
** Changed in: irqbalance (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/406
Hello Valentijn and thanks for this bug report, it really helped me
figure out an otherwise obscure printing issue.
However I don't agree with the suggested solution: the security model of
cups for ipps is TOFU (trust on first use): the certificate is accepted
the first time and then expected to b
Hello Valentijn and thanks for this bug report, it really helped me
figure out an otherwise obscure printing issue.
However I don't agree with the suggested solution: the security model of
cups for ipps is TOFU (trust on first use): the certificate is accepted
the first time and then expected to b
Actually, it would be nice if the new patch had some dep-3 headers (see
[1], `quilt --dep3` and maybe dep3changelog). In particular I think we
miss bug references an a description of the patch. Do you think you
could add the relevant ones? Thanks!
[1] https://dep-team.pages.debian.net/deps/dep3/
Thanks for digging into this issue and updating the relevant Debian bug,
refreshing the debdiff. This LGTM, tested locally, the manpage renders
fine. I am going to sponsor this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** 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.net/bugs/2038561
Title:
Requesting Ubuntu package manager to rel
Hello, while [1] by itself is a straightforward patch, I don't think we
can acknowledge this to be a bug in in Ubuntu, given that you are trying
to use an Ubuntu packaged software using a manually compiled version of
a library it depends on. This is not a supported use case, so the
prerequisites fo
The bug description says "dnsmasq on Ubuntu Jammy/Lunar crashes [...]",
but IIUC it's actually only the Jammy one that crashes (the lunar-on-
jammy one maybe has other issues, but doesn't exhibit the crash). Am I
right? In this case please update the bug description accordingly.
Thanks!
Edit: I di
Hello, I verified that Sergio's PPA contains the candidate upstream
patch (upstream commit d290630d31f4517ab26392d00753d1397f9a4114). If the
crash is still happening that probably wasn't the issue after all.
I see two possible ways forward here. One is classic git based
debugging:
1. compile 2.86
Stumbled on this in triage.
The bug description writes about "added functionality for systemd v250
which ubuntu does not have yet", which is not the case anymore.
The bug report didn't have any significant activity in >1 year. Is this
still an issue?
** Changed in: launchpad-buildd
Status
Given that this is required for hardware support, rc3 is tested already
in Debian and other distros, Mantic is an interim release, and also
taking into account Timo's familiarity with the package (see
d/changelog), I'm +1 with this request. I also tested the PPA packages
and they worked fine for me
Hello, I had a look at the debdiffs and they look good (clean upstream
cherry-picks). I think the packages are ready for sponsoring, but before
doing so I have a couple of questions.
1. The issue only happens *exactly* after 52 weeks, or something like
that, am I right? as I have systems that have
Hello Andrey, that's expected as from openssh 9.0 scp actually uses
sftp. From the release notes [1]:
This release switches scp(1) from using the legacy scp/rcp protocol
to using the SFTP protocol by default.
The release notes then shortly elaborate on why legacy scp was
problematic.
I'm mar
This popped up in triage as a stale bug, but looks like everything looks
good here: openssh 1:8.2p1-4ubuntu0.6 is in focal-proposed, verification
is done, migration is blocked by the block-proposed-focal tag (staged
SRU).
--
You received this bug notification because you are a member of Ubuntu
To
I think I found a relevant upstream bug [0], fixed by [1]. If the patch
applies fairly cleanly to the version in Focal this could be good SRU
material.
[0] https://bugzilla.mindrot.org/show_bug.cgi?id=3122
[1]
https://github.com/openssh/openssh-portable/commit/7af1e92cd289b7eaa9a683e9a6f2fddd98
Hello, I didn't go into the specifics of the bug, but according to LP:
#2007837 the security team (Cc: mdeslaur) is going to release rsync
3.2.7 to jammy and kinetic as a security update, so this bug should get
fixed too.
--
You received this bug notification because you are a member of Ubuntu
To
** Bug watch added: github.com/WayneD/rsync/issues #375
https://github.com/WayneD/rsync/issues/375
** Also affects: rsync via
https://github.com/WayneD/rsync/issues/375
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
To
Thanks. According to the package versions the bug is not present in >=
Kinetic, so setting the devel release task as Fix Released.
** Changed in: rsync (Ubuntu)
Status: New => Fix Released
** Changed in: rsync (Ubuntu Jammy)
Status: Incomplete => Triaged
** Tags added: server-todo
Hello Atharva and thanks for this bug report.
Since there isn't enough information in your report to differentiate
between a problem specific to your system and a bug in Ubuntu, I'm
marking this bug as Incomplete.
If you believe that this is really a bug, please provide some extra
context on what
Hello Vijay and thanks for this bug report. The ca-certificates package
is periodically upgraded in stable releases. The package changelog [1]
will tell you which CAs are added/removed with the past updates.
If you still believe you spotted an issue with missing certificate
please specify:
1. Whi
That's consistent with the comments above as the USB->SSD transfer
doesn't use the rsync protocol.
What we need to move this forward is a verification that applying [1] to
the version of rsync in Bionic (3.1.2) or Focal (3.1.3) fixes the issue.
If any of you affected users is available for testin
Uploading rsync_3.2.3-8ubuntu3.1.dsc
Uploading rsync_3.2.3-8ubuntu3.1.debian.tar.xz
Uploading rsync_3.2.3-8ubuntu3.1_source.buildinfo
Uploading rsync_3.2.3-8ubuntu3.1_source.changes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Assigning this to myself to do the sponsoring.
** Changed in: rsync (Ubuntu Jammy)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: rsync (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Looks like the culprit here is python3, as doing
apt install python3:i386
causes the removal of several important packages. This in a Jammy LXD
container and after doing `dpkg --add-architecture i386`.
The python3 package is marked Multi-Arch: allowed, so I would expect the
i386 package to be
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1993081
Title:
Installing sa
Thanks! I didn't test it, but formally it LGTM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1965076
Title:
rsync --update incorrectly reports file "is newer" than itself
Stumbled on this in Triage and I did a quick review of the debdiff
(thanks for preparin it!).
The patch cherry-picking LGTM, but I think we want ubuntu3.1 in the
d/changelog version string. Also the DEP-3 headers could have a Bug:
line pointing to the upstream bug [1].
[1] https://github.com/Wayn
Hello and thanks for this bug report. In my understanding, when ssh-
agent is in use, what matters is the order in which identities are added
to the agent. While I agree this is not clearly documented it's likely
that openssh is just working as expected.
The new agent restrictions feature of OpenS
I am a bit confused by the bug report.
I think ssh-add is correctly adding the DSA key to the agent, and the
fact that running ssh-add again requests the password again is normal
and expected. Looks Trusty behaves the same:
ubuntu@paride-t:~$ eval $(ssh-agent -s)
Agent pid 2406
ubuntu@paride-t:~$
Looks like there' also an openSUSE bug about this issue:
https://bugzilla.opensuse.org/show_bug.cgi?id=1175854
As I understand it the culprit is the old rsync (3.1.3). Upstream
suggests recompiling it with -with-included-zlib=yes, which I doubt
we're going to do, especially in stable releases. Th
Public bug reported:
[Partial copypaste from the linked upstream bug.]
Setting
NO_PROXY=localhost,127.0.0.1,::1
enables connections to http://localhost and http://127.0.0.1 and does
not work for http://[::1] at all. Apparently the problem is caused by an
assumption [1] that a hostname cannot
Fixed upstream and in >= Focal by:
https://github.com/curl/curl/commit/b7f90470be9b75f57167abbcd63aadb2e3b33958
** Description changed:
+ [Partial copypaste from the linked upstream bug.]
+
Setting
- NO_PROXY=localhost,127.0.0.1,::1
+ NO_PROXY=localhost,127.0.0.1,::1
enables conne
I see your point, and I find the one about "fixing it the Kinetic way"
especially convincing, it may save us headaches in the future, and may
help with backports. My concern is that other packages or scripts users
wrote and tested on Jammy systems refer to the "wrong" path
(/usr/lib/x86_64-linux-gn
Confirmed still happening on the Jammy 20220719 daily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1974483
Title:
autoinstall ssh:install-server:false is misleading
Hello James and thanks for your bug report. The "Make
ClientAliveCountMax=0 have sensible semantics" change you refer to is
actually an upstream change, see the OpenSSH bugfixes here:
https://www.openssh.com/releasenotes.html
the upstream bug being:
https://bugzilla.mindrot.org/show_bug.cgi?
aptly is Fix Release in Kinetic in:
aptly (1.4.0+ds1-7) unstable; urgency=medium
* Team upload.
* Add support for zstd compression (Closes: #1010465)
** Changed in: aptly (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
T
Well, "large" can span orders of magnitude, depending who you ask. :-)
Can you please try to identify some steps to reproduce that include the
big file generation? For example:
# 100MB file, random data (difficult to compress)
head -c 100M /dev/urandom > foo
# 100MB file, all 0s (easy to c
** Tags added: server-todo
--
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/1966886
Title:
ssh-copy-id and Dropbear Server
Status in openssh package in Ubuntu:
Triaged
B
I found a (somehow stale) upstream PR that addresses this:
https://github.com/openssh/openssh-portable/pull/250
We could include this as an Ubuntu patch, but it would be better to
first see it merged upstream. It may be worth pinging there.
** Changed in: openssh (Ubuntu)
Status: New =>
Hello and thanks for this bug report. I tried to reproduce this locally
but I failed. We're certainly willing to investigate this, but first we
need some steps to reproduce the problem. Could you please try to
identify a somehow reliable way to reproduce the issue and share your
findings? Thanks!
Hello Thomas. You filed this bug against:
DistroRelease: Ubuntu 21.10
Package: openssh-server 1:8.4p1-6ubuntu2.1
By "Solved by a later version of systemd and sshd". Do you mean that you
found you can't reproduce the issue on Jammy (22.04 LTS)? Can you still
reproruce the issue on Impish? Than
Hello Alvaro and thanks for this bug report. We have many systems
running Jammy and they're able to connect to GitHub with no issues. I
also tried with GitLab.com and it works just fine. This is not to
dismiss your report, but there's clearly something else involved in the
problem you're hitting. M
Hello Lars and thanks for this bug report. I can confirm this: libmnl-
dev 1.0.4-2 installs
/usr/lib/x86_64-linux-gnu/libmnl.a
while libmnl-dev 1.0.4-3 does not. I tracked this down to this Debian
packaging change (see the debian/libmnl-dev.install diff):
https://salsa.debian.org/pkg-netfilter
ring in it.
** Affects: base-files (Ubuntu)
Importance: Undecided
Assignee: Paride Legovini (paride)
Status: Triaged
** Changed in: base-files (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: base-files (Ubuntu)
Status: New => Triaged
I tried reproducing the issue on a Rpi4, cloning a repository via ssh
using pubkey authentication with a rsa2048 key stored in ssh-agent, it
worked fine. If you believe there's actually a bug here please provide
some steps we can follow to reproduce the issue from a clean Jammy
system, and we'll lo
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
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/1968876
Title:
ssh-agent: Error connecting to agent: Connec
Also: you mention that "ssh agent crashes". What do you see exactly to
be able to tell it's a crash and not some other authentication or key
handling issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
ht
Hello testpi and thanks for this bug report. Can you reproduce this
issue from a fresh install on the Raspberry, and attempting a simple ssh
login instead of a git clone? Something on these lines:
-
ssh-keygen
cp ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys
killall ssh-agent || true
eval $(ssh-age
Hello Alexander, note that Xorg is available in Jammy both as the native
graphical session and via xwayland. On this bug report: could you please
elaborate more on what exactly happens? In particular could you guide us
into reproducing the problem on a clean Jammy install, making clear
"what should
Still no activity in the upstream issue, however I think OpenSSH 8.9
offers a mechanism that can help avoiding hitting MaxAuthTries in some
cases: "destination constraints", see documentation for -h in ssh-
add(1). AIUI constraining should limit the number of keys tried against
a given host, making
I see your point; my suggestion here is to file a bug upstream with your
findings:
https://github.com/WayneD/rsync/issues
I don't think this should be tackled on the Ubuntu side, especially
given that the issue is really minor and unlikely to affect a
significant amount of users. As you say wha
Hello Ian and thanks for this bug report. My question here is: is this
actually a bug?
The manpage for --update says:
This forces rsync to skip any files which exist on the destination
and have a modified time that is newer
It seems sensible to me to make this a '>=' comparison, and not a st
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
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/1964642
Title:
Packer virtualbox ssh can't connect to unatt
Hello Barto,
If I understand it correctly you can create working images using 20.04
ISOs *right now*, but with the exact same tooling images created with
20.04.x ISOs do not work. I think you have been clear about this, but it
is of course very important to know that the only moving part is the IS
1 - 100 of 226 matches
Mail list logo
