Control: close -1
On Wed, 29 May 2024 20:15:36 +0200 Michael Biebl
wrote:
> Control: reopen -1
>
> On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi
wrote:
> > Control: tags -1 wontfix
> > Control: close -1
> >
> > On Tue, 28 May 2024 17:44:54 +0200 Michae
nes ***
"some software crash at system start-up" is not an actionable bug
report. Please provide details - what, where, how, decoded backtraces,
etc.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Wed, 29 May 2024 11:16:22 +0100 Luca Boccassi
wrote:
> On Tue, 28 May 2024 10:59:58 +0100 Luca Boccassi
> wrote:
> > Source: debos
> > Version: 1.1.1-2.1
> > Severity: important
> > Tags: patch
> >
> > Hi,
> >
> > debos ca
On Tue, 28 May 2024 10:59:58 +0100 Luca Boccassi
wrote:
> Source: debos
> Version: 1.1.1-2.1
> Severity: important
> Tags: patch
>
> Hi,
>
> debos calls debootstrap in /tmp/. Since systemd 256~rc3-3 /tmp/ is a
> tmpfs, mounted nodev, so debootstrap doesn't like it:
&
On Tue, 28 May 2024 at 14:45, Luca Boccassi wrote:
>
> On Tue, 28 May 2024 at 14:19, Luca Boccassi wrote:
> >
> > On Tue, 28 May 2024 at 14:18, Anthony Bourguignon
> > wrote:
> > >
> > > Le mardi 28 mai 2024 à 14:06 +0100, Luca Boccassi a écrit :
>
understands
xkb console handling. More details:
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/189#note_379435
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
n/lock 1777 root root - -
> /usr/lib/tmpfiles.d/legacy.conf:d /run/lock 0755 root root -
>
> triggering unnecessary warnings.
This is needed to apply debian-specific changes, just ignore it, it's
harmless
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Control: tags -1 patch
On Tue, 28 May 2024 12:08:37 +0100 Luca Boccassi
wrote:
> Source: piuparts
>
> Hi,
>
> When piuparts runs debootstrap, it is pointed to the default --
tmpdir,
> which absent any configuration or env var is /tmp/, which is now
(since
> systemd 256~
attached. This should make debci on Debian stable happy again.
The list of commits included can be seen at:
https://github.com/systemd/systemd-stable/compare/v252.25...v252.26
--
Kind regards,
Luca Boccassi
diff -Nru systemd-252.25/debian/changelog systemd-252.26/debian/changelog
--- systemd-252.25
On Tue, 28 May 2024 at 14:19, Luca Boccassi wrote:
>
> On Tue, 28 May 2024 at 14:18, Anthony Bourguignon
> wrote:
> >
> > Le mardi 28 mai 2024 à 14:06 +0100, Luca Boccassi a écrit :
> > > On Tue, 28 May 2024 at 14:05, Anthony Bourguignon
> > > wrote:
&g
On Tue, 28 May 2024 at 14:18, Anthony Bourguignon wrote:
>
> Le mardi 28 mai 2024 à 14:06 +0100, Luca Boccassi a écrit :
> > On Tue, 28 May 2024 at 14:05, Anthony Bourguignon
> > wrote:
> > >
> > > Le mardi 28 mai 2024 à 12:38 +0100, Luca Boccassi a écrit :
On Tue, 28 May 2024 at 14:05, Anthony Bourguignon wrote:
>
> Le mardi 28 mai 2024 à 12:38 +0100, Luca Boccassi a écrit :
> > On Tue, 28 May 2024 13:09:53 +0200 Anthony Bourguignon
> > wrote:
> > > Hi,
> > >
> > > Since 256~rc3-3, I can’t login anym
synced the /etc/pam.d/common* files from another computer, deleted
> the systemd-homed file in the
> same directory, and everything is back to normal.
uff I tested it from a TTY rather than GNOME and it worked. Does it
work from the console for you?
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
that as it
wants to create fresh node files.
Please make piuparts --tmpdir default to /var/tmp if nothing is set, to
avoid this issue.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
fixes the issue. I'd
appreciate a quick upload, as it blocks systemd's migration.
I'd also be happy to NMU this if you are busy.
Thanks!
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
..
> /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path
"/run/lock", ignoring.
It's harmless, just ignore it
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Tue, 28 May 2024 at 04:47, Salvatore Bonaccorso wrote:
>
> Hi Luca,
>
> On Mon, May 27, 2024 at 09:49:47PM +0100, Luca Boccassi wrote:
> > On Mon, 27 May 2024 14:31:37 +0200 Thorsten Leemhuis
> > wrote:
> > > On 27.05.24 14:22, Luca Boccassi wrote:
> >
On Sun, 5 May 2024 at 21:04, Luca Boccassi wrote:
>
> On Tue, 5 Jul 2022 19:42:37 +0200 Michael Biebl
> wrote:
> >
> > Hi Eric
> >
> > On Fri, 31 Jul 2020 15:12:48 + Eric Desrochers
> > wrote:
> > > Package: systemd
> > > Version: 2
/etc/tmpfiles.d/precious.conf
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Mon, 27 May 2024 at 20:02, Steve Langasek wrote:
>
> On Sun, May 26, 2024 at 07:01:30PM +0100, Luca Boccassi wrote:
> > Control: tags -1 help
>
> > This is the pam config I ship:
>
> > # cat /usr/share/pam-configs/systemd-homed
> > Name: Enable user manageme
On Mon, 27 May 2024 22:44:21 +0100 Luca Boccassi
wrote:
> On Fri, 30 Sep 2022 23:34:46 -0300 ng wrote:
> > Now, I think is worth mentioning that:
> >
> > Adding 'x-initrd.attach' to the device holding root at
> /etc/crypttab,
> > does in fact solve systemd
nown option" message, as the
Debian-specific initramfs-tools scripts do not know about it, but
that's fine, it's for the shutdown path anyway. And the finalize
messages can also be ignored.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Mon, 27 May 2024 at 22:15, Ian Jackson
wrote:
>
> bl...@debian.org writes ("Bug#1072021: hippotat-server: drop dependency on
> system-log-daemon"):
> > As per https://lists.debian.org/debian-devel/2024/05/msg00425.html we
> > want to drop dependencies on system-log-daemon when they are set
>
On Mon, 27 May 2024 14:31:37 +0200 Thorsten Leemhuis
wrote:
> On 27.05.24 14:22, Luca Boccassi wrote:
> >> https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461
> >
> > This has been reported upstream 3 weeks ago, but so far it seems no
> > action
t;
> > [1]
https://sources.debian.org/src/sysvinit/2.93-8/src/shutdown.c/#L467
> >
> >
>
> I've forwarded this feature request upstream. Please follow up there
if
> you have further feedback.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ng with systemd upstream myself given my past experiences
on
> systemd developer mailinglist, please respect that.
>
> Thank you,
> Martin
As explained in the upstream ticket this is pretty much intentional,
hence closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
idea could be to list all sub-services
> (instance names) in the output. maybe showing a one line status for
all
> instances would make the top-level status all the more useful.
>
> I don't know much about the systemd code though so I don't know which
> option is more feasible. I
e.g. systemd-tty-ask-password-agent can
> be fired off by the target users to respond to queries.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
/system-sleep. systemd-sleep
> should clearly look in /etc/systemd/system-sleep too for local
> changes.
As explained in the upstream ticket, this is intentional as these are
runnable binaries rather than configuration, so it is unlikely to ever
be changed, hence closing.
--
Kind regards,
L
ed getty@.service.
>
> Would you mind filing this upstream at
> https://github.com/systemd/systemd/issues
>
> I think you are in a better position to argue why this change should
be
> done in systemd and not agetty.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
bility problem because of the perceived
> > delay during interactive work.
>
> > This behaviour is observed on several installations of the
> > up-to-date Debian Buster. This seems to be a regression compared
> > to the Stretch version:
> >
> > # systemctl --v
t; >> Since this appears to be a regression in v251, please file this
> >> upstream at https://github.com/systemd/systemd/issues
> >
> > OK, I've just reported the issue upstream.
> >
>
> Thanks, appreciated.
This is tracked upstream, there are no patches nor conf
of minor severity.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
s poweroff.target' for details.
>
> Ok, so it's not a local user. So the password prompt is expected.
> It then prompts you for two separate actions:
> Setting the wall message and the actual poweroff
>
> This particular issue is already known and tracked upstream. Marking
> accordi
> https://github.com/systemd/systemd/issues
>
> we do not ship any downstream patches in that regard.
>
> Please report back with the upstream issue number so we can mark it
> accordingly.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Control: close -1
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
o be due to how the
> multicast DNS (`src/resolve/resolved-mdns*`) discards packets for
> various reasons on reception.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
emd/systemd-stable/issues
This is too complex to backport, so unless somebody provides and tests
a PR for systemd-stable upstream it is not going to happen.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
t; - "vm-other" on AMD (like my bug report upstream)
> >
>
> Ok, let's mark https://github.com/systemd/systemd/issues/28113 as the
> relevant upstream bug report.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
tracked upstream, and also as mentioned there it can't really
be done because we lack the kernel APIs to check things without
triggering automounts.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
he upstream ticket, this is likely a davs issue,
nothing we can do here.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
> you!
>
> Thanks, marking accordingly.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Control: close -1 256~rc1-1
On Sat, 20 Mar 2021 10:15:35 +0900 (JST) Ryutaroh Matsumoto
wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/19060
>
> I brought #982929 to the upstream as above.
> Best regards, Ryutaroh
Fixed in unstable now.
--
Kind r
gets SIGTERM after "OPENING →
AUTHENTICATING".
> Also the Login Service and Authorization Manager are stopped.
As mentioned in the upstream ticket this was actually a problem in
other services, so closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
inhibitor into account ("Refusing suspend operation,
> handle-lid-switch is inhibited"). And just after the VT change,
> it suspends the system.
As explained in the upstream ticket, this is mostly a misunderstanding
and a documentation issue, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
t; https://github.com/systemd/systemd/issues/20358
>
> Thanks, marking it accordingly.
This is tracked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
-wait-sync.service is not explicitly disabled).
Given this was never enabled, and there are no other configuration or
patches, and it is tracked upstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
imple video, of course - other services starting up around this
added
> a lot of noise. My server runs lots of services. Of course, I didn't
> get to capture the output directly, just the logs.
fsckd has now been dropped (after being out of tree for many years), so
this won't apply anymore, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
anks, marking the bug report accordingly.
>
> > If this gets fixed upstream, will the fix move back to stretch?
>
> Depends on how invasive the fix is and if it can be backported
easily.
>
> Regards,
> Michael
This is tracked upstream, there are no patches nor configuration
ked upstream, there are no patches nor configuration
downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
d X
> desktop). The 4 xf86CloseConsole lines aren't there, but the other
stuff looks
> mostly the same.
>
> Sorry for the previous mangled text. That's what I get for posting
from
> gmail...
This is tracked upstream, no configuration nor patches downstrema.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
on is used,
and I
> > can confirm this also works correctly.
> >
> > But "systemd-delta" does not show this extension:
>
> Filed upstream a while ago:
> https://github.com/systemd/systemd/issues/45
This is tracked upstream, there's no config or patch downstream,
closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
them, with
postinst machinery and whatnot. If you test this and send a MR on Salsa
I will review it, but I will not do the work myself.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
owever, we can reduce the amount of packages depending on
system-log-daemon which is just as well - MBF failed with usertag:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=bl...@debian.org;tag=system-log-daemon
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Mon, 27 May 2024 at 01:38, Sam Hartman wrote:
>
> >>>>> "Luca" == Luca Boccassi writes:
>
> Luca> Ah thanks for the pointer to the file, I had missed that
> Luca> somehow in the first reply. I see it now: the pam-config for
> Lu
is fixed by the
package currently in p-u)
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html
The source debdiff is attached.
--
Kind regards,
Luca Boccassi
diff -Nru systemd-247.3/debian/changelog systemd-247.3/debian/changelog
--- systemd-247.3/debian/changelog 2023-06
On Mon, 27 May 2024 13:02:12 +0100 Luca Boccassi
wrote:
> Source: linux
> Version: 6.8.9-1
> Severity: grave
> Justification: breaks autopkgtest jobs running in qemu, breaking
amd64 debci
> X-Debbugs-CC: elb...@debian.org, m...@tls.msk.ru
>
> Hi,
>
> Kernel 6.8 inclu
, that would break migration debci autopkgtest jobs. Example:
https://ci.debian.net/packages/s/systemd/unstable/amd64/47041978/
The launchpad ticket has more details:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461
--
Kind regards,
Luca Boccassi
signature.asc
Description
to see this fixed for v252-stable, please backport the
> commit to the v252-stable branch [1], test it and then submit a PR
[2]
This is fixed in testing. If somebody sends a tested PR for v252-stable
it can be fixed there too, but it hasn't happened in 6 months so
closing for now.
--
K
m
> within a debci run. Help with providing additional info would be
> very welcome.
Root cause for this is the same as #1050256 and will be fixed shortly
and backported. Same as that one, the fix only gracefully falls back
and disables PrivateIPC=, the kernel fix is needed to make the
and is already tracked
upstream, nothing we can do downstream, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
> > implemented upstream. One problematic issue I can imagine is that
it's not
> > trivial to reliably determine whether a disk is really removable or
not.
> > That said, if you are still interested, would you mind filing an
upstream
> > bug report at https://github.com/systemd/systemd/issues.
>
> Filed upstream as https://github.com/systemd/systemd/issues/18304 .
>
> Thank you again for all your work on systemd and udev, including
triage!
As mentioned in the bug report, giving unrestricted access to block
devices to unprivileged users is really not safe on Linux, so this is
not going to happen by default. udev rules can be configured locally
just as well, so one can do that on their own machine if these security
issues are not a problem.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Mon, 27 May 2024 at 00:30, Sam Hartman wrote:
>
> >>>>> "Luca" == Luca Boccassi writes:
>
> Luca>
> https://www.freedesktop.org/software/systemd/man/latest/pam_systemd_home.html
>
> It's going to be a long time (a couple of weeks) before
EST—Mo 2015-07-20 08
> > >
> > > No idea what happened to the logs.
> >
> > Do you have persistent logging enabled? I think you do not. Please
> > follow the instructions of the README.Debian if you want to enable
it.
>
> Done, waiting for repro situation...
issue anymore as per upstream ticket, closing
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ng 2
lines:
>
> [Unit]
> IgnoreOnIsolate=true
>
> In this way wpa_supplicant is not reset when isolating a target.
>
> Do you think it is a good solution ?
> wpa_supplicant.service will be patched in that way ?
Yes, if you want a unit to survive into an unrelated isolate, then you
need to mark it as such, or pull it in. This is working as intended.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Sun, 26 May 2024 at 21:46, Sam Hartman wrote:
>
>
> Hi.
> I'm not really swapped in on Debian this weekend; dealing with a
> transition for day job.
>
> But quick thoughts.
>
> I'm surprised that systemd-home is a pam auth module.
> That is, I wouldn't expect systemd-home to be able to decide
t; I think the journal takes quite a bit of space compared to what
rsyslog
> produces with its standard logrotate settings (especially if you
> substract the 143M atop performance data):
compact mode has been implemented, that's good enough already, for
other RFEs just open them upstream, n
rom within a shell worked fine.
>
> I did some investigation and found out that dbus-daemon is not
started
> be the pam-authenticated user session anymore, but
> via /lib/systemd/systemd --user.
As mentioned on the upstream ticket, this really needs to be fixed in
AFS, nothing we
o, which break
everything. Removing those manually fix things again. I have no idea
where they are coming from... PAM experts, any idea?
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Sun, 26 May 2024 18:57:31 +0200 Marc Haber
wrote:
> On Sun, May 26, 2024 at 05:53:01PM +0100, Luca Boccassi wrote:
> > So yeah, not going to risk this for the benefit of a non-default
> > package with 0.19% popcon, sorry. Feel free to document the
workaround
> > and link t
]
> > Any updates here?
>
> Sorry, no.
> This is relatively low priority for me.
No update in 4 years, and it was in the meanwhile worked around in
udisks2. It is not appropriate to patch to change return values
downstream, so closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
; ./src/fsckd/fsckd.c: ngettext("Checking
in progress on %d disk (%3.1f%% complete)",
> ./src/fsckd/fsckd.c: "Checking
in progress on %d disks (%3.1f%% complete)", m->numdevices),
fsckd has now been dropped
be able to
register an interest in /usr/lib/systemd/boot/efi/ and do its stuff
when it is updated.
I am not going to work on this, anybody who is interested in this
should provide MRs to the appropriate packages.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
use networkd and for GUI systems use
network-manager.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Sun, 26 May 2024 at 17:37, Marc Haber
wrote:
>
> On Sun, May 26, 2024 at 04:57:10PM +0100, Luca Boccassi wrote:
> > I am pretty sure this is working as intended, we do not want the ESP to
> > be always mounted by default. You can disable this generator in
> > multipl
Control: close -1 256~rc1-1
On Thu, 24 Aug 2023 11:45:41 +0200 Michael Biebl
wrote:
> On Thu, 29 Jun 2023 11:24:33 +0100 Luca Boccassi
wrote:
> > On Thu, 29 Jun 2023 10:16:19 + undef
wrote:
> > > Package: systemd
> > > Version: 252.6-1
> > > Severity
at the moment, but this is not a stable interface,
and in fact we are likely going to change to a different format. So it
is not advisable to build functionality to rely on them. If you really
want to, you can fetch the source package using apt, but I recommend
against it.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
the preferred one).
Very nice, thank you!
In the meanwhile, I found a way to reliably detecting this and
gracefully skipping it in systemd, so debci is now fixed. However, it
still results in PrivateNetwork= being quietly disabled, so the
backport is still very much needed, as it is a useful security
regard.
>
> I didn't know about this tool. Thanks for the tip :)
Yes this is a known debootstrap issue, and we don't want to workaround
it here. Also, I am not sure the systemd-container package is actually
needed _inside_ the container, as it provides tools and services to run
containers
u don't want this behaviour - via the cmdline as
already mentioned, or by masking it with:
touch /etc/systemd/system-generators/systemd-gpt-auto-generator
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ompat symlink has been around for many years, and documentation
has long since been updated. Given the initrd tools are not going to
add checks, I will just drop it now. Any user still setting manually
init=/bin/systemd will just have to fix their local configuration after
they notice the breakage
patch manpages like this. You can use dracut in
Debian, a few people do, so it is technically correct.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
install the systemd v254 version from
> bookworm-backports.
> https://backports.debian.org/Instructions/
No follow-up in half a year, unreproducible, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Control: close -1
On Sat, 20 Jan 2024 20:52:20 +0100 Michael Biebl
wrote:
> Hi Corin
>
>
> On Wed, 03 Jan 2024 12:50:13 +0100 Luca Boccassi
wrote:
> > Control: severity -1 normal
> > Control: tags -1 moreinfo
> >
> > On Wed, 03 Jan 2024 12:02:40 +0100 Cori
ely hit. I work around it now and do not plan to look
> deeper, in Trixie it also does not exist.
There are no patches downstream that could affect that behaviour as far
as I am aware, and given it's fixed in testing I'll close this now.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
simply apt fails, I wouldn't consider this a bug in the test but
> rather in how your test image/environment is setup.
arm64 autopkgtest runs work as expected on debci (lxc) and on ubuntu ci
(qemu) these days, hence closing as unreproducible.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
> Without further information, this issue is not really actionable.
No follow-up in half a year, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
e who complains about its ServerName.
> >
>
>
> In case you can still reproduce the issue with an up-to-date version
of
> systemd (i.e. v250 or v251), please report this upstream at
> https://github.com/systemd/systemd/issues
No follow-up in 7 years, closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ile is actually generated by systemd-localed (invoked by
> dbus from gnome-control-center), so you could probably achieve the
same
> effect by running localectl.
We have made writing console layouts via localectl a no-op some time
ago, so closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
haviour
that
> was hoping for here?
>
> Thanks,
> Joachim
It looks like this was worked around a long time ago, and no updates
since. We do not patch nor reconfigure path units behaviour downstream,
so any issue with them needs to be tested in unstable on the latest
version and then reported upstream.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Control: close -1 256~rc2-1
On Fri, 3 May 2024 14:16:10 +0200 =?utf-8?Q?C=C3=A9dric?= Hannotier
wrote:
> Dear Luca Boccassi, Dear Maintainers,
>
> On Sun, 28 Apr 2024 11:42:11 +0100 Luca Boccassi
wrote:
> > On Sun, 28 Apr 2024 11:53:17 +0200 Adrien CLERC
> > wrote:
&
rw---) Uid: ( 0/ root) Gid: ( 0/
root)
> Access: 2024-05-06 01:03:09.107874379 +
> Modify: 2119-06-23 05:10:17.721082481 +
> Change: 2119-06-23 05:10:17.721082481 +
> Birth: 2119-06-23 05:10:17.491093577 +
What is causing the rootfs timestamp to overflo
oday it worked when I wanted to reproduce the issue.
> I'll report back when it occurs again.
Closing since it is not reproducible.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
produced, please
open an issue with all the details upstream on Github.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
gt; the v252-stable branch upstream at
> https://github.com/systemd/systemd-stable.
>
> Unfortunately I lack the required setup to run this git bisect myself
so
> the fix for this issue will rely on your help.
Unless somebody provides a tested backport upstream to the v252-stable
branch,
more info than we already have. Gioele could you please make a
recommendation and update the MR so that we can do something, one way
or the other?
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
;
> If you login locally and you get the password change request, do you
> also get a failed user@.service?
No follow-up in almost a year, hence closing for now. If it can be
proved it's still an issue, and not a problem in the pam ssh config,
then it can be reopened with the requested info.
1 - 100 of 1838 matches
Mail list logo
