Camera not working after the last system update (2026-08-23)

[jotabe]

Since the last system update (stable update 2026-08-23), the camera isn’t working correctly in any program (the camera activates but the image isn’t displayed). This happens on both my computers: a desktop PC with an external camera connected via USB, and a laptop with an integrated camera, and it affects both the KDE and XFCE desktop environments. Before this update, the camera worked fine in all programs.
If I revert the update (using Timeshift), the camera image is displayed correctly again. Is anyone else experiencing this or know of a possible solution? Thank you very much.

[soundofthunder]

@jotabe

Is anyone else experiencing this

I’m not. I’m not aware of any other reports, which doesn’t mean there won’t be.

Please provide your system information in accordance with forum guidelines – See the Mini-HowTo’s (below) – Perhaps others with similar systems might experience something similar.

---

[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:

---

Suggested inxi command (use either):

inxi -zv8	(short-form)
inxi --filter --verbosity=8	(long-form)

• man inxi (The inxi manual)

---

Command output should be presented as pre-formatted text in accordance with forum guidelines.

---

Running inxi within a chroot environment

• Add --color=0 to the long-form command, or…
• Change the short-form command to inxi -zv8c0

Your privacy is respected

Run inxi using the --filter or -z parameters: personally identifiable information is filtered from the resulting output.

---

[Mini-HowTo] Present code or command output

Code or command output is expected to be presented similarly to how it would appear in a text editor (monospaced). The Discourse forum software makes it easy to create an enclosure (a text box) that is already pre-formatted for this purpose.

Note: Grave accent (or, backtick) characters are used.

For inline code or to show a single command:

• please follow this simple example: code here.

For multi-line command output:

• place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
• use the </> button in the Compose window to achieve the same result.

Important: Click the </> button and paste text between the backticks (if using the old Compose layout). Otherwise, paste into the box generated (if using the new Compose layout).

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.

---

[BG405]

Hello @jotabe and welcome to the Manjaro Community!

Whilst I might not be able to help with your specific issue (I haven’t experienced this yet myself), it will help if you can furnish us with some System Information.

To this end, could you provide the output of this Terminal command? (quick guide below):

inxi -zv8

Note that the output produced by this command is privacy-filtered.

Please also remember to use proper code formatting as this makes it much easier to read on the Forum:

[Mini How-To] format code or command output

Select and copy all the text in the Terminal window (minus the prompt, if you are using zsh).
Then paste the output in between two lines containing three backticks
```
or three tildes
~~~

Or:
Copy & paste, then highlight the pasted text and click the </> button at the top of the reply window (easier for smaller outputs).

Cheers!

[Teo]

I don’t have it too. So it is probably driver related, in which case the exact hardware is relevant. Besides inxi, lsusb can also be useful for troubleshooting.

Also note that sometimes several “fake cameras” are available in theory in the apps - i have 3 according to the video4linux driver, but of course only one, the real one, works. Be sure to check the drop down menu in the app and check for other devices.

[jotabe]

Thank you for your responses and interest. Here is the inxi output on my desktop computer:

❯ inxi -zv8
System:
  Kernel: 6.18.45-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
    root=UUID=6d6ae727-21c3-463c-a677-b46950b9d916 rw quiet splash
    udev.log_priority=3 resume=UUID=31f4b41c-9198-4ebe-9faf-d07f32ab7a9d
  Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A info: frameworks v: 6.29.0
    wm: kwin_wayland vt: 2 dm: N/A Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B760M-PLUS II v: Rev 1.xx
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 1836 date: 04/16/2026
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
Memory:
  System RAM: total: 32 GiB available: 31.09 GiB used: 3.94 GiB (12.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 256 GiB slots: 4 modules: 2 EC: None
    max-module-size: 64 GiB note: est.
  Device-1: Controller0-DIMM0 type: no module installed
  Device-2: Controller0-DIMM1 type: DDR5 detail: synchronous size: 16 GiB
    speed: 4800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: Corsair part-no: CMK32GX5M2B6400C32
    serial: N/A
  Device-3: Controller1-DIMM0 type: no module installed
  Device-4: Controller1-DIMM1 type: DDR5 detail: synchronous size: 16 GiB
    speed: 4800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: Corsair part-no: CMK32GX5M2B6400C32
    serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-14700F bits: 64 type: MST AMCP arch: Raptor Lake
    gen: core 14 level: v3 note: check built: 2022+ process: Intel 7 (10nm)
    family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x137
  Topology: cpus: 1x dies: 1 clusters: 11 cores: 20 threads: 28 mt: 8 tpc: 2
    st: 12 smt: enabled cache: L1: 1.8 MiB desc: d-12x32 KiB, 8x48 KiB; i-8x32
    KiB, 12x64 KiB L2: 28 MiB desc: 8x2 MiB, 3x4 MiB L3: 33 MiB desc: 1x33 MiB
  Speed (MHz): avg: 800 min/max: 800/5300:5400:4200 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
    15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800 22: 800 23: 800
    24: 800 25: 800 26: 800 27: 800 28: 800 bogomips: 118272
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
    rdtscp rep_good sdbg sep serialize sha_ni smap smep split_lock_detect ss
    ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
    tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme vmx
    vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA AD104 [GeForce RTX 4070 SUPER] vendor: Micro-Star MSI
    driver: nvidia v: 610.57.04 alternate: nouveau,nova_core,nvidia_drm
    non-free: 550-6xx.xx+ status: current (as of 2026-07) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 1
    speed: 2.5 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2783
    class-ID: 0300
  Device-2: Guillemot Hercules Dualpix Infinite
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-10.1:11 chip-ID: 06f8:300a class-ID: 0102
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) ULTRAGEAR serial: <filter>
    built: 2024 res: mode: 2560x1440 hz: 165 scale: 100% (1) dpi: 108 gamma: 1.2
    chroma: red: x: 0.686 y: 0.310 green: x: 0.263 y: 0.671 blue: x: 0.149
    y: 0.055 white: x: 0.314 y: 0.329 size: 697x392mm (27.44x15.43")
    diag: 690mm (27.2") ratio: 16:9 modes: 2560x1440, 1920x1080, 1280x720,
    1024x768, 800x600, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 610.57.04
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070
    SUPER/PCIe/SSE2 memory: 11.71 GiB display-ID: :0.0
  API: Vulkan v: 1.4.357 layers: 6 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 4070 SUPER driver: nvidia v: 610.57.04 device-ID: 10de:2783
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 700 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
  Device-2: NVIDIA AD104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
  Device-3: Guillemot Hercules Dualpix Infinite
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-10.1:11 chip-ID: 06f8:300a class-ID: 0102
  API: ALSA v: k6.18.45-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: ASUSTek Bluetooth Controller driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 0b05:1bef
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel RST Volume Management Device Controller driver: vmd v: 0.6
    port: N/A bus-ID: 00:0e.0 chip-ID: 8086:a77f rev: class-ID: 0104
Drives:
  Local Storage: total: 7.73 TiB used: 3.01 TiB (38.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT2000T500SSD8
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P8CR004 temp: 47.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:15 vendor: Crucial model: CT2000T500SSD8
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P8CR003 temp: 51.9 C
    scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:18 vendor: Samsung
    model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 33.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Crucial model: CT4000MX500SSD1
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 80 GiB size: 78.19 GiB (97.74%) used: 29.05 GiB (37.2%)
    fs: ext4 dev: /dev/nvme0n1p9 maj-min: 259:9 label: MjroKDEroot
    uuid: 6d6ae727-21c3-463c-a677-b46950b9d916
  ID-2: /boot/efi raw-size: 2 GiB size: 2 GiB (99.80%)
    used: 744.7 MiB (36.4%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: EFI uuid: FA1B-E465
  ID-3: /home raw-size: 80 GiB size: 78.19 GiB (97.74%)
    used: 33.56 GiB (42.9%) fs: ext4 dev: /dev/nvme0n1p10 maj-min: 259:10
    label: MjroKDEhome uuid: 077b177b-fa32-451b-9b24-3fba59616374
  ID-4: /media/Datos raw-size: 931.5 GiB size: 916.69 GiB (98.41%)
    used: 274.65 GiB (30.0%) fs: ext4 dev: /dev/nvme0n1p14 maj-min: 259:14
    label: Datos uuid: 66c20865-b291-4af2-a0ba-49e2dbb53643
  ID-5: /media/Games raw-size: 1.5 TiB size: 1.48 TiB (98.36%)
    used: 1.38 TiB (93.4%) fs: ext4 dev: /dev/nvme1n1p1 maj-min: 259:16
    label: Games uuid: a77aebab-6b5b-4c98-ba5c-d077fdb0edbd
  ID-6: /media/Media raw-size: 1.5 TiB size: 1.48 TiB (98.42%)
    used: 1.3 TiB (88.0%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: Media
    uuid: b0e566c2-00ce-4aa3-92c9-2e840a9e79cc
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 32.54 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: 31f4b41c-9198-4ebe-9faf-d07f32ab7a9d
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-2:2 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:19af class-ID: 0300
    serial: <filter>
  Device-2: 1-6:3 info: ASUSTek Bluetooth Controller type: bluetooth
    driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 0b05:1bef class-ID: e001
  Hub-2: 1-9:4 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-9.1:6 info: American Power Conversion Uninterruptible Supply
    type: HID driver: hid-generic,usbhid interfaces: 1 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 2mA
    chip-ID: 051d:0002 class-ID: 0300 serial: <filter>
  Hub-3: 1-10:5 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 174c:2074 class-ID: 0900
  Device-1: 1-10.1:11 info: Guillemot Hercules Dualpix Infinite
    type: video,audio driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 168mA
    chip-ID: 06f8:300a class-ID: 0102
  Hub-4: 1-10.3:7 info: Texas Instruments TUSB8041 4-Port Hub ports: 4
    rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0451:8142
    class-ID: 0900
  Device-1: 1-10.3.2:8 info: CX 2.4G Receiver type: keyboard,mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 3554:fc05 class-ID: 0301
  Device-2: 1-10.3.3:9 info: Logitech Nano Receiver type: keyboard,mouse
    driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c534 class-ID: 0301
  Device-3: 1-10.3.4:10 info: LG USA 27UP850 - WK.AEUDCSN External Monitor
    4K type: HID driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 043e:9a39
    class-ID: 0300 serial: <filter>
  Hub-5: 2-0:1 info: super-speed hub ports: 9 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 2-9:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
    chip-ID: 174c:3074 class-ID: 0900
  Hub-7: 2-9.3:3 info: Texas Instruments TUSB8041 4-Port Hub ports: 4
    rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1
    chip-ID: 0451:8140 class-ID: 0900
Sensors:
  System Temperatures: cpu: 42.0 C mobo: 46.0 C
  Fan Speeds (rpm): fan-1: 1048 fan-2: 843 fan-3: 0 fan-4: 1024 fan-5: 1057
    fan-6: 0 fan-7: 0
Repos:
  Packages: pm: pacman pkgs: 1501 libs: 413 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    2: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    3: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    4: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    5: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    6: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    8: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 448
  1: cpu: 18.9% command: librewolf pid: 2016 mem: 849.0 MiB (2.6%)
  2: cpu: 18.2% command: Telegram pid: 8793 mem: 738.1 MiB (2.3%)
  3: cpu: 15.0% command: kwin_wayland pid: 1247 mem: 311.6 MiB (0.9%)
  4: cpu: 13.9% command: librewolf pid: 2952 mem: 390.5 MiB (1.2%)
  5: cpu: 6.8% command: konsole pid: 11338 mem: 136.6 MiB (0.4%)
  Memory top: 5 of 448
  1: mem: 849.0 MiB (2.6%) command: librewolf pid: 2016 cpu: 18.9%
  2: mem: 738.1 MiB (2.3%) command: Telegram pid: 8793 cpu: 18.2%
  3: mem: 613.7 MiB (1.9%) command: plasmashell pid: 1357 cpu: 6.0%
  4: mem: 400.2 MiB (1.2%) command: librewolf pid: 3151 cpu: 0.1%
  5: mem: 390.5 MiB (1.2%) command: librewolf pid: 2952 cpu: 13.9%
Info:
  Processes: 448 Power: uptime: 1h 21m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.33 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 261 default: graphical
    tool: systemctl
  Compilers: gcc: 16.2.1 Shell: Zsh v: 5.9.2 running-in: konsole
    inxi: 3.3.41

After running some tests, I’ve found that the issue seems to be with certain programs rather than the cameras:

Cameractrls fails to open, and kamoso shows a black video window even though it’s able to take photos and record video (and the resulting photo or video files can be viewed correctly afterward, even though the kamoso video window was black while they were being captured)

These issues occur after the 2026-08-23 system update with both of my USB webcams (a Logitech BRIO 4K and a Hercules Dualpix Infinity), on both my desktop computer and my Lenovo laptop (where they also fail using the built-in camera).

However, programs like guvcview or OBS continue working without issues and show the image correctly on the video window so it appears that the problem isn’t with the cameras, but rather that some programs fail to run properly after the latest system update.

This is the console output when I run cameractrls:

❯ cameractrls
/usr/bin/cameractrls:297: DeprecationWarning: Due to '_pack_', the 'v4l2_plane_pix_format' Structure will use memory layout compatible with MSVC (Windows). If this is intended, set _layout_ to 'ms'. The implicit default is deprecated and slated to become an error in Python 3.19.
  class v4l2_plane_pix_format(ctypes.Structure):
/usr/bin/cameractrls:306: DeprecationWarning: Due to '_pack_', the 'v4l2_pix_format_mplane' Structure will use memory layout compatible with MSVC (Windows). If this is intended, set _layout_ to 'ms'. The implicit default is deprecated and slated to become an error in Python 3.19.
  class v4l2_pix_format_mplane(ctypes.Structure):
/usr/bin/cameractrls:821: DeprecationWarning: Due to '_pack_', the 'v4l2_querymenu' Structure will use memory layout compatible with MSVC (Windows). If this is intended, set _layout_ to 'ms'. The implicit default is deprecated and slated to become an error in Python 3.19.
  class v4l2_querymenu(ctypes.Structure):
usage: /usr/bin/cameractrls [--help] [-d DEVICE] [--list] [-c CONTROLS]

optional arguments:
  -h, --help         show this help message and exit
  -d DEVICE          use DEVICE, default /dev/video0
  -l, --list         list the controls and values
  -L, --list-devices list capture devices
  -c CONTROLS        set CONTROLS (eg.: hdr=on,fov=wide)

example:
  /usr/bin/cameractrls -c brightness=128,kiyo_pro_hdr=on,kiyo_pro_fov=wide

It show warning messages but I don’t know how to interpret or correct them. Cameractrls is a great program with more options than others to set the camera controls, and I would like to continue using it. Any help or suggestion will be welcome.

[Teo]

And what does cameractrls -L list?

[jotabe]

❯ cameractrls -L
/usr/bin/cameractrls:297: DeprecationWarning: Due to '_pack_', the 'v4l2_plane_pix_format' Structure will use memory layout compatible with MSVC (Windows). If this is intended, set _layout_ to 'ms'. The implicit default is deprecated and slated to become an error in Python 3.19.
  class v4l2_plane_pix_format(ctypes.Structure):
/usr/bin/cameractrls:306: DeprecationWarning: Due to '_pack_', the 'v4l2_pix_format_mplane' Structure will use memory layout compatible with MSVC (Windows). If this is intended, set _layout_ to 'ms'. The implicit default is deprecated and slated to become an error in Python 3.19.
  class v4l2_pix_format_mplane(ctypes.Structure):
/usr/bin/cameractrls:821: DeprecationWarning: Due to '_pack_', the 'v4l2_querymenu' Structure will use memory layout compatible with MSVC (Windows). If this is intended, set _layout_ to 'ms'. The implicit default is deprecated and slated to become an error in Python 3.19.
  class v4l2_querymenu(ctypes.Structure):
"BRIO 4K Stream Edition (/dev/video0)" at /dev/v4l/by-id/usb-046d_BRIO_4K_Stream_Edition_C42AB180-video-index0 -> /dev/video0
"Integrated Camera: Integrated C (/dev/video2)" at /dev/v4l/by-id/usb-Azurewave_Integrated_Camera-video-index0 -> /dev/video2

[Teo]

So you have 2 cameras, built-in and usb? Which one doesn’t work?

[jotabe]

I copied the output of cameracrtls -L from my Lenovo laptop, which has an integrated Azurewave camera and an external Logitech BRIO 4K camera connected via USB.

As I mentioned in my second post, I was able to confirm that the problem isn’t with the cameras themselves; both are working correctly. (I also tested another USB camera, a Hercules Infinity Dualpix, with the same result.)

The issue lies with some applications, such as kamoso (which displays a completely black image window even though the camera is working and taking photos correctly, which I can then view).

And in the case of cameracrtls (the program I usually use to configure the camera), it seems to fail to run and crashes before the program window even opens. Based on the warning messages, could there be a problem with Python and this program since the last system update? Before the update, it ran without any issues.

[Teo]

Cameractrls indeed does not start anymore, i just tested. A bit strange, since those are warnings, not yet errors. Maybe there is something else.
I guess until it is fixed you will have to use another app for configuring the camera. Try Qt v4l2 test utility.

When is new tag getting released, arch package is broken on current version with new python update

The flatpak may be still working, it is worth testing.

Cameractrls unter Linux installieren | Flathub

[jotabe]

Thank you very much for the replies. I see that the Python problem is affecting other packages and users as well. I will use Qtv4l2 (I prefer it to using cameractrls flatpak) to configure the camera until cameractrls can run without problems again.