When I turn off the computer, the mouse light and the num lock button I switched on are still on and will not turn off when the computer is turned off.
This bug has been present in version 2.6.33 to date. The bug report by Bruno Jacquet also indicates a problem that has existed since 2010 and has been reported id = 15770
We need more information. I assume this is not a notebook/laptop. Is that correct?
If a desktop, are the keyboard and mouse connected wirelessly? What drivers are used for those devices?
Please post the dmesg output from a short run.
Yes, it's not a notebook or laptop, it's a desktop
The keyboard and mouse are USB
I do not use any drivers
This problem exists in all GNU Linux distributions. If you have a desktop system, you can test it.
I use Kali distribution as a live boot
This is a problem even if I install this distribution
Created attachment 288213 [details]
dmesg For USBs
Was this attachment what you wanted? Did I send it correctly?
I think this is a problem with the Linux kernel programming code
Let's solve this problem once and for all
I suspect that your system is remaining in a low-power state waiting for an event to wake it up, and not really in full shutdown. See Documentation/driver-api/pm/devices.rst, particularly the paragraph below:
The initial value in the :file:`power/wakeup` file is "disabled" for the
majority of devices; the major exceptions are power buttons, keyboards, and
Ethernet adapters whose WoL (wake-on-LAN) feature has been set up with ethtool.
It should also default to "enabled" for devices that don't generate wakeup
requests on their own but merely forward wakeup requests from one bus to another
(like PCI Express ports).
Does your BIOS have a setting to control USB power for wakeup?
After shutdown, do those lights remain on when you cut the power to the computer?
My BIOS does not have such settings
When I disconnect the power cord from the computer
The mouse light turns off after 8 seconds, as well as the keyboard
The problem seems to be in this direction. By changing the programming files in this place, the problem can be solved.
*** Bug 207405 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 15770 ***