Bug#1079150: cryptsetop: Waiting for encrypted source device

On Tue, Sep 03, 2024 at 01:04:34PM GMT, Alejandro Colomar wrote: > Hi Ben, > > On Thu, Aug 22, 2024 at 02:29:02PM GMT, Ben Hutchings wrote: > > On Thu, 2024-08-22 at 13:43 +0200, Alejandro Colomar wrote: > > [...] > > > Should I open a separate bug? Or is it a

Bug#1079150: cryptsetop: Waiting for encrypted source device

Hi Ben, On Thu, Aug 22, 2024 at 02:29:02PM GMT, Ben Hutchings wrote: > On Thu, 2024-08-22 at 13:43 +0200, Alejandro Colomar wrote: > [...] > > Should I open a separate bug? Or is it a consequence of (a combination) > > of the current bugs? How should I fix it? > > It&#

Bug#1079333: initramfs-tools: upgrading causes dpkg(1) to fail

Hi Ben, On Thu, Aug 22, 2024 at 03:52:01PM GMT, Ben Hutchings wrote: > Control: reopen -1 > Control: severity -1 serious > > Sorry, I got confused by the multiple reports of this and thought you > had > opened two different bug reports for this. No problem. BTW, I chose critical, because now I

Bug#1079333: initramfs-tools: upgrading causes dpkg(1) to fail

Package: initramfs-tools Version: 0.144 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: a...@kernel.org Dear Maintainer, I've tried upgrading earlier today (`apt-get upgrade`), and had some error. I've rebooted just in case that would fix it, and then tried to `apt-get --

Bug#1079150: cryptsetop: Waiting for encrypted source device

Hi Ben, On Thu, Aug 22, 2024 at 01:06:37PM GMT, Ben Hutchings wrote: > Control: forcemerge 1079066 -1 > > On Thu, 2024-08-22 at 12:34 +0200, Alejandro Colomar wrote: > [...] > > It shows errors. > > > > $ sudo update-initramfs -u -k 6.10.4-amd64 > > update-in

Bug#1079150: cryptsetop: Waiting for encrypted source device

Hi Ben, On Thu, Aug 22, 2024 at 02:35:08AM GMT, Ben Hutchings wrote: > On Thu, 2024-08-22 at 01:11 +0200, Alejandro Colomar wrote: > > On Thu, Aug 22, 2024 at 12:46:00AM GMT, Ben Hutchings wrote: > > > Please send the output of this command: > > > > > >

Bug#1079150: cryptsetop: Waiting for encrypted source device

Hi Ben, On Thu, Aug 22, 2024 at 12:46:00AM GMT, Ben Hutchings wrote: > Please send the output of this command: > > lsinitramfs /boot/initrd.img-6.9.12-amd64 | grep /lib/modules | head I've purged 6.9.12, but I keep 6.10.4 --which is also broken--, so I've run it with that: $ lsinitr

Bug#1079150: Info received (Bug#1079150: Acknowledgement (cryptsetop: Waiting for encrypted source device))

I've seen that there are some new packages that are related to this bug. $ sudo apt-get dist-upgrade -V Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer

Bug#1079150: Acknowledgement (cryptsetop: Waiting for encrypted source device)

> 1079150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079150 Should I report this bug also against linux-image-amd64, or against the newer version, or is that automatically migrated? Cheers, Alex -- signature.asc Description: PGP signature

Bug#1079150: cryptsetop: Waiting for encrypted source device

Package: src:linux Version: 6.9.12-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: a...@kernel.org Dear Maintainer, I ran `apt-get upgrade` earlier today. I rebooted, since the update had a new kernel, and the system wouldn't boot with the new kernel. My old kernel was

Bug#1010458: linux/sysctl.h: unknown type name 'size_t'

Package: linux-libc-dev Version: 5.17.3-1 Severity: normal Tags: upstream X-Debbugs-Cc: alx.manpa...@gmail.com I was cleaning up the example programs in the man-pages by using iwyu(1), when I found that is using 'size_t' without including any definition for it. See the following example program

Bug#974166: 5.9.0-1-amd64 (5.9.11-1) has fixed the issue

Hi, I'm glad to say that just now I upgraded to the unstable kernel: $ sudo apt-get install linux-image-amd64 and now I can boot normally: $ uname -a Linux debian 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux I'm curious: I'd like to see the changelog and the code to see w

Bug#974166: I'd like to help

Hi, I suspect it may have to do with the 5th gen (Broadwell Desktop) only, as they have a very special (and powerful) iGPU. And maybe that's why the bug passed inadvertently so much time: those CPUs didn't sell very well. Yes, I have that package installed: ||/ NameVersion Archi

Bug#974166: I'd like to help

Hi, I received no answer at all, so I guess you are very busy. I know the bug was introduced somewhere between 5.6 and 5.7. If you have an idea of what the source of the bug could be, I'd like to help by testing on my computers, or providing code. I have two computers with similar CPUs (i5-5675

Bug#974166: Boot logs

I tried booting in recovery mode, and it also didn't work. However, I could see the some info. The 3 last lines of the boot log were: { [4.817936] hub 4-0:1.0: 2 ports detected [4.819372] i915 :00:02.0: [drm] Found 128MB of eDRAM [4.819882] fb0: switching to inteldrmfb from EFI VG

Bug#974166: linux/5.9.6-1 (unstable) has the same bug

I tried installing the new kernel from unstable, but I still can't boot with it. Same problems.

Bug#974166: linux-image-5.9.0-1-amd64: The system goes black when trying to boot graphical mode

Package: src:linux Version: 5.9.1-1 Severity: important X-Debbugs-Cc: alx.manpa...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? When I upgreeaded from kernel 5.6 to 5.7 a long time ago, my sy