Camera not working

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
First things first, sorry for my English.
I updated my POP-OS to version 22.04 and my camera stopped working.
When I open a camera application, most of the time, the led on the side of the camera flashes once, but the camera doesn't work.

This is part of the syslog file:
Bash:
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) config/udev: Adding input device Integrated Camera: Integrated C (/dev/input/event5)
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (**) Integrated Camera: Integrated C: Applying InputClass "libinput keyboard catchall"
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) Using input driver 'libinput' for 'Integrated Camera: Integrated C'
May 16 18:01:03 pop-os mtp-probe: checking bus 1, device 19: "/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4"
May 16 18:01:03 pop-os mtp-probe: bus: 1, device: 19 was not an MTP device
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 90 paused 0
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (**) Integrated Camera: Integrated C: always reports core events
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (**) Option "Device" "/dev/input/event5"
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) event5  - Integrated Camera: Integrated C: is tagged by udev as: Keyboard
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) event5  - Integrated Camera: Integrated C: device is a keyboard
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) event5  - Integrated Camera: Integrated C: device removed
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4/1-4:1.0/input/input29/event5"
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) XINPUT: Adding extended input device "Integrated Camera: Integrated C" (type: KEYBOARD, id 9)
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (**) Option "xkb_layout" "it"
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) event5  - Integrated Camera: Integrated C: is tagged by udev as: Keyboard
May 16 18:01:03 pop-os /usr/libexec/gdm-x-session[3812]: (II) event5  - Integrated Camera: Integrated C: device is a keyboard
May 16 18:01:03 pop-os gnome-shell[4483]: Window manager warning: Overwriting existing binding of keysym 6f with keysym 6f (keycode 20).
May 16 18:01:42 pop-os wpa_supplicant[871]: wlp2s0: WPA: Group rekeying completed with b8:d5:26:67:fa:ce [GTK=CCMP]
May 16 18:01:42 pop-os wpa_supplicant[871]: wlp2s0: WPA: Group rekeying completed with b8:d5:26:67:fa:ce [GTK=CCMP]
May 16 18:04:47 pop-os gnome-shell[4483]: Could not create transient scope for PID 41109: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 41109 does not exist.
May 16 18:04:48 pop-os systemd[3756]: Started Application launched by gnome-shell.
May 16 18:04:48 pop-os kernel: [14432.164389] usb 1-4: USB disconnect, device number 19
May 16 18:04:48 pop-os pipewire[3766]: spa.v4l2: '/dev/video5' VIDIOC_STREAMON: Errore di protocollo
May 16 18:04:48 pop-os pipewire[3766]: pw.node: (v4l2_input.pci-0000_04_00.3-usb-0_4_1.0-67) suspended -> error (Start error: Errore di protocollo)
May 16 18:04:48 pop-os pipewire[3766]: spa.v4l2: VIDIOC_REQBUFS: Nessun device corrisponde
May 16 18:04:48 pop-os /usr/libexec/gdm-x-session[3812]: (II) event5  - Integrated Camera: Integrated C: device removed
May 16 18:04:48 pop-os /usr/libexec/gdm-x-session[3812]: (II) config/udev: removing device Integrated Camera: Integrated C

This is the camera (lsusb):
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0cf3:e500 Qualcomm Atheros Communications
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 020: ID 174f:2426 Syntek Integrated Camera
Bus 001 Device 007: ID 0951:1643 Kingston Technology DataTraveler G3
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

from xinput list-props 9
Bash:
Device 'Integrated Camera: Integrated C':
    Device Enabled (156):    1
    Coordinate Transformation Matrix (158):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    libinput Send Events Modes Available (279):    1, 0
    libinput Send Events Mode Enabled (280):    0, 0
    libinput Send Events Mode Enabled Default (281):    0, 0
    Device Node (282):    "/dev/input/event5"
    Device Product ID (283):    5967, 9254

in udevadm info -a /dev/input/by-id/* only these lines seem to be related to the camera.
Bash:
looking at device '/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4/1-4:1.0/input/input30/event5':
    KERNEL=="event5"
    SUBSYSTEM=="input"
    DRIVER==""
    ATTR{power/async}=="disabled"
    ATTR{power/control}=="auto"
    ATTR{power/runtime_active_kids}=="0"
    ATTR{power/runtime_active_time}=="0"
    ATTR{power/runtime_enabled}=="disabled"
    ATTR{power/runtime_status}=="unsupported"
    ATTR{power/runtime_suspended_time}=="0"
    ATTR{power/runtime_usage}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4/1-4:1.0/input/input30':
    KERNELS=="input30"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{capabilities/abs}=="0"
    ATTRS{capabilities/ev}=="3"
    ATTRS{capabilities/ff}=="0"
    ATTRS{capabilities/key}=="100000 0 0 0"
    ATTRS{capabilities/led}=="0"
    ATTRS{capabilities/msc}=="0"
    ATTRS{capabilities/rel}=="0"
    ATTRS{capabilities/snd}=="0"
    ATTRS{capabilities/sw}=="0"
    ATTRS{id/bustype}=="0003"
    ATTRS{id/product}=="2426"
    ATTRS{id/vendor}=="174f"
    ATTRS{id/version}=="0108"
    ATTRS{inhibited}=="0"
    ATTRS{name}=="Integrated Camera: Integrated C"
    ATTRS{phys}=="usb-0000:04:00.3-4/button"
    ATTRS{power/async}=="disabled"
    ATTRS{power/control}=="auto"
    ATTRS{power/runtime_active_kids}=="0"
    ATTRS{power/runtime_active_time}=="0"
    ATTRS{power/runtime_enabled}=="disabled"
    ATTRS{power/runtime_status}=="unsupported"
    ATTRS{power/runtime_suspended_time}=="0"
    ATTRS{power/runtime_usage}=="0"
    ATTRS{properties}=="0"
    ATTRS{uniq}==""

  looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4/1-4:1.0':
    KERNELS=="1-4:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="uvcvideo"
    ATTRS{authorized}=="1"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bInterfaceClass}=="0e"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceProtocol}=="00"
    ATTRS{bInterfaceSubClass}=="01"
    ATTRS{bNumEndpoints}=="01"
    ATTRS{iad_bFirstInterface}=="00"
    ATTRS{iad_bFunctionClass}=="0e"
    ATTRS{iad_bFunctionProtocol}=="00"
    ATTRS{iad_bFunctionSubClass}=="03"
    ATTRS{iad_bInterfaceCount}=="02"
    ATTRS{interface}=="Integrated Camera"
    ATTRS{power/async}=="enabled"
    ATTRS{power/runtime_active_kids}=="0"
    ATTRS{power/runtime_enabled}=="enabled"
    ATTRS{power/runtime_status}=="suspended"
    ATTRS{power/runtime_usage}=="0"
    ATTRS{supports_autosuspend}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4':
    KERNELS=="1-4"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="ef"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bDeviceSubClass}=="02"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="500mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 2"
    ATTRS{bcdDevice}=="0108"
    ATTRS{bmAttributes}=="80"
    ATTRS{busnum}=="1"
    ATTRS{configuration}=="USB Camera"
    ATTRS{devnum}=="20"
    ATTRS{devpath}=="4"
    ATTRS{idProduct}=="2426"
    ATTRS{idVendor}=="174f"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="201406250001"
    ATTRS{maxchild}=="0"
    ATTRS{power/active_duration}=="12928"
    ATTRS{power/async}=="enabled"
    ATTRS{power/autosuspend}=="2"
    ATTRS{power/autosuspend_delay_ms}=="2000"
    ATTRS{power/connected_duration}=="1135768"
    ATTRS{power/control}=="auto"
    ATTRS{power/level}=="auto"
    ATTRS{power/persist}=="1"
    ATTRS{power/runtime_active_kids}=="0"
    ATTRS{power/runtime_active_time}=="13107"
    ATTRS{power/runtime_enabled}=="enabled"
    ATTRS{power/runtime_status}=="suspended"
    ATTRS{power/runtime_suspended_time}=="1122381"
    ATTRS{power/runtime_usage}=="0"
    ATTRS{product}=="Integrated Camera"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="fixed"
    ATTRS{rx_lanes}=="1"
    ATTRS{serial}=="200901010001"
    ATTRS{speed}=="480"
    ATTRS{tx_lanes}=="1"
    ATTRS{urbnum}=="100"
    ATTRS{version}==" 2.00"

the driver modinfo uvcvideo :
Bash:
filename:       /lib/modules/5.17.5-76051705-generic/kernel/drivers/media/usb/uvc/uvcvideo.ko
version:        1.1.1
license:        GPL
description:    USB Video Class driver
author:         Laurent Pinchart <[email protected]>
srcversion:     794FD697E7B928D12C9D1C6
alias:          usb:v*p*d*dc*dsc*dp*ic0Eisc01ip01in*
alias:          usb:v*p*d*dc*dsc*dp*ic0Eisc01ip00in*
...
alias:          usb:v045Ep00F8d*dc*dsc*dp*ic0Eisc01ip00in*
alias:          usb:v0458p706Ed*dc*dsc*dp*ic0Eisc01ip00in*
alias:          usb:v0416pA91Ad*dc*dsc*dp*ic0Eisc01ip00in*
depends:        videobuf2-v4l2,videodev,videobuf2-common,videobuf2-vmalloc,mc
retpoline:      Y
name:           uvcvideo
vermagic:       5.17.5-76051705-generic SMP preempt mod_unload modversions
parm:           clock:Video buffers timestamp clock
parm:           hwtimestamps:Use hardware timestamps (uint)
parm:           nodrop:Don't drop incomplete frames (uint)
parm:           quirks:Forced device quirks (uint)
parm:           trace:Trace level bitmask (uint)
parm:           timeout:Streaming control requests timeout (uint)

v4l2-ctl --list-devices
This is my fault. Originally there were video0 and video1, but the response to the command was no different from this. So I tried to remove video0 and the system created these two new numbers.
Bash:
Integrated Camera: Integrated C (usb-0000:04:00.3-4):
    /dev/video5
    /dev/video7
    /dev/media0

Cannot open device /dev/video0, exiting.
sudo guvcview
Bash:
...
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (VIDIOC_REQBUFS) Failed to delete buffers: Dispositivo o risorsa occupata (errno 16)
V4L2_CORE: failed to unsubscribe events: Nessun device corrisponde

I don't know a lot about Linux, and for this reason, I just inserted a lot of output that appears to be related, hoping for help.
 


Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,665
Reaction score
1,113
Credits
12,440
Integrated Camera: Integrated C: is tagged by udev as: Keyboard
libinput doesn't always recognize hardware properly which seems to be your problem

Need to create a new udev rule

Code:
sudo {text editor of choice} /etc/udev/rules.d/90-blacklist-webcam-keyboard.rules
In that file, record the driver, manufacturer ID, and product ID in a format like this: which I based on the info you supplied so it should be correct

# Not a keyboard!
SUBSYSTEM=="usb", DRIVER=="libinput", ATTRS{idVendor}=="174f", ATTRS{idProduct}=="2426", ATTR{authorized}="0"

Save the file

reboot - does it work
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
Thank you for the straight-to-the-point answer, but it doesn't work. The reason, I think, is that the result of the command: udevadm info -a /dev/input/by-id/* |grep libinput is null.
For this reason, your command didn't make any change, and libinput is still called.
In the log file, this is related to the libinput call:
Bash:
LoadModule: "libinput"
Loading /usr/lib/xorg/modules/input/libinput_drv.so
Module libinput: vendor="X.Org Foundation"
Using input driver 'libinput' for 'Power Button'
Video Bus: Applying InputClass "libinput keyboard catchall"
Using input driver 'libinput' for 'Video Bus'
Power Button: Applying InputClass "libinput keyboard catchall"
Using input driver 'libinput' for 'Power Button'
Integrated Camera: Integrated C: Applying InputClass "libinput keyboard catchall"
Using input driver 'libinput' for 'Integrated Camera: Integrated C'
Ideapad extra buttons: Applying InputClass "libinput keyboard catchall"
Other things that I found are that libinput is not present in lsmod but there is his folder in /usr/libexec.
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
I'm very confused. I thought that libinput was the problem, but launching linux mint on my usb, the problem persists even if uvc is lunced properly. This is the mint log file:

Bash:
mint kernel: [  298.220906] usb 1-4: new high-speed USB device number 4 using xhci_hcd
mint kernel: [  298.403653] usb 1-4: New USB device found, idVendor=174f, idProduct=2426, bcdDevice= 1.08
mint kernel: [  298.403658] usb 1-4: New USB device strings: Mfr=3, Product=1, SerialNumber=2
mint kernel: [  298.403660] usb 1-4: Product: Integrated Camera
mint kernel: [  298.403663] usb 1-4: Manufacturer: 201406250001
mint kernel: [  298.403664] usb 1-4: SerialNumber: 200901010001
mint kernel: [  298.415004] uvcvideo: Found UVC 1.00 device Integrated Camera (174f:2426)
mint kernel: [  298.423821] uvcvideo: Failed to initialize entity for entity 6
mint kernel: [  298.423823] uvcvideo: Failed to register entities (-22).
mint kernel: [  298.423995] input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4/1-4:1.0/input/input14
mint mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4"
mint mtp-probe: bus: 1, device: 4 was not an MTP device
mint mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4"
mint mtp-probe: bus: 1, device: 4 was not an MTP device
mint kernel: [  298.539681] usb 1-4: USB disconnect, device number 4
Is my camera broken?
 
Last edited:

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,665
Reaction score
1,113
Credits
12,440
Integrated Camera: Integrated C: Applying InputClass "libinput keyboard catchall"
PopOS is still showing as keyboard
mint kernel: [ 298.423995] input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-4/1-4:1.0/input/input14
Where Linux Mint has it correct but "failed to initialize for entry 6" - this is usually cause by "gucview" not loading
Also have a look at
Code:
xinput list
you camera should be listed under "Virtual core keyboard" as HD Webcam id=some number - Also check Users &Groups and make sure your privileges are set correctly to access it - you may have to click on Advanced settings and check User Privileges and make sure there is a check mark in Use Video Devices

Are you using Cheese or VLC to open your Camera?
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
(I'm on pop-os)


Hi, you are definitely right. This is xinput list:
Bash:
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ ELAN469D:00 04F3:304B Touchpad              id=11    [slave  pointer  (2)]
⎜   ↳ ELAN469D:00 04F3:304B Mouse                 id=12    [slave  pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ Power Button                                id=6    [slave  keyboard (3)]
    ↳ Video Bus                                   id=7    [slave  keyboard (3)]
    ↳ Power Button                                id=8    [slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C             id=9    [slave  keyboard (3)]
    ↳ Ideapad extra buttons                       id=10    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard                id=13    [slave  keyboard (3)]

With VLC I tried to start video0 and video1 files on /dev but almost nothing except video0 which flashes the right led of the webcam once and then nothing works.
Instead, this is the cheese error that repeats itself:
Bash:
(cheese:155363): GLib-GObject-CRITICAL **: 18:00:54.268: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(cheese:155363): dconf-WARNING **: 18:00:54.328: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)
...

the cheese behaviour with the camera is not different from VLC (only led flash once)
 

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,665
Reaction score
1,113
Credits
12,440
earlier in post you said "Originally there were video0 and video1, but the response to the command was no different from this. So I tried to remove video0 and the system created these two new numbers" maybe try changing it back to video0
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
When I rebooted, everything returned to how it was before:
v4l2-ctl --list-devices
Bash:
Integrated Camera: Integrated C (usb-0000:04:00.3-4):
    /dev/video0
    /dev/video1
    /dev/media0
 

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,665
Reaction score
1,113
Credits
12,440
Does your syslog still show - Integrated Camera: Integrated C: is tagged by udev as: Keyboard - since you have rebooted? If it does not then you may have to delete the udev rule I had you create earlier in post #2
 
Last edited:
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
it's the same I posted before
Bash:
(cheese:159472): GLib-GObject-CRITICAL **: 18:48:17.837: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(cheese:159472): dconf-WARNING **: 18:48:17.896: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.897: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.898: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.898: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.898: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.898: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.898: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): dconf-WARNING **: 18:48:17.898: failed to commit changes to dconf: Esecuzione del processo figlio «dbus-launch» non riuscita (File o directory non esistente)

(cheese:159472): GLib-GObject-CRITICAL **: 18:48:17.899: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
...
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
Sorry, I changed to English.
Code:
(cheese:163293): GLib-GObject-CRITICAL **: 18:51:40.828: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(cheese:163293): dconf-WARNING **: 18:51:40.892: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(cheese:163293): dconf-WARNING **: 18:51:40.892: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(cheese:163293): dconf-WARNING **: 18:51:40.892: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(cheese:163293): dconf-WARNING **: 18:51:40.893: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
...
 

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,665
Reaction score
1,113
Credits
12,440
The only I can think of is what version of Cheese are you running it may not be fully compatible with the gstreamer-plugin you are running or you are missing one you need might want to try looking in Synaptics Package Manager and see if gstreamer1.0-plugins-bad is installed or not I am willing to guess the gstreamer1.0-plugins-good is installed as well as gstreamer1.0-plugins-ugly
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
Thank you for the help. The only package that was not installed is gstreamer1.0-plugins-ugly. I checked it for the installation, but nothing changed.
 
OP
jifulinx

jifulinx

New Member
Joined
May 16, 2022
Messages
10
Reaction score
0
Credits
77
It's a fascinating app, but it can't catch the camera.
I'm seriously thinking that it is broken because I tried to run a camera application even on Manjaro, in the usb and nothing.
xinput list-props 9 :
Bash:
Device 'Integrated Camera: Integrated C':
    Device Enabled (156):    1
    Coordinate Transformation Matrix (158):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    libinput Send Events Modes Available (279):    1, 0
    libinput Send Events Mode Enabled (280):    0, 0
    libinput Send Events Mode Enabled Default (281):    0, 0
    Device Node (282):    "/dev/input/event6"
    Device Product ID (283):    5967, 9254
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Latest posts

Top