[Desktop-packages] [Bug 2056758] Autopkgtest regression report (apport/2.28.1-0ubuntu3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apport (2.28.1-0ubuntu3) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:24.04.16 (arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  ubuntu-bug doesn't let me file bugs for Snap thunderbird

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid
Status in apport source package in Noble:
  Fix Committed

Bug description:
  I'm trying to report a bug in the new Snap for Thunderbird.

  When I run "ubuntu-bug thunderbird", it:
  * Collects information correctly after I input the sudo password
  * Opens a page like 
https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?,
 which does not seem to be valid.

  This is not the case for Firefox, which works fine with ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 
14:47:27.874792575 
+0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash
   640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 
17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash
  CurrentDesktop: KDE
  Date: Mon Mar 11 16:54:18 2024
  InstallationDate: Installed on 2022-08-29 (560 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2056758/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2063221] Autopkgtest regression report (glib2.0/2.80.0-6ubuntu3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glib2.0 (2.80.0-6ubuntu3) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu2 (ppc64el)
cluster-glue/1.0.12-22.1ubuntu3 (ppc64el)
cpdb-backend-cups/2.0~b5-0ubuntu6 (armhf)
cpdb-libs/2.0~b5-1.2build1 (armhf)
dbus-test-runner/19.04.0-1build2 (arm64)
lasi/unknown (arm64)
libsoup2.4/2.74.3-6ubuntu1 (arm64, ppc64el)
mender-client/3.4.0+ds1-5build3 (armhf)
snapd-glib/1.64-0ubuntu5 (ppc64el, s390x)
software-properties/unknown (amd64, arm64, armhf, i386, ppc64el, s390x)
surf/2.1+git20221016-6build2 (armhf)
ymuse/0.22-1build2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  Fix Committed

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Technically, Steve Langasek already removed libglib2.0-0 from noble
  release just before release. This upload is necessary to ensure that
  we don't accidentally bring it back.

  Test Case
  -
  1. Is libglib2.0-0 built?

  2. Run rmadison libglib2.0-0
  There should be 0 results for noble, noble-proposed, or noble-updates

  3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu
  22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is
  currently set to disallow upgrades to 24.04 LTS. If this is still the
  case when it is time to verify this SRU, you can manually substitute
  jammy → noble in /etc/apt/sources.list for purposes of testing this
  upgrade, probably in a VM since that's not the supported way to
  upgrade.

  Where Problems Could Occur
  --
  Doing an upload to not build a package that already does not exist in Ubuntu 
24.04 LTS should have no regression potential. The only other change in this 
SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 
is also removed for people who were using Ubuntu 24.04 LTS early. That also 
should not cause problems since the package was an empty transitional package 
for early Ubuntu 24.04 LTS users.

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  removing the transitional package and some other workarounds in other
  packages, like in the transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

  We have landed the removal in Debian Unstable and it successfully
  migrated to Debian Testing on April 27 as one of the first t64
  packages to migrate there.

  The removal was recommended by Julian Klode, the apt maintainer for
  Debian and Ubuntu.

  The original transitional package was added by Simon McVittie in hopes
  that it would help apt be able to calculate the upgrade easier. At
  least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like
  it was the opposite. (Although that particular detail was fixed by the
  removal that already happened.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1980836] Autopkgtest regression report (poppler/22.02.0-2ubuntu0.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted poppler (22.02.0-2ubuntu0.4) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

xapers/0.9.0-1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#poppler

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Regression in Ubuntu 22.04: Content of form field stored invisibly

Status in Poppler:
  Fix Released
Status in evince package in Ubuntu:
  Invalid
Status in poppler package in Ubuntu:
  Triaged
Status in evince source package in Jammy:
  Invalid
Status in poppler source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  The bug causes text entered in certain PDF form fields to be stored
  but both displayed and printed white (on white background).

  [ Test Plan ]

  1. Download the attached 230-muster-01.pdf.
  2. Try to input to any of the main content fields starting with 06-09 
("Anrede des Zahlungspflichtigen etc").
  3. Observe that it does not work.
  4. Install the updated poppler package versions
  5. Try the same fields and see they're functoning properly now with visible 
text.
  6. Test also that the fields like "Aktenzeichen", "TL-Nr." or 
"Buchungsstelle" that weren't broken, continue to work.

  [ Where problems could occur ]

  It is a merged upstream fix to Annot.cc file that fixed two upstream
  bugs https://gitlab.freedesktop.org/poppler/poppler/-/issues/1189 and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267.

  There are no indications of upstream regressions caused by this fix,
  and it was released in upstream stable release 22.08.0 (Ubuntu 22.04
  LTS has version based on 22.02.0).

  However, since it's an individual cherry-pick there could always be a
  PDF somewhere having issues with this, so it's useful to let it be
  tested with various files in addition to the problematic ones.

  --- original report ---

  Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly
  anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu
  20.04.

  The symptom is that one can edit the form content and also save it,
  but that the entered text is only visible when the form field is
  focused and in edit mode. Otherwise the text it is invisible, also on
  printouts.

  Such bugs have been reported against Evince for a long time (e.g.,
  https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I
  am reporting this as a new bug because for the current form with which
  I am experiencing this it is a regression.

  I have attached the problematic form with two form fields filled out, one in 
the upper left corner and the big one in the lower half.
  I have produced this by taking the original, empty form (produced by somebody 
else) and first opened it in Evince 41.4, which I have installed from the snap 
package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field 
and saved the form.
  Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and 
entered text in the big field and saved the form.

  Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince
  41.4.

  When I open the PDF again, only the text in the first field is
  visible. The text in the second field is visible only if I click into
  the field. The visibility of the field contents is the same for Evince
  41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems
  that the problem is with Evince 42.3 incorrectly saving the field
  content, not with displaying it.

  Firefox shows and prints the content of both fields, though.

  Note that I cannot switch back to Evince 41 because for some other
  forms that I have the exact same problem happens only with the old
  version and the new version fixes it. So it seems that something
  changed that fixed it for some forms and broke it for others.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:32:27 2022
  InstallationDate: Installed on 2021-11-26 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes:
   ID   Status  Spawn  Bereit 
Zusammenfassung
   137  Done2022-07-06T12:48:33+02:00  

[Desktop-packages] [Bug 2056331] Autopkgtest regression report (xorg-server/2:21.1.7-3ubuntu2.10)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server (2:21.1.7-3ubuntu2.10) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

at-spi2-core/2.50.0-1 (armhf)
balsa/2.6.4-2 (armhf)
cataclysm-dda/0.G-4 (armhf)
dogtail/0.9.11-12 (armhf)
jsurf-alggeo/0.4.1+ds-4ubuntu1 (armhf)
libsoup2.4/2.74.3-1 (arm64)
mediaconch/23.07-1 (armhf)
mutter/45.2-0ubuntu4 (armhf)
openmsx/19.0-1ubuntu1 (armhf)
pango1.0/1.51.0+ds-2 (armhf)
puzzle-jigsaw/1.0.2+git20201007.527c529+dfsg-4 (arm64)
rust-gtk4/0.7.3-2 (armhf)
rust-x11-clipboard/0.6.1-1 (armhf)
silx/1.1.2+dfsg-2 (armhf)
surf/2.1+git20221016-5 (arm64)
ubuntu-release-upgrader/1:23.10.14 (arm64, armhf, ppc64el, s390x)
uqm/0.8.0+dfsg-2 (armhf)
xlbiff/4.6.5-1 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2056331

Title:
  [SRU] fix suspend/resume when there are no input devices

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Mantic:
  Fix Committed
Status in xorg-server source package in Noble:
  Fix Released

Bug description:
  [Impact]

  Bug is impacting the suspend/resume flow when there is no input device
  connected to machine. xorg hangs in this case.

  [Where problems could occur]

  The problem could occur in places where there is no input device
  connected to the system but a suspend/resume is triggered.

  [Test Case]

  * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed)
  * Update xorg-server to the version in -proposed: sudo apt install -t 
jammy-proposed xorg-server
  * Unplug all USB devices such as USB drive, keyboard, mouse, etc.
  * Set RTC timer and suspend the system via UART console
  $ echo 8 > /proc/sys/kernel/printk
  $ sudo rtcwake -v -m no -s 240
  $ sudo systemctl suspend

  [Regression Potential]

  The patch defines a default behavior in systemd_logind_drop_master
  function so there is a possibility that there might be a regression
  that may affect all the systems that utilizes
  systemd_logind_drop_master

  
  Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2056331/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2056331] Autopkgtest regression report (xorg-server/2:21.1.4-2ubuntu1.7~22.04.11)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server 
(2:21.1.4-2ubuntu1.7~22.04.11) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

airport-utils/2-8 (armhf)
apport/2.20.11-0ubuntu82.5 (armhf)
at-spi2-atk/2.38.0-3 (i386)
auto-multiple-choice/unknown (armhf)
libsoup3/3.0.7-0ubuntu1 (s390x)
mutter/42.9-0ubuntu7 (arm64)
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)
pytest-qt/4.0.2-1 (armhf)
python-qtpy/2.0.0-3 (amd64, arm64, armhf, ppc64el, s390x)
sasview/5.0.4-1 (armhf)
sphinx/4.3.2-1 (s390x)
update-manager/1:22.04.20 (amd64, arm64, armhf, i386, ppc64el, s390x)
xlbiff/4.6.3-1 (arm64)
xpra/3.1-1build5 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2056331

Title:
  [SRU] fix suspend/resume when there are no input devices

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Mantic:
  Fix Committed
Status in xorg-server source package in Noble:
  Fix Released

Bug description:
  [Impact]

  Bug is impacting the suspend/resume flow when there is no input device
  connected to machine. xorg hangs in this case.

  [Where problems could occur]

  The problem could occur in places where there is no input device
  connected to the system but a suspend/resume is triggered.

  [Test Case]

  * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed)
  * Update xorg-server to the version in -proposed: sudo apt install -t 
jammy-proposed xorg-server
  * Unplug all USB devices such as USB drive, keyboard, mouse, etc.
  * Set RTC timer and suspend the system via UART console
  $ echo 8 > /proc/sys/kernel/printk
  $ sudo rtcwake -v -m no -s 240
  $ sudo systemctl suspend

  [Regression Potential]

  The patch defines a default behavior in systemd_logind_drop_master
  function so there is a possibility that there might be a regression
  that may affect all the systems that utilizes
  systemd_logind_drop_master

  
  Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2056331/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2058687] Autopkgtest regression report (libreoffice/4:7.6.6-0ubuntu0.23.10.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libreoffice (4:7.6.6-0ubuntu0.23.10.1) 
for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.6.6-0ubuntu0.23.10.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] libreoffice 7.6.6 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release

   * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of 39 bugs):
   https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs

   7.6.6 RC3 is identical to the 7.6.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_76/1898/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 39 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2051895] Autopkgtest regression report (pulseaudio/1:16.1+dfsg1-2ubuntu4.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pulseaudio (1:16.1+dfsg1-2ubuntu4.1) 
for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

libopenmpt/0.7.2-1 (i386)
libsdl2/2.28.3+dfsg-2 (i386)
pipewire/0.3.79-2 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in pulseaudio source package in Mantic:
  Fix Committed
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2051895] Autopkgtest regression report (pulseaudio/1:15.99.1+dfsg1-1ubuntu2.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pulseaudio (1:15.99.1+dfsg1-1ubuntu2.2) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 (i386)
pipewire/0.3.48-1ubuntu3 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in pulseaudio source package in Mantic:
  Fix Committed
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2051074] Autopkgtest regression report (mutter/45.2-0ubuntu4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (45.2-0ubuntu4) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu4 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2054510] Autopkgtest regression report (mutter/45.2-0ubuntu4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (45.2-0ubuntu4) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu4 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

  https://gitlab.gnome.org/GNOME/mutter/-/issues/2880

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2046360] Autopkgtest regression report (mutter/45.2-0ubuntu2~really45.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (45.2-0ubuntu2~really45.0) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu2~really45.0 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Heavy stuttering in Firefox with mutter 45.1/45.2

Status in mutter package in Ubuntu:
  New
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  There is heavy stuttering visible in Firefox with mutter 45.1/45.2.
  This is a regression introduced upstream in mutter 45.1 (8f27ebf8),
  although it only hurts the triple buffering patch so that's where it's
  fixed:

  
https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689
  
https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45

  [ Workaround ]

  In /etc/environment:

    MUTTER_DEBUG_TRIPLE_BUFFERING=always

  or "never" also works. Just not "auto".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2037604] Autopkgtest regression report (mesa/23.2.1-1ubuntu3.1~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (23.2.1-1ubuntu3.1~22.04.1) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.9-0ubuntu5 (arm64, ppc64el)
vtk9/9.1.0+really9.1.0+dfsg2-3build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2045667] Autopkgtest regression report (gnome-shell/45.2-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-shell (45.2-0ubuntu1) for mantic 
have finished running.
The following regressions have been reported in tests triggered by the package:

riseup-vpn/0.21.11+ds1-5build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#gnome-shell

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2045667

Title:
  Update gnome-shell to 45.2

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Mantic:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.2/NEWS

  Test Case
  -
  Complete all the non-optional test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  gnome-shell provides the GNOME version number for the Settings app About 
page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by 
gnome-desktop/gnome-desktop3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045667/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2035076] Autopkgtest regression report (mutter/45.2-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (45.2-0ubuntu1) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Can't enter capital accented letters with Caps Lock on Wayland

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter package in Fedora:
  Unknown

Bug description:
  Impact
  --
  Capital accented letters can't be entered using CAPS LOCK in the Wayland 
session

  Test Case
  -
  Open a terminal and install basic French support:
  sudo apt install language-pack-gnome-fr

  Open the Settings app. In the sidebar, click Keyboard
  Click +, choose French (France), then choose the French (AZERTY) keyboard
  Close the Settings app
  In the top right of the screen, click en and switch the keyboard layout to 
French (AZERTY)
  In the text editor, type é (this is the number 2 key on a US English 
keyboard).
  Now, press the Caps Lock key to enable Caps Lock.
  Press the same key. You should get É

  What Could Go Wrong
  ---
  This fix is included in mutter 45.2 so see the master bug for this upstream 
update: LP: #2043000

  Original bug report
  ---
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.

  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.

  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']

  If you want É:
  [Super left] + [E] + [']

  Do the same for the other vowels.
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2043000] Autopkgtest regression report (mutter/45.2-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (45.2-0ubuntu1) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update mutter to 45.2

Status in mutter package in Ubuntu:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits 
cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa 
regression is handled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2043027] Autopkgtest regression report (mutter/45.2-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (45.2-0ubuntu1) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Wacom Intuos S stop working after upgrading to Ubuntu 23.10

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  Impact
  --
  Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 
sessions

  Test Case
  -
  One of the people affected by this issue will verify whether their Wacom 
tablet is working noticably better with the upgraded Mutter packages

  What Could Go Wrong
  ---
  The fix for this issue is included in upstream's mutter 45.2 release so 
please see bug 2043000 as the master bug for this upgrade

  Original Bug Report
  ---
  Tablet seems to work until I open Krita (as I could read on Internet, it may 
be related with Qt Apps).

  When Krita is open, mouse movement works ok with the tablet, but when
  it comes to click action it doesn't work and any further action with
  mouse is not captured (even outside Krita!).

  To regain control of the mouse I have to Alt+Tab and then I can click
  again.

  Some details that may be handy:
  - I've got two monitors
  - Maybe Qt apps related
  - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535

  Thanks for your effort. I love Ubuntu!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 17:20:34 2023
  DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2022-04-09 (578 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
  dmi.bios.date: 06/15/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0608
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B550-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  

[Desktop-packages] [Bug 2038834] Autopkgtest regression report (mesa/23.2.1-1ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (23.2.1-1ubuntu3.1) for mantic 
have finished running.
The following regressions have been reported in tests triggered by the package:

asymptote/2.86+ds-1 (armhf)
clutter-1.0/1.26.4+git2779b932+dfsg-5 (armhf)
freeglut/3.4.0-1 (armhf)
gle/3.1.0-10 (armhf)
glfw3/3.3.8-1 (armhf)
gtk+3.0/3.24.38-5ubuntu1 (armhf)
libcsfml/2.5-1.1 (armhf)
libsdl2/2.28.3+dfsg-2 (armhf)
mutter/45.0-3ubuntu3.1 (armhf)
njplot/2.4-9 (armhf)
vtk9/9.1.0+really9.1.0+dfsg2-7 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Mantic:
  Fix Committed
Status in mesa source package in Noble:
  Fix Released

Bug description:
  
  [ Impact ] 
   * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs 

   * This was reported by someone else upstream and is already fixed by 
 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

  [ Test Plan ]

   * I've tested the patch on an affected macOS host running Ubuntu in UTM with 
 OpenGL enabled on both Mantic and Noble VMs.

   * Anyone else can do the same on an affected host by simply installing the 
 patched package and booting to the desktop.

  [ Where problems could occur ]

   * This patch fixes an upstream mesa regression which caused libvirglrendrer 
to 
 crash on the host side.

   * This makes a non-working use case work, VirGL on affected hosts cannot 
 regress as it simply didn't work before.

   * Risk of breakage is mainly from other packages possible affected by a mesa 
 rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1794064] Autopkgtest regression report (evince/42.3-0ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted evince (42.3-0ubuntu3.1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

apparmor/3.0.4-2ubuntu2.2 (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#evince

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  Fix Committed
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040153] Autopkgtest regression report (network-manager/1.44.2-1ubuntu1.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted network-manager (1.44.2-1ubuntu1.2) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.44.2-1ubuntu1.2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#network-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040153

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  In Progress
Status in netplan.io source package in Mantic:
  Invalid
Status in network-manager source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete
  Network Manager connections persistently. That means that, when the 
connection is
  deliberately deleted by the user, it will re-appear when the system is 
rebooted or
  netplan apply is executed.

  This is happening because the systemd service unit is setting the property 
"ProtectSystem"
  to true. Because of that, /usr is being presented to the Network Manager 
daemon as read-only.
  When connections are deleted, libnetplan will try to open its YAML files with 
writing permissions
  and will fail for files from /usr/lib/netplan. Even if the user hasn't added 
any files there manually,
  the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by 
the package ubuntu-settings.

  This issue is fixed by allow-listing /usr/lib/netplan with 
ReadWritePaths=/usr/lib/netplan in systemd
  so the Network Manager's daemon will be able to write to that directory.

  This upload also improves the autopkgtests related to Netplan. Network 
Manager will be
  started by systemd, which ensures we are testing in the same environment 
conditions
  used by a desktop installation. It also adds a few more instances of 
connections deletions so
  we can test a bit more that YAML files are being removed. It also adds all 
the dependencies
  required by the test script (which sadly was causing the nm_netplan.py tests 
to be skipped).

  [ Test Plan ]

  Launch a new Mantic VM:

  $ lxc launch ubuntu:mantic --vm

  Install network-manager and ubuntu-settings:

  # apt install network-manager ubuntu-settings

  Run Netplan

  # netplan apply

  Create a dummy connection via nmcli:

  # nmcli con add type dummy connection.interface-name dummy0

  Check a new YAML will be created in /etc/netplan

  Delete the connection with nmcli

  # nmcli con del dummy-dummy0

  Check the YAML WAS NOT removed from /etc/netplan

  You will see the error below in the NetworkManager's journal

  netplan_delete_connection: Cannot write output state: Read-only file
  system

  Add the PPA containing the fix and run the same test described above

  # add-apt-repository ppa:danilogondolfo/network-manager
  # apt update
  # apt upgrade

  Check that the YAML will be created when the connection is added and
  deleted and the connection is removed.

  [ Where problems could occur ]

  As the only change is a relaxation of the restrictions applied by systemd on 
the environment where Network Manager
  runs, we are not expecting any regression.

  As for the changes in the autopkgtest related to Netplan, they are
  passing on all architectures.

  Autopkgtests

  amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz
  ppc64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz
  s390x - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz
  arm64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz
  armhf - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz

  [ Other Info ]

  
  --- Original description ---

  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will
  be recreated when "netplan generate" runs again.

  This is probably being caused by a combination of two things. First,
  the NM's systemd unit has this setting "ProtectSystem=true", which
  will mount 

[Desktop-packages] [Bug 2037274] Autopkgtest regression report (libreoffice/4:7.5.7-0ubuntu0.23.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libreoffice (4:7.5.7-0ubuntu0.23.04.1) 
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.5.7-0ubuntu0.23.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] libreoffice 7.5.7 for lunar

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.7 is in its seventh bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.7_release

   * Version 7.5.6 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.6 see the list of bugs fixed in the release candidates of 7.5.7 
(that's a total of 14 bugs):
   https://wiki.documentfoundation.org/Releases/7.5.7/RC1#List_of_fixed_bugs

   7.5.7 RC1 is identical to the 7.5.7 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1697/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15171690/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20230925_122613_dc43d@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20230925_154920_2e924@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20230926_164913_a0855@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20230925_123824_567d4@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20230925_131148_33d08@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 14 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2028082] Autopkgtest regression report (glib2.0/2.76.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glib2.0 (2.76.4-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

adsys/0.11.0 (arm64)
balsa/2.6.4-2 (arm64)
cmake-extras/1.6-1 (armhf)
firewalld/1.3.0-1 (arm64)
libsoup3/3.4.0-1 (amd64)
slurm-wlm/22.05.8-3 (armhf)
surf/2.1+git20221016-4build1 (armhf)
udisks2/2.9.4-4 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2028082

Title:
  Update glib to 2.76.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.76 series

  The current release in Ubuntu 23.04 is 2.76.1

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopkgtest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  The upstream gnome-remote-desktop maintainer requested that we do this update 
to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1990341] Autopkgtest regression report (ubuntu-drivers-common/1:0.9.7.1.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-drivers-common (1:0.9.7.1.2) for 
lunar have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-drivers-common/1:0.9.7.1.2 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#ubuntu-drivers-common

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Confirmed
Status in ubuntu-drivers-common source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033643] Autopkgtest regression report (libreoffice/4:7.5.6-0ubuntu0.23.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libreoffice (4:7.5.6-0ubuntu0.23.04.1) 
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.5.6-0ubuntu0.23.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] libreoffice 7.5.6 for lunar

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release

   * Version 7.5.5 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 
(that's a total of 53 bugs):
   https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs

   7.5.6 RC2 is identical to the 7.5.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1671/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 53 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/6.2.0-1013.13)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(6.2.0-1013.13) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-525-server/525.125.06-0ubuntu0.23.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1971242] Autopkgtest regression report (cups/2.4.1op1-1ubuntu4.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted cups (2.4.1op1-1ubuntu4.5) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/blacklisted (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#cups

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed
Status in cups source package in Lunar:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2027671] Autopkgtest regression report (libreoffice/4:7.5.5-0ubuntu0.23.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libreoffice (4:7.5.5-0ubuntu0.23.04.1) 
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.5.5-0ubuntu0.23.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] libreoffice 7.5.5 for lunar

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.5 is in its fifth bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.5_release

   * Version 7.5.4 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.4 see the list of bugs fixed in the release candidates of 7.5.5 
(that's a total of 70 bugs):
   https://wiki.documentfoundation.org/Releases/7.5.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.5.5/RC2#List_of_fixed_bugs

   7.5.5 RC2 is identical to the 7.5.5 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1589/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15016907/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230718_033443_f8aa9@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230714_103204_cba01@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230714_150913_425f2@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230714_061923_700ec@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230715_114537_85189@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 70 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2027671/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1971242] Autopkgtest regression report (cups/2.4.2-3ubuntu2.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted cups (2.4.2-3ubuntu2.3) for lunar have 
finished running.
The following regressions have been reported in tests triggered by the package:

cmake/3.25.1-1ubuntu1 (armhf)
foo2zjs/20200505dfsg0-2ubuntu3 (arm64)
libreoffice/4:7.5.4-0ubuntu0.23.04.1 (armhf)
samba/2:4.17.7+dfsg-1ubuntu1.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#cups

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed
Status in cups source package in Lunar:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2019212] Autopkgtest regression report (mesa/23.0.4-0ubuntu1~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (23.0.4-0ubuntu1~22.04.1) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk4/blacklisted (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport packages for 22.04.3 HWE stack

Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa-amber source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3

  mesa
  - new major release (23.0.4)

  mesa-amber
  - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no 
changes to the classic dri drivers
  - drops old i915 driver, while mesa provides the more modern i915_dri.so 
called 
i915g
  - fixes installation (LP: #2006744) and image build

  [Test case]
  mesa:
  Install the new mesa on various hw configs, check that everything still works 
like before or better.

  mesa-amber:
  no need to test anything besides checking that the packages can be installed 
next to mesa and image build is fixed

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2021948] Autopkgtest regression report (mesa/23.0.4-0ubuntu1~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (23.0.4-0ubuntu1~22.04.1) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk4/blacklisted (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  New bugfix release 23.0.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 23.0.x-series, we should put it
  in lunar so latest bugfixes would get there, and in jammy for 22.04.3
  image.

  We'll include an additional bugfix (a revert) to fix GPU hangs on some
  AMD gpu's running certain games.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2012978] Autopkgtest regression report (gjs/1.72.4-0ubuntu0.22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gjs (1.72.4-0ubuntu0.22.04.1) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gjs/1.72.4-0ubuntu0.22.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#gjs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Memory leak

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed
Status in gjs source package in Kinetic:
  Won't Fix

Bug description:
  [ Impact ]

  High Memory Usage 3.1gb in 2h after reboot

  [ Test case ]

  Run:
    env G_SLICE=always-malloc valgrind --leak-check=full \
  --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
  gjs -c "const GLib=imports.gi['GLib'];function leak(){const 
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"

  No leak should be detected

  Running more installed tests under valgrind should output no leaks
  (unless those caused by gobject-introspection):

  sudo apt install gjs-tests
  env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js

  There may be only two leaks caused by
  gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
  after a ObjectInstance::prop_setter_impl call (these are leaks in the
  test library that are expected with gobject-introspection 42, but
  fixed in later versions).

  env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js

  No leak expected

  [ Regression potential ]

  Gjs applications (including gnome Shell) using GVariant may misbehave

  ---

  ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  Uname: Linux 6.2.8-060208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 22:46:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-25 (366 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2023572] Autopkgtest regression report (gjs/1.72.4-0ubuntu0.22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gjs (1.72.4-0ubuntu0.22.04.1) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gjs/1.72.4-0ubuntu0.22.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#gjs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  SRU gjs 1.72.4 to jammy

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  That's the GNOME 42 stable update, including some fixes:
  https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  The test plan that will be used is documented at
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  [ Regression potential ]

  Gjs is fundamental part of the ubuntu desktop, so any failure of it
  may cause the desktop not even to boot (because it's being used by gdm
  too).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966413] Autopkgtest regression report (ubuntu-drivers-common/1:0.9.7.1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-drivers-common (1:0.9.7.1.1) for 
lunar have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties/0.99.35 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#ubuntu-drivers-common

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1966413

Title:
  [SRU] --no-oem option is broken

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed
Status in ubuntu-drivers-common source package in Kinetic:
  Won't Fix
Status in ubuntu-drivers-common source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  * ubuntu-drivers supports the --no-oem option, which is meant to filter-out 
the OEM metapackages when running on certified hardware.

  * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., 
`ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script 
crashes with the following exception:
    NameError: name 'install_oem_meta' is not defined

  * When ubuntu-drivers is invoked with --no-oem as a sub-option of
  "install" (i.e., `ubuntu-drivers install --no-oem`), the script does
  not crash but the option is silently ignored - resulting in an OEM
  metapackage to be installed if we are running on certified hardware.
  This defeats the purpose of the option.

  * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a 
suboption of `ubuntu-drivers install`. By default, the option is not passed to 
ubuntu-drivers but the users can opt-in using preseeds. If they do, their 
decision is essentially ignored since the OEM metapackage will still be 
installed:
  https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20

  * As part of the 23.10 cycle, subiquity will start replacing the
  functionality from ubiquity for OEM installs. At the moment, subiquity
  relies on the version of ubuntu-drivers-common from the system being
  installed. But going forward, we might have to ship ubuntu-drivers-
  common in the subiquity snap. This means we will fetch the deb from
  jammy-updates since subiquity is a core22-based snap.

  [Test plan]
  1. We will compare the result of the following commands with and without the 
patch (both on certified and on un-certified hardware):
    * ubuntu-drivers --no-oem list
    -> crashes without the patch. Should not crash with the patch. The list 
returned should not include the OEM metapackage.
    * ubuntu-drivers --no-oem install
    -> crashes without the patch. Should not crash with the patch. The list 
of packages installed should not include the OEM metapackage.
    * ubuntu-drivers install --no-oem
    -> without the patch, the OEM metapackage gets installed on certified 
hardware. With the patch, it should not.

  2. We will ensure ubiquity stills manages to install ubuntu on
  certified hardware. We will also ensure that the OEM metapackage does
  not get installed when it should not.

  [Where problems could occur]
  * When used as a global option, --no-oem currently makes the script crash 
unconditionally. Therefore, the change should be very low risk in that regard.
  * When used as a suboption of "install", the --no-oem option currently gets 
ignored silently. If people have been automating ubuntu deployment in one way 
or another and have used --no-oem, they might be surprised to notice that fewer 
packages get installed on their target system, after the option is fixed. This 
is theoretically a good thing, but might require some adjustments on their end.

  [Original description]
  $ ubuntu-drivers --no-oem install
  Traceback (most recent call last):
    File "/usr/bin/ubuntu-drivers", line 490, in 
  greet()
    File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
  return self.main(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
  rv = self.invoke(ctx)
    File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
  Command.invoke(self, ctx)
    File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
  return ctx.invoke(self.callback, **ctx.params)
    File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
  return ctx.invoke(f, obj, *args, 

[Desktop-packages] [Bug 1971242] Autopkgtest regression report (cups/2.4.1op1-1ubuntu4.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted cups (2.4.1op1-1ubuntu4.3) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

pappl/1.0.3-2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#cups

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Committed
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Chcke whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1794064] Autopkgtest regression report (apparmor/3.0.4-2ubuntu2.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apparmor (3.0.4-2ubuntu2.3) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

dbus/1.12.20-2ubuntu4.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#apparmor

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Incomplete
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1985089] Autopkgtest regression report (mutter/42.9-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (42.9-0ubuntu1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.9-0ubuntu1 (arm64, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Resizing two edge tiled windows is laggy

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Mutter 42.9 includes a fix for tiled window resizing. Before the fix, window 
resizing could use very large amounts of memory and be laggy.

  Test Case
  -
  0. Install the updated mutter packages. Log out then log back in.
  1. Open System Monitor. Tile it to the Left.
  2. Open a Terminal. Tile it to the right.
  3. Click the Resources tab in System Monitor.
  3. Right-click the System Monitor in the headerbar and click Resize.
  4. Move your mouse left and right to resize the window.
  5. The memory should not dramatically spike higher as seen in the System 
Monitor's Resources tab.

  What Could Go Wrong
  ---
  See the master mutter 42.9 bug LP: #1998286

  Original Bug Report
  ---
  Just to report an issue that other people have reported to GNOME and in 
Reddit, that seems to also affect Ubuntu 22.04.

  If you snap 2 windows side-by-side in Wayland and then try to resize
  them, it's very slow and uses a lot of memory.

  Check here for more details:
  - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246
  - 
https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1985089/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1998286] Autopkgtest regression report (mutter/42.9-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (42.9-0ubuntu1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.9-0ubuntu1 (arm64, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Release mutter 42.9 to jammy

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS

  The overall GNOME project considers GNOME 42 to be end of life now and
  there are no more scheduled releases for mutter 42 after 42.9

  This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913

  The current version of Mutter in Jammy is 42.5.

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  Extra Test Case 1
  -
  This release also cherry-picks a patch to fix the prompt to enable 
accessibility features using keyboard shortcuts.

  0. Install the updated mutter packages. Then log out and log back in.
  1. Open the Settings app (gnome-control-center)
  2. In the left sidebar, click Accessibility
  3. In the typing section, lick Typing Assist
  4. Turn on the first switch to enable turning accessibility features on and 
off using the keyboard
  5. Close the Settings app
  6. Press the Shift key 5 or 6 times in a row
  7. You should see a system prompt about turning on Sticky Keys

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  Upstream assumes that people will be using matching versions of mutter and 
gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME 
Shell 42.9 to require mutter >= 42.9 (even though GNOME Shell 42.9 appears to 
run ok with Mutter 42.5). I believe the only way to make the dependency 
relationship work the other way (not allow Mutter 42.9 with GNOME Shell 42.5) 
requires bumping the Breaks version but I don't think it's worth using Breaks 
unless necessary.

  This release will also enable AMD Xilinx/Mali support on Wayland. See
  https://ubuntu.com/download/amd-xilinx or private bug 1961563 or the
  42.6 release notes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2022889] Autopkgtest regression report (libreoffice/4:7.5.4-0ubuntu0.23.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libreoffice (4:7.5.4-0ubuntu0.23.04.1) 
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.5.4-0ubuntu0.23.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] libreoffice 7.5.4 for lunar

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.4 is in its forth bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.4_release

   * Version 7.5.3 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.3 see the list of bugs fixed in the release candidates of 7.5.4 
(that's a total of ? bugs):
   https://wiki.documentfoundation.org/Releases/7.5.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.5.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1460/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14936260/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230605_142135_2b00f@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230605_113325_1478c@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230605_085103_17f17@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230605_092012_906e0@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230605_104011_2ff4a@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of ? bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2022889/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2013235] Autopkgtest regression report (mutter/44.2-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (44.2-0ubuntu1) for lunar have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/44.2-0ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Drag and Drop not working in Qt-Applications on Gnome 44

Status in Kdenlive:
  Invalid
Status in Mutter:
  Fix Released
Status in OpenShot Video Editor:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  Impact
  ==
  Drag and drop items within Qt applications not working since upgrade to 
Ubuntu Lunar developmental release. The items can be picked up then the cursor 
changed to the "forbid" sign and no further interaction to the app.

  Confirmed affected apps: 3d Slicer, Krita.

  Test Case
  =
  1. Start from Ubuntu 23.04 (the default desktop not KDE or Kubuntu)
  2. Open a terminal and run
  sudo apt install krita
  3. Install the updated mutter packages then log out and log back in.
  4. Run Krita
  5. Click New File. Then click Create
  6. Select the rectangle from the left sidebar. Draw a rectangle on the canvas.
  7. In the menu, select Layer > New > Add Paint Layer
  8. Select the ellipse/circle from the left sidebar. Draw an ellipse on the 
canvas.
  9. In the right sidebar, drag Paint Layer 1 on top of Paint Layer 2 so that 
they switch places. This should work with the updated mutter packages but does 
not work with mutter 44.0 or mutter 44.1.

  What Could Go Wrong
  ===
  This fix is included in the upstream mutter 44.2 release so see the master 
bug for that update: https://launchpad.net/bugs/2022951

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdenlive/+bug/2013235/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2022951] Autopkgtest regression report (mutter/44.2-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (44.2-0ubuntu1) for lunar have 
finished running.
The following regressions have been reported in tests triggered by the package:

mutter/44.2-0ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update mutter to 44.2

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 44 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/44.2/NEWS

  This is basically a prerequisite for GNOME Shell 44.2 LP: #2022961

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  This also includes an update of the triple buffering patch to add one commit 
to fix a potential crash with resuming from suspend. That triple buffering 
patch is maintained in a targeted mutter 44 branch by Canonical Desktop 
engineer Daniel. I was unable to easily reproduce the crash so I didn't include 
LP: #2020652 in the SRU changelog.

  I dropped 2 patches to mark some tests as flaky since mutter seems to
  build reliably enough on Debian and Ubuntu without those patches.

  Upstream assumes that people will be using matching versions of mutter
  and gnome-shell. To be cautious, I therefore bumped the dependency
  version in GNOME Shell 44.2 to require mutter >= 44.2 (even though
  GNOME Shell 44.2 appears to run ok with Mutter 44.1). I believe the
  only way to make the dependency relationship work the other way (not
  allow Mutter 44.2 with GNOME Shell 44.1) requires bumping the Breaks
  version but I don't think it's worth using Breaks unless necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2022951/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2022851] Autopkgtest regression report (gtk4/4.10.4+ds-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gtk4 (4.10.4+ds-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.5.3-0ubuntu0.23.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#gtk4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Nautilus displays invalid directory content after deleting

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  When files are deleted in Nautilus, they can still show up but in the wrong 
order. This can also happen if the files are rearranged.

  This bug is marked Critical because it happen with gtk4
  4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1
  which was originally released with Lunar.

  Test Case
  -
  Install the gtk4 update

  1. Close the file browser windows if they are open
  2. From  a terminal, run these commands:
  mkdir delete-test
  cd delete-test
  touch a b c d e f
  3. Open the Nautilus file browser window
  4. Navigate to the delete-test folder
  5. Select the f file and press the Delete key to delete the file.

  The file should be deleted and you should see only the files
  a b c d e
  in the current folder view

  What Could Go Wrong
  ---
  This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031

  Original Bug Report
  ---
  When I delete or reorganize files, they can be displayed wrong. After going 
to another directory and then back, everything displays properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  4 18:25:47 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)'
  InstallationDate: Installed on 2022-07-22 (317 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2022851/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2023031] Autopkgtest regression report (gtk4/4.10.4+ds-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gtk4 (4.10.4+ds-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/4:7.5.3-0ubuntu0.23.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#gtk4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update gtk4 to 4.10.4

Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  -
  There is a new point release in the stable GTK 4.10 series.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/4.10.4/NEWS

  The version currently in Ubuntu 23.04 is 4.10.3

  Test Case 0
  ---
  gtk4 has an extensive build test suite, and failures will fail the build.
  gtk4 also has thorough autopkgtests.
  Ensure that the build succeeds and that the autopgktests pass.

  Test Case 1
  ---
  Make sure that opening and saving files from the Firefox and Chromium snaps 
still work

  Test Case 2
  ---
  snap install portal-test
  snap run portal-test
  Verify that the app seems to still work ok

  What Could Go Wrong
  ---
  Ubuntu includes xdg-desktop-portal-gnome by default which is used for many 
snap actions like providing a file chooser. This is critical functionality for 
our snaps.

  The Ubuntu flavors use a different portal backend, most commonly xdg-
  desktop-portal-gtk which uses GTK3 so it's not affected by this SRU.

  Many of the default Ubuntu 23.04 desktop apps use GTK4. A serious
  enough regression could severely break the Ubuntu Desktop.

  gtk4 is included in the GNOME micro release exception.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2023031/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1027.28~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 
(5.19.0-1027.28~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-515/515.105.01-0ubuntu0.22.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2020604] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.3) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1990089] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in 

[Desktop-packages] [Bug 2003339] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2017142] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [jammy] VA-API doesn't work on DCN 3.1.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]
  VA-API decoding doesn't work on DCN 3.1.4.
  Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

  The device ID was included in upstream mesa 22.3.1.

  [ Test Plan ]

   * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
   * Verify that '# vainfo' shows the correct information.

  [ Where problems could occur ]

   * If just the new ID is backported then they would be unique to DCN 3.1.4 as 
it's now running VA-API codepaths.
   * If newer mesa point release is adopted, then it could be a regression that 
happened in changes on common code in mesa between those two point releases.

  [ Other Info ]
  * It can be cherry picked with this single commit:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

  * AMD has already tested cherry-picked commit on top of the Ubuntu
  mesa 22.2.5 package and verified it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2020674] Autopkgtest regression report (gtk4/4.10.3+ds-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gtk4 (4.10.3+ds-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

libadwaita-1/1.3.1-1ubuntu2 (amd64, arm64, armhf, ppc64el, s390x)
libreoffice/4:7.5.3-0ubuntu0.23.04.1 (amd64, armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#gtk4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Artifacts at window borders with mutter 44.1

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  Mutter 44.1 switched from using the GL renderer to using Cairo to avoid 
rendering artifacts with the Nvidia drivers. However, this also needed a change 
in GTK4 to avoid other artifacts.

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2976

  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857

  Test Case
  -
  Install gnome-shell 44.1 (currently in lunar-proposed).
  Install this gtk4 update.
  After installing the updates, log out and log back in.
  Open a terminal and the Chromium web browser.
  Tile the terminal to the left and tile Chromium to the right.

  Verify that there aren't rectangle rendering artifacts near the border
  between the two apps.

  What Could Go Wrong
  ---
  This is a one-line patch, cherry-picked from the gtk-4-10 branch that will be 
included in GTK 4.10.4 (which is expected to be released any day now). This 
puts us just a bit ahead of some other distros.

  See the master bug LP: #2020708 for more details about what it means
  to update GTK4.

  Excerpt from Original Report
  
  I wanted to report that I'm now seeing artifacts around window borders, when 
they are arranged to occupy all available area. I should note I'm also using 
gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2.

  I'm attaching a screen recording of what I'm seeing.

  The artifact at the border also happens across monitors. The tall
  chrome window on the right of the left monitor interferes with the
  windows aligned to the left of the right monitor.

  This happened immediately after updating mutter and gnome shell to
  44.1, it wasn't happening before.

  So far I'm seeing them with just google-chrome and chromium (snap),
  but not other apps I quickly tried (gnome-terminal, firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libmutter-12-0 44.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 10:17:44 2023
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2020674/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2020708] Autopkgtest regression report (gtk4/4.10.3+ds-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gtk4 (4.10.3+ds-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

libadwaita-1/1.3.1-1ubuntu2 (amd64, arm64, armhf, ppc64el, s390x)
libreoffice/4:7.5.3-0ubuntu0.23.04.1 (amd64, armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#gtk4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update gtk4 to 4.10.3

Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  -
  There is a new point release in the stable GTK 4.10 series.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/4.10.3/NEWS

  The version currently in Ubuntu 23.04 is 4.10.1

  Test Case 0
  ---
  gtk4 has an extensive build test suite, and failures will fail the build.
  gtk4 also has thorough autopkgtests.
  Ensure that the build succeeds and that the autopgktests pass.

  Test Case 1
  ---
  Make sure that opening and saving files from the Firefox and Chromium snaps 
still work

  Test Case 2
  ---
  snap install portal-test
  snap run portal-test
  Verify that the app seems to still work ok

  What Could Go Wrong
  ---
  Ubuntu includes xdg-desktop-portal-gnome by default which is used for many 
snap actions like providing a file chooser. This is critical functionality for 
our snaps.

  The Ubuntu flavors use a different portal backend, most commonly xdg-
  desktop-portal-gtk which uses GTK3 so it's not affected by this SRU.

  Many of the default Ubuntu 23.04 desktop apps use GTK4. A serious
  enough regression could severely break the Ubuntu Desktop.

  gtk4 is included in the GNOME micro release exception.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  The libadwaita autopkgtest needed to be updated to pass with gtk 4.10.3. This 
is being handled with LP: #2019989

  gtk4 needs to be updated before or at the same time as mutter 44.1 to
  avoid a regression with artifacts near window borders. See LP:
  #2020674 for the gtk4 fix and LP: #2020225 for the mutter 44.1 SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2020708/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1990089] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  

[Desktop-packages] [Bug 2003339] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2017142] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [jammy] VA-API doesn't work on DCN 3.1.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]
  VA-API decoding doesn't work on DCN 3.1.4.
  Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

  The device ID was included in upstream mesa 22.3.1.

  [ Test Plan ]

   * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
   * Verify that '# vainfo' shows the correct information.

  [ Where problems could occur ]

   * If just the new ID is backported then they would be unique to DCN 3.1.4 as 
it's now running VA-API codepaths.
   * If newer mesa point release is adopted, then it could be a regression that 
happened in changes on common code in mesa between those two point releases.

  [ Other Info ]
  * It can be cherry picked with this single commit:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

  * AMD has already tested cherry-picked commit on top of the Ubuntu
  mesa 22.2.5 package and verified it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1987976] Autopkgtest regression report (mutter/44.0-2ubuntu4.23.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mutter (44.0-2ubuntu4.23.04.1) for 
lunar have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/44.0-2ubuntu4.23.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1025.26~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 
(5.19.0-1025.26~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1026.29~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 
(5.19.0-1026.29~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1036.40~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 
(5.15.0-1036.40~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1038.45~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 
(5.15.0-1038.45~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1038.45)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.15.0-1038.45) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1036.40)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1036.40) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1026.29)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.19.0-1026.29) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1025.26)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.19.0-1025.26) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.4.0-1102.110)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.4.0-1102.110) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.4.0-1108.114)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.4.0-1108.114) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1023.24)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.19.0-1023.24) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1023.24~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 
(5.19.0-1023.24~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1036.43)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.15.0-1036.43) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1023.24)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.19.0-1023.24) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1034.38)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1034.38) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
nvidia-graphics-drivers-525/525.89.02-0ubuntu0.22.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2009767] Autopkgtest regression report (xorg-server/2:21.1.4-2ubuntu1.7~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server 
(2:21.1.4-2ubuntu1.7~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

aptdaemon/1.1.1+bzr982-0ubuntu39 (amd64)
gnudatalanguage/1.0.1-3build1 (amd64)
gscan2pdf/2.12.6-1 (amd64)
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
openmsx/17.0-1ubuntu3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2009767

Title:
  External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  New
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Committed
Status in xorg-server source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  NVIDIA driver has a hardcoded version check to see if a bug has been fixed in 
the xserver version. It does not help to backport the fix to the jammy xserver, 
as the driver has no way to check if the fix is there or not.

  We need to backport xorg-server from kinetic to jammy.

  [Test case]
  install xserver update, check that lagginess is gone

  [Regression potential]
  This is a backport of kinetic xorg-server to jammy, with 34 new upstream 
commits of which three were already backported due to CVE's, and a bugfix. 18 
commits only touch darwin/XQuartz and won't affect us. As such, there should be 
a low chance of things breaking. Here's a list of the remaining 12 commits with 
above filtered out:

  6bf62381d0a1fb5 xserver 21.1.4
  855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver
  b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec
  cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a 
keytype
  f575524314e9f20 Revert "os: Try to discover the current seat with the 
XDG_SEAT var first"
  433f53a1a08390a tests: Fix build failure from missing micmap.c
  3868f364728ae0c xf86-input-inputtest: Fix build on systems without 
SOCK_NONBLOCK
  afcaaac96767d77 print_edid: Fix a format string error
  663af2f17eec2cc X11Application: Ensure TIS operations are done on the main 
thread
  bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is 
already defined)
  53173fdab492f0f render: Fix build with gcc 12
  69774044716039f present: Check for NULL to prevent crash

  
  --- original info

  [Summary]
  When the graphic mode is on-demand mode and plug in the monitor to HDMI port, 
there are two issue occures:
  1. External monitor's screen is very laggy in external monitor mode only.
  2. External monitor's screen sometimes (~50%) will be black in join display 
mode.

  [Steps to reproduce]
  1. Boot in OS
  2. Plug in the external monitor in HDMI port
  3. Find the cursor moving in external monitor is laggy

  [Workaround]
  Downgrade to NVIDIA driver 515.

  [Additional information]
  Feedback from NV:

  An NVIDIA driver built with the features needed to get rid of the laggy 
monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix 
the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it 
was first included in the 1.21.1.4 release.
  Since the older X servers crash, NVIDIA deliberately does a version check in 
the driver and enables these features for Xorg servers that are known to work, 
i.e. 1.21.1.4 or higher.

  This unfortunately prevents backporting the fix to 1.21.1.3.
  Engineering has chosen this approach since a crash is worse than the
  low FPS lag and the user might lose work merely by plugging/unplugging
  displays. If it was about a performance degradation, slight
  corruption, or something non-fatal, we wouldn't need to check Xorg
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages

[Desktop-packages] [Bug 1998267] Autopkgtest regression report (glib2.0/2.72.4-0ubuntu2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glib2.0 (2.72.4-0ubuntu2) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

auto-multiple-choice/1.5.2-1willsync1 (arm64)
dbus/1.12.20-2ubuntu4.1 (armhf)
fwupd/1.7.9-1~22.04.1 (armhf)
golang-github-ostreedev-ostree-go/0.0+git20190702.759a8c1-4 (s390x)
gvfs/1.48.2-0ubuntu1 (ppc64el)
mutter/42.5-0ubuntu1 (amd64)
udisks2/2.9.4-1ubuntu2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1036.43~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 
(5.15.0-1036.43~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1034.38~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 
(5.15.0-1034.38~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1034.38)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1034.38) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
nvidia-graphics-drivers-525/525.89.02-0ubuntu0.22.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1023.24~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 
(5.19.0-1023.24~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1036.43)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.15.0-1036.43) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1023.24~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 
(5.19.0-1023.24~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.4.0-1106.112)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.4.0-1106.112) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.4.0-1100.108)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.4.0-1100.108) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1023.24)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.19.0-1023.24) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1023.24)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.19.0-1023.24) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-gcp-5.19/5.19.0-1020.22~22.04.2+1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19 
(5.19.0-1020.22~22.04.2+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-gcp-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2011770] Autopkgtest regression report (gnome-settings-daemon/43.0-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-settings-daemon (43.0-1ubuntu1.1) 
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/43.0-1ubuntu4 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#gnome-settings-daemon

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2011770] Autopkgtest regression report (gnome-settings-daemon/42.1-1ubuntu2.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-settings-daemon (42.1-1ubuntu2.2) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.5-0ubuntu1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#gnome-settings-daemon

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1032.36~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 
(5.15.0-1032.36~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.4.0-1098.106)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.4.0-1098.106) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-cvm/5.4.0-1105.111+cvm1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-cvm 
(5.4.0-1105.111+cvm1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure-cvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2007331] Autopkgtest regression report (pulseaudio/1:16.1+dfsg1-1ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pulseaudio (1:16.1+dfsg1-1ubuntu3.1) 
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u362-ga-0ubuntu1~22.10 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1022.23~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 
(5.19.0-1022.23~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1021.22~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 
(5.19.0-1021.22~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1021.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.19.0-1021.22) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1022.23)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.19.0-1022.23) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993621] Autopkgtest regression report (xorg-server/2:21.1.3-2ubuntu2.8)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server (2:21.1.3-2ubuntu2.8) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

libaperture-0/0.1.0+git20200908-3 (ppc64el)
aptdaemon/1.1.1+bzr982-0ubuntu39 (amd64)
notify-osd/0.9.35+20.04.20191129-0ubuntu2 (amd64)
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
libsoup3/3.0.7-0ubuntu1 (amd64)
mpv-mpris/0.6-2 (amd64)
openmsx/17.0-1ubuntu3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1993621

Title:
  Force update keyboard LEDs after calling EnableDevice to fix its
  hardware state after VT switching

Status in OEM Priority Project:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * This change will force update keyboard LED status after calling
  EnableDevice, in order to resolve LED status not syncing after
  switching VT to a X session.

   * This also fixes the issue with NVIDIA driver and Xorg, that after
  resuming from suspend the keyboard LED is always off.

  [ Test Plan ]

  1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around)

  2. Turn on NumLock on the keyboard

  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to
  switch back to desktop

  NumLock LED should be on after switching back to the desktop

  [ Where problems could occur ]

   * The changes are to push status to the device when enabling it
  regardless of actual keyboard state change, therefore switching
  between VTs and adding/removing keyboard/mouse/xinput devices should
  be affected by this change.

  [ Original Report ]

  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs.

  This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)

  To reproduce:
  1. Log on a X session desktop (GNOME Xorg for example)
  2. Turn on NumLock
  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch 
back to desktop

  Expected:
  NumLock LED should be on

  Actual:
  NumLock LED is off, but functions like NumLock is on.  If NumLock is pressed 
the LED turns off as well as the function.  If CapsLock is pressed the LED 
states sync back (LED turns back on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993621] Autopkgtest regression report (xorg-server/2:21.1.4-2ubuntu1.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server (2:21.1.4-2ubuntu1.6) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
gnudatalanguage/1.0.1-3maysync1 (amd64)
libsoup3/3.2.0-1 (amd64)
gscan2pdf/2.13.0-1 (amd64)
qlcplus/4.12.5-3 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1993621

Title:
  Force update keyboard LEDs after calling EnableDevice to fix its
  hardware state after VT switching

Status in OEM Priority Project:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * This change will force update keyboard LED status after calling
  EnableDevice, in order to resolve LED status not syncing after
  switching VT to a X session.

   * This also fixes the issue with NVIDIA driver and Xorg, that after
  resuming from suspend the keyboard LED is always off.

  [ Test Plan ]

  1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around)

  2. Turn on NumLock on the keyboard

  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to
  switch back to desktop

  NumLock LED should be on after switching back to the desktop

  [ Where problems could occur ]

   * The changes are to push status to the device when enabling it
  regardless of actual keyboard state change, therefore switching
  between VTs and adding/removing keyboard/mouse/xinput devices should
  be affected by this change.

  [ Original Report ]

  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs.

  This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)

  To reproduce:
  1. Log on a X session desktop (GNOME Xorg for example)
  2. Turn on NumLock
  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch 
back to desktop

  Expected:
  NumLock LED should be on

  Actual:
  NumLock LED is off, but functions like NumLock is on.  If NumLock is pressed 
the LED turns off as well as the function.  If CapsLock is pressed the LED 
states sync back (LED turns back on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1035.42~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 
(5.15.0-1035.42~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1032.36~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 
(5.15.0-1032.36~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.4.0-1098.106)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.4.0-1098.106) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.4.0-1105.111)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.4.0-1105.111) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1035.42)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.15.0-1035.42) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1980805] Autopkgtest regression report (llvm-toolchain-13/1:13.0.1-2ubuntu2~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted llvm-toolchain-13 
(1:13.0.1-2ubuntu2~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

cargo/0.62.0ubuntu0libgit2-0ubuntu0.20.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#llvm-toolchain-13

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport packages for 20.04.5 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-13 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-13 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  New
Status in mesa-amber source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: pci-id updates, some minor api updates

  mesa: a new major release, but we'll pull the final stable release of
  22.0.x series, so there shouldn't be any regressions left at that
  point

  mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI
  drivers that were removed from main mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp