Logitech webcam works in cheese and mplayer -- not zoom under
Firefox nor Chrome
by John W. Himpel
I am running a fully updated F34 on x86_64 hardware. I have a Logitech QuickCam Pro 9000 web cam (webcam +
microphone). I can view the video stream with cheese. I can view the video stream with mplayer. When I start zoom, I
can get no video.
zoom version 5.6.16888.0424-1
heese version 2:3.38.0-3.fc34
mplayer version 1.4.1-0.1.20210313svn.fc34
firefox-wayland version 88.0-5.fc34
google-chrome-stable 90.0.4430.93-1
Journalctl output while plugging in usb cable:
Apr 30 20:45:48 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792] (EE) event3 - Das Keyboard Das Keyboard P13: client
bug: event processing lagging behind by 25ms, your system is too slow
Apr 30 20:45:56 dubby.jlhimpel.net postfix/smtpd[18967]: connect from unknown[212.70.149.55]
Apr 30 20:45:58 dubby.jlhimpel.net audit[20327]: NETFILTER_CFG table=filter family=2 entries=30 op=xt_replace pid=20327
subj=system_u:system_r:iptables_t:s0 comm="iptables"
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: New USB device found, idVendor=046d, idProduct=0990, bcdDevice=
0.05
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: New USB device strings: Mfr=0, Product=0, SerialNumber=2
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: SerialNumber: D4C0E1E4
Apr 30 20:46:01 dubby.jlhimpel.net kernel: uvcvideo: Found UVC 1.00 device <unnamed> (046d:0990)
Apr 30 20:46:01 dubby.jlhimpel.net kernel: input: UVC Camera (046d:0990) as /devices/pci0000:00/0000:00:14.0/usb1/1-
11/1-11:1.0/input/input33
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: Warning! Unlikely big volume range (=3072), cval->res is probably
wrong.
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1
Apr 30 20:46:01 dubby.jlhimpel.net mtp-probe[20330]: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11"
Apr 30 20:46:01 dubby.jlhimpel.net mtp-probe[20330]: bus: 1, device: 7 was not an MTP device
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) config/udev: Adding input device UVC Camera
(046d:0990) (/dev/input/event21)
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): Applying InputClass
"evdev keyboard catchall"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): Applying InputClass
"libinput keyboard catchall"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): Applying InputClass
"system-keyboard"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) Using input driver 'libinput' for 'UVC Camera
(046d:0990)'
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) systemd-logind: got fd for /dev/input/event21
13:85 fd 73 paused 0
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): always reports core
events
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "Device" "/dev/input/event21"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "_source" "server/udev"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): is tagged by
udev as: Keyboard
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): device is a
keyboard
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): device
removed
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0/input/input33/event21"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) XINPUT: Adding extended input device "UVC
Camera (046d:0990)" (type: KEYBOARD, id 18)
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "xkb_layout" "us"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): is tagged by
udev as: Keyboard
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): device is a
keyboard
Apr 30 20:46:02 dubby.jlhimpel.net /usr/libexec/gdm-x-session[20351]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 30 20:46:02 dubby.jlhimpel.net /usr/libexec/gdm-x-session[20351]: > Warning: Could not resolve keysym
XF86FullScreen
Apr 30 20:46:02 dubby.jlhimpel.net /usr/libexec/gdm-x-session[20351]: Errors from xkbcomp are not fatal to the X server
Apr 30 20:46:02 dubby.jlhimpel.net mtp-probe[20358]: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11"
Apr 30 20:46:02 dubby.jlhimpel.net mtp-probe[20358]: bus: 1, device: 7 was not an MTP device
lsusb output:
Bus 004 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 24f0:0105 Metadot Das Keyboard 4
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
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 003: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 007: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Any suggestions are greatly appreciated.
3 years, 1 month
- 1
- 0
Problems upgrading to Fedora 34
by Feoli, Dr. Enrique
Hello,
I am unfamiliar on how to communicate in th users lists. I hope not to be breaking Code of Conduct by sending this emal.
I have found Fedora a great working tool and need to upgrade from Fedora 33 to Fedora 34. But the download in the Software app is giving the following error:
Error running transaction: file/usr/.build-id/c7/-dcd663e38adaac7a2d6d137c46f337ab5543cf conflicts between attempted installs of openjfx8-80.202-26.b07.fc34x86_64 and openjfx-3:11.0.9.2-4.fc34x86_64
Would anyone help in fixing this problem?
Thanks and regards
Enrique Feoli
3 years, 1 month
- 5
- 12
download gets partial data
by Eyal Lebedinsky
In the last day I am having a problem downloading files.
Using ff I downloaded the f34 Workstation image but the download stopped after 1.1GB of 1.9GB.
I tried to download directly from the mirror and I get:
$ curl -LO 'https://fedora.mirror.digitalpacific.com.au/linux/releases/34/Workstation...'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 1914M 0 623k 0 0 1303k 0 0:25:03 --:--:-- 0:25:03 1303k
curl: (18) transfer closed with 2006729431 bytes remaining to read
Same with wget.
Another data point: I later did a "dnf update" and noticed a similar failure:
Downloading Packages:
(1/4): java-1.8.0-openjdk-1.8.0.282.b08-0.fc32_1.8.0.292.b10-0.fc32.x86_64.drpm
[MIRROR] java-1.8.0-openjdk-headless-1.8.0.292.b10-0.fc32.x86_64.rpm: Curl error (18): Transferred a partial file for https://fedora.mirror.digitalpacific.com.au/linux/updates/32/Everything/x... [transfer closed with 34257290 bytes remaining to read]
(2/4): java-1.8.0-openjdk-devel-1.8.0.282.b08-0.fc32_1.8.0.292.b10-0.fc32.x86_64.drpm
[DRPM 1/2] java-1.8.0-openjdk-1.8.0.282.b08-0.fc32_1.8.0.292.b10-0.fc32.x86_64.drpm: done
(3/4): xdg-desktop-portal-1.8.1-2.fc32.x86_64.rpm
(4/4): java-1.8.0-openjdk-headless-1.8.0.292.b10-0.fc32.x86_64.rpm
[DRPM 2/2] java-1.8.0-openjdk-devel-1.8.0.282.b08-0.fc32_1.8.0.292.b10-0.fc32.x86_64.drpm: done
I see this on two f32 machines.
A search did not return recent reports like this.
I tried to download (with curl) ubuntu-21.04-live-server-amd64.iso and this downloaded OK.
Maybe fedora and the mirrors have an issue as f34 is being distributed?
This looks like some sort of systemic problem somewhere. Anyone else sees this?
--
Eyal Lebedinsky (fedora(a)eyal.emu.id.au)
3 years, 1 month
- 2
- 2