On Wed, 13 Jul 2022 18:17:51 +0200 Andras Korn
wrote:
> On Mon, Jul 11, 2022 at 10:47:26AM +0300, Martin-Éric Racine wrote:
>
> > On Thu, 6 Jan 2022 18:38:47 +0100 Michael Biebl wrote:
> > > On 06.01.22 17:26, Andras Korn wrote:
> > > > Package: systemd-timesyncd
> > > > Version: 249.7-1
> > > >
On Mon, Jul 11, 2022 at 10:47:26AM +0300, Martin-Éric Racine wrote:
> On Thu, 6 Jan 2022 18:38:47 +0100 Michael Biebl wrote:
> > On 06.01.22 17:26, Andras Korn wrote:
> > > Package: systemd-timesyncd
> > > Version: 249.7-1
> > > Severity: normal
> > > Tags: upstream
> > >
> > > Hi,
> > >
> > > I
On Thu, 6 Jan 2022 18:38:47 +0100 Michael Biebl wrote:
> On 06.01.22 17:26, Andras Korn wrote:
> > Package: systemd-timesyncd
> > Version: 249.7-1
> > Severity: normal
> > Tags: upstream
> >
> > Hi,
> >
> > I noticed that it took a while for the network to become available
after my
> > laptop
Does the issue still apply to dhcpcd5 version 9.4.1-1 or newer?
Martin-Éric
On 06.01.22 17:26, Andras Korn wrote:
Package: systemd-timesyncd
Version: 249.7-1
Severity: normal
Tags: upstream
Hi,
I noticed that it took a while for the network to become available after my
laptop wakes up from suspend.
I traced the problem to systemd-timesyncd.
I use dhcpcd5, which
Package: systemd-timesyncd
Version: 249.7-1
Severity: normal
Tags: upstream
Hi,
I noticed that it took a while for the network to become available after my
laptop wakes up from suspend.
I traced the problem to systemd-timesyncd.
I use dhcpcd5, which ships
6 matches
Mail list logo