On Fri, 28 Dec 2018 12:00:14 +0100
Michael Biebl wrote:
> Am 28.12.18 um 07:04 schrieb Ben Hutchings:
>
> > And if you downgrade udev and libudev1 to version 239-15, that will
> > trigger an update of the 4.19 initramfs (only) and you should then be
> > able to boot with Linux 4.19.
>
> Or
Am 28.12.18 um 07:04 schrieb Ben Hutchings:
> And if you downgrade udev and libudev1 to version 239-15, that will
> trigger an update of the 4.19 initramfs (only) and you should then be
> able to boot with Linux 4.19.
Or upgrade to udev 240-2, which should fix this issue.
signature.asc
On Wed, 2018-12-26 at 21:57 -0500, Celejar wrote:
> On Wed, 26 Dec 2018 15:39:19 +
> Ben Hutchings wrote:
>
> > On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote:
> > > On Tue, 25 Dec 2018 20:52:46 +
> > > Ben Hutchings wrote:
> > >
> > > > Control: reassign -1 udev 240-1
> > > >
On Wed, 26 Dec 2018 15:39:19 +
Ben Hutchings wrote:
> On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote:
> > On Tue, 25 Dec 2018 20:52:46 +
> > Ben Hutchings wrote:
> >
> > > Control: reassign -1 udev 240-1
> > > Control: forcemerge 917124 -1
> > >
> > > This seems to be a bug
On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote:
> On Tue, 25 Dec 2018 20:52:46 +
> Ben Hutchings wrote:
>
> > Control: reassign -1 udev 240-1
> > Control: forcemerge 917124 -1
> >
> > This seems to be a bug in udev, not the kernel. You will only have
> > noticed it once you
On Tue, 25 Dec 2018 20:52:46 +
Ben Hutchings wrote:
> Control: reassign -1 udev 240-1
> Control: forcemerge 917124 -1
>
> This seems to be a bug in udev, not the kernel. You will only have
> noticed it once you rebooted for the kernel upgrade.
Nope - in my system's current state, when
Control: reassign -1 udev 240-1
Control: forcemerge 917124 -1
This seems to be a bug in udev, not the kernel. You will only have
noticed it once you rebooted for the kernel upgrade.
Ben.
--
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.
Hi!
I have the same issue. Not sure the problem is with the kernel package though,
because even purging and/or reinstalling linux-image-4.18.0-3 fails (see
below). Any suggestion which package may be responsible? The problem started
after a dist-upgrade on Dec 24...
Thanks!
Tiziano
#
Package: src:linux
Version: 4.19.12-1
Severity: important
Hi,
[I'm not sure whether this is the right package to report against - feel
free to reassign as appropriate.]
I have / on a luks volume, mounted with dm-crypt (automatically,
via /etc/fstab - /etc/crypttab). As recently as kernel
9 matches
Mail list logo