Your message dated Wed, 12 Aug 2026 08:03:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#1144085: RETRACTION: Kernel reversion: Intel 
Corporation Wireless 8265 / 8275 not recognized by kernel 6.12.100+deb13-amd64
has caused the Debian Bug report #1144085,
regarding Kernel reversion: Intel Corporation Wireless 8265 / 8275 not 
recognized by kernel 6.12.100+deb13-amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1144085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144085
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-6.12.100+deb13-amd64
Version: linux-image-6.12.100+deb13-amd64

In the current version of the kernel (6.12.100) Gnome NetworkManager applet 
doesn't detect any wifi hardware. It does detect my ethernet card (I tested 
this and it detected the connection), but not the wifi card. 

I reverted to the previous kernel in response to this and detected the wifi 
card as usual and I was (and am) able to use it. I'm reporting this as a kernel 
reversion because the problem seems to be with the updated kernel.

The package and version of the NetworkManager applet are:

Package: network-manager-applet/stable
Version: 1.36.0-3+b1 amd64 

The wifi card I have is:

Intel Corporation Wireless 8265 / 8275 (rev 78)

--- End Message ---
--- Begin Message ---
Hi,

On Tue, Aug 11, 2026 at 02:38:05AM +0000, mat-cp wrote:
> I wish to retract the earlier bug report. First, I misidentified the
> kernel update as 100, but in fact it was 101, not 100 (which was the
> previous version), and second, I just retested and it works fine. 
> 
> I don't know what was causing this, but I can state that it did
> repeatedly not work on the new kernel (which, again, is
> actually linux-image-6.12.101+deb13-amd64) after multiple reboots.
> However, it is now working. Sorry for the confusion!

Thanks for the followup, in this case I'm closing the bugreport.

Regards,
Salvatore

--- End Message ---

Reply via email to