date:20220615

This bug was fixed in the package libnvidia-nscq-510 -
510.73.08-0ubuntu0.22.04.1

---
libnvidia-nscq-510 (510.73.08-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Thu, 26 May 2022 00:24:26 -0500

** Changed in: libnvidia-nscq-510 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: fabric-manager-510 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package libnvidia-nscq-510 -
510.73.08-0ubuntu0.21.10.1

---
libnvidia-nscq-510 (510.73.08-0ubuntu0.21.10.1) impish; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Thu, 26 May 2022 00:19:53 -0500

** Changed in: fabric-manager-510 (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package fabric-manager-510 -
510.73.08-0ubuntu0.22.04.1

---
fabric-manager-510 (510.73.08-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Wed, 25 May 2022 23:08:22 -0500

** Changed in: libnvidia-nscq-510 (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package fabric-manager-510 -
510.73.08-0ubuntu0.20.04.1

---
fabric-manager-510 (510.73.08-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Wed, 25 May 2022 22:41:10 -0500

** Changed in: libnvidia-nscq-510 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package libnvidia-nscq-510 -
510.73.08-0ubuntu0.20.04.1

---
libnvidia-nscq-510 (510.73.08-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Wed, 25 May 2022 23:56:26 -0500

** Changed in: fabric-manager-510 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package libnvidia-nscq-510 -
510.73.08-0ubuntu0.18.04.1

---
libnvidia-nscq-510 (510.73.08-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Wed, 25 May 2022 23:41:27 -0500

** Changed in: fabric-manager-510 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package fabric-manager-510 -
510.73.08-0ubuntu0.21.10.1

---
fabric-manager-510 (510.73.08-0ubuntu0.21.10.1) impish; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Wed, 25 May 2022 23:01:46 -0500

** Changed in: libnvidia-nscq-510 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

This bug was fixed in the package fabric-manager-510 -
510.73.08-0ubuntu0.18.04.1

---
fabric-manager-510 (510.73.08-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1975509).

 -- Ian May   Wed, 25 May 2022 22:47:53 -0500

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in fabric-manager-510 package in Ubuntu:
  Fix Committed
Status in libnvidia-nscq-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-510 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Released
Status in fabric-manager-510 source package in Focal:
  Fix Released
Status in libnvidia-nscq-510 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Released
Status in fabric-manager-510 source package in Impish:
  Fix Released
Status in libnvidia-nscq-510 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Released
Status in fabric-manager-510 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Released
Status in fabric-manager-510 source package in Kinetic:
  Fix Committed
Status in libnvidia-nscq-510 source package in Kinetic:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1978822] [NEW] package nvidia-driver-510 510.73.05-0ubuntu0.20.04.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置

2022-06-15 Thread Yao Zhibo

Public bug reported:

vendor   : NVIDIA Corporation
model: GP106 [GeForce GTX 1060 3GB]
driver   : nvidia-driver-390 - distro non-free
driver   : nvidia-driver-510 - distro non-free recommended
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-510-server - distro non-free
driver   : nvidia-driver-418-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-450-server - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-510 510.73.05-0ubuntu0.20.04.1
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
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jun 15 20:34:41 2022
ErrorMessage: 依赖关系问题 - 仍未被配置
InstallationDate: Installed on 2022-06-15 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
SourcePackage: nvidia-graphics-drivers-510
Title: package nvidia-driver-510 510.73.05-0ubuntu0.20.04.1 failed to 
install/upgrade: 依赖关系问题 - 仍未被配置
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu.
https://bugs.launchpad.net/bugs/1978822

Title:
  package nvidia-driver-510 510.73.05-0ubuntu0.20.04.1 failed to
  install/upgrade: 依赖关系问题 - 仍未被配置

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  vendor   : NVIDIA Corporation
  model: GP106 [GeForce GTX 1060 3GB]
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-510 - distro non-free recommended
  driver   : nvidia-driver-470-server - distro non-free
  driver   : nvidia-driver-510-server - distro non-free
  driver   : nvidia-driver-418-server - distro non-free
  driver   : nvidia-driver-470 - distro non-free
  driver   : nvidia-driver-450-server - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-510 510.73.05-0ubuntu0.20.04.1
  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
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jun 15 20:34:41 2022
  ErrorMessage: 依赖关系问题 - 仍未被配置
  InstallationDate: Installed on 2022-06-15 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: nvidia-graphics-drivers-510
  Title: package nvidia-driver-510 510.73.05-0ubuntu0.20.04.1 failed to 
install/upgrade: 依赖关系问题 - 仍未被配置
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1978822/+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 1978145] Re: Request to back port vmci patches to Ubuntu kernel

2022-06-15 Thread Tim Gardner

Hi Vishnu - can you expand a bit as to the purpose of these patches ?
Are they solely for the purpose of adding arm64 support ?

rtg

-- 
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/1978145

Title:
  Request to back port vmci patches to Ubuntu kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The request is to bring vmci to TOT and back port the following patches into
  Ubuntu kernels.

  1.  fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace 
formatting change for vmci register defines")
  2.  e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access 
to registers")
  3.  eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA 
datagram capability")
  4.  8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page 
size")
  5.  cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy 
IRQ handlers for DMA datagrams")
  6.  5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send 
and receive buffers for DMA datagrams")
  7.  22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for 
DMA datagrams sends")
  8.  463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for 
DMA datagrams receive")
  9.  77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling 
paths in vmci_guest_probe_device()")
  10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release 
notification_bitmap in error path")
  11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors 
when freeing interrupt 1")
  12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
  13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the 
work is already queued")

  Thanks,
  Vishnu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+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 1978824] [NEW] ERROR (dkms apport): kernel package linux-headers-5.15.0-37-generic is not supported

2022-06-15 Thread Yao Zhibo

Public bug reported:

DKMS make.log for nvidia-418.226.00 for kernel 5.15.0-37-generic (x86_64)
2022年 06月 15日 星期三 20:54:51 CST
make[1]: 进入目录“/usr/src/linux-headers-5.15.0-37-generic”
tcc: error: invalid option -- '-print-file-name=include'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
  You are using:   tcc version 0.9.27 (x86_64 Linux)
make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia/418.226.00/build \
single-build= \
need-builtin=1 need-modorder=1
tcc: error: no input files

The kernel you are installing for is a PREEMPT_RT kernel!

The NVIDIA driver does not support real-time kernels. If you 
are using a stock distribution kernel, please install 
a variant of this kernel that does not have the PREEMPT_RT 
patch set applied; if this is a custom kernel, please 
install a standard Linux kernel.  Then try installing the 
NVIDIA kernel module again.

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu.
https://bugs.launchpad.net/bugs/1978824

Title:
  ERROR (dkms apport): kernel package linux-headers-5.15.0-37-generic is
  not supported

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  DKMS make.log for nvidia-418.226.00 for kernel 5.15.0-37-generic (x86_64)
  2022年 06月 15日 星期三 20:54:51 CST
  make[1]: 进入目录“/usr/src/linux-headers-5.15.0-37-generic”
  tcc: error: invalid option -- '-print-file-name=include'
  test -e include/generated/autoconf.h -a -e include/config/auto.conf || (  
\
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid."; \
  echo >&2 " include/generated/autoconf.h or include/config/auto.conf 
are missing.";\
  echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";\
  echo >&2 ;\
  /bin/false)
  warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
You are using:   tcc version 0.9.27 (x86_64 Linux)
  make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia/418.226.00/build \
  single-build= \
  need-builtin=1 need-modorder=1
  tcc: error: no input files

  The kernel you are installing for is a PREEMPT_RT kernel!

  The NVIDIA driver does not support real-time kernels. If you 
  are using a stock distribution kernel, please install 
  a variant of this kernel that does not have the PREEMPT_RT 
  patch set applied; if this is a custom kernel, please 
  install a standard Linux kernel.  Then try installing the 
  NVIDIA kernel module again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1978824/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

*** This bug is a duplicate of bug 1977699 ***
https://bugs.launchpad.net/bugs/1977699

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: zfs-linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978347

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laperlej   4100 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 15:52:12 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-05-10 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP EliteBook 850 G8 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2022
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.08.00
  dmi.board.name: 8846
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.37.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.55
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G8 Notebook PC
  dmi.product.sku: 4V1S3UP#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

2022-06-15 Thread Harshal Prakash Patankar

*** This bug is a duplicate of bug 1977699 ***
https://bugs.launchpad.net/bugs/1977699

duplicate of https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1977699

will be fixed by https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1969482

** This bug has been marked a duplicate of bug 1977699
   zfs icp has deselected all optimized aes & gcm impls

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978347

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laperlej   4100 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 15:52:12 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-05-10 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP EliteBook 850 G8 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2022
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.08.00
  dmi.board.name: 8846
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.37.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.55
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G8 Notebook PC
  dmi.product.sku: 4V1S3UP#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+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 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter

2022-06-15 Thread Heather Lemon

** Description changed:

- Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0"
- parameter.
+ 
+ [Impact]
+ 
+ Azure VM instances hit I/O error on boot causing kernel crash
+ 
+ 
+ [Test Plan]
+ 
+ Execute commands
+ 
+ apt-get install kdump-tools -y
+ 
+ #print out the crashkernel config
+ kdump-config test
+ 
+ # Output shows the parameter "ata_piix.prefer_ms_hyperv=0" is not listed
+ kdump-config test | grep "ata_piix.prefer_ms_hyperv=0" 
+ 
+ Full output of kdump-config test 
+  * no crashkernel= parameter in the kernel cmdline
+  * Invalid symlink : /var/lib/kdump/initrd.img
+  * Invalid symlink : /var/lib/kdump/vmlinuz
+  * /etc/default/kdump-tools: KDUMP_KERNEL does not exist: 
/var/lib/kdump/vmlinuz
+ USE_KDUMP:1
+ KDUMP_COREDIR:/var/crash
+ crashkernel addr  
+ kdump kernel addr 
+ kdump kernel:
+/var/lib/kdump/vmlinuz
+ kdump initrd: 
+/var/lib/kdump/initrd.img
+ kexec command to be used:
+   /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.13.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" 
/var/lib/kdump/vmlinuz
+ 
+ 
+ [Where Problems Could Occur]
+ 
+ This change modifies the debian/rules. 
+ The package could fail to build properly if mistyped. 
+ 
+ [Other]
+ Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" 
parameter.
  
  target series - Kinetic-> Bionic
  
  upstream patch
  
  https://salsa.debian.org/debian/kdump-
  tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503
  
- *Note: There are two source packages needed changes, kdump-tools for Impish 
-> Kinetic 
- and makedumpfile for series Focal -> Bionic 
- 
- 
- Thanks!
+ *Note: There are two source packages needed changes, kdump-tools for
+ Impish -> Kinetic and makedumpfile for series Focal -> Bionic

** Description changed:

- 
  [Impact]
  
  Azure VM instances hit I/O error on boot causing kernel crash
- 
  
  [Test Plan]
  
  Execute commands
  
  apt-get install kdump-tools -y
  
+ Say (y) to all questions during install
+ 
+ #A reboot is needed 
+ sudo reboot
+ 
  #print out the crashkernel config
  kdump-config test
  
  # Output shows the parameter "ata_piix.prefer_ms_hyperv=0" is not listed
- kdump-config test | grep "ata_piix.prefer_ms_hyperv=0" 
+ kdump-config test | grep "ata_piix.prefer_ms_hyperv=0"
  
- Full output of kdump-config test 
-  * no crashkernel= parameter in the kernel cmdline
-  * Invalid symlink : /var/lib/kdump/initrd.img
-  * Invalid symlink : /var/lib/kdump/vmlinuz
-  * /etc/default/kdump-tools: KDUMP_KERNEL does not exist: 
/var/lib/kdump/vmlinuz
+ Full output of kdump-config test
+  * no crashkernel= parameter in the kernel cmdline
+  * Invalid symlink : /var/lib/kdump/initrd.img
+  * Invalid symlink : /var/lib/kdump/vmlinuz
+  * /etc/default/kdump-tools: KDUMP_KERNEL does not exist: 
/var/lib/kdump/vmlinuz
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
- crashkernel addr  
- kdump kernel addr 
+ crashkernel addr
+ kdump kernel addr
  kdump kernel:
-/var/lib/kdump/vmlinuz
- kdump initrd: 
-/var/lib/kdump/initrd.img
+    /var/lib/kdump/vmlinuz
+ kdump initrd:
+    /var/lib/kdump/initrd.img
  kexec command to be used:
-   /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.13.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" 
/var/lib/kdump/vmlinuz
- 
+   /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.13.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" 
/var/lib/kdump/vmlinuz
  
  [Where Problems Could Occur]
  
- This change modifies the debian/rules. 
- The package could fail to build properly if mistyped. 
+ This change modifies the debian/rules.
+ The package could fail to build properly if mistyped.
  
  [Other]
  Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" 
parameter.
  
  target series - Kinetic-> Bionic
  
  upstream patch
  
  https://salsa.debian.org/debian/kdump-
  tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503
  
  *Note: There are two source packages needed changes, kdump-tools for
  Impish -> Kinetic and makedumpfile for series Focal -> Bionic

** Description changed:

  [Impact]
  
  Azure VM instances hit I/O error on boot causing kernel crash
  
  [Test Plan]
  
  Execute commands
  
+ lxc launch ubuntu:impish kdumpimpish
+ 
+ lxc exec kdumpimpish bash
+ 
  apt-get install kdump-tools -y
  
  Say (y) to all questions during install
  
- #A reboot is needed 
+ #A reboot is needed
  sudo reboot
  
  #print out the crashkernel config
  kdump-config test
  
  # Output shows the parameter "ata_piix.prefer_ms_hyperv=0" is not listed
  kdump-config test | grep "ata_piix.prefer_ms_h

[Kernel-packages] [Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"

2022-06-15 Thread Thiago Flaulhabe Xavier Gomes

So is there something I can do right now? I did not understand very well
if there's already a updated fix I can try.

-- 
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/1931715

Title:
  [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not
  appear on "cat /proc/bus/input/devices"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop model: Lenovo Ideapad S145 82DJ0001BR
  Manufacturer of the Touchpad: Elan, Synaptics
  When the symptom first appeared: At the time I installed Ubuntu on my 
notebook (dual-boot) - it works fine on Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 11 11:58:39 2021
  InstallationDate: Installed on 2021-06-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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 1977968] Re: Security update tracking bug

This bug was fixed in the package bluez - 5.48-0ubuntu3.9

---
bluez (5.48-0ubuntu3.9) bionic-security; urgency=medium

  * SECURITY UPDATE: various security improvements (LP: #1977968)
- debian/patches/avdtp-security.patch: check if capabilities are valid
  before attempting to copy them in profiles/audio/avdtp.c.
- debian/patches/avdtp-security-2.patch: fix size comparison and
  variable misassignment in profiles/audio/avdtp.c.
- debian/patches/avrcp-security.patch: make sure the number of bytes in
  the params_len matches the remaining bytes received so the code don't
  end up accessing invalid memory in profiles/audio/avrcp.c.
- No CVE numbers

 -- Marc Deslauriers   Wed, 08 Jun 2022
07:19:20 -0400

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1977968

Title:
  Security update tracking bug

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This bug is to track the security update that will contain these
  possibly security-relevant commits:

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968/+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 1977968] Re: Security update tracking bug

This bug was fixed in the package bluez - 5.53-0ubuntu3.6

---
bluez (5.53-0ubuntu3.6) focal-security; urgency=medium

  * SECURITY UPDATE: various security improvements (LP: #1977968)
- debian/patches/avdtp-security.patch: check if capabilities are valid
  before attempting to copy them in profiles/audio/avdtp.c.
- debian/patches/avdtp-security-2.patch: fix size comparison and
  variable misassignment in profiles/audio/avdtp.c.
- debian/patches/avrcp-security.patch: make sure the number of bytes in
  the params_len matches the remaining bytes received so the code don't
  end up accessing invalid memory in profiles/audio/avrcp.c.
- No CVE numbers

 -- Marc Deslauriers   Wed, 08 Jun 2022
07:09:00 -0400

** Changed in: bluez (Ubuntu)
   Status: New => Fix Released

** Changed in: bluez (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1977968

Title:
  Security update tracking bug

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This bug is to track the security update that will contain these
  possibly security-relevant commits:

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968/+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 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

2022-06-15 Thread Victor Abend

I'm having exactly the same problems. (Lenovo ideapat, Linux Mint 19)
Just tested with #187. Problems remain. 
Last working Kernel was #176.

-- 
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/1973167

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  == SRU Justification ==
  [Impact]
  Freeze at boot. intel-lpss is trying to synchronously load idma64 module
  in asynchronous conext.

  [Fix]
  Let userspace load the module to avoid the deadlock.

  [Test]
  Users confirmed the proposed fix can solve the issue.

  [Where problems could occur]
  Userspace can handle modules loading just fine, so there shouldn't be
  any surprise.

  == Original Bug Report ==
  After updating to linux-image-4.15.0-177-generic, my machine completely 
freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI mode. 
The mouse pointer is frozen, the keyboard does not even respond to CAPS LOCK or 
NUM LOCK, pressing CTRL+ALT+F2 shows no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)

2022-06-15 Thread Tushar

> The bug exists on 5.15.35, 5.16.20, 5.17.5, 5.15.36. In addition to this, the 
> bug exists on 5.15.37 and 5.17.6.
I have been using 5.17.7 for around 16 hours, and the problem has not occurred 
so far.

-- 
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/1958191

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1978865] [NEW] openvswitch: nf_ct_put is called with null pointer

2022-06-15 Thread Nick Rogers

Public bug reported:

Using an openvswitch bridge with conntrack flows causes a kernel warning
trace for every packet. This does not break conntrack functionality, but
causes a big packet forwarding performance degradation and very noisy
and large kernel.log/journal/syslog/etc. The cause is a regression in
the 5.15 LTS kernel. This seems to have been fixed in mainline 5.15.36,
but I don't see the fix in any of the jammy branches.

Upgrading to mainline 5.15.36 or beyond from the Ubuntu PPA fixes the
problem.

Here is a relevant discussion with reference to the fix applied to mainline:
https://lore.kernel.org/netdev/ymajlos1ytpaq...@kroah.com/T/

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-39-generic 5.15.0-39.42
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
Uname: Linux 5.15.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 15 15:38 seq
 crw-rw 1 root audio 116, 33 Jun 15 15:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Wed Jun 15 15:41:13 2022
InstallationDate: Installed on 2022-06-15 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-E300-8D
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-39-generic N/A
 linux-backports-modules-5.15.0-39-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2017
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X10SDV-TP8F
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/31/2017:br5.6:svnSupermicro:pnSYS-E300-8D:pvr0123456789:rvnSupermicro:rnX10SDV-TP8F:rvr1.01:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: SYS-E300-8D
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: openvswitch (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

-- 
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/1978865

Title:
  openvswitch: nf_ct_put is called with null pointer

Status in linux package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New

Bug description:
  Using an openvswitch bridge with conntrack flows causes a kernel
  warning trace for every packet. This does not break conntrack
  functionality, but causes a big packet forwarding performance
  degradation and very noisy and large kernel.log/journal/syslog/etc.
  The cause is a regression in the 5.15 LTS kernel. This seems to have
  been fixed in mainline 5.15.36, but I don't see the fix in any of the
  jammy branches.

  Upgrading to mainline 5.15.36 or beyond from the Ubuntu PPA fixes the
  problem.

  Here is a relevant discussion with reference to the fix applied to mainline:
  https://lore.kernel.org/netdev/ymajlos1ytpaq...@kroah.com/T/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-39-generic 5.15.0-39.42
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 15 15:38 seq
   crw-rw 1 root audio 116, 33 Jun 15 15:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Dat

[Kernel-packages] [Bug 1978865] Re: openvswitch: nf_ct_put is called with null pointer

2022-06-15 Thread Nick Rogers

Please refer to the many Call Trace messages in CurrentDmesg.txt.

** Also affects: openvswitch (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1978865

Title:
  openvswitch: nf_ct_put is called with null pointer

Status in linux package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New

Bug description:
  Using an openvswitch bridge with conntrack flows causes a kernel
  warning trace for every packet. This does not break conntrack
  functionality, but causes a big packet forwarding performance
  degradation and very noisy and large kernel.log/journal/syslog/etc.
  The cause is a regression in the 5.15 LTS kernel. This seems to have
  been fixed in mainline 5.15.36, but I don't see the fix in any of the
  jammy branches.

  Upgrading to mainline 5.15.36 or beyond from the Ubuntu PPA fixes the
  problem.

  Here is a relevant discussion with reference to the fix applied to mainline:
  https://lore.kernel.org/netdev/ymajlos1ytpaq...@kroah.com/T/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-39-generic 5.15.0-39.42
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 15 15:38 seq
   crw-rw 1 root audio 116, 33 Jun 15 15:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Wed Jun 15 15:41:13 2022
  InstallationDate: Installed on 2022-06-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Supermicro SYS-E300-8D
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SDV-TP8F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/31/2017:br5.6:svnSupermicro:pnSYS-E300-8D:pvr0123456789:rvnSupermicro:rnX10SDV-TP8F:rvr1.01:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SYS-E300-8D
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978865/+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 1978865] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1978865

Title:
  openvswitch: nf_ct_put is called with null pointer

Status in linux package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  New

Bug description:
  Using an openvswitch bridge with conntrack flows causes a kernel
  warning trace for every packet. This does not break conntrack
  functionality, but causes a big packet forwarding performance
  degradation and very noisy and large kernel.log/journal/syslog/etc.
  The cause is a regression in the 5.15 LTS kernel. This seems to have
  been fixed in mainline 5.15.36, but I don't see the fix in any of the
  jammy branches.

  Upgrading to mainline 5.15.36 or beyond from the Ubuntu PPA fixes the
  problem.

  Here is a relevant discussion with reference to the fix applied to mainline:
  https://lore.kernel.org/netdev/ymajlos1ytpaq...@kroah.com/T/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-39-generic 5.15.0-39.42
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 15 15:38 seq
   crw-rw 1 root audio 116, 33 Jun 15 15:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Wed Jun 15 15:41:13 2022
  InstallationDate: Installed on 2022-06-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Supermicro SYS-E300-8D
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SDV-TP8F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/31/2017:br5.6:svnSupermicro:pnSYS-E300-8D:pvr0123456789:rvnSupermicro:rnX10SDV-TP8F:rvr1.01:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SYS-E300-8D
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978865/+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 1978867] [NEW] usb uas Device Removal not detected in 22.04

2022-06-15 Thread Harald Rudell

Public bug reported:

22.04 5.15.0-37-generic xhci_hcd has some issues

2012 hardware no longer work with 2109:0715 #1978397
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086
:1e31] (rev 04) 
   
Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family USB 
xHCI Host Controller [8086:7270]  
Kernel driver in use: xhci_hcd

2018 hardware no longer work with 2109:0822 (this bug)
00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI 
Host Controller [8086:a36d] (rev 10)
Subsystem: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller [8086:7270]
Kernel driver in use: xhci_hcd

The problemprompting this bug is that uas disk removal from 2109:0715 is not 
detected by 8086:a36d
the /dev/sd device for the no longer present disk remains until:
echo 1 > /sys/block/sdd/device/delete

Here is 3:25 device removal:
Jun 15 03:25:54 c68z systemd[1]: mnt-vlx10-c68x.mount: Deactivated successfully.
Jun 15 03:25:55 c68z zed: eid=494 class=pool_export pool='vlx10' 
pool_state=EXPORTED
Jun 15 03:25:55 c68z zed: eid=495 class=config_sync pool='vlx10' 
pool_state=UNINITIALIZED

Here is 3:26 Synchronizing SCSI cache reading from the removed device:
Jun 15 03:26:13 c68z kernel: [ 5307.245185] usb 2-5.2: Disable of 
device-initiated U1 failed.
Jun 15 03:26:13 c68z kernel: [ 5307.252087] usb 2-5.2: Disable of 
device-initiated U2 failed.
Jun 15 03:26:13 c68z kernel: [ 5307.993998] usb 2-5.2: reset SuperSpeed USB 
device number 7 using xhci_hcd
Jun 15 03:26:29 c68z kernel: [ 5323.181119] usb 2-5.2: Disable of 
device-initiated U1 failed.
Jun 15 03:26:29 c68z kernel: [ 5323.188084] usb 2-5.2: Disable of 
device-initiated U2 failed.
Jun 15 03:26:29 c68z kernel: [ 5323.929678] usb 2-5.2: reset SuperSpeed USB 
device number 7 using xhci_hcd
Jun 15 03:26:41 c68z kernel: [ 5335.933396] sd 2:0:0:0: [sdc] tag#21 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jun 15 03:26:41 c68z kernel: [ 5335.933407] sd 2:0:0:0: [sdc] tag#21 Sense Key 
: Illegal Request [current] 
Jun 15 03:26:41 c68z kernel: [ 5335.933414] sd 2:0:0:0: [sdc] tag#21 Add. 
Sense: Invalid command operation code
Jun 15 03:26:41 c68z kernel: [ 5335.933420] sd 2:0:0:0: [sdc] tag#21 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fa 50 00 00 00 e0 00 00
Jun 15 03:26:41 c68z kernel: [ 5335.933424] blk_update_request: critical target 
error, dev sdc, sector 19532872272 op 0x0:(READ) flags 0x0 phys_seg 28 prio 
class 0
Jun 15 03:26:41 c68z kernel: [ 5335.934158] sd 2:0:0:0: [sdc] tag#22 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jun 15 03:26:41 c68z kernel: [ 5335.934170] sd 2:0:0:0: [sdc] tag#22 Sense Key 
: Illegal Request [current] 
Jun 15 03:26:41 c68z kernel: [ 5335.934177] sd 2:0:0:0: [sdc] tag#22 Add. 
Sense: Invalid command operation code
Jun 15 03:26:41 c68z kernel: [ 5335.934184] sd 2:0:0:0: [sdc] tag#22 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fc 50 00 00 00 e0 00 00
Jun 15 03:26:41 c68z kernel: [ 5335.934187] blk_update_request: critical target 
error, dev sdc, sector 19532872784 op 0x0:(READ) flags 0x0 phys_seg 28 prio 
class 0
Jun 15 03:27:05 c68z kernel: [ 5360.036887] sd 2:0:0:0: [sdc] tag#22 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jun 15 03:27:05 c68z kernel: [ 5360.036926] sd 2:0:0:0: [sdc] tag#22 Sense Key 
: Illegal Request [current] 
Jun 15 03:27:05 c68z kernel: [ 5360.036935] sd 2:0:0:0: [sdc] tag#22 Add. 
Sense: Invalid command operation code
Jun 15 03:27:05 c68z kernel: [ 5360.036944] sd 2:0:0:0: [sdc] tag#22 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fa 50 00 00 00 e0 00 00
Jun 15 03:27:05 c68z kernel: [ 5360.036949] blk_update_request: critical target 
error, dev sdc, sector 19532872272 op 0x0:(READ) flags 0x0 phys_seg 28 prio 
class 0
Jun 15 03:27:05 c68z kernel: [ 5360.037677] sd 2:0:0:0: [sdc] tag#23 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jun 15 03:27:05 c68z kernel: [ 5360.037687] sd 2:0:0:0: [sdc] tag#23 Sense Key 
: Illegal Request [current] 
Jun 15 03:27:05 c68z kernel: [ 5360.037700] sd 2:0:0:0: [sdc] tag#23 Add. 
Sense: Invalid command operation code
Jun 15 03:27:05 c68z kernel: [ 5360.037707] sd 2:0:0:0: [sdc] tag#23 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fc 50 00 00 00 e0 00 00
Jun 15 03:27:05 c68z kernel: [ 5360.037711] blk_update_request: critical target 
error, dev sdc, sector 19532872784 op 0x0:(READ) flags 0x0 phys_seg 28 prio 
class 0
Jun 15 03:30:21 c68z kernel: [ .149307] usb 2-5.2: Disable of 
device-initiated U1 failed.
Jun 15 03:30:21 c68z kernel: [ .156162] usb 2-5.2: Disable of 
device-initiated U2 failed.
Jun 15 03:30:21 c68z kernel: [ .897428] usb 2-5.2: reset SuperSpeed USB 
device number 7 using xhci_hcd
Jun 15 03:33:26 c68z kernel: [ 5740.221793] usb 2-5.2: Disable of 
device-initiated U1 failed.
Jun 15 03:33:

[Kernel-packages] [Bug 1978867] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1978867

Title:
  usb uas Device Removal not detected in 22.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  22.04 5.15.0-37-generic xhci_hcd has some issues

  2012 hardware no longer work with 2109:0715 #1978397
  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086
  :1e31] (rev 04)   
 
  Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family USB 
xHCI Host Controller [8086:7270]  
  Kernel driver in use: xhci_hcd

  2018 hardware no longer work with 2109:0822 (this bug)
  00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI 
Host Controller [8086:a36d] (rev 10)
  Subsystem: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller [8086:7270]
  Kernel driver in use: xhci_hcd

  The problemprompting this bug is that uas disk removal from 2109:0715 is not 
detected by 8086:a36d
  the /dev/sd device for the no longer present disk remains until:
  echo 1 > /sys/block/sdd/device/delete

  Here is 3:25 device removal:
  Jun 15 03:25:54 c68z systemd[1]: mnt-vlx10-c68x.mount: Deactivated 
successfully.
  Jun 15 03:25:55 c68z zed: eid=494 class=pool_export pool='vlx10' 
pool_state=EXPORTED
  Jun 15 03:25:55 c68z zed: eid=495 class=config_sync pool='vlx10' 
pool_state=UNINITIALIZED

  Here is 3:26 Synchronizing SCSI cache reading from the removed device:
  Jun 15 03:26:13 c68z kernel: [ 5307.245185] usb 2-5.2: Disable of 
device-initiated U1 failed.
  Jun 15 03:26:13 c68z kernel: [ 5307.252087] usb 2-5.2: Disable of 
device-initiated U2 failed.
  Jun 15 03:26:13 c68z kernel: [ 5307.993998] usb 2-5.2: reset SuperSpeed USB 
device number 7 using xhci_hcd
  Jun 15 03:26:29 c68z kernel: [ 5323.181119] usb 2-5.2: Disable of 
device-initiated U1 failed.
  Jun 15 03:26:29 c68z kernel: [ 5323.188084] usb 2-5.2: Disable of 
device-initiated U2 failed.
  Jun 15 03:26:29 c68z kernel: [ 5323.929678] usb 2-5.2: reset SuperSpeed USB 
device number 7 using xhci_hcd
  Jun 15 03:26:41 c68z kernel: [ 5335.933396] sd 2:0:0:0: [sdc] tag#21 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
  Jun 15 03:26:41 c68z kernel: [ 5335.933407] sd 2:0:0:0: [sdc] tag#21 Sense 
Key : Illegal Request [current] 
  Jun 15 03:26:41 c68z kernel: [ 5335.933414] sd 2:0:0:0: [sdc] tag#21 Add. 
Sense: Invalid command operation code
  Jun 15 03:26:41 c68z kernel: [ 5335.933420] sd 2:0:0:0: [sdc] tag#21 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fa 50 00 00 00 e0 00 00
  Jun 15 03:26:41 c68z kernel: [ 5335.933424] blk_update_request: critical 
target error, dev sdc, sector 19532872272 op 0x0:(READ) flags 0x0 phys_seg 28 
prio class 0
  Jun 15 03:26:41 c68z kernel: [ 5335.934158] sd 2:0:0:0: [sdc] tag#22 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
  Jun 15 03:26:41 c68z kernel: [ 5335.934170] sd 2:0:0:0: [sdc] tag#22 Sense 
Key : Illegal Request [current] 
  Jun 15 03:26:41 c68z kernel: [ 5335.934177] sd 2:0:0:0: [sdc] tag#22 Add. 
Sense: Invalid command operation code
  Jun 15 03:26:41 c68z kernel: [ 5335.934184] sd 2:0:0:0: [sdc] tag#22 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fc 50 00 00 00 e0 00 00
  Jun 15 03:26:41 c68z kernel: [ 5335.934187] blk_update_request: critical 
target error, dev sdc, sector 19532872784 op 0x0:(READ) flags 0x0 phys_seg 28 
prio class 0
  Jun 15 03:27:05 c68z kernel: [ 5360.036887] sd 2:0:0:0: [sdc] tag#22 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
  Jun 15 03:27:05 c68z kernel: [ 5360.036926] sd 2:0:0:0: [sdc] tag#22 Sense 
Key : Illegal Request [current] 
  Jun 15 03:27:05 c68z kernel: [ 5360.036935] sd 2:0:0:0: [sdc] tag#22 Add. 
Sense: Invalid command operation code
  Jun 15 03:27:05 c68z kernel: [ 5360.036944] sd 2:0:0:0: [sdc] tag#22 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fa 50 00 00 00 e0 00 00
  Jun 15 03:27:05 c68z kernel: [ 5360.036949] blk_update_request: critical 
target error, dev sdc, sector 19532872272 op 0x0:(READ) flags 0x0 phys_seg 28 
prio class 0
  Jun 15 03:27:05 c68z kernel: [ 5360.037677] sd 2:0:0:0: [sdc] tag#23 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
  Jun 15 03:27:05 c68z kernel: [ 5360.037687] sd 2:0:0:0: [sdc] tag#23 Sense 
Key : Illegal Request [current] 
  Jun 15 03:27:05 c68z kernel: [ 5360.037700] sd 2:0:0:0: [sdc] tag#23 Add. 
Sense: Invalid command operation code
  Jun 15 03:27:05 c68z kernel: [ 5360.037707] sd 2:0:0:0: [sdc] tag#23 CDB: 
Read(16) 88 00 00 00 00 04 8c 3f fc 50 00 00 00 e0 00 00
  Jun 15 03:27:05 c68z kernel: [ 5360.037711] blk_update_request: critical 
target error, dev sdc, sector 19532872784 op 0x0:(R

[Kernel-packages] [Bug 1978873] [NEW] no picture from camera on starlabs starlite mk IV

Public bug reported:

camera is reported as :

Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

When using Cheese the camera turns on and syslog shows this :

Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

I get nothing from either picture or video options.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cheese 41.1-1build1
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
Uname: Linux 5.15.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 15 23:12:11 2022
InstallationDate: Installed on 2022-04-26 (50 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Star Labs Lite
RelatedPackageVersions:
 cheese41.1-1build1
 cheese-common 41.1-1build1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2022
dmi.bios.release: 4.16
dmi.bios.vendor: coreboot
dmi.bios.version: 4.16
dmi.board.name: Lite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 1.0
dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
dmi.product.family: I4
dmi.product.name: Lite
dmi.product.sku: I4
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug gstreamer-error jammy wayland-session

-- 
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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  New

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  Installat

[Kernel-packages] [Bug 1978873] Re: no picture from camera on starlabs starlite mk IV

attached screenshot showing what appears on screen when using Cheese


** Attachment added: "Screenshot from 2022-06-15 23-11-23.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978873/+attachment/5597537/+files/Screenshot%20from%202022-06-15%2023-11-23.png

-- 
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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  New

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978873/+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 1978873] Re: no picture from camera on starlabs starlite mk IV

It is supposed to be supported form 2.26 and up but it's not working on
my Ubuntu 22.04

https://linux-hardware.org/index.php?id=usb:0c45-6310

Gonna contact Starlab's tech support and ask them if anyone else
reported this to them.

-- 
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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  New

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978873/+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 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq

2022-06-15 Thread dann frazier

** Changed in: linux (Ubuntu Jammy)
   Status: Fix Committed => 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/1952933

Title:
  impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  Fix Released

Bug description:
  During MAAS deployment:

  [  107.768146] Unable to handle kernel read from unreadable memory at
  virtual address 

   domain : maas[  107.943413] 
Mem abort info:
  
   rootserver: 10.229.32.21 rootpath: 
   filename  :[  108.043666]   ESR = 0x9604
   lpxelinux.0
  :: root=squash:http://10.229.32.21:5248/images/ubu[  108.147045]   EC = 0x25: 
DABT (current EL), IL = 32 bits
  ntu/arm64/xgene-uboot/impish/stable/squashfs
  :: mount_squash do[  108.277541]   SET = 0, FnV = 0
  wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[  
108.380921]   EA = 0, S1PTW = 0
  ot/impish/stable/squashfs to /root.tmp.img
  Connecting to 10.229[  108.485351] Data abort info:
  .32.21:5248 (10.229.32.21:5248)
  [  108.586639]   ISV = 0, ISS = 0x0004
  [  108.667060]   CM = 0, WnR = 0
  [  108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000
  root.tmp.img [  108.779941] [] pgd=, 
p4d=
4% [  108.884372] Internal error: Oops: 9604 [#1] SMP
  [  108.948102] Modules linked in: raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core 
gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs 
aes_neon_blk crypto_simd cryptd
  [  109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic 
#20-Ubuntu
  [  109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [  109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--)
  [  109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en]
  [  109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en]
  [  109.652828] sp : 8000129cbc60
  [  109.692470] x29: 8000129cbc60 x28: 012c x27: 
000ff7e95fc0
  [  109.778115] x26:  x25: 20908508 x24: 
21b40940
  [  109.863763] x23: 20908508 x22: 20908400 x21: 
21b4
  [  109.949409] x20: 0040 x19: 0040 x18: 
0014
  [  110.035056] x17: 1122e350 x16: cb46f8bb x15: 
e2b6a183
  [  110.120703] x14: 26fff11e x13: 9312ff0b x12: 

  [  110.206349] x11: 0006 x10: 0040 x9 : 
89119320
  [  110.291997] x8 : 08acdc00 x7 : 02c0 x6 : 
dff8
  [  110.377642] x5 : 0394 x4 : 03960040 x3 : 
21c2
  [  110.463289] x2 :  x1 :  x0 : 

  [  110.548937] Call trace:
  [  110.578147]  mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en]
  [  110.637719]  __napi_poll+0x40/0x1e0
  [  110.679551]  net_rx_action+0x2d8/0x34c
  [  110.724513]  __do_softirq+0x128/0x388
  [  110.768432]  run_ksoftirqd+0x6c/0x94
  [  110.811308]  smpboot_thread_fn+0x15c/0x1a0
  [  110.860443]  kthread+0x114/0x120
  [  110.899145]  ret_from_fork+0x10/0x18
  [  110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) 
  [  111.015158] ---[ end trace b37ae99414884442 ]---
  [  111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt
  [  111.152964] SMP: stopping secondary CPUs
  [  111.200016] Kernel Offset: 0x8 from 0x80001000
  [  111.265837] PHYS_OFFSET: 0x40
  [  111.309651] CPU features: 0x0251,0046
  [  111.361915] Memory Limit: none
  [  111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in 
interrupt ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+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 1978873] 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 1978873

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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978873/+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 1978145] Re: Request to back port vmci patches to Ubuntu kernel

2022-06-15 Thread Vishnu Dasa

Hi Tim,
No, not exactly.  We have a new version of the VMCI device itself and
patches #1 to #11 provide support for that, see [1] for some information
on what is new.  #12 adds arm64 support (we only support the new version
of the VMCI device in arm64, but both old and new versions of VMCI
device are supported in x86).  #13 is a general bugfix.  All 13 patches
can build on both x86 and arm64.  Please let me know if this helps.

[1] https://lore.kernel.org/all/20220203131237.3380-1-jhan...@vmware.com

Thanks,
Vishnu

-- 
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/1978145

Title:
  Request to back port vmci patches to Ubuntu kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The request is to bring vmci to TOT and back port the following patches into
  Ubuntu kernels.

  1.  fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace 
formatting change for vmci register defines")
  2.  e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access 
to registers")
  3.  eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA 
datagram capability")
  4.  8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page 
size")
  5.  cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy 
IRQ handlers for DMA datagrams")
  6.  5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send 
and receive buffers for DMA datagrams")
  7.  22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for 
DMA datagrams sends")
  8.  463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for 
DMA datagrams receive")
  9.  77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling 
paths in vmci_guest_probe_device()")
  10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release 
notification_bitmap in error path")
  11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors 
when freeing interrupt 1")
  12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
  13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the 
work is already queued")

  Thanks,
  Vishnu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+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 1978873] Re: no picture from camera on starlabs starlite mk IV

Been able to get "some" kind of colorless picture using guvcview
So camera seems to be working

But there are almost no colors, and default settings produce a very
dark, useless content.

The attached screenshot was done using the following setrings in
guvcview :

Saturation : 19
Contrat : 64
Saturation : 128
Hue : 0
White Balance : auto
Gamma : 110
Gain : 85
Power Line Frequency : disabled
Sharpness : 6
Backlight Compensation : 0

The setting that has the most dramatic effect is the Exposure
It must be set to manual or the picture I get is a white blur

Exposure Absolute : 3200
Exposure Auto Priority : OFF


Hoping this information will help you make that camera work on Cheese ?


** Attachment added: "Screenshot from 2022-06-15 23-49-52.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978873/+attachment/5597540/+files/Screenshot%20from%202022-06-15%2023-49-52.png

** Tags added: apport-collected

** Description changed:

  camera is reported as :
  
  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
  
  When using Cheese the camera turns on and syslog shows this :
  
  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
  
  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor
  
  I get nothing from either picture or video options.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  gf 1497 F pulseaudio
+  /dev/snd/controlC1:  gf 1497 F pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-04-26 (50 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
+  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
+  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Star Labs Lite
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro

[Kernel-packages] [Bug 1978873] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597546/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log presen

[Kernel-packages] [Bug 1978873] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597547/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log presen

[Kernel-packages] [Bug 1978873] AlsaInfo.txt

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597541/+files/AlsaInfo.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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log pres

[Kernel-packages] [Bug 1978873] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597542/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade

[Kernel-packages] [Bug 1978873] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597543/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log pres

[Kernel-packages] [Bug 1978873] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1978873/+attachment/5597548/+files/PaInfo.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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (

[Kernel-packages] [Bug 1978873] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1978873/+attachment/5597544/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (pr

[Kernel-packages] [Bug 1978873] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597545/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log pres

[Kernel-packages] [Bug 1978873] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597557/+files/acpidump.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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log pres

[Kernel-packages] [Bug 1978873] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597553/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade lo

[Kernel-packages] [Bug 1978873] Re: no picture from camera on starlabs starlite mk IV

Log from using guvcview :

Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Activating service name='org.gnome.ControlCenter.SearchProvider' requested by 
':1.33' (uid=1000 pid=1663 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Activating service name='org.gnome.Nautilus' requested by ':1.33' (uid=1000 
pid=1663 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Activating service name='org.gnome.Calculator.SearchProvider' requested by 
':1.33' (uid=1000 pid=1663 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Activating service name='org.gnome.Characters.BackgroundService' requested by 
':1.33' (uid=1000 pid=1663 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Successfully activated service 'org.gnome.Nautilus'
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Successfully activated service 'org.gnome.Characters.BackgroundService'
Jun 15 23:54:37 pluton dbus-daemon[1512]: [session uid=1000 pid=1512] 
Successfully activated service 'org.gnome.Calculator.SearchProvider'
Jun 15 23:54:37 pluton gnome-calculato[9968]: search-provider.vala:140: Failed 
to spawn Calculator: Child process killed by signal 9
Jun 15 23:54:37 pluton nautilus[9969]: Connecting to 
org.freedesktop.Tracker3.Miner.Files
Jun 15 23:54:39 pluton systemd[1488]: Started Application launched by 
gnome-shell.
Jun 15 23:54:39 pluton guvcview.desktop[10006]: V4L2_CORE: (UVCIOC_CTRL_MAP) 
Error: No such file or directory
Jun 15 23:54:39 pluton guvcview.desktop[10006]: message repeated 8 times: [ 
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory]
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm_route.c:877:(find_matching_chmap) Found no matching channel map
Jun 15 23:54:39 pluton guvcview.desktop[10006]: message repeated 3 times: [ 
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map]
Jun 15 23:54:39 pluton guvcview.desktop[10006]: Cannot connect to server socket 
err = No such file or directory
Jun 15 23:54:39 pluton guvcview.desktop[10006]: Cannot connect to server 
request channel
Jun 15 23:54:39 pluton guvcview.desktop[10006]: jack server is not running or 
cannot be started
Jun 15 23:54:39 pluton guvcview.desktop[10006]: 
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping 
unlock
Jun 15 23:54:39 pluton guvcview.desktop[10006]: 
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping 
unlock
Jun 15 23:54:39 pluton guvcview.desktop[10006]: Cannot connect to server socket 
err = No such file or directory
Jun 15 23:54:39 pluton guvcview.desktop[10006]: Cannot connect to server 
request channel
Jun 15 23:54:39 pluton guvcview.desktop[10006]: jack server is not running or 
cannot be started
Jun 15 23:54:39 pluton guvcview.desktop[10006]: 
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping 
unlock
Jun 15 23:54:39 pluton guvcview.desktop[10006]: 
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping 
unlock
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
confmisc.c:160:(snd_config_get_card) Invalid field card
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
confmisc.c:160:(snd_config_get_card) Invalid field card
Jun 15 23:54:39 pluton guvcview.desktop[10006]: ALSA lib 
pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
Jun 15 23:54:39 pluton guvcview.desktop[10006]: Cannot connect to server socket 
err = No such file or directory
Jun 15 23:54:39 pluton guvcview.desktop[10006]: Cannot connect to server 
request channel
Jun 15 23:54:39 pluton guvcview.desktop[10006]: jack server is not running or 
cannot be started
Jun 15 23:54:39 pluton guvcview.desktop[10006]: 
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping 
unlock
Jun 15 23:54:39 pluton guvcview.desktop[10006]: 
JackSh

[Kernel-packages] [Bug 1978873] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597552/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgr

[Kernel-packages] [Bug 1978873] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1978873/+attachment/5597554/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (

[Kernel-packages] [Bug 1978873] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1978873/+attachment/5597555/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (

[Kernel-packages] [Bug 1978873] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

[Kernel-packages] [Bug 1978873] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597551/+files/ProcEnviron.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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade lo

[Kernel-packages] [Bug 1978873] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597556/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log

[Kernel-packages] [Bug 1978873] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597549/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade lo

[Kernel-packages] [Bug 1978873] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1978873/+attachment/5597550/+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/1978873

Title:
  no picture from camera on starlabs starlite mk IV

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  camera is reported as :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  When using Cheese the camera turns on and syslog shows this :

  Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera

  Jun 15 23:08:28 pluton cheese[4493]: Native Windows taller than 65535 pixels 
are not supported
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: Unsupported modifier, resource 
creation failed.
  Jun 15 23:08:29 pluton org.gnome.Cheese[4493]: XXX: resource creation failed
  Jun 15 23:08:29 pluton cheese[4493]: A lot of buffers are being dropped.: 
../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:#012There
 may be a timestamping problem, or this computer is too slow.
  Jun 15 23:09:05 pluton cheese[4493]: Unable to create dummy onscreen: No 
foreign surface, and wl_shell unsupported by the compositor

  I get nothing from either picture or video options.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 15 23:12:11 2022
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Star Labs Lite
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1497 F pulseaudio
   /dev/snd/controlC1:  gf 1497 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (50 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  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.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus:

[Kernel-packages] [Bug 1978881] [NEW] Built-in laptop webcam not working on Ubuntu 22.04 LTS

2022-06-15 Thread Patrick Aziken

Public bug reported:

On Ubuntu 22.04, the web camera does not work. It worked previously
until about a week ago, after a few operating system updates. One of the
updates may have broken the camera functionality.

In apps like web browsers (Chrome, Firefox, Edge) the camera does not
work in Google Meet, Facebook or any website that utilizes the webcam.
In desktop apps like the Camera app from the Ubuntu software center, the
camera does not work either, the screen just shows blank when you launch
the camera desktop app.

On my computer, there is always a red light that shows when the camera
is on, but in the last one week, it has stopped showing, to mean that
the camera is not working.

** Affects: linux-signed-hwe-5.13 (Ubuntu)
Importance: Undecided
Status: New

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1978881

Title:
Built-in laptop webcam not working on Ubuntu 22.04 LTS

Status in linux-signed-hwe-5.13 package in Ubuntu:
New

Bug description:
On Ubuntu 22.04, the web camera does not work. It worked previously
until about a week ago, after a few operating system updates. One of
the updates may have broken the camera functionality.

In apps like web browsers (Chrome, Firefox, Edge) the camera does not
work in Google Meet, Facebook or any website that utilizes the webcam.
In desktop apps like the Camera app from the Ubuntu software center,
the camera does not work either, the screen just shows blank when you
launch the camera desktop app.

On my computer, there is always a red light that shows when the camera
is on, but in the last one week, it has stopped showing, to mean that
the camera is not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978881/+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 1961996] Re: Webcams no longer have correct names

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1961996

Title:
  Webcams no longer have correct names

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  I've got two webcams: one of them is built in to my Lenovo T14s
  (running Ubuntu 20.04.4), and the other is an external USB device.
  They used to have obvious names: one was called something like
  "Integrated Camera C" and the other was called something like
  "HuddleCamHD". Strangely, they have both been renamed to be "Video
  Capture 4", which means I can't easily distinguish between them when
  switching cameras in tools such as Zoom or OBS Studio. Here's some
  output showing this:

  $ v4l2-ctl --list-devices  
  Video Capture 4 (usb-:00:14.0-5.2.3):
  /dev/video2
  /dev/video3

  Video Capture 4 (usb-:00:14.0-8):
  /dev/video0
  /dev/video1

  Likewise, I'm seeing precisely the same issue on my desktop computer,
  which is also running Ubuntu 20.04.04:

  Video Capture 4 (usb-:00:14.0-3.4.3):
  /dev/video0
  /dev/video1

  I'm running kernel version 5.13.0-30. This error first occurs with
  kernel version 5.13.0-28. If I boot with an earlier version, it
  detects the webcam names just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 23 07:09:46 2022
  InstallationDate: Installed on 2020-05-08 (655 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961996/+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 1978881] Re: Built-in laptop webcam not working on Ubuntu 22.04 LTS

2022-06-15 Thread Patrick Aziken

Please close this bug. I realized this was my error with deactivating
the camera. So it is no longer valid.

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
Status: New => Invalid

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1978881

Title:
Built-in laptop webcam not working on Ubuntu 22.04 LTS

Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid

In apps like web browsers (Chrome, Firefox, Edge) the camera does not
work in Google Meet, Facebook or any website that utilizes the webcam.
In desktop apps like the Camera app from the Ubuntu software center,
the camera does not work either, the screen just shows blank when you
launch the camera desktop app.

On my computer, there is always a red light that shows when the camera
is on, but in the last one week, it has stopped showing, to mean that
the camera is not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978881/+subscriptions

[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)

2022-06-15 Thread ska

I have the same Problem on the following Model:

HP ENVY x360 Convertible 15-eu0xxx (3Y5D5EA#ABD)

Before the recent UEFI update form 20.03.2022 the install was possible.

-- 
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/1970127

Title:
  Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7
  3700U)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY
  X360 notebook (Ryzen 7 3700U).

  Model:
  HP ENVY X360
  13-ar0777ng
  9YN58EA#ABD

  After a few minutes the screen simply switches to black. No
  possibility to get a console by pressing CTRL-ALT-F1, F2, ...

  I removed the boot options "quiet splash" and recorded the boot via video.
  (just ask if you need the full video)
  I attach a significantly looking screenshot from that video, showing a kernel 
bug message.

  
  Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel.
  But suspend to memory isn't working.
  Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+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 1978905] [NEW] Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)

2022-06-15 Thread Daniel van Vugt

Public bug reported:

Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to
Intel GPU display ports)

This is different to the usual dual GPU setup where Intel is primary and
Nvidia is secondary.

** Affects: mutter
 Importance: Unknown
 Status: Unknown

** Affects: mutter (Ubuntu)
 Importance: Wishlist
 Status: Triaged

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: multimonitor nvidia nvidia-wayland wayland wayland-session

** Tags added: wayland wayland-session

** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2295
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2295

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2295
   Importance: Unknown
   Status: Unknown

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided => Wishlist

** Tags added: multimonitor

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu.
https://bugs.launchpad.net/bugs/1978905

Title:
  Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to
  Intel GPU display ports)

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to
  Intel GPU display ports)

  This is different to the usual dual GPU setup where Intel is primary
  and Nvidia is secondary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1978905/+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 1946507] Re: Ubuntu Install Setup Freeze

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1946507

Title:
  Ubuntu Install Setup Freeze

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  While trying to Install Ubuntu 21.10 , the setup freeze after clicking
  continue on Step 4 where it asks if you wish to install Updates , and
  i have selected Normal Installation when i click continue then setup
  freeze so im not able to click any other button just QUIT button is
  working , other buttons are grayed out and not clickable , i have
  tried many methods since 2 days been trying nomodeset acpi=off and
  other but nothing works for me , i need help .

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity 21.10.6 [modified: 
lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 15:56:06 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset 
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+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 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?

2022-06-15 Thread Kai-Heng Feng

So it's because the audio part of the discrete GFX is not runtime
suspended.

-- 
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/1973633

Title:
  wrong acpi_call sent at boot, how to disable discrete graphic card?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi to the Ubuntu team,

  
  Key info:
  MSI Delta 15 A5EFK laptop
  dual boot Ubuntu 22.04 LTS/Windows 11
  Ubuntu 5.15.0-27.28-generic 5.15.30
  hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD 
Ryzen 9 5900HX)
  open source amdgpu drivers
  

  I tried to combined one bug report with one related question hoping
  this is fine.

  -The bug-
  I've noticed the following error when booting on my ubuntu partition:

  [0.649628] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330)
  [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 
219896/6725632 files, 3948761/2688 blocks

  I did not really worried about that first. But then when I wanted to
  reduce my battery draining on my ubuntu partition (half of the battery
  life on my windows partition for similar usage) I've seen that
  disabling my discrete graphic card could be one thing to try to reduce
  power consumption. So I thought about using (i) acpi_call as stated or
  (ii) vga_switcheroo as stated in
  https://help.ubuntu.com/community/HybridGraphics . However, for (i) I
  need to know the correct calls to send to ACPI and my latptop is not
  listed here: https://hybrid-graphics-
  linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call
  that the kernel is trying to send at boot (for whatever reason) is
  also wrong. For (ii) I think that vga_switcheroo is also using
  acpi_call under the hood to disable the discrete graphic card. Which
  leads now to:

  -Question-
  Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I 
just want to be really sure about what I'm doing here because the doc states to 
modifiy the grub config and I'm really not confortable with dealing with the 
boot manager knowing the above bug. Is there a way to find the correct ACPI 
call?
  Adittional output asked by the doc:
  mustang@MSI:~$ sudo grep -i switcheroo /boot/config-*
  /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y
  /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y

  Thank you for you help,
  Best regards,
  Jeremy
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-08 (8 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-27-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: 10/28/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E15CKAMS.105
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-15CK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1:
  dmi.product.family: Delta
  dmi.product.name: Delta 15 A5EFK
  dmi.product.sku: 15CK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+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 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?

2022-06-15 Thread Kai-Heng Feng

Can you please give more recent kernel a try:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18.4/amd64/

-- 
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/1973633

Title:
  wrong acpi_call sent at boot, how to disable discrete graphic card?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi to the Ubuntu team,

  
  Key info:
  MSI Delta 15 A5EFK laptop
  dual boot Ubuntu 22.04 LTS/Windows 11
  Ubuntu 5.15.0-27.28-generic 5.15.30
  hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD 
Ryzen 9 5900HX)
  open source amdgpu drivers
  

  I tried to combined one bug report with one related question hoping
  this is fine.

  -The bug-
  I've noticed the following error when booting on my ubuntu partition:

  [0.649628] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330)
  [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 
219896/6725632 files, 3948761/2688 blocks

  I did not really worried about that first. But then when I wanted to
  reduce my battery draining on my ubuntu partition (half of the battery
  life on my windows partition for similar usage) I've seen that
  disabling my discrete graphic card could be one thing to try to reduce
  power consumption. So I thought about using (i) acpi_call as stated or
  (ii) vga_switcheroo as stated in
  https://help.ubuntu.com/community/HybridGraphics . However, for (i) I
  need to know the correct calls to send to ACPI and my latptop is not
  listed here: https://hybrid-graphics-
  linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call
  that the kernel is trying to send at boot (for whatever reason) is
  also wrong. For (ii) I think that vga_switcheroo is also using
  acpi_call under the hood to disable the discrete graphic card. Which
  leads now to:

  -Question-
  Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I 
just want to be really sure about what I'm doing here because the doc states to 
modifiy the grub config and I'm really not confortable with dealing with the 
boot manager knowing the above bug. Is there a way to find the correct ACPI 
call?
  Adittional output asked by the doc:
  mustang@MSI:~$ sudo grep -i switcheroo /boot/config-*
  /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y
  /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y

  Thank you for you help,
  Best regards,
  Jeremy
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-08 (8 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-27-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: 10/28/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E15CKAMS.105
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-15CK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1:
  dmi.product.family: Delta
  dmi.product.name: Delta 15 A5EFK
  dmi.product.sku: 15CK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+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 1978915] [NEW] alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec

2022-06-15 Thread Hui Wang

Public bug reported:

This bug is for tracking purpose.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: New

** Affects: linux-oem-5.14 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-5.14 (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux-oem-5.14 (Ubuntu Jammy)
 Importance: Undecided
 Status: Invalid


** Tags: oem-priority originate-from-1978898 sutton

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Tags added: oem-priority originate-from-1978898 sutton

-- 
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/1978915

Title:
  alsa/hda: mute led can't work on the lenovo machine with cs35l41
  s-codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978915/+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 1978915] Missing required logs.