On 11/28/18 8:26 PM, Pablo Pasquín Rosillo wrote:
> Just checked and it works fine with DefaultDependencies=no :)
>
I'm interested in the kernel oops, that should be fixed independently of
the systemd configuration.
Just checked and it works fine with DefaultDependencies=no :)
Gracias!
On Wed, Nov 28, 2018 at 10:32 AM Arturo Borrero Gonzalez
wrote:
>
> Control: tags -1 moreinfo
>
> On Thu, 1 Feb 2018 09:50:31 +0100 Paolo Rosquin wrote:
> > No idea why it only happens to me. Anyway, I have narrowed down the
Control: tags -1 moreinfo
On Thu, 1 Feb 2018 09:50:31 +0100 Paolo Rosquin wrote:
> No idea why it only happens to me. Anyway, I have narrowed down the
> problem to one line in nftables.service:
>
> DefaultDependencies=no
>
> Without this everything works fine.
>
Could you please check if this
No idea why it only happens to me. Anyway, I have narrowed down the
problem to one line in nftables.service:
DefaultDependencies=no
Without this everything works fine.
On Tue, Jan 30, 2018 at 2:05 PM, Arturo Borrero Gonzalez
wrote:
> On 28 January 2018 at 11:12, Paolo Rosquin wrote:
>> Package
On 28 January 2018 at 11:12, Paolo Rosquin wrote:
> Package: nftables
> Version: 0.8.1-1
> Severity: important
> Tags: upstream
>
> Dear Maintainer,
>
> When nftables is enabled at boot time, it will fail to load and stop the whole
> booting process with "A start job is running for...". If I am no
Package: nftables
Version: 0.8.1-1
Severity: important
Tags: upstream
Dear Maintainer,
When nftables is enabled at boot time, it will fail to load and stop the whole
booting process with "A start job is running for...". If I am not mistaken, it
started when I updated to kernel 4.14.
A workaround
6 matches
Mail list logo
