On 9/2/18 16:42, Guus Sliepen wrote:
> On Sun, Sep 02, 2018 at 03:34:46PM +0200, Michael Biebl wrote:
>
>> On Mon, 28 May 2018 11:08:00 +0200 Eric Valette
>> wrote:
>>
>>> When upgrading, you're stuck with the last message in console "setting up
>>> ifupdown" and nothing else. The machine dropped
On Sun, Sep 02, 2018 at 03:34:46PM +0200, Michael Biebl wrote:
> On Mon, 28 May 2018 11:08:00 +0200 Eric Valette
> wrote:
>
> > When upgrading, you're stuck with the last message in console "setting up
> > ifupdown" and nothing else. The machine dropped its ip address but
> > seems to fails to a
On Mon, 28 May 2018 11:08:00 +0200 Eric Valette
wrote:
> When upgrading, you're stuck with the last message in console "setting up
> ifupdown" and nothing else. The machine dropped its ip address but
> seems to fails to acquire a new one. and stay like this for minutes.
I'm suprised ifupdown rec
On Thu, 7 Jun 2018 12:34:31 + Martin Hradil wrote:
> This is caused by systemd-tty-ask-password-agent:
>
> rxvt-unicode(28371)-+-bash(28373)---sudo(14210)---dpkg(14211)---ifupdown.postin(14214)---systemctl(15338)---systemd-tty-ask(15342)
>
systemd-tty-ask-password-agent is a symptom, not th
This is caused by systemd-tty-ask-password-agent:
rxvt-unicode(28371)-+-bash(28373)---sudo(14210)---dpkg(14211)---ifupdown.postin(14214)---systemctl(15338)---systemd-tty-ask(15342)
(from pstree)
But it seems like the systemd helper is trying to talk to tty1, while
the terminal I've ran dpkg --co
Package: ifupdown
Version: 0.8.34
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I now have been experiency three freeze during apt upgrade on three
machines with the lattest update.
When upgrading, you're stuck with the last message in console "setting up
ifupdown" a
6 matches
Mail list logo
