Hi Greg
Thank you for taking the time to explain in detail.
> Sent: Monday, December 11, 2023 at 10:16 PM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Release process notes [WAS Need clarifications about how to
> deal with the installed
On Mon, Dec 11, 2023 at 02:35:07PM +0100, Stella Ashburne wrote:
> Suppose linux-image-6.1.0-15-amd64 is installed successfully and I reboot my
> device.
>
> A few days from now, I decide to remove linux-image-6.1.0-15-amd64 because it
> is buggy and so in a terminal, I type the commands:
>
>
Hi Andy
> Sent: Monday, December 11, 2023 at 3:13 PM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Release process notes [WAS Re: Need clarifications about how to deal
> with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1
Hi Andy
> Sent: Monday, December 11, 2023 at 3:20 PM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
> dpkg is low le
Hi Greg
> Sent: Monday, December 11, 2023 at 11:40 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
> On Mon, D
On 11 Dec 2023 04:31 +0100, from rewe...@gmx.com (Stella Ashburne):
> Someone on a social media platform stated that there are only two
> "canonical" [sic] ways to verify the version of Debian installed on
> a system. They are:
>
> uname -a
>
> /proc/version
>
> Do you agree with the above
fications about how to deal with the installed
> > problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
> >
> >
> > This combination is expected under the circumstances, assuming that
> > you mean /etc/debian_version. Booting into a different kernel does not
>
On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote:
> Hi Greg
>
> > Sent: Sunday, December 10, 2023 at 11:08 PM
> > From: "Greg Wooledge"
> > To: debian-user@lists.debian.org
> > Subject: Re: Need clarifications about how to deal with the
Hi Greg
> Sent: Monday, December 11, 2023 at 11:27 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> Well, th
On Mon, Dec 11, 2023 at 04:31:22AM +0100, Stella Ashburne wrote:
> Someone on a social media platform stated that there are only two "canonical"
> [sic] ways to verify the version of Debian installed on a system. They are:
>
> uname -a
>
> /proc/version
>
> Do you agree with the above
Hi Michael
> Sent: Sunday, December 10, 2023 at 9:29 PM
> From: "Michael Kjörling" <2695bd53d...@ewoof.net>
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux
On Mon, Dec 11, 2023 at 03:26:16AM +0100, Stella Ashburne wrote:
> What command did you use? Was it
>
> sudo dpkg -i linux-image-amd64_6.1.55-1_amd64.deb
Yes.
On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote:
> As of writing this reply, there's a new point release, 12.4.0
>
>
Hi Greg
> Sent: Sunday, December 10, 2023 at 11:08 PM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> Note that
Hi Greg
> Sent: Monday, December 11, 2023 at 2:06 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> In order
On Sun, Dec 10, 2023 at 10:08:21AM -0500, Greg Wooledge wrote:
> On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote:
> > That will work: you might also want to apt-get purge
> > linux-image-6.1.0-14-amd64
> > but you've done the main thing.
>
> Note that purging 6.1.0-14 will also
On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote:
> That will work: you might also want to apt-get purge
> linux-image-6.1.0-14-amd64
> but you've done the main thing.
Note that purging 6.1.0-14 will also remove the linux-image-amd64
metapackage, which has a hard dependency on
On Sun, Dec 10, 2023 at 01:48:52PM +0100, Stella Ashburne wrote:
> Hi,
>
> I am using Debian Bookworm, the current stable release with the whole SSD
> being encrypted with LUKS2. After decryption, the file system of the logical
> volume is ext4.
>
> This is what happened to my computer many
On 10 Dec 2023 13:48 +0100, from rewe...@gmx.com (Stella Ashburne):
> I highlight linux-image-6.1.0-13-amd64 and press Enter.
>
> After supply the decryption password and entering my desktop
> environment, I did the following:
>
> cat /etc/debian_user
> *Result* is 12.3, even though I boot using
Hi,
I am using Debian Bookworm, the current stable release with the whole SSD being
encrypted with LUKS2. After decryption, the file system of the logical volume
is ext4.
This is what happened to my computer many hours ago.
My device upgraded to the latest kernel, linux-image-6.1.0-14-amd64
19 matches
Mail list logo
