Integrated webcam is not sending back image

Final Update: I ran some hardware tests without booting into the OS and it seems that it's a purely hardware problem (some internal connections may broke off), thus this question is now closed

Whenever I launch cheese (or similar programs), the light on the webcam lights up, but no images were sent back.

My hardware is a Dell Inspiron 14-3442, and software Kubuntu 20.04

Here are output of some commands:

• lsusb

Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 8087:07dc Intel Corp. 
Bus 001 Device 003: ID 0c45:670b Microdia 
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 24ae:2010 RAPOO Rapoo 2.4G Wireless Device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I suppose that 0c45:670b is the camera, but it seems that this has been supported in the kernel since the 2.x era.

Verbose output (lsusb -v) here

• dmesg | grep usb

This is a little long so I posted it here

If more info is needed please ask me.

Update #1: lspci:

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)
08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1)

Update #2: I had searched nearly every driver db that google told me, none of them included my model. But this is a 2018 laptop, not that antique, so why can't I find anything about it?

Update #3: dmesg | grep -i video

[    0.138785] ACPI: Added _OSI(Linux-Dell-Video)
[    0.319659] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.951453] videodev: Linux video capture interface: v2.00
[    1.068811] ACPI: Video Device [PEGP] (multi-head: yes  rom: yes  post: no)
[    1.069045] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/LNXVIDEO:00/input/input7
[    1.116118] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.116337] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input13
[    6.009940] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0c45:670b)
[    6.064805] usbcore: registered new interface driver uvcvideo
[    6.064806] USB Video Class driver (1.1.1)

Many device access problems can be resolved through group membership changes.

Specifically, if ls -l shows that the group permissions (the second "rwx" triplet) is "rw" (e.g."-rw-rw----"), then, adding oneself to the group that owns the device will grant rw access.

Here's how:

device="/dev/whatever"
sudo adduser $USER $(stat -c "%G" $device)

This allows you membership in the group that can rw the device, but there is one more step.

To make all your processes members of the new group, logout and login. Group memberships are set up at login time.

To create a single process in the new group (for testing, prior to logout/login):

newgrp $(stat -c "%G" $device)  

or, just type the group name. See man newgrp.