[17:48] rbalint: I was checking the systemd autopkgtests which were
flaky retries and which were real issues
[17:48] rbalint: and it seems all were flaky (most resolved now and
src:audit in the queue to be tested)
[17:49] rbalint: but one remained - plymouth - that seemed to be a
genuine
Hmm thanks Raphaël.
So files were still around that were unowned, that really should not happen.
Thanks for the exact file names.
The files you had in your case were part of libseccomp2 2.3.1-2.1ubuntu4 which
is what Ubuntu had in Bionic-release.
libseccomp2 | 2.3.1-2.1ubuntu4 |
still build-depends on python-evdev - we will have to remove autopilot-
gtk as it didn't build for two releases now (F+G).
Fixable with a new upload that resolves the dependency issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
When running the build in a local groovy qemu riscv64 guest the test
left no dbus-test-runner processes for debugging around :-/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dee in Ubuntu.
Bumping the timeout isn't enough :-/
It still gets into the hang and breaks build.
Chances are we are not actually facing a timeout issue, but something around
/var/log/launchpad-buildd/default.log-20200812:2020-08-11 12:45:42+ [-]
Build log: (dbus-test-runner:1807632):
It turned out that this has happened in the past and then resolved, so this is
a comeback.
For "dee" we can bump the timeout or skip the test on riscv64 for the immediate
problem
But the "dbus-test-runner timeout makes riscv64 builds" hang is a problem on
its own.
Therefore I added a bug task
>From IRC:
[13:34] Laney: ha - timeout = 1 on x86 triggers the same
warnings/erorrs, but NOT the hang of the builder
[13:34]
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4200/+build/19818311
is an example
[13:34] interesting
[13:35] perhaps riscv64 does process reaping
When lowering the timeout to trigger the same on x86 (to see if the hang
occurs there as well) I can see that the test breaks as it does on
riscv64, but the hang does not happen.
task-0: /Model/Transaction/Target2ChangeRemoveAppend:
OK
** (dbus-test-runner:15767): WARNING **: 11:26:03.671:
Good case:
task-0: Shutting down
DBus daemon: Shutdown
make[4]: Leaving directory '/<>/dee-1.2.7+17.10.20170616/tests'
Bad case:
task-0: /ModelTags/SharedModel/TwoTags: OK
** (dbus-test-runner:2028709): WARNING **: 12:41:16.457: Timing out at
maximum wait of 60 seconds.
If you catch the log at the right time there is a related test failure:
** (dbus-test-runner:1577514): WARNING **: 12:15:11.723: Timing out at maximum
wait of 60 seconds.
(dbus-test-runner:1577514): libdbustest-CRITICAL **: 12:15:11.736:
dbus_test_service_run: assertion 'all_tasks(service,
FYI - I'm driving soem debugging enabled test builds at
https://launchpad.net/~paelzer/+archive/ubuntu/dee-groovy-hang/+packages
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4192/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
The builds for riscv64 on e.g.
https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1
hang eventually.
All other architectures work fine.
Build log tail will be like:
...
symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4
pkgstripfiles:
The new code now handles sockets and services differently from libvirt
packaging.
There might also have been changes to the various debhelpers, but the TL;DR is
that I no more see this issue with libvirt 6.6.
I'll mark the bug as closed with that, but please report back if you
happen to find a
Due to that hint with SciLinux I have fetched
http://ftp.scientificlinux.org/linux/scientific/7.8/SRPMS/vendor/openssh-7.4p1-21.el7.src.rpm
I can't see it but that is https://bugzilla.redhat.com/show_bug.cgi?id=991186
I can see follow on issues referring to it
Hi Toby,
It seems that is an ongoing topic for years, I've found this discussed
from the KRB POV [1] and on openssh [2]. Especially following [1] it
seems things aren't too easy but there are a few workarounds/hints that
might or might not help your use case.
In general having this configurable
Hi Seb, as far as I understood Cliff it only started to occur with version
3.2.1 in Groovy.
And after we found the root cause that is now confirmed, 3.2.1 has:
ProtectSystem=full
ProtectHome=on
PrivateDevices=on
NoNewPrivileges=on
But the version in Focal doesn't have that and thereby is fine
@Malek - hi, chances that you have a different bug that just seems to be
similar are very very high.
I recommend reporting a new bug so that your logs are automatically attached.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This won't auto-sync as there is Delta.
This MP is up to merge the latest version from Debian.
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/rsync/+git/rsync/+merge/388554
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Maybe permission differences of the path to /home/cliff/Bin vs
/mnt/testrsync
Did you start the daemon like I did as root or under a different user?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
Thanks Cliff!
Note: the server question you wondered would have been the details how exactly
(commands( you do "syncd is enabled and started at boot with the
rsyncd.conf". Because in that might lay the details we need.
I was setting up a server on my own aligned to your config.
The following
@Cliff
- if you run the above simplified case does it work for you?
- if it does, could you try making it closer and closer to your setup until
you've identified what
makes it break?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks, with that config (or a subset thereof) how do you run your
server (if it is anything more than sshd or such) and your client (the
actual rsync call)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
Hi Cliff and thank you for the report.
Hmm, neither the later 3.2.2 nor the yet unreleased 3.2.3 mention any fix in
that regard.
https://download.samba.org/pub/rsync/NEWS#3.2.2
I guess we'd be down to bisecting for the offending change or something like it.
As-is I'm not seeing the issue when
Fixed in 1:8.2p1-1 and
openssh | 1:8.2p1-4 | focal| source
openssh | 1:8.2p1-4ubuntu0.1 | focal-updates| source
openssh | 1:8.3p1-1 | groovy | source
So this should be fix released, btu wasn't updated.
** Changed in: openssh (Ubuntu)
The last two updates went smooth for me, not triggering it.
I'm still too afraid to "just update while working" as I did in the past since
it could drag things down thou :-/
I was feeling like this could be solved, but reading that Steve is also
affected I'm worried that I might just not hit the
** Bug watch added: Debian Bug tracker #963702
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963702
** Also affects: binutils (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963702
Importance: Unknown
Status: Unknown
--
You received this bug notification
Autopkgtest issues resolved, all good now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1883880
Title:
fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
with:
2.30-21ubuntu1~18.04.3
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
avx.o | grep vmovaps
0: 62 f1 7c 48 28 04 05vmovaps 0x1(,%rax,1),%zmm0
with:
2.30-21ubuntu1~18.04.4
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
Hi Joi,
thanks for the extra data, I still can't think of a case to create this.
Looking forward to what you find checking this in more detail.
When in the error case could you look around which seccomp the system still has
around?
For example via:
$ ls -laF /lib/x86_64-linux-gnu/libseccomp*
Note: overall bugs with this tag
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=writable-etc
--
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/1849560
Title:
Please
Hmm,
are we sure anyone still cares about this.
Sadly Matthieu isn't around anymore and we had no one else from UC20 speak up
at all since then.
If someone really still depends on this please speak up here!
IMHO "whishlist" + "server-next" are almost kind of mutually exclusive.
Further I can
To have a bileto PPA with security only (thanks Sil2100 for stopping it to
reconfigure itself) look at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4151
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
On first check by the SRU team I got:
[18:34] cpaelzer: ok, looking at the binutils SRU, so you talked to
do_ko about it, right? Was he +1 on the change?
He was in a private IRC, I now asked him to state it here as well so
that it is visible to the SRU team. And he already did so - thanks!
This is server-next as soon as 8.4 is in groovy, I tagged it already to
not forget it.
--
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/1885990
Title:
server: Match has no
ged in: openssh (Ubuntu)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Hi Harry,
the real action/verification will be needed ocne the SRU team has accepted that
into proposed [1].
If you want to test the PPA the following will enable it on your system:
$ sudo add-apt-repository ppa:ci-train-ppa-service/4105
The PPA tells you that on its front page [2] as well, I
FIY uploaded to groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1885125
Title:
merge 8.2006.0-1 and include apparmor fixes
Status in rsyslog package in Ubuntu:
Hi Yuri,
there was no recent change in regard to lvm handling in libvirt or lvm itself
that would obviously be related. Which Ubuntu release are you on - and between
which package versions did you upgrade?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Yeah I have considered it as nice drive-by improvement unrelated to this bug -
and thanks for doing so.
I just had sorted out some lose ends on rsyslog and they both where part of it.
Since this didn't work last time it is not closed yet, but open at low prio.
As explained TBH I think we won't
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/386381
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1885125
upload/8.2001.0-1ubuntu1 has the former delta already split
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1885125
Title:
merge 8.2006.0-1 and include apparmor fixes
: Undecided
Assignee: Christian Ehrhardt (paelzer)
Status: In Progress
** Changed in: rsyslog (Ubuntu)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification becau
Let us kill the SRU - given what happened last time and that this is a
a) disabled by default profile
and
b) user fixable by editing a conffile
If it is ok with you I'd better focus on merging the latest version +
your improvement in
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
I want to look at this again ...
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.
as well.
I uploaded to bionic-unapproved for consideration by the SRU Team.
** Changed in: binutils (Ubuntu Bionic)
Status: New => In Progress
** Changed in: binutils (Ubuntu Bionic)
Assignee: Matthias Klose (doko) => Christian Ehrhardt (paelzer)
** Tags added: server-next
-
A few dep8 tests failed in the sniff, but all of them are existing known
overrides in Bionic:
ubuntu-release:9:force-badtest dh-ada-library/6.12
ubuntu-release:18:force-badtest lintian/2.5.81ubuntu1
pitti:2:force-badtest rpmlint/1.9-6
ubuntu-sru:17:force-badtest snapcraft/2.43.1+18.04/amd64
Tested in Bionic Container:
no PPA:
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
avx.o | grep vmovaps
0: 62 f1 7c 48 28 04 05vmovaps 0x1(,%rax,1),%zmm0
with PPA:
root@b:~# echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
avx.o | grep
Added an SRU Teamplate entry in the description, thanks Bruce for the
test.
The changes build fine, all self tests on build are good [1].
The dep8 sniff tests have just started at [2] and will later be available there.
The changes are rather small as seen on [3]
But while all that shall help by
Retest as-is:
root@f:~# dpkg -l openssh-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
Public bug reported:
Hi,
DPDK has run into some issues in the past
https://bugs.dpdk.org/show_bug.cgi?id=97
https://bugs.dpdk.org/show_bug.cgi?id=249
Eventually the issues got resolved in binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=23465
After binutils is fixed people
FYI: The tests were already retried (thanks seb128) and are good now
--
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/1876320
Title:
Port parameter sshd_config is 22 AND
** Changed in: openldap (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: openldap (Ubuntu Trusty)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
FYI
- 1:8.2p1-4ubuntu1 migrated into groovy
- 1:8.3p1-1 got into Debian containing the fix, so this can be a sync again
- added SRU template here
- uploaded to Focal-unapproved
** Description changed:
+ [Impact]
+
+ * The "Port" option in sshd_config is accumulative, but due to a bug re-
+
Ok, uploaded to Groovy as Delta for now.
In addition I filed https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=962035 to later on be able to make it a sync
again.
** Bug watch added: Debian Bug tracker #962035
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962035
** Also affects: openssh
MPs ready, I asked cjwatson if in Groovy he prefers this as Ubuntu Delta
or as a new Debian upload that will sync in. Once Groovy is complete
either way we can start the SRU process for focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I have prepared a PPA with the fix and would appreciate if that could be tried
and tested:
@Adriaan - would you be so kind to confirm that this fixes your real case?
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4080
Furthermore as I expect this will work well I also have
Final committed fix for this issue:
https://anongit.mindrot.org/openssh.git/commit/?id=0a9a611619b0a1fecd0195ec86a9885f5d681c84
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
FYI: "Include" functionality was added in 8.2 by upstream.
Thereby as already triaged only >=Focal is affected
--
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/1876320
Title:
*** This bug is a duplicate of bug 1876055 ***
https://bugs.launchpad.net/bugs/1876055
Thanks Jamie, that will fix this bug here as well then, IMHO we should
mark it as a dup then.
** This bug has been marked a duplicate of bug 1876055
SRU: Backport 2.4.3-1ubuntu2 from groovy to
FYI - I'm facing a bug where it would have been really helpful to have
this fixed for better reporting. Therefore giving this nudge by pinging
here ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I hit that again today on an upgrade.
Network manager didn't come up again.
Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected
error response from GetNameOwner(): Connection terminated
Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9491]
caught
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
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/1878752
Title:
vgcreate fails on
This is now merged upstream.
Eventually https://github.com/systemd/systemd/pull/15801 was the PR that got
merged.
I'd ask to backport those to Groovy/Focal to fix this kind of output
truncation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
FYI reworked by L. Poettering in
https://github.com/systemd/systemd/pull/15801 now
--
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/1875708
Title:
Truncated messages in
I have not seen it again in any environment since then.
Interesting that you hit it in such a specific environment.
I'd have expected that it might be incompatible components.
Do you have other things than the kernel from outside the Ubuntu Archive?
--
You received this bug notification because
Both fixes are in v4.19.0 and later
** Also affects: iproute2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: New => Fix Released
** Changed in: iproute2 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: iproute2 (Ubuntu
Yeah Dan, thanks for chiming in.
In particular that would be at least (but not lmited to) the changes:
8.04
Rework DTLS MTU detection. (#10)
7.08
Support automatic DTLS MTU detection with OpenSSL.
7.07
Automatic DTLS MTU detection.
Ubuntu has these newer versions.
Bionic 18.04 is on 7.08 and the
Hi,
this seems to be this upstream issue:
https://github.com/vx/connectbot/issues/141
These things come every now and then, in [1] you see more such being dropped in
the past.
Until the client is able to use the newer key exchanges you might need to make
your server less secure by adding to
** Also affects: apparmor (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1872564
Title:
The upstream submission is still being discussed (now got tests added
and some more questions answered), but it is still on its way.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi,
even Bionic which you upgraded from would have been
/lib/x86_64-linux-gnu/libseccomp.so.2.4.1
2.2 was last available in
libseccomp2 | 2.2.3-2ubuntu1~ubuntu14.04.1 | trusty-backports | amd64, arm64,
armhf, i386, powerpc, ppc64el
libseccomp2 | 2.2.3-3ubuntu3 | xenial
Thanks for the report Jeremy,
The fix is in V_7_5_P1 and by that >=Bionic is fixed - I agree to you this only
has to target Xenial.
** Tags added: bitesize server-next
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Xenial)
Of course now it had to work :-/
I'm suggesting enhanced debug to Debian in
https://salsa.debian.org/debian/chrony/-/merge_requests/4
And consider this done for now.
** Changed in: libcap2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: chrony (Ubuntu)
Status: New =>
It was flaky and now resolved in proposed migration.
But I'd want to understand why we fail 4/5 times.
So the debugging tests in the bileto ticket [1] will go on for a bit.
[1]: https://bileto.ubuntu.com/#/ticket/4049
--
You received this bug notification because you are a member of Ubuntu
I have restarted it again on LP in case it was a flaky network after
all.
At the same time I have added some debug statements and prepare a bileto
ticket to run the tests there as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Ha, that was a good red-herring
It doesn't fail at this test despite all the error messages thrown out.
It does
1. build chrony without root (works with tests skipped as it isn't root)
2. passes other tests as it ERRORs but detects that the environment is the
reason for that
The actual error
At the actual build time it is skipped for being "non-root".
But I think this is as easy as now trying to set HW-time in a container.
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch
It is the build phase that fails.
Reproduced in armhf container on canonistack.
1. get the source and build deps
2. build that until it breaks
3. re-run via
$ cd ~/chrony-3.5/test/system
$ ./run -i 20 -m 2
In this repro environment I get two extra fails at:
005-scfilter Testing system
Example log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/c/chrony/20200501_151956_0271e@/log.gz
Old issue was: https://bugzilla.kernel.org/show_bug.cgi?id=206539
and resolved in 2.32
The release notes on 2.33 are not
Public bug reported:
Test fails on armhf only:
running chronyc makestep ERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output
FYI: the fixes will also need a minor backport change due to [1], but
cmsg isn't touched in the new changes so no backport of [1] itself is
needed (which would in turn change more than we want and affect other
subsystems)
[1]:
I have a branch [1] and a PPA [2] based on the upstream suggested fix.
For now these are only meant to test to provide feedback to [3]
[1]:
https://code.launchpad.net/~paelzer/ubuntu/+source/systemd/+git/systemd/+merge/383390
[2]:
file..etc.libvirt.qemu.networks.default.xml: [inaccessible:
[Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml']
** Changed in: libvirt (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch s
@RCJ - can you help by testing the PPA that I provided and chime in on
the upstream discussion to get things moving a bit better - just to show
that people would really care about this feature.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Filed upstream for a discussion at
https://bugzilla.mindrot.org/show_bug.cgi?id=3153 and linked in the bug
here.
** Bug watch added: OpenSSH Portable Bugzilla #3153
https://bugzilla.mindrot.org/show_bug.cgi?id=3153
** Also affects: openssh via
** Also affects: openssh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203700
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
I have a PPA at:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-872145-ssh-prefer-user-configured-key
I have tested and the "IdentityFile" directive in /etc/ssh/ssh_config
does not count as "user defined". I'd have preferred if that would count
as well, but for now at least preferring the
Without checking deeper I'm unsure if keys listed in e.g.
/etc/ssh/ssh_config are considered as "userprovided" but lets give this
a shot.
Gladly the debug already contains "explicit" if id->userprovided is
true.
I usually get:
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
There are plenty of workarounds and the internet is full of this issue.
-
https://serverfault.com/questions/36291/how-to-recover-from-too-many-authentication-failures-for-user-root
- https://www.tecmint.com/fix-ssh-too-many-authentication-failures-error/
-
** Summary changed:
- 245.4-2ubuntu1 has broken chrony autopkgtest
+ 245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp hook
** No longer affects: chrony (Ubuntu Bionic)
** No longer affects: chrony (Ubuntu Eoan)
--
You received this bug notification because you are a
Oh I just read "Docker on Mac" plus the qemulation layer I assume
through qemu-static, but it even isn't "our" qemu of Ubuntu then :-/
Not sure what to suggest, but just generally doe this trigger with all
qemu's?
--
You received this bug notification because you are a member of Ubuntu
Touch
Hi,
to be sure - this is qemu-tcg (emulation) for ppc64 right?
We hit quite some issues when glibc added new instructions, that qemu-
tcg could not run it anymore. Newer qemu fixed that just to see 20.04
added even more instrcutions that now fail now. But the lessons learned
is that TCG on ppc64
** Tags added: server-next
--
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/1872145
Title:
explicit key offered after all agent keys, auth can fail before
explicit key
Chrony fix in focal completed tests and should migrate any minute.
But as that is only a mitigation of the symptoms not a fix to the problem in
systemd-timesyncd at all.
** Changed in: chrony (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a
I have tried to get this into 20.04 but it really does not behave the way it
should.
- sockets are still restarted (more than ever)
- libvirt-guest is restarted (killing guests on upgrades)
...
This needs some more time and isn't feasible for a late minute change in 20.04.
I'm considering it as
I filed bug 1873031 for the latter
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
installed
Public bug reported:
systemd has broken this by the split of timesyncd.
On a system that installed chrony (or other NTP servers) you'll have:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required
FYI : This also has broken dhcp based ntp info updates
This is hit by the chrony autopkgtests, how did you get this systemd upload to
migrate without fixing that?
$ sudo dhclient dummy0
Failed to try-restart systemd-timesyncd.service: Unit systemd-timesyncd.service
is masked.
--
You received
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
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/1869796
Title:
vague er
501 - 600 of 1232 matches
Mail list logo
