Am 22.03.2018 um 10:24 schrieb LEDUQUE Mickaël:
> Ah yes.
> I'm not sure you'll get much more from my system and logs now, can I
> install systemd:amd64 back now ?
Please go ahead and install systemd:amd64 again.
--
Why is it that all of the instruments seeking intelligent life in the
universe
Ah yes.
I'm not sure you'll get much more from my system and logs now, can I
install systemd:amd64 back now ?
2018-03-21 16:08 GMT+01:00 Michael Biebl :
> Am 19.03.2018 um 16:36 schrieb LEDUQUE Mickaël:
> > Start-Date: 2018-03-15 09:28:21
> > Commandline: apt dist-upgrade
>
> [..]
>
> > Remove:
Am 19.03.2018 um 16:36 schrieb LEDUQUE Mickaël:
> Start-Date: 2018-03-15 09:28:21
> Commandline: apt dist-upgrade
[..]
> Remove: bundler:amd64 (1.15.1-1), systemd:amd64 (237-4),
> ruby-bundler:amd64 (1.15.1-1)
> End-Date: 2018-03-15 09:28:29
>
> Also it seems at some point I had systemd:amd64
Am 19.03.2018 um 09:51 schrieb LEDUQUE Mickaël:
> You're right, but honestly, I have no idea how this happened :
>
> $ dpkg -l systemd
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
> |
> État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchemen
Is it possible it could be because I put a package (I think it was a
systemd package) on hold because apt warned me about a critical bug on
systemd or udev about one week ago ?
2018-03-19 9:51 GMT+01:00 LEDUQUE Mickaël :
> You're right, but honestly, I have no idea how this happened :
>
> $ dpkg
You're right, but honestly, I have no idea how this happened :
$ dpkg -l systemd
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
|
État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscu
Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël:
> No I don't think I have one
> dpkg -l udev only shows udev and64
what about systemd? i386 or amd64
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenP
No I don't think I have one
dpkg -l udev only shows udev and64
2018-03-18 22:39 GMT+01:00 Michael Biebl :
> Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> > Looks like commenting out
> >
> > SystemCallArchitectures=native
> >
> > fixes the issue.
>
> Does that mean you have a udev:i386 instal
Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> Looks like commenting out
>
> SystemCallArchitectures=native
>
> fixes the issue.
Does that mean you have a udev:i386 installed on a amd64 system?
If so, that would basically be a duplicate of #869719
--
Why is it that all of the instrumen
Looks like commenting out
SystemCallArchitectures=native
fixes the issue.
2018-03-18 22:27 GMT+01:00 LEDUQUE Mickaël :
> I disabled them all and got a normal startup.
> Now I'll try to find the one (or more) that causes the problem.
> Thanks.
>
> 2018-03-18 21:48 GMT+01:00 Michael Biebl :
>
>>
I disabled them all and got a normal startup.
Now I'll try to find the one (or more) that causes the problem.
Thanks.
2018-03-18 21:48 GMT+01:00 Michael Biebl :
> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> > Package: systemd
> > Version: 238-2
> > Followup-For: Bug #893369
> >
> > It didn'
Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> Package: systemd
> Version: 238-2
> Followup-For: Bug #893369
>
> It didn't work so I just added the options in /etc/default/grub.
> Here are the journal and the systemctl list-jobs output (which is just "no
> jobs").
>
Ok, thanks.
Once you are
Package: systemd
Version: 238-2
Followup-For: Bug #893369
It didn't work so I just added the options in /etc/default/grub.
Here are the journal and the systemctl list-jobs output (which is just "no
jobs").
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers
Ok, I was more searching for a way to do it from inside grub itself, but
this will have to do.
2018-03-18 18:55 GMT+01:00 Michael Biebl :
> Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël:
> > I'll do all that, thanks. Do you know how I can set a correct keymap in
> > the grub "e" text editor ?
>
Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël:
> I'll do all that, thanks. Do you know how I can set a correct keymap in
> the grub "e" text editor ?
I don't. But this is literally the first google hit regarding that question
https://askubuntu.com/questions/751259/how-to-change-grub-command-line-
I'll do all that, thanks. Do you know how I can set a correct keymap in the
grub "e" text editor ?
2018-03-18 16:57 GMT+01:00 Michael Biebl :
> On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?=
> wrote:
> > Package: systemd
> > Version: 238-2
> > Severity: critical
> > Justific
On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?=
wrote:
> Package: systemd
> Version: 238-2
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> After an update and a restart of the system, boot fails. It enters a loop,
> where (apparently) s
Package: systemd
Version: 238-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
After an update and a restart of the system, boot fails. It enters a loop,
where (apparently) systemd-udevd fails to start and is retries for a certain
time.
After thaat, I am dropped into
18 matches
Mail list logo
