[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
Not only the resolution is wrong for the USB-C display but also the order is different. Unplugging and plugging the connector seems to fix the issue (Ubuntu 22 LTS). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku: LENOVO_MT_20NE_BU_Th
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991480] [NEW] Second video device not accessible in Cheese
Public bug reported:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second device,
/dev/video2), both working in applications such as guvcview, vlc, OBS or
webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the menu
to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1184, height=(int)656,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)960, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)
[Kernel-packages] [Bug 1991480] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1991480
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Incomplete
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1,
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
The suggested workaround (disabling nvidia systemd suspend services) worked for me. Driver 470, GTX 660, Old MSI MB (B75MA-P45). I tried forcing GDM to use XOrg first, so I've only tested on a XOrg only system. Upgraded system (from 21.10). Note: I could not find anything in the logs (no trace of nv_restore_user_channels, or similar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991480] Re: Second video device not accessible in Cheese
apport information
** Tags added: apport-collected
** Description changed:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second device,
/dev/video2), both working in applications such as guvcview, vlc, OBS or
webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1184, height=(int)656,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)960, height=(int)720,
pixel-aspect-ratio=(fraction)
[Kernel-packages] [Bug 1991480] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620526/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
[Kernel-packages] [Bug 1991480] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620525/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-rati
[Kernel-packages] [Bug 1991480] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620528/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ra
[Kernel-packages] [Bug 1991480] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620527/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-as
[Kernel-packages] [Bug 1991480] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620529/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-as
[Kernel-packages] [Bug 1991480] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620530/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ra
[Kernel-packages] [Bug 1991480] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620531/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspe
[Kernel-packages] [Bug 1991480] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620535/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pi
[Kernel-packages] [Bug 1991480] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620538/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-
[Kernel-packages] [Bug 1991480] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620537/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-
[Kernel-packages] [Bug 1991480] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620536/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-
[Kernel-packages] [Bug 1991480] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620539/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixe
[Kernel-packages] [Bug 1991480] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620532/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspe
[Kernel-packages] [Bug 1991480] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620533/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height
[Kernel-packages] [Bug 1991480] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620534/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)72
[Kernel-packages] [Bug 1991480] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1991480/+attachment/5620540/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991366 Title: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [SRU Justification] [Impact] Some Dell laptops where booting with Thunderbolt/USB4 devices connected the BIOS leaves some of the PCIe devices unconfigured. The kernel message shows "No bus number available for hot-added bridge". The connected devices can't be found. [Fix] Current linux PCI distribute the "spare" resources between hotplug ports on hot-add but have not done that upon the initial scan. The patches make the initial root bus scan path to do the same. The additional patches are just a small cleanups that can be applied separately too. [Test] 1. Power on the machine with Thunderbolt/USB4 devices connected. 2. Check the kernel message to see if "No bus number available for hot-added bridge" shows up or not. 3. Check if the Thunderbolt/USB4 devices works or not. [Where problems could occur] The patches only apply the same procedures on initial root bus scan which was not done. If the BIOS configures the PCI correctly, everything is OK. It only takes effect for the BIOS w/ unconfigured PCIe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: New Status in linux package in Ubuntu: Fix Released Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991220] Re: "dpc: probe of 0000:00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6
apport information ** Tags added: apport-collected bionic uec-images ** Description changed: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 3 02:10 seq + crw-rw 1 root audio 116, 33 Oct 3 02:10 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.28 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2022-09-29 (3 days ago) + InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro + ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-193-generic N/A + linux-backports-modules-4.15.0-193-generic N/A + linux-firmware 1.173.21 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic uec-images + Uname: Linux 4.15.0-193-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/25/2022 + dmi.bios.vendor: Lenovo + dmi.bios.version: IYE101N-1.10 + dmi.board.asset.tag: None + dmi.board.name: SB27B33703 + dmi.board.vendor: Lenovo + dmi.board.version: 03 + dmi.chassis.asset.tag: None + dmi.chassis.type: 0 + dmi.chassis.vendor: Lenovo + dmi.chassis.version: None + dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25/2022:svnLENOVO:pnThinkEdgeSE350V2CPUPlanar:pvr03:rvnLenovo:rnSB27B33703:rvr03:cvnLenovo:ct0:cvrNone: + dmi.product.family: ThinkSystem + dmi.product.name: ThinkEdge SE350 V2 CPU Planar + dmi.product.version: 03 + dmi.sys.vendor: LENOVO ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620638/+files/CRDA.txt -- You received this bug noti
[Kernel-packages] [Bug 1991220] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620641/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25/2022:svnLENO
[Kernel-packages] [Bug 1991220] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620640/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25/2022:svnLENO
[Kernel-packages] [Bug 1991220] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620639/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/
[Kernel-packages] [Bug 1991220] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620642/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25
[Kernel-packages] [Bug 1991220] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620646/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25/2022:svnLE
[Kernel-packages] [Bug 1991220] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620647/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25/2
[Kernel-packages] [Bug 1991220] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620643/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101
[Kernel-packages] [Bug 1991220] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620644/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:b
[Kernel-packages] [Bug 1991220] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1991220/+attachment/5620645/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: dmi:bvnLenovo:bvrIYE101N-1.10:bd09/25
[Kernel-packages] [Bug 1991220] Re: "dpc: probe of 0000:00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6
I have run the apport-collect 1991220 to this bug and set the status as confirmed. Please help on it. Thank you. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Confirmed Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 02:10 seq crw-rw 1 root audio 116, 33 Oct 3 02:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2022-09-29 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro ProcVersionSignature: Ubuntu 4.15.0-193.204-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-193-generic N/A linux-backports-modules-4.15.0-193-generic N/A linux-firmware 1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-193-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2022 dmi.bios.vendor: Lenovo dmi.bios.version: IYE101N-1.10 dmi.board.asset.tag: None dmi.board.name: SB27B33703 dmi.board.vendor: Lenovo dmi.board.version: 03 dmi.chassis.asset.tag: None dmi.chassis.type: 0 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.modalias: d
[Kernel-packages] [Bug 1989556] Re: Add support for Raptor Lake S CPUs
** Changed in: thermald (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989556 Title: Add support for Raptor Lake S CPUs Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991437] Re: Keyboard inoperative on Lenovo Yoga 7 Gen 7 (AMD Ryzen 6800u)
this patch may break my laptop keyboard. my laptop is GPD Win Max2 with AMD 6800U after upgrade kernel 5.19.10 from 5.19.9. the build-in keyboard of GPD Win Max2 not working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991437 Title: Keyboard inoperative on Lenovo Yoga 7 Gen 7 (AMD Ryzen 6800u) Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The builtin keyboard on the Lenovo Yoga 7 Gen 7 doesn't work on linux 5.19.0.15-generic (ubuntu-22.10-beta-desktop-amd64.iso; same problem exists in 5.15.0-43-generic of ubuntu-22.04.1-desktop- amd64.iso) [Fix] 9946e39fe8d0a5da9eb947d8e40a7ef204ba016e ACPI: resource: skip IRQ override on AMD Zen platforms https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.19.y&id=37c81d9f1d1b1458894454efcb857f6a769b6bc4 > IRQ override isn't needed on modern AMD Zen systems. > There's an active low keyboard IRQ on AMD Ryzen 6000 and it will stay > this way on newer platforms. This IRQ override breaks keyboards for > almost all Ryzen 6000 laptops currently on the market. > Skip this IRQ override for all AMD Zen platforms because this IRQ > override is supposed to be a workaround for buggy ACPI DSDT and we can't > have a long list of all future AMD CPUs/Laptops in the kernel code. > If a device with buggy ACPI DSDT shows up, a separated list containing > just them should be created. The fix is in Linux 5.19.10. [Other Info] The keyboard worked when using a linux kernel 5.19.10 (in debian testing). I tried to patch the kernel on the ubuntu live CD ubuntu-22.04.1-desktop-amd64.iso, but the live filesystem could not be mounted and I only got the busybox environment. The keyboard was working though. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2048 F wireplumber /dev/snd/controlC0: ubuntu 2048 F wireplumber /dev/snd/seq:ubuntu 2045 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: LENOVO 82QF NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/28/2022 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrK5CN31WW:bd07/28/2022:br1.31:efr1.31:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
I've just installed 22.10 in VirtualBox and still can't reproduce this bug. What changes from the default VirtualBox settings might be causing it? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. Status in linux package in Ubuntu: Incomplete Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991480] Re: Second video device not accessible in Cheese
** Package changed: linux (Ubuntu) => cheese (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in cheese package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
