[Desktop-packages] [Bug 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out

[Steve Langasek]

Hello Simon, or anyone else affected,

Accepted gnome-session into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
session/46.0-1ubuntu4.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-session (Ubuntu Noble)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  [SRU] Ubuntu Unity takes 90 seconds to log out

Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-session source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
  user-level gnome-session.service systemd unit not properly terminating
  gnome-session on logout. An attempt is made to send SIGTERM to the
  process, which gnome-session does not care about.

  Instead, gnome-session-quit should be invoked when the systemd unit
  shuts down, which acts effectively and immediately.

  [ Test Plan ]

  Actual behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that only the wallpaper is shown for 90 seconds prior to the 
login manager showing again.

  Expected behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

  [ Where problems could occur ]

  If the gnome-session or gnome-session-quit binaries change the
  arguments they accept by default, log in and log out functionality on
  Unity sessions are likely to break.

  Additionally, if lightdm or systemd changes in a non-reverse-
  compatible way, this increases the chance of a user-facing regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+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 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird

[Steve Langasek]

Hello Helga, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apport (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

-- 
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 2019137] Proposed package upload rejected

[Steve Langasek]

An upload of gnome-software to noble-proposed has been rejected from the
upload queue for the following reason: "not an SRU, should be synced to
oracular".

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

Title:
  gnome-software should (?) be separated from the packagekit

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Given that the Snap Store is currently the default in Ubuntu instead
  of GNOME Software, the only reason GNOME Software (along with the Snap
  Store) can be installed is to support Flatpak applications.

  In the current instance, if you want to add flatpak support, GNOME
  Software is installed with both the apt packagekit add-on and the
  flatpak plugin, which is duplication of work (Software Updater already
  works on updates, and Snap Store works on showing deb apps).

  And since the future app store explicitly refuses [1], [2] to support
  flatpak applications, users who need this package format will be
  forced to put GNOME Software with everything I pointed out above.

  Therefore, it would be very nice if the developers removed the
  packagekit add-on from the "gnome-software part" and made it a "plug-
  in for gnome-software".

  I, unfortunately, have no such experience with packaging deb packages
  at the moment, and it turns out that it will obviously be necessary to
  work out both the code part (which, as far as I can see, won't be very
  difficult [3]), as well as the part where we will have to figure out
  where and how to insert the plugin as mandatory (for example, when the
  user completely gives up on snap packages) and as optional (because
  the Snap Store already stands).

  Also, let me know if this needs to be sent to upstream (Debian) instead of 
here.
  
---
  1. https://github.com/ubuntu-flutter-community/software/issues/126
  2. https://github.com/ubuntu-flutter-community/software/issues/30
  3. https://build.opensuse.org/request/show/1031279

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+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 2056767] Proposed package upload rejected

[Steve Langasek]

An upload of gnome-software to noble-proposed has been rejected from the
upload queue for the following reason: "not an SRU, should be synced to
oracular".

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

Title:
  FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main)
  with gnome-software packaging split

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Impact
  --
  I request permission to sync the gnome-software packaging from Debian. The 
biggest change is splitting gnome-software's .deb support into a separate 
package, gnome-software-plugin-deb, to match the existing -snap and -flatpak 
packages. This will allow users and flavors to specifically opt into the parts 
of the GNOME Software experience they want. For instance, someone may want to 
use only the Flatpak part because they use the Snap Store to manage .debs and 
Snaps. Or maybe they want a different combination.

  This has been requested by multiple users on Ubuntu Discourse and at
  least one Launchpad bug and one Debian bug.

  fwupd plugin
  
  I am dropping the fwupd plugin (now in a separate package too) to Suggests so 
upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs 
won't have it either unless a user explicitly installs it later.

  Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu
  desktop flavors also include it. For people who don't want snaps,
  there is also the gnome-firmware app packaged as a .deb.

  Because Ubuntu already has update-manager to handle apt update
  notifications, I am also dropping the autostart file to reduce
  background RAM use.

  A few Ubuntu desktop flavors do not provide any firmware updater app
  at all. Ubuntu Budgie developers thought a firmware updater app was
  too technical for inclusion in the default Ubuntu 24.04 LTS install.

  autostart
  -
  I have also dropped the autostart file since the fwupd plugin is no longer 
included by default and Ubuntu already has ways to notify users about available 
apt updates (update-manager and unattended upgrades) and snaps already 
automatically update.

  Potential Problems
  ---
  gnome-software has an explicit Recommend: gnome-software-plugin-deb so that 
people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That 
recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed 
then. (There is a Depends on the virtual packages that enable installing apps.)

  Full Changelog Entries
  --
  gnome-software (46.0-4) unstable; urgency=medium

    * Fix typo in gnome-software-plugin-deb package description
    * Add lintian overrides for desktop-command-not-in-package

   -- Jeremy Bícha  Fri, 29 Mar 2024 16:45:30 -0400

  gnome-software (46.0-3) unstable; urgency=medium

    * Update Homepage
    * Release to Unstable

   -- Jeremy Bícha  Thu, 28 Mar 2024 13:23:28 -0400

  gnome-software (46.0-2) experimental; urgency=medium

    * Split deb support into separate gnome-software-plugin-deb package
  (Closes: #1066030) (LP: #2019137, #2056767)
    * Have each plugin provide a virtual gnome-software-plugin package
    * Suggest all the gnome-software plugins
    * Recommend gnome-software-plugin-deb for upgrades
    * Split firmware update support into separate fwupd plugin & recommend it
  except on Ubuntu which provides a separate firmware-updater app
  Intentionally, do not have this provides the virtual gnome-software-plugin
  since it doesn't allow browsing apps.
    * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803)
    * Drop Depends: software-properties-gtk
    * Stop recommending gnome-software-plugin-snap on Ubuntu

   -- Jeremy Bícha  Wed, 27 Mar 2024 18:33:03 -0400

  Build Logs
  --
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra

  Desktop Flavors Affected
  
  GNOME Software is currently included in the default install for only
  Ubuntu Cinnamon. See Joshua's comment below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+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 2059818] Re: Regression: Jammy to Noble, set_label no longer functions

[Steve Langasek]

Hello theofficialgman, or anyone else affected,

Accepted gnome-shell-extension-appindicator into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/58-1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Regression: Jammy to Noble, set_label no longer functions

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, set_label can be used to set the text 
to display instead of an appindicator icon. In ubuntu noble set_label no longer 
functions at all.
  
https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label

  [ Test Case ]

  - Download the test indicator and its dependencies:
* wget 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
* apt install gir1.2-appindicator3-0.1

  - Run the test indicator:
gjs -m testTool.js

  - Ensure the indicator icon shows up (it has an ubuntu icon)
  - Click on it and activate the "Set Label" item
  - A random numeric label should show next to the icon

  [ Regression potential ]

  The icon is not visible anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059818/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

[Steve Langasek]

sorry, the template is there but I had loaded this page yesterday and
not refreshed!

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Incomplete => New

** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2042844] Re: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow

[Steve Langasek]

Hello iMac, or anyone else affected,

Accepted gnome-shell-extension-appindicator into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/58-1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-noble

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

Title:
  JS ERROR: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in
  AboutToShow

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  With several indicator icons (Chrome, Slack, 1Password) a GDBus.Error
  systemd error message appears with each iteration of a left-click of
  any impacted indicator icon prior to the icon's menu appearing.

  Ubuntu Mantic 23.10, gnome-shell 45.0-1ubuntu2, gnome-shell-extension-
  appindicator 57-1

  Also reported upstream here: https://github.com/ubuntu/gnome-shell-
  extension-appindicator/issues/445

  Nov 06 08:32:20 ubuntu-mantic gnome-shell[3927]: JS ERROR: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow
  
_promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2042844/+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 2059819] Please test proposed package

[Steve Langasek]

Hello theofficialgman, or anyone else affected,

Accepted gnome-shell-extension-appindicator into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/58-1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

[Steve Langasek]

An upload of gnome-shell-extension-appindicator has been uploaded to
noble for this issue, but this bug lacks an SRU test case.

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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] Re: Drop libglib2.0-0 transitional package

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted glib2.0 into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.80.0-6ubuntu3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: glib2.0 (Ubuntu Noble)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-noble

-- 
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 1968215] Proposed package upload rejected

[Steve Langasek]

An upload of xdg-desktop-portal to noble-proposed has been rejected from
the upload queue for the following reason: "merge changelog includes
references to long-fixed bugs, needs cleanup".

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

Title:
   [FFe] include a new webextensions portal to be used by firefox and
  other confined browsers

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released

Bug description:
  The request is to add the new webextensions portal which is up for
  review upstream on https://github.com/flatpak/xdg-desktop-
  portal/pull/705

  The patch to add to the package would be https://patch-
  diff.githubusercontent.com/raw/flatpak/xdg-desktop-
  portal/pull/705.patch

  The code has been written by James from the Desktop Team and reviewed
  by Olivier from Desktop and got a security review from Alex.

  The regression potential is null since that's a new feature

  The code is needed for the firefox messaging protocol to keep working
  which is seen as an important feature that would regress in the deb to
  snap transition otherwise.

  The feature has been discussed on https://forum.snapcraft.io/t/native-
  messaging-support-in-strictly-confined-browser-snaps

  Olivier is working on getting the firefox side of the changes ready
  but those aren't part of this FFe since they will be integrated as the
  firefox snap gets updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1968215/+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 2062394] Proposed package upload rejected

[Steve Langasek]

An upload of xdg-desktop-portal to noble-proposed has been rejected from
the upload queue for the following reason: "merge changelog includes
references to long-fixed bugs, needs cleanup".

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

Title:
  Update xdg-desktop-portal to 1.18.4

Status in xdg-desktop-portal package in Ubuntu:
  In Progress

Bug description:
  This includes part of a CVE security fix; the more important part of
  the CVE is in flatpak but there is some hardening on the xdg-desktop-
  portal side.

  https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.18.4

  https://github.com/flatpak/xdg-desktop-portal/compare/1.18.3...1.18.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2062394/+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 2063855] [NEW] desktop-file-utils lists snap-store as a default handler for Debian packages but it doesn't handle them

[Steve Langasek]

Public bug reported:

Currently, desktop-file-utils lists the snap store as the default
handler for Debian packages:

$ grep debian /usr/share/applications/defaults.list 
application/vnd.debian.binary-package=snap-store_ubuntu-software-local-file.desktop
application/x-debian-package=snap-store_ubuntu-software-local-file.desktop
$

However, as discussed at https://github.com/ubuntu/app-
center/issues/1407 it does not, in fact, have support for handling these
packages.

We should correct this so that handling of the packages falls through to
something that actually does.

** Affects: desktop-file-utils (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: desktop-file-utils (Ubuntu Noble)
 Importance: High
 Status: Triaged

** Changed in: desktop-file-utils (Ubuntu)
   Status: New => Triaged

** Changed in: desktop-file-utils (Ubuntu)
   Importance: Undecided => High

** Also affects: desktop-file-utils (Ubuntu Noble)
   Importance: High
   Status: Triaged

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

Title:
  desktop-file-utils lists snap-store as a default handler for Debian
  packages but it doesn't handle them

Status in desktop-file-utils package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Noble:
  Triaged

Bug description:
  Currently, desktop-file-utils lists the snap store as the default
  handler for Debian packages:

  $ grep debian /usr/share/applications/defaults.list 
  
application/vnd.debian.binary-package=snap-store_ubuntu-software-local-file.desktop
  application/x-debian-package=snap-store_ubuntu-software-local-file.desktop
  $

  However, as discussed at https://github.com/ubuntu/app-
  center/issues/1407 it does not, in fact, have support for handling
  these packages.

  We should correct this so that handling of the packages falls through
  to something that actually does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2063855/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install

[Steve Langasek]

** Changed in: webkit2gtk (Ubuntu)
Milestone: ubuntu-24.04 => noble-updates

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

Title:
  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install

Status in Webkit:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install.

  [ Test Plan ]

  1. Log into a Xorg session on a Raspberry Pi 4/400.

  2. Open the default Help app by clicking the question mark icon in the
  dock or by running 'yelp'.

  3. Verify it didn't crash and the window contents are not corrupt.

  [ Where problems could occur ]

  The fix is limited to webkit2gtk so can only affect apps such as yelp
  or the Raspberry Pi installer.

  [ Other Info ]

  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/2037015/+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 2060693] Re: No welcome/login sound on Ubuntu desktop

[Steve Langasek]

recent discussion out-of-band suggested this might have been a rpi-
specific failure, is that accurate?

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

Title:
  No welcome/login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi

[Steve Langasek]

This is targeted to 24.04 and marked as 'in progress' but is definitely
not landing before 24.04 GA on Thursday.  What is the overall plan here?
should this go to SRU?  (It can, but in that case doesn't benefit users
wrt the corruption issue in the *installer* until 24.04.1.)

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

Title:
  Screen corruption of slides during install on Raspberry Pi

Status in Webkit:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/2037015/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

[Steve Beattie]

** Also affects: xorg-server (Ubuntu Noble)
   Importance: High
   Status: Triaged

** Also affects: xwayland (Ubuntu Noble)
   Importance: High
   Status: Triaged

** Also affects: xorg-server (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: xorg-server (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: xwayland (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: xorg-server (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Mantic)
   Status: New => In Progress

** No longer affects: xwayland (Ubuntu Focal)

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

** Changed in: xwayland (Ubuntu Jammy)
   Status: New => In Progress

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

** Changed in: xwayland (Ubuntu Mantic)
   Status: New => In Progress

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xwayland package in Ubuntu:
  Triaged
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Jammy:
  In Progress
Status in xwayland source package in Jammy:
  In Progress
Status in xorg-server source package in Mantic:
  In Progress
Status in xwayland source package in Mantic:
  In Progress
Status in xorg-server source package in Noble:
  Triaged
Status in xwayland source package in Noble:
  Triaged

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 

[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

[Steve Beattie]

I have prepared test packages for ubuntu 22.04 LTS/jammy in the
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages PPA for both xorg-server:

  https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+sourcepub/15921802/+listing-archive-extra

and for xwayland:

  https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+sourcepub/15921798/+listing-archive-extra

I was able to reproduce the crash under Xwayland in a jammy vm with both
intellij and the glyph_memleak.c reproducer, and using the proposed
upstream patch seems to address the crash, but more testing is welcome.

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2060354/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

[Steve Beattie]

The reproducer https://bugs.freedesktop.org/attachment.cgi?id=28621 from
the original 2009 bug report
https://bugs.freedesktop.org/show_bug.cgi?id=23286 does seem to work at
triggering this issue, at least under Xwalyand.

** Bug watch added: freedesktop.org Bugzilla #23286
   https://bugs.freedesktop.org/show_bug.cgi?id=23286

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

[Steve Beattie]

Are people seeing this issue with any other Ubuntu releases, which also
received updates addressing CVE-2024-31083, or is this strictly
affecting the version in 22.04/jammy?

It looks like
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1476 has a
proposed fix, in
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1476.patch
.

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+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 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1

[Steve Langasek]

** Changed in: c2esp (Ubuntu)
   Status: New => Fix Committed

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

Status in c2esp package in Ubuntu:
  Fix Committed
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  multiple cups-related packages are having test failures on armhf after time_t 
transition.
  https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
  https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

  I am suspecting a common cups-based issue.

  cups-browsed already has a separate bug open at
  https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Steve Langasek]

** Changed in: c2esp (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

Status in c2esp package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+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 2059158] Re: proposed-migration for gtk4 4.14.1+ds-0ubuntu1

[Steve Langasek]

still tagged 'time-t' because it's in the batch of test regressions
we've allowed as part of the time_t migration

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

Title:
  proposed-migration for gtk4 4.14.1+ds-0ubuntu1

Status in gtk4 package in Ubuntu:
  New

Bug description:
  gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on
  armhf.

  1706s # Running test: gtk-4.0/tools/settings.test
  1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126)
  1706s not ok - gtk-4.0/tools/settings.test

  2100s # Running test: gtk-4.0/tools/simplify.test
  2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126)
  2100s not ok - gtk-4.0/tools/simplify.test

  almost certainly time-t related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2059158/+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 1986542] Re: Issue building the debian source archive

[Steve Langasek]

Since this bug report was filed, there has been a security update of
gst-plugins-good1.0 in jammy which built successfully. Closing invalid.

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Issue building the debian source archive

Status in gst-plugins-good1.0 package in Ubuntu:
  Invalid

Bug description:
  I cannot build the ubuntu source package gst-plugins-
  good1.0_1.20.3-0ubuntu1.dsc. I am doing:

  > dget -q 
http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc
  > cd gst-plugins-good1.0-1.20.3/
  > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b

  and I receive the error:

  ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown
  variable "static_build".

  I am testing inside of an ubuntu:jammy-20220801 container.

  I have narrowed the issue down to a patch in the changelog on the 15th
  Mar which states "Import plugins from -bad that are needed for main
  applications". This patch imports some "bad" plugins into the source
  but the meson file isn't setup correctly for this to work. Manually
  removing the patches related to the bad plugins fixed the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1986542/+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 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1

[Steve Langasek]

c2esp autopkgtest still fails with the current cups in noble-proposed -
though it appears to fail differently now.

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

Status in c2esp package in Ubuntu:
  New
Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  multiple cups-related packages are having test failures on armhf after time_t 
transition.
  https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
  https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

  I am suspecting a common cups-based issue.

  cups-browsed already has a separate bug open at
  https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2058769] Re: proposed-migration for click 0.5.2-2

[Steve Langasek]

** Description changed:

- click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on ppc64el,
- s390x.
+ click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on all archs
+ except amd64.
  
  In order to be able to run the tests without all-proposed=1, glib 2.0 is
  needed, which is why I marked it as affected.
  
  Excerpt of the test logs:
  
  ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
- self.click_install(path_to_click, name, user)
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
- subprocess.check_call(cmd)
-   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
- raise CalledProcessError(retcode, cmd)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
+ self.click_install(path_to_click, name, user)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
+ subprocess.check_call(cmd)
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '--allow-unauthenticated', 
'/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit 
status 1.
  
  ==
  ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature)
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in test_debsig_install_valid_signature
- subprocess.check_call(
-   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
- raise CalledProcessError(retcode, cmd)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in test_debsig_install_valid_signature
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' 
returned non-zero exit status 1.
  
  ==
  ERROR: test_debsig_install_can_install_with_sig_override 
(click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override)
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 164, in test_debsig_install_can_install_with_sig_override
- subprocess.check_call(
-   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
- raise CalledProcessError(retcode, cmd)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 164, in test_debsig_install_can_install_with_sig_override
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--allow-unauthenticated', '--user=root', 
'/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero 
exit status 1.

** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  proposed-migration for click 0.5.2-2

Status in click package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on all
  archs except amd64.

  In order to be able to run the tests without all-proposed=1, glib 2.0
  is needed, which is why I marked it as affected.

  Excerpt of the test logs:

  ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
  --
  Traceback (most recent call last):
    File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
  

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[Steve Langasek]

** Changed in: ubuntu-unity-backgrounds (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in budgie-desktop-environment package in Ubuntu:
  Fix Released
Status in budgie-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-unity-backgrounds package in Ubuntu:
  Triaged
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  Fix Committed
Status in ubuntucinnamon-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntukylin-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Fix Released
Status in ubuntustudio-look package in Ubuntu:
  Fix Released

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-artwork/+bug/2056591/+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 2059158] [NEW] proposed-migration for gtk4 4.14.1+ds-0ubuntu1

[Steve Langasek]

Public bug reported:

gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on
armhf.

1706s # Running test: gtk-4.0/tools/settings.test
1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126)
1706s not ok - gtk-4.0/tools/settings.test

2100s # Running test: gtk-4.0/tools/simplify.test
2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126)
2100s not ok - gtk-4.0/tools/simplify.test

almost certainly time-t related.

** Affects: gtk4 (Ubuntu)
 Importance: Critical
 Status: New


** Tags: time-t update-excuse

** Description changed:

- gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed.
+ gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on
+ armhf.
+ 
+ 1706s # Running test: gtk-4.0/tools/settings.test
+ 1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126)
+ 1706s not ok - gtk-4.0/tools/settings.test
+ 
+ 2100s # Running test: gtk-4.0/tools/simplify.test
+ 2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126)
+ 2100s not ok - gtk-4.0/tools/simplify.test
+ 
+ almost certainly time-t related.

** Changed in: gtk4 (Ubuntu)
   Importance: Undecided => Critical

** Tags added: time-t

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

Title:
  proposed-migration for gtk4 4.14.1+ds-0ubuntu1

Status in gtk4 package in Ubuntu:
  New

Bug description:
  gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on
  armhf.

  1706s # Running test: gtk-4.0/tools/settings.test
  1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126)
  1706s not ok - gtk-4.0/tools/settings.test

  2100s # Running test: gtk-4.0/tools/simplify.test
  2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126)
  2100s not ok - gtk-4.0/tools/simplify.test

  almost certainly time-t related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2059158/+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 2059157] [NEW] proposed-migration for cups 2.4.7-1.2ubuntu1

[Steve Langasek]

Public bug reported:

multiple cups-related packages are having test failures on armhf after time_t 
transition.
https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

I am suspecting a common cups-based issue.

cups-browsed already has a separate bug open at
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

** Affects: c2esp (Ubuntu)
 Importance: Critical
 Status: New

** Affects: cups (Ubuntu)
 Importance: Critical
 Status: New


** Tags: time-t update-excuse

** Description changed:

- cups 2.4.7-1.2ubuntu1 is stuck in -proposed.
+ multiple cups-related packages are having test failures on armhf after time_t 
transition.
+ https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
+ https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9
+ 
+ I am suspecting a common cups-based issue.
+ 
+ cups-browsed already has a separate bug open at
+ https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

** Tags added: time-t

** Changed in: cups (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: c2esp (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

Status in c2esp package in Ubuntu:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  multiple cups-related packages are having test failures on armhf after time_t 
transition.
  https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
  https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

  I am suspecting a common cups-based issue.

  cups-browsed already has a separate bug open at
  https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1

[Steve Langasek]

marking critical because these packages are being allowed into the
release pocket as-is but the printing stack may be broken, which is of
high importance in a server/embedded context.

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

Status in c2esp package in Ubuntu:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  multiple cups-related packages are having test failures on armhf after time_t 
transition.
  https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
  https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

  I am suspecting a common cups-based issue.

  cups-browsed already has a separate bug open at
  https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

[Steve Langasek]

Thanks!  Since this issue was seen only with the package in -proposed,
I'm closing this bug.

There are other unrelated test failures now blocking  the build on
armhf. I will open a separate bug for these.

** Changed in: cups-browsed (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: apparmor (Ubuntu)
   Status: New => Invalid

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

** Changed in: privoxy (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  Invalid
Status in cups-browsed package in Ubuntu:
  Fix Released
Status in privoxy package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2059089] [NEW] proposed-migration for cups-browsed 2.0.0-0ubuntu9

[Steve Langasek]

Public bug reported:

cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed with test failures on
armhf.

** Affects: cups-browsed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: time-t update-excuse

** Tags added: time-t

** Description changed:

- cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed.
+ cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed with test failures on
+ armhf.

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu9

Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed with test failures
  on armhf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089/+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 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main

[Steve Langasek]

** Tags removed: update-excuse

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

Title:
  FFe: [MIR] freedp2 -> freerdp3 in main

Status in freerdp3 package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop package in Ubuntu:
  Fix Committed
Status in remmina package in Ubuntu:
  Fix Committed

Bug description:
  Feature Freeze Exception Request
  --
  There are only 2 packages in Ubuntu main that use freerdp2: remmina and 
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore 
only one version of freerdp will be in main. freerdp2 will be demoted to 
universe since many universe packages use it and are not prepared to switch to 
freerdp3.

  This also requests updating gnome-control-center to fully enable the
  features of gnome-remote-desktop 46.

  Impact
  --
  A headline feature of GNOME 46 is support as a Remote Desktop server without 
requiring someone to already be logged in locally ("headless" mode). This 
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires 
freerdp3.

  Impact if this does not happen
  --
  - We would need to patch gnome-control-center to use the older Remote Desktop 
panel (or at least hide the new tab for Remote Login)
  - We would need to keep using gnome-remote-desktop 45 instead of 46. The 
gnome-remote-desktop upstream maintainers would be unhappy with this decision. 
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may 
require changes in gnome-remote-desktop for things to work well although a 
simple test showed that basic remote desktop seems to work ok with the 
mismatch. (See comment #1 from upstream developer.)

  Why this did not land sooner
  ---
  It required the packaging of a new source package freerdp3. And we had to do 
this sooner than Debian. Sorry too many things to do before Feature Freeze and 
this did not make it.

  Affected Packages
  -
  - gnome-remote-desktop 45 -> 46
  - gnome-control-center (to update the Remote Desktop settings page)
  - remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not 
work  with freerdp 3.3 in my testing
  - gnome-connections (build-dependency swap): Not required by other changes 
and not in Main but makes sense to switch it also

  Affected Flavors
  
  Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center, 
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships 
gnome-control-center but this appears to be a bug since they ship 
cinnamon-control-center and is likely already fixed in noble-proposed)

  Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.

  gnome-connections has no reverse dependencies or recommends.

  Upstream Changes
  
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS

  https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md

  gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature 
Freeze. It will be updated to 46.0. The relevant part here is whether we use 
the 46~beta version of the Remote Desktop page or the 46.0 version.
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS

  Build Logs
  --
  I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA. 
The PPA currently has noble-proposed disabled so that it is easily possible to 
try this set of packages without dealing with the incomplete 32-bit time 
transition in noble-proposed. In addition, the PPA has the affected packages 
from this FFe.

  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages

  Testing Done
  ---
  1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect 
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46 
RC. Remote control worked.

  2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
  freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
  worked.

  3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
  with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
  control worked.

  4. I added a new Remote Login test case to
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
  verified that remote login worked. Notably, enabling this changes the
  port for the older service, now called "Desktop Sharing" to 3390.
  Since 3389 is the default port, users would then need to manually
  specific port 3390 for Desktop Sharing in their remote connection app
  (Remmina, GNOME Connections, etc.).

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


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

[Desktop-packages] [Bug 2059076] [NEW] proposed-migration for gnome-remote-desktop 46~rc-0ubuntu2

[Steve Langasek]

Public bug reported:

gnome-remote-desktop 46~rc-0ubuntu2 is built in -proposed but not on
armhf.  This will not block migration because armhf binaries are being
removed from the release pocket, but unless addressed will regress armhf
availability of this package in 24.04 LTS.

** Affects: gnome-remote-desktop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: time-t update-excuse

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

Title:
  proposed-migration for gnome-remote-desktop 46~rc-0ubuntu2

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  gnome-remote-desktop 46~rc-0ubuntu2 is built in -proposed but not on
  armhf.  This will not block migration because armhf binaries are being
  removed from the release pocket, but unless addressed will regress
  armhf availability of this package in 24.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2059076/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

[Steve Langasek]

[1724567.629003] audit: type=1400 audit(1711133926.877:813):
apparmor="DENIED" operation="file_mmap" class="file"
namespace="root//lxd-noble-armhf_"
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed"
pid=876865 comm="cups-browsed" requested_mask="rm" denied_mask="rm"
fsuid=1000110 ouid=100


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

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058866] [NEW] proposed-migration for cups-browsed 2.0.0-0ubuntu8

[Steve Langasek]

Public bug reported:

cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via
an autopkgtest), early enough that LD_DEBUG=all gives no output.  A
local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable
ran, so 8 was uploaded to try to fix this.  But the executable somehow
ONLY runs as ./debian/cups-browsed/usr/sbin/cups-browsed and segfaults
when invoked as /usr/sbin/cups-browsed.

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

** Affects: cups-browsed (Ubuntu)
 Importance: Undecided
 Assignee: Steve Langasek (vorlon)
 Status: New


** Tags: update-excuse

** Changed in: cups-browsed (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Description changed:

- cups-browsed 2.0.0-0ubuntu8 is stuck in -proposed.
+ cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via
+ an autopkgtest), early enough that LD_DEBUG=all gives no output.  A
+ local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable
+ ran, so 8 was uploaded to try to fix this.  But the executable somehow
+ ONLY runs as ./debian/cups-browsed/usr/sbin/cups-browsed and segfaults
+ when invoked as /usr/sbin/cups-browsed.

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058827] [NEW] proposed-migration for cpdb-backend-cups 2.0~b5-0ubuntu5

[Steve Langasek]

Public bug reported:

cpdb-backend-cups 2.0~b5-0ubuntu5 has a build-time test failure on
armhf.

** Affects: cpdb-backend-cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: time-t update-excuse

** Tags added: time-t

** Description changed:

- cpdb-backend-cups 2.0~b5-0ubuntu5 is stuck in -proposed.
+ cpdb-backend-cups 2.0~b5-0ubuntu5 has a build-time test failure on
+ armhf.

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

Title:
  proposed-migration for cpdb-backend-cups 2.0~b5-0ubuntu5

Status in cpdb-backend-cups package in Ubuntu:
  New

Bug description:
  cpdb-backend-cups 2.0~b5-0ubuntu5 has a build-time test failure on
  armhf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-cups/+bug/2058827/+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 2058767] Re: proposed-migration for auto-multiple-choice 1.6.0-3build3

[Steve Langasek]

mesa bootstrap had not been unwound all the way.  Fixed mesa is building
now.

** Package changed: auto-multiple-choice (Ubuntu) => mesa (Ubuntu)

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

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  proposed-migration for auto-multiple-choice 1.6.0-3build3

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  auto-multiple-choice 1.6.0-3build3 is stuck in -proposed due to
  regressing armhf autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2058767/+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 2057822] Re: Removing irqbalance disables power button on Raspberry Pi 5

[Steve Langasek]

** Package changed: ubuntu-meta (Ubuntu) => ubuntu-raspi-settings
(Ubuntu)

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

Title:
  Removing irqbalance disables power button on Raspberry Pi 5

Status in ubuntu-raspi-settings package in Ubuntu:
  New

Bug description:
  As discussed in Bug #1833322: "Please consider no more having
  irqbalance enabled by default (per image/use-case/TBD)"
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322)
  the irqbalance package will no longer be installed by default in
  Noble. So as a test I removed the package from my Raspberry Pi 5
  running Mantic Server, after which the Pi 5's power button no longer
  worked to poweroff the system. Re-installing irqbalance caused the
  button to work again.

  With irqbalance installed I see these messages at boot time:

  kernel: input: pwr_button as /devices/platform/pwr_button/input/input1
  systemd-logind[694]: Watching system buttons on /dev/input/event0 (pwr_button)

  Without irqbalance I see this:

  kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0,
  error -6

  So the Raspberry Pi 5 might still need irqbalance installed, or
  perhaps there's a better solution for enabling the button.

  I have the following appended to the Mantic default
  /boot/firmware/config.txt:

  # Trickle charge the RTC battery (default: don't charge)
  dtparam=rtc_bbat_vchg=300
  # Enable the PCIe external connector
  dtparam=nvme
  # Force PCIe Gen 3.0 (default: Gen 2.0; not certified for Gen 3.0)
  # dtparam=pciex1_gen=3
  # Enable second serial port on GPIO 14 & 15 (default: disabled)
  dtparam=uart0
  # Change activity LED behavior (default: blink for MMC access)
  dtparam=act_led_trigger=heartbeat
  # Disable Bluetooth (not wanted on a server)
  dtoverlay=disable-bt-pi5
  # Enable PPS on GPIO 18 for MAX-M8Q GNSS HAT
  dtoverlay=pps-gpio,gpiopin=18,capture_clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2057822/+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 2056591] Re: [UIFe] Noble Flavor Wallpapers

[Steve Langasek]

The UI Freeze exists to ensure that documentation team and translation
team efforts aren't wasted working on a UI that isn't finalized.

https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions

UIFreeze granted, provided you notify ubuntu-...@lists.ubuntu.com in
advance.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Triaged

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/2056591/+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] Re: Lenovo XT99 BT headset can't work in HFP profile

[Steve Langasek]

I've sponsored this for noble.  For the SRUs, I would like to see a test
case explicitly included that says you will regression-test this on
other bluetooth pairings on other devices: the patch is not a platform-
specific quirk, it is a change to generic bluetooth code, so there
should be explicit tests that it does not break other devices.

You mention in "where problems could occur" that you *have* tested the
patch; but we should test the actual binaries produced as part of the
SRU process, to be certain.

** Changed in: pulseaudio (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Changed in: pulseaudio (Ubuntu Mantic)
   Status: In Progress => Incomplete

** Changed in: pulseaudio (Ubuntu Jammy)
   Status: In Progress => Incomplete

-- 
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:
  Incomplete
Status in pulseaudio source package in Mantic:
  Incomplete
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]
  Install the patched pulseaudio and reboot, connect to the LENOVO XT99
  bt headset, select it to work in HFP mode, tested playback and capture,
  all worked well.

  [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 2051838] Re: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send

[Steve]

The Firefox issue can be found at:
https://bugzilla.mozilla.org/show_bug.cgi?id=1882449

The issue has been closed and supposedly fixed. The target milestone has
been set to 125, which I assume means that it should be included in the
Firefox 125 release planned for 16 April 2024. In the meantime, the
recommended workaround is to run Firefox with
`MOZ_DISABLE_WAYLAND_PROXY=1`.

** Bug watch added: Mozilla Bugzilla #1882449
   https://bugzilla.mozilla.org/show_bug.cgi?id=1882449

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

Title:
  /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too
  many files to send

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  GDM, or more specifically is flooding systemd journal and
  /var/log/syslog via rsyslogd with gigabytes of the following messages:

  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: 
WaylandMessage::Write() too many files to send

  
  I noticed the problem when I started to run out of disk because 
/var/log/syslog was consuming more than 400GiB. I noticed that rsyslogd starts 
to consume a lot of CPU trying to process such volume of messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051838/+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 2051838] Re: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send

[Steve]

Also have this issue (100% cpu usage by /usr/sbin/rsyslogd) with Firefox
in Sway on Ubuntu 22.04. So far I've only noticed this after reloading
the sway config (`swaymsg reload` or Mod+Shift+c).

Fabien (afabien) wrote:
> To avoid having disk full problems, I used the following workaround:
>
> I created a file /etc/rsyslog.d/10-no-gdm-wayland.conf
> Containing the following lines:
> :msg, contains, "Error: WaylandMessage::Write() too many files to send" ~
> :msg, contains, " :" ~
>
> And then restarted rsyslog (as root): systemctl restart rsyslog.service

This workaround didn't work for me, even after replacing the `~` with
`stop`.

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

Title:
  /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too
  many files to send

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  GDM, or more specifically is flooding systemd journal and
  /var/log/syslog via rsyslogd with gigabytes of the following messages:

  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: 
WaylandMessage::Write() too many files to send
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]:  :
  Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: 
WaylandMessage::Write() too many files to send

  
  I noticed the problem when I started to run out of disk because 
/var/log/syslog was consuming more than 400GiB. I noticed that rsyslogd starts 
to consume a lot of CPU trying to process such volume of messages.

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

Re: [Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[Steve Langasek]

Belated response, but just for the record, Paride's recounting of upstream's
position in the context of the Debian decision was definitive for me:

On Wed, Jan 10, 2024 at 11:47:56AM -, Paride Legovini wrote:
> Back in the day I asked upstream their take on irqbalance usefulness
> with newer kernels, here is their reply:

In effect what this says is that: irqbalance is still useful, but unless
the admin configures it, the policy it provides is not a discernable
improvement over the in-kernel default policy.

Therefore I think it is the right path forward to unseed this and let users
install it in situations where they want to configure it.

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  In Progress
Status in Ubuntu on IBM z Systems:
  Opinion
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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

Re: [Desktop-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed

[Steve Langasek]

On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote:
> @vorlon @jchittum @paelzer given the above findings are you still -1 on
> any snap preseeding? Based on the data, I vote not to preseed any snaps.

That is my position.  Thanks for bringing data to this!

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

Title:
  Always preseed core and snapd snap in server seed

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New

Bug description:
  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.

  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.

  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```

  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```

  This is a significant difference and for a workload we intend to
  remain as a core tested and tracked workload. As such I propose we re-
  introduce core22 and snapd snaps to our seed.

  LXD do intend to move to the core24 snap as their base as I'm sure
  snapd does too so when that does happen we need to update the
  preseeded core snap.

  This bug is to track the work of making that change in the server seed
  @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n69

  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051572] Re: Always preseed core and snapd snap in server seed

[Steve Langasek]

> This is a significant difference and for a workload we intend to remain as a 
> core tested
> and tracked workload. As such I propose we re-introduce core22 and snapd 
> snaps to our seed.

I disagree that the image should be optimized by default to prioritize
the one-time startup performance of an optional use case.

15 seconds vs 30 seconds, on a thing that won't affect most cloud
customers, and happens at most once per image, AND should be weighed
against the first-boot speed improvements in clouds resulting from
having a smaller image?

Also, statically seeding a particular base snap is bad form, as soon as
lxd upgrades its base you lose your performance benefit and have to play
catch-up in a stable release.

If "time to initialize lxd" is your metric, I think you're measuring the
wrong thing :)

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

Title:
  Always preseed core and snapd snap in server seed

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New

Bug description:
  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.

  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.

  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```

  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```

  This is a significant difference and for a workload we intend to
  remain as a core tested and tracked workload. As such I propose we re-
  introduce core22 and snapd snaps to our seed.

  LXD do intend to move to the core24 snap as their base as I'm sure
  snapd does too so when that does happen we need to update the
  preseeded core snap.

  This bug is to track the work of making that change in the server seed
  @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n69

  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-515-server 515.105.01-0ubuntu2 in noble
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble armhf
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble ppc64el
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble riscv64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble s390x
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble armhf
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble i386
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble ppc64el
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble riscv64
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble s390x
libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble i386
nvidia-compute-utils-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-compute-utils-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-dkms-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-dkms-510-server 515.105.01-0ubuntu2 in noble arm64
nvidia-driver-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-driver-510-server 515.105.01-0ubuntu2 in noble arm64
nvidia-headless-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-headless-510-server 515.105.01-0ubuntu2 in noble arm64
nvidia-headless-no-dkms-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-headless-no-dkms-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-kernel-common-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-kernel-common-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-kernel-source-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-kernel-source-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-utils-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-utils-510-server 515.105.01-0ubuntu2 in noble arm64
xserver-xorg-video-nvidia-510-server 515.105.01-0ubuntu2 in 
noble amd64
xserver-xorg-video-nvidia-510-server 515.105.01-0ubuntu2 in 
noble arm64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-515-server (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-460 460.91.03-0ubuntu1 in noble
libnvidia-cfg1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-cfg1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-450 460.91.03-0ubuntu1 in noble arm64
libnvidia-common-450 460.91.03-0ubuntu1 in noble armhf
libnvidia-common-450 460.91.03-0ubuntu1 in noble i386
libnvidia-common-450 460.91.03-0ubuntu1 in noble ppc64el
libnvidia-common-450 460.91.03-0ubuntu1 in noble riscv64
libnvidia-common-450 460.91.03-0ubuntu1 in noble s390x
libnvidia-common-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-455 460.91.03-0ubuntu1 in noble arm64
libnvidia-common-455 460.91.03-0ubuntu1 in noble armhf
libnvidia-common-455 460.91.03-0ubuntu1 in noble i386
libnvidia-common-455 460.91.03-0ubuntu1 in noble ppc64el
libnvidia-common-455 460.91.03-0ubuntu1 in noble riscv64
libnvidia-common-455 460.91.03-0ubuntu1 in noble s390x
libnvidia-common-460 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-460 460.91.03-0ubuntu1 in noble arm64
libnvidia-common-460 460.91.03-0ubuntu1 in noble armhf
libnvidia-common-460 460.91.03-0ubuntu1 in noble i386
libnvidia-common-460 460.91.03-0ubuntu1 in noble ppc64el
libnvidia-common-460 460.91.03-0ubuntu1 in noble riscv64
libnvidia-common-460 460.91.03-0ubuntu1 in noble s390x
libnvidia-compute-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-compute-450 460.91.03-0ubuntu1 in noble i386
libnvidia-compute-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-compute-455 460.91.03-0ubuntu1 in noble i386
libnvidia-decode-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-decode-450 460.91.03-0ubuntu1 in noble i386
libnvidia-decode-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-decode-455 460.91.03-0ubuntu1 in noble i386
libnvidia-encode-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-encode-450 460.91.03-0ubuntu1 in noble i386
libnvidia-encode-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-encode-455 460.91.03-0ubuntu1 in noble i386
libnvidia-extra-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-extra-450 460.91.03-0ubuntu1 in noble i386
libnvidia-extra-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-extra-455 460.91.03-0ubuntu1 in noble i386
libnvidia-fbc1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-fbc1-450 460.91.03-0ubuntu1 in noble i386
libnvidia-fbc1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-fbc1-455 460.91.03-0ubuntu1 in noble i386
libnvidia-gl-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-gl-450 460.91.03-0ubuntu1 in noble i386
libnvidia-gl-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-gl-455 460.91.03-0ubuntu1 in noble i386
libnvidia-ifr1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-ifr1-450 460.91.03-0ubuntu1 in noble i386
libnvidia-ifr1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-ifr1-455 460.91.03-0ubuntu1 in noble i386
nvidia-compute-utils-450 460.91.03-0ubuntu1 in noble amd64
nvidia-compute-utils-455 460.91.03-0ubuntu1 in noble amd64
nvidia-dkms-450 460.91.03-0ubuntu1 in noble amd64
nvidia-dkms-455 460.91.03-0ubuntu1 in noble amd64
nvidia-driver-450 460.91.03-0ubuntu1 in noble amd64
nvidia-driver-455 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-450 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-455 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-450 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-455 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-common-450 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-common-455 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-source-450 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-source-455 460.91.03-0ubuntu1 in noble amd64
nvidia-utils-450 460.91.03-0ubuntu1 in noble amd64
nvidia-utils-455 460.91.03-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-450 460.91.03-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-455 460.91.03-0ubuntu1 in noble amd64
Comment: 

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

All older source packages listed in this bug report have been removed,
and yet:

$ reverse-depends src:nvidia-graphics-drivers-460
Reverse-Depends
===
* libnvidia-decode-455  (for libnvidia-decode-460)
* libnvidia-encode-455  (for libnvidia-encode-460)
* nvidia-headless-455 [amd64]   (for nvidia-headless-460)
* nvidia-kernel-common-455 [amd64]

Packages without architectures listed are reverse-dependencies in: amd64, i386
$

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Same for 515-server:

$ reverse-depends src:nvidia-graphics-drivers-515-server
Reverse-Depends
===
* libnvidia-decode-510-server   (for libnvidia-decode-515-server)
* libnvidia-encode-510-server   (for libnvidia-encode-515-server)

Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, i386
$

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-450 450.119.03-0ubuntu1 in noble
libnvidia-cfg1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-440 450.119.03-0ubuntu1 in noble arm64
libnvidia-common-440 450.119.03-0ubuntu1 in noble armhf
libnvidia-common-440 450.119.03-0ubuntu1 in noble i386
libnvidia-common-440 450.119.03-0ubuntu1 in noble ppc64el
libnvidia-common-440 450.119.03-0ubuntu1 in noble riscv64
libnvidia-common-440 450.119.03-0ubuntu1 in noble s390x
libnvidia-common-450 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-450 450.119.03-0ubuntu1 in noble arm64
libnvidia-common-450 450.119.03-0ubuntu1 in noble armhf
libnvidia-common-450 450.119.03-0ubuntu1 in noble i386
libnvidia-common-450 450.119.03-0ubuntu1 in noble ppc64el
libnvidia-common-450 450.119.03-0ubuntu1 in noble riscv64
libnvidia-common-450 450.119.03-0ubuntu1 in noble s390x
libnvidia-compute-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-compute-440 450.119.03-0ubuntu1 in noble i386
libnvidia-decode-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-decode-440 450.119.03-0ubuntu1 in noble i386
libnvidia-encode-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-encode-440 450.119.03-0ubuntu1 in noble i386
libnvidia-extra-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-extra-440 450.119.03-0ubuntu1 in noble i386
libnvidia-fbc1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-fbc1-440 450.119.03-0ubuntu1 in noble i386
libnvidia-gl-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-gl-440 450.119.03-0ubuntu1 in noble i386
libnvidia-ifr1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-ifr1-440 450.119.03-0ubuntu1 in noble i386
nvidia-compute-utils-440 450.119.03-0ubuntu1 in noble amd64
nvidia-dkms-440 450.119.03-0ubuntu1 in noble amd64
nvidia-driver-440 450.119.03-0ubuntu1 in noble amd64
nvidia-headless-440 450.119.03-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-440 450.119.03-0ubuntu1 in noble amd64
nvidia-kernel-common-440 450.119.03-0ubuntu1 in noble amd64
nvidia-kernel-source-440 450.119.03-0ubuntu1 in noble amd64
nvidia-utils-440 450.119.03-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-440 450.119.03-0ubuntu1 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048792] Re: Firefox utilizing 100% of station CPU

[Steve Smaldone]

** Summary changed:

- Firefox utilizins 100% of station CPU
+ Firefox utilizing 100% of station CPU

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

Title:
  Firefox utilizing 100% of station CPU

Status in firefox package in Ubuntu:
  New

Bug description:
  At a high level, in certain instances we’re experiencing sustained
  abnormally high (100%) CPU utilization from Firefox.  This utilization
  is competing with other critical application processes on the systems,
  starving them of resources, causing issues in the application
  processing.  This happens, at times, when the browser should be idle,
  even.

  We have not isolated this issue to be a bug with firefox itself or an issue 
with the webpage content being provided to the browser. Regardless, here are 
the symptoms:
  * CPU usage is extremely high for the FireFox process (>100% on average 
vs <10% average for healthy stations) even while the screen is sitting idle (no 
animations, user interactions, etc.)
 * We have isolated the thread within FireFox causing the most CPU usage to 
the Renderer thread with the SwComposite threads also consuming abnormally high 
CPU.
 * In the FireFox Task and Process Managers, we have validated there is no 
single tab or window consuming abnormally high CPU, just the FireFox master 
process.
 * Additionally, we have confirmed that the FireFox browser history (taken 
from the places.sqlite file) does not have any webpages being loaded during the 
times when CPU consumption experiences a step function change up or down.
 * We also have linux perf logs for the FireFox process on healthy stations 
and impacted stations while sitting idle on the login screen, which can provide 
some stack traces for the Renderer and other threads which may be more useful 
to someone with FireFox expertise.
 * The biggest difference is that the impacted workcells have the Renderer 
and Compositor 'tracks' very active while the healthy workcells see no usage of 
these tracks at all.
 * These 2 tracks also have supporting tracks such as SwComposite and 
WRRendererBackend#X. There were 2 of each of these, which may indicate the 
issue is happening across both FireFox windows. For reference, the stations 
always have 2 windows open: one for the screen UI and one for the projector on 
the pod face.
 * (Using the term 'track' here as defined by the open source FireFox 
profiler: https://profiler.firefox.com/. Basically a thread within the FireFox 
main process) 
 * There are many memory copy and SW interrupt calls being made in these 
tracks.
 * This validates that FireFox is contributing to increased software 
interrupt load
 * Additionally, we found an interesting pair of calls occurring 
periodically in the Renderer track. We have not deep dived these yet, but on 
the off chance it matters, we're including it in this report:
 * viaduct_log_error - every 50 - 500ms
 * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048792] Re: Firefox utilizins 100% of station CPU

[Steve Smaldone]

Additional info:
Firefox is at version 100.0.2
It is installed as a deb package
We're running Ubuntu 20.04

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

Title:
  Firefox utilizins 100% of station CPU

Status in firefox package in Ubuntu:
  New

Bug description:
  At a high level, in certain instances we’re experiencing sustained
  abnormally high (100%) CPU utilization from Firefox.  This utilization
  is competing with other critical application processes on the systems,
  starving them of resources, causing issues in the application
  processing.  This happens, at times, when the browser should be idle,
  even.

  We have not isolated this issue to be a bug with firefox itself or an issue 
with the webpage content being provided to the browser. Regardless, here are 
the symptoms:
  * CPU usage is extremely high for the FireFox process (>100% on average 
vs <10% average for healthy stations) even while the screen is sitting idle (no 
animations, user interactions, etc.)
 * We have isolated the thread within FireFox causing the most CPU usage to 
the Renderer thread with the SwComposite threads also consuming abnormally high 
CPU.
 * In the FireFox Task and Process Managers, we have validated there is no 
single tab or window consuming abnormally high CPU, just the FireFox master 
process.
 * Additionally, we have confirmed that the FireFox browser history (taken 
from the places.sqlite file) does not have any webpages being loaded during the 
times when CPU consumption experiences a step function change up or down.
 * We also have linux perf logs for the FireFox process on healthy stations 
and impacted stations while sitting idle on the login screen, which can provide 
some stack traces for the Renderer and other threads which may be more useful 
to someone with FireFox expertise.
 * The biggest difference is that the impacted workcells have the Renderer 
and Compositor 'tracks' very active while the healthy workcells see no usage of 
these tracks at all.
 * These 2 tracks also have supporting tracks such as SwComposite and 
WRRendererBackend#X. There were 2 of each of these, which may indicate the 
issue is happening across both FireFox windows. For reference, the stations 
always have 2 windows open: one for the screen UI and one for the projector on 
the pod face.
 * (Using the term 'track' here as defined by the open source FireFox 
profiler: https://profiler.firefox.com/. Basically a thread within the FireFox 
main process) 
 * There are many memory copy and SW interrupt calls being made in these 
tracks.
 * This validates that FireFox is contributing to increased software 
interrupt load
 * Additionally, we found an interesting pair of calls occurring 
periodically in the Renderer track. We have not deep dived these yet, but on 
the off chance it matters, we're including it in this report:
 * viaduct_log_error - every 50 - 500ms
 * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048792] [NEW] Firefox utilizins 100% of station CPU

[Steve Smaldone]

Public bug reported:

At a high level, in certain instances we’re experiencing sustained
abnormally high (100%) CPU utilization from Firefox.  This utilization
is competing with other critical application processes on the systems,
starving them of resources, causing issues in the application
processing.  This happens, at times, when the browser should be idle,
even.

We have not isolated this issue to be a bug with firefox itself or an issue 
with the webpage content being provided to the browser. Regardless, here are 
the symptoms:
* CPU usage is extremely high for the FireFox process (>100% on average vs 
<10% average for healthy stations) even while the screen is sitting idle (no 
animations, user interactions, etc.)
   * We have isolated the thread within FireFox causing the most CPU usage to 
the Renderer thread with the SwComposite threads also consuming abnormally high 
CPU.
   * In the FireFox Task and Process Managers, we have validated there is no 
single tab or window consuming abnormally high CPU, just the FireFox master 
process.
   * Additionally, we have confirmed that the FireFox browser history (taken 
from the places.sqlite file) does not have any webpages being loaded during the 
times when CPU consumption experiences a step function change up or down.
   * We also have linux perf logs for the FireFox process on healthy stations 
and impacted stations while sitting idle on the login screen, which can provide 
some stack traces for the Renderer and other threads which may be more useful 
to someone with FireFox expertise.
   * The biggest difference is that the impacted workcells have the Renderer 
and Compositor 'tracks' very active while the healthy workcells see no usage of 
these tracks at all.
   * These 2 tracks also have supporting tracks such as SwComposite and 
WRRendererBackend#X. There were 2 of each of these, which may indicate the 
issue is happening across both FireFox windows. For reference, the stations 
always have 2 windows open: one for the screen UI and one for the projector on 
the pod face.
   * (Using the term 'track' here as defined by the open source FireFox 
profiler: https://profiler.firefox.com/. Basically a thread within the FireFox 
main process) 
   * There are many memory copy and SW interrupt calls being made in these 
tracks.
   * This validates that FireFox is contributing to increased software 
interrupt load
   * Additionally, we found an interesting pair of calls occurring periodically 
in the Renderer track. We have not deep dived these yet, but on the off chance 
it matters, we're including it in this report:
   * viaduct_log_error - every 50 - 500ms
   * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms

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

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

Title:
  Firefox utilizins 100% of station CPU

Status in firefox package in Ubuntu:
  New

Bug description:
  At a high level, in certain instances we’re experiencing sustained
  abnormally high (100%) CPU utilization from Firefox.  This utilization
  is competing with other critical application processes on the systems,
  starving them of resources, causing issues in the application
  processing.  This happens, at times, when the browser should be idle,
  even.

  We have not isolated this issue to be a bug with firefox itself or an issue 
with the webpage content being provided to the browser. Regardless, here are 
the symptoms:
  * CPU usage is extremely high for the FireFox process (>100% on average 
vs <10% average for healthy stations) even while the screen is sitting idle (no 
animations, user interactions, etc.)
 * We have isolated the thread within FireFox causing the most CPU usage to 
the Renderer thread with the SwComposite threads also consuming abnormally high 
CPU.
 * In the FireFox Task and Process Managers, we have validated there is no 
single tab or window consuming abnormally high CPU, just the FireFox master 
process.
 * Additionally, we have confirmed that the FireFox browser history (taken 
from the places.sqlite file) does not have any webpages being loaded during the 
times when CPU consumption experiences a step function change up or down.
 * We also have linux perf logs for the FireFox process on healthy stations 
and impacted stations while sitting idle on the login screen, which can provide 
some stack traces for the Renderer and other threads which may be more useful 
to someone with FireFox expertise.
 * The biggest difference is that the impacted workcells have the Renderer 
and Compositor 'tracks' very active while the healthy workcells see no usage of 
these tracks at all.
 * These 2 tracks also have supporting tracks such as SwComposite and 
WRRendererBackend#X. There were 2 of each of these, which may indicate the 
issue 

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-440 440.100-0ubuntu1 in noble
libnvidia-cfg1-430 440.100-0ubuntu1 in noble amd64
libnvidia-common-430 440.100-0ubuntu1 in noble amd64
libnvidia-common-430 440.100-0ubuntu1 in noble arm64
libnvidia-common-430 440.100-0ubuntu1 in noble armhf
libnvidia-common-430 440.100-0ubuntu1 in noble i386
libnvidia-common-430 440.100-0ubuntu1 in noble ppc64el
libnvidia-common-430 440.100-0ubuntu1 in noble riscv64
libnvidia-common-430 440.100-0ubuntu1 in noble s390x
libnvidia-common-440 440.100-0ubuntu1 in noble amd64
libnvidia-common-440 440.100-0ubuntu1 in noble arm64
libnvidia-common-440 440.100-0ubuntu1 in noble armhf
libnvidia-common-440 440.100-0ubuntu1 in noble i386
libnvidia-common-440 440.100-0ubuntu1 in noble ppc64el
libnvidia-common-440 440.100-0ubuntu1 in noble riscv64
libnvidia-common-440 440.100-0ubuntu1 in noble s390x
libnvidia-compute-430 440.100-0ubuntu1 in noble amd64
libnvidia-compute-430 440.100-0ubuntu1 in noble i386
libnvidia-decode-430 440.100-0ubuntu1 in noble amd64
libnvidia-decode-430 440.100-0ubuntu1 in noble i386
libnvidia-encode-430 440.100-0ubuntu1 in noble amd64
libnvidia-encode-430 440.100-0ubuntu1 in noble i386
libnvidia-fbc1-430 440.100-0ubuntu1 in noble amd64
libnvidia-fbc1-430 440.100-0ubuntu1 in noble i386
libnvidia-gl-430 440.100-0ubuntu1 in noble amd64
libnvidia-gl-430 440.100-0ubuntu1 in noble i386
libnvidia-ifr1-430 440.100-0ubuntu1 in noble amd64
libnvidia-ifr1-430 440.100-0ubuntu1 in noble i386
nvidia-compute-utils-430 440.100-0ubuntu1 in noble amd64
nvidia-dkms-430 440.100-0ubuntu1 in noble amd64
nvidia-driver-430 440.100-0ubuntu1 in noble amd64
nvidia-headless-430 440.100-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-430 440.100-0ubuntu1 in noble amd64
nvidia-kernel-common-430 440.100-0ubuntu1 in noble amd64
nvidia-kernel-source-430 440.100-0ubuntu1 in noble amd64
nvidia-utils-430 440.100-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-430 440.100-0ubuntu1 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

[Steve Langasek]

Hi Christian,

I see a lot of strong opinions being given, but aside from the "don't
use it in KVM" guidance which appears to be based on GCE's engineering
expertise, very little evidence that irqbalance is actually a problem.

I think it's true that in the default config, irqbalance can interfere
with putting CPUs into higher C states to conserve power.  However, I
don't see any indication of quantitative analysis showing the impact.

Recent versions of irqbalance have a '--powerthresh' argument that can
be used to tell irqbalance to rebalance across fewer cores when CPU load
is low, to allow some of the cores to be put into a sleep state and
conserve power.  My own initial testing on my desktop shows that this
gets used for all of about 10 seconds at a time every few hours, before
the load increases and irqbalance wakes the core back up...

I would want any decision to remove irqbalance from the desktop to be
based on evidence, not conjecture.  At a minimum, I think what I would
like to see is output from powertop showing both power consumption and
CPU idle stats over a reasonable amount of time (10 minutes?), on a
representative client machine, for a 2x3 matrix of configurations:

 - idle vs normal desktop load
 - irqbalance disabled vs irqbalance enabled with defaults vs irqbalance 
enabled with IRQBALANCE_ARGS=--powerthresh=1

System should be rebooted between each of the irqbalance configurations,
as I'm not sure what does or doesn't persist in the CPU config after
irqbalance exits.

I am specifically not going to try to rebut the various webpages
referenced here, beyond saying that there's an awful lot of these pages
pointing to one other as authoritative sources on irqbalance without
there actually being evidence to back them up (and a heaping spoonful of
misinformation / outdated information along the way).  So if we're going
to make a change, there should be due diligence to demonstrate a
benefit, it should not be based on Internet hype.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-515 515.105.01-0ubuntu3 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

The other packages in this listed are reported by reverse-depends to
have non-empty revdeps.  However it looks like these all come from other
packages that have just been removed.  Rather than tracing this manually
and possibly making a mistake, I'll let the others sit for another
round.

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-510 510.108.03-0ubuntu3 in noble
libnvidia-cfg1-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-495 510.108.03-0ubuntu3 in noble arm64
libnvidia-common-495 510.108.03-0ubuntu3 in noble armhf
libnvidia-common-495 510.108.03-0ubuntu3 in noble i386
libnvidia-common-495 510.108.03-0ubuntu3 in noble ppc64el
libnvidia-common-495 510.108.03-0ubuntu3 in noble riscv64
libnvidia-common-495 510.108.03-0ubuntu3 in noble s390x
libnvidia-common-510 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-510 510.108.03-0ubuntu3 in noble arm64
libnvidia-common-510 510.108.03-0ubuntu3 in noble armhf
libnvidia-common-510 510.108.03-0ubuntu3 in noble i386
libnvidia-common-510 510.108.03-0ubuntu3 in noble ppc64el
libnvidia-common-510 510.108.03-0ubuntu3 in noble riscv64
libnvidia-common-510 510.108.03-0ubuntu3 in noble s390x
libnvidia-compute-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-compute-495 510.108.03-0ubuntu3 in noble i386
libnvidia-decode-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-decode-495 510.108.03-0ubuntu3 in noble i386
libnvidia-encode-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-encode-495 510.108.03-0ubuntu3 in noble i386
libnvidia-extra-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-extra-495 510.108.03-0ubuntu3 in noble i386
libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble i386
libnvidia-gl-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-gl-495 510.108.03-0ubuntu3 in noble i386
nvidia-compute-utils-495 510.108.03-0ubuntu3 in noble amd64
nvidia-dkms-495 510.108.03-0ubuntu3 in noble amd64
nvidia-driver-495 510.108.03-0ubuntu3 in noble amd64
nvidia-headless-495 510.108.03-0ubuntu3 in noble amd64
nvidia-headless-no-dkms-495 510.108.03-0ubuntu3 in noble amd64
nvidia-kernel-common-495 510.108.03-0ubuntu3 in noble amd64
nvidia-kernel-source-495 510.108.03-0ubuntu3 in noble amd64
nvidia-utils-495 510.108.03-0ubuntu3 in noble amd64
xserver-xorg-video-nvidia-495 510.108.03-0ubuntu3 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


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

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-530 530.41.03-0ubuntu2 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-530 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-455 455.45.01-0ubuntu1 in noble
libnvidia-cfg1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-435 455.45.01-0ubuntu1 in noble arm64
libnvidia-common-435 455.45.01-0ubuntu1 in noble armhf
libnvidia-common-435 455.45.01-0ubuntu1 in noble i386
libnvidia-common-435 455.45.01-0ubuntu1 in noble ppc64el
libnvidia-common-435 455.45.01-0ubuntu1 in noble riscv64
libnvidia-common-435 455.45.01-0ubuntu1 in noble s390x
libnvidia-common-455 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-455 455.45.01-0ubuntu1 in noble arm64
libnvidia-common-455 455.45.01-0ubuntu1 in noble armhf
libnvidia-common-455 455.45.01-0ubuntu1 in noble i386
libnvidia-common-455 455.45.01-0ubuntu1 in noble ppc64el
libnvidia-common-455 455.45.01-0ubuntu1 in noble riscv64
libnvidia-common-455 455.45.01-0ubuntu1 in noble s390x
libnvidia-compute-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-compute-435 455.45.01-0ubuntu1 in noble i386
libnvidia-decode-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-decode-435 455.45.01-0ubuntu1 in noble i386
libnvidia-encode-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-encode-435 455.45.01-0ubuntu1 in noble i386
libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble i386
libnvidia-gl-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-gl-435 455.45.01-0ubuntu1 in noble i386
libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble i386
nvidia-compute-utils-435 455.45.01-0ubuntu1 in noble amd64
nvidia-dkms-435 455.45.01-0ubuntu1 in noble amd64
nvidia-driver-435 455.45.01-0ubuntu1 in noble amd64
nvidia-headless-435 455.45.01-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-435 455.45.01-0ubuntu1 in noble amd64
nvidia-kernel-common-435 455.45.01-0ubuntu1 in noble amd64
nvidia-kernel-source-435 455.45.01-0ubuntu1 in noble amd64
nvidia-utils-435 455.45.01-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-435 455.45.01-0ubuntu1 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-435 435.21-0ubuntu8 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-430 430.50-0ubuntu3 in noble
libnvidia-cfg1-418 430.50-0ubuntu3 in noble amd64
libnvidia-common-418 430.50-0ubuntu3 in noble amd64
libnvidia-common-418 430.50-0ubuntu3 in noble arm64
libnvidia-common-418 430.50-0ubuntu3 in noble armhf
libnvidia-common-418 430.50-0ubuntu3 in noble i386
libnvidia-common-418 430.50-0ubuntu3 in noble ppc64el
libnvidia-common-418 430.50-0ubuntu3 in noble riscv64
libnvidia-common-418 430.50-0ubuntu3 in noble s390x
libnvidia-common-430 430.50-0ubuntu3 in noble amd64
libnvidia-common-430 430.50-0ubuntu3 in noble arm64
libnvidia-common-430 430.50-0ubuntu3 in noble armhf
libnvidia-common-430 430.50-0ubuntu3 in noble i386
libnvidia-common-430 430.50-0ubuntu3 in noble ppc64el
libnvidia-common-430 430.50-0ubuntu3 in noble riscv64
libnvidia-common-430 430.50-0ubuntu3 in noble s390x
libnvidia-compute-418 430.50-0ubuntu3 in noble amd64
libnvidia-compute-418 430.50-0ubuntu3 in noble i386
libnvidia-decode-418 430.50-0ubuntu3 in noble amd64
libnvidia-decode-418 430.50-0ubuntu3 in noble i386
libnvidia-encode-418 430.50-0ubuntu3 in noble amd64
libnvidia-encode-418 430.50-0ubuntu3 in noble i386
libnvidia-fbc1-418 430.50-0ubuntu3 in noble amd64
libnvidia-fbc1-418 430.50-0ubuntu3 in noble i386
libnvidia-gl-418 430.50-0ubuntu3 in noble amd64
libnvidia-gl-418 430.50-0ubuntu3 in noble i386
libnvidia-ifr1-418 430.50-0ubuntu3 in noble amd64
libnvidia-ifr1-418 430.50-0ubuntu3 in noble i386
nvidia-compute-utils-418 430.50-0ubuntu3 in noble amd64
nvidia-dkms-418 430.50-0ubuntu3 in noble amd64
nvidia-driver-418 430.50-0ubuntu3 in noble amd64
nvidia-headless-418 430.50-0ubuntu3 in noble amd64
nvidia-headless-no-dkms-418 430.50-0ubuntu3 in noble amd64
nvidia-kernel-common-418 430.50-0ubuntu3 in noble amd64
nvidia-kernel-source-418 430.50-0ubuntu3 in noble amd64
nvidia-utils-418 430.50-0ubuntu3 in noble amd64
xserver-xorg-video-nvidia-418 430.50-0ubuntu3 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

[Steve Langasek]

Removing packages from noble:
nvidia-graphics-drivers-340 340.108-0ubuntu8 in noble
libcuda1-340 340.108-0ubuntu8 in noble amd64
libcuda1-340 340.108-0ubuntu8 in noble armhf
nvidia-340 340.108-0ubuntu8 in noble amd64
nvidia-340 340.108-0ubuntu8 in noble armhf
nvidia-340-dev 340.108-0ubuntu8 in noble amd64
nvidia-340-dev 340.108-0ubuntu8 in noble armhf
nvidia-340-uvm 340.108-0ubuntu8 in noble amd64
nvidia-340-uvm 340.108-0ubuntu8 in noble armhf
nvidia-libopencl1-340 340.108-0ubuntu8 in noble amd64
nvidia-opencl-icd-340 340.108-0ubuntu8 in noble amd64
Comment: Unsupported driver version; LP: #2048087


** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2047008] Re: [SRU] Add Telit FN990 compositions

[Steve Langasek]

Hello Laider, or anyone else affected,

Accepted modemmanager into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: modemmanager (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] Add Telit FN990 compositions

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Jammy:
  Fix Committed

Bug description:
  [SRU] Add Telit FN990 compositions

  [ Impact ]

  The modemmanager v1.20.0 doesn't have Telit FN990 compositions.
  It works with compatibility mode.
  (lp: #2046699)

  [ Test Plan ]

  Under Jammy environment,
  check modemmanager can identify Telit FN990 modem correctly.

  [ Where problems could occur ]

  The Telit FN990 compositions is upstreamed to modemmanager v1.20.6
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2

  Noble and Mantic already working with modemmanager v1.20.6.
  The target platform modem function works well on Mantic.

  The change parts just only add VID/PIDs for Telit's FN990 modems under
  the Telit plugin.

  [ Other Info ]

  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047008/+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] Re: Heavy stuttering in Firefox with mutter 45.1/45.2

[Steve Langasek]

Hello Daniel, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done-mantic
** Tags added: verification-needed-mantic

-- 
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:
  Fix Released
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  There is heavy stuttering visible in Firefox with mutter 45.1/45.2
  when kinetic scrolling a non-animated web page with a touchpad. This
  is a regression introduced upstream in mutter 45.1 (8f27ebf8).

  [ Test Plan ]

  0. Find a laptop with a touchpad.
  1. Open a simple web page like a Wikipedia page in Firefox.
  2. Use two fingers on the touchpad to fling it so it continues scrolling.

  Expect: The scrolling proceeds and slows perfectly smoothly.

  [ Where problems could occur ]

  Anywhere in frame scheduling (visual smoothness), since that is the
  code affected.

  [ Other Info ]

  The bug was introduced upstream in 45.1 by
  
https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d
  but since it only hurts the triple buffering patch, that's where it
  has been 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" because the bug is in auto mode
  (the default).

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 2043000] Re: Update mutter to 45.2

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-mantic

-- 
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:
  Fix Released
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
  --
  This update landed in mantic-updates just before the end of year holidays but 
was reverted with 
https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0

  Compared to mutter 45.2-0ubuntu1, this changes or adds about 3 lines
  of code in the triple buffering patch to avoid the regression reported
  in LP: #2046360

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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland

[Steve Langasek]

Hello Jeremie, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-mantic

-- 
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 Released
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 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10

[Steve Langasek]

Hello Gonzalo, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-mantic

-- 
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 Released
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 

[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading

[Steve Langasek]

One of the possible impacts of bumping the version like this is that if
a user has a local deb of chromium-browser installed that is higher than
the current version, the new epoch will cause them to be upgraded to the
transitional package that they had already opted out of.

This should be called out and the pros and cons weighed in the bug
description ("Where problems can occur" / "Regression potential")

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Lunar:
  In Progress
Status in chromium-browser source package in Mantic:
  Incomplete

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2007702] Re: [SRU] Deb version numbering is misleading

[Steve Langasek]

One of the possible impacts of bumping the version like this is that if
a user has a local deb of chromium-browser installed that is higher than
the current version, the new epoch will cause them to be upgraded to the
transitional package that they had already opted out of.

This should be called out and the pros and cons weighed in the bug
description ("Where problems can occur" / "Regression potential")

** Changed in: chromium-browser (Ubuntu Mantic)
   Status: In Progress => Incomplete

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Lunar:
  In Progress
Status in chromium-browser source package in Mantic:
  Incomplete

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Steve Langasek]

I actually agree that we should aim to remove these packages entirely,
rather than merely demoting them.

I think removal of the server is a clear-cut case.  Nobody should need
to run a pptp server nowadays on Ubuntu, and if anyone is, forcing them
to migrate to a better VPN solution on upgrade (or maintaining their own
pptpd without Ubuntu support) is IMHO reasonable.

Removing the client, I think, is less clear-cut.  If you don't have a
pptp server to talk to, then shipping the client is harmless.  If you DO
have a pptp server to talk to, then the client is essential.  Anyone
running a PPTP server on Windows these days should upgrade... but
dropping the client support from Ubuntu doesn't give the Ubuntu users
any more leverage to make their server admin upgrade, it just makes
Ubuntu unusable in such an environment.

So I think we should remove pptpd from the archive for noble, but that
we should propose removal of the clients via discussion with the Debian
maintainers.

** Changed in: pptpd (Ubuntu)
   Status: Incomplete => New

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Fix Released

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  Current Windows versions natively support IPSec and L2TP as much
  better alternatives.

  https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
  configuration#how-to-use-wfp-to-configure-ipsec-policies

  https://learn.microsoft.com/en-US/troubleshoot/windows-
  server/networking/configure-l2tp-ipsec-server-behind-nat-t-device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Steve Langasek]

LP: #2048087 has been opened with a superset of removal requests, so
marking invalid the tasks here in favor of that separate bug with
independent history.

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Invalid

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Steve Langasek]

Removing packages from noble:
pptpd 1.4.0-12build2 in noble
bcrelay 1.4.0-12build2 in noble amd64
bcrelay 1.4.0-12build2 in noble arm64
bcrelay 1.4.0-12build2 in noble armhf
bcrelay 1.4.0-12build2 in noble ppc64el
bcrelay 1.4.0-12build2 in noble riscv64
bcrelay 1.4.0-12build2 in noble s390x
pptpd 1.4.0-12build2 in noble amd64
pptpd 1.4.0-12build2 in noble arm64
pptpd 1.4.0-12build2 in noble armhf
pptpd 1.4.0-12build2 in noble ppc64el
pptpd 1.4.0-12build2 in noble riscv64
pptpd 1.4.0-12build2 in noble s390x
Comment: server implementation of an obsolete insecure protocol; LP: #2041751
1 package successfully removed.


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

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Fix Released

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  Current Windows versions natively support IPSec and L2TP as much
  better alternatives.

  https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
  configuration#how-to-use-wfp-to-configure-ipsec-policies

  https://learn.microsoft.com/en-US/troubleshoot/windows-
  server/networking/configure-l2tp-ipsec-server-behind-nat-t-device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Steve Langasek]

** Description changed:

  Remove dangerously insecure MPPE PPTP from Ubuntu
  
  https://pptpclient.sourceforge.net/protocol-security.phtml
  
  It has been dead for over 20 years now.
  
- IPSec OpenVPN Strongswan are much better alternatives.
+ Current Windows versions natively support IPSec and L2TP as much better
+ alternatives.
+ 
+ https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
+ configuration#how-to-use-wfp-to-configure-ipsec-policies
+ 
+ https://learn.microsoft.com/en-US/troubleshoot/windows-
+ server/networking/configure-l2tp-ipsec-server-behind-nat-t-device

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  New

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  Current Windows versions natively support IPSec and L2TP as much
  better alternatives.

  https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
  configuration#how-to-use-wfp-to-configure-ipsec-policies

  https://learn.microsoft.com/en-US/troubleshoot/windows-
  server/networking/configure-l2tp-ipsec-server-behind-nat-t-device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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 2046971] Re: RM signon from noble

[Steve Langasek]

Removing packages from noble:
signon 8.59+17.10.20170606-0ubuntu3 in noble
Comment: superseded by signond; LP: #2046971
1 package successfully removed.


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

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

Title:
  RM signon from noble

Status in signon package in Ubuntu:
  Fix Released

Bug description:
  signond was merged from Debian, making this signon a source package
  providing no binaries.

  Please kick it out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/2046971/+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] Update Released

[Steve Langasek]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  There is heavy stuttering visible in Firefox with mutter 45.1/45.2
  when kinetic scrolling a non-animated web page with a touchpad. This
  is a regression introduced upstream in mutter 45.1 (8f27ebf8).

  [ Test Plan ]

  0. Find a laptop with a touchpad.
  1. Open a simple web page like a Wikipedia page in Firefox.
  2. Use two fingers on the touchpad to fling it so it continues scrolling.

  Expect: The scrolling proceeds and slows perfectly smoothly.

  [ Where problems could occur ]

  Anywhere in frame scheduling (visual smoothness), since that is the
  code affected.

  [ Other Info ]

  The bug was introduced upstream in 45.1 by
  
https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d
  but since it only hurts the triple buffering patch, that's where it
  has been 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" because the bug is in auto mode
  (the default).

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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Steve Langasek]

>From the linked page:

However, that doesn't mean people don't accept the risks. There are many
corporations and individuals using PPTP with full knowledge of these
risks. Some use mitigating controls, and some don't.

No one has ever run pptp on Linux, as either a client or server, because
they thought it was a good protocol.  It was used because compatibility
was required with the other end.

> IPSec OpenVPN Strongswan are much better alternatives.

What is the compatibility story for these on Windows?

The page you link also says:

> Microsoft promote something else.

What, specifically, and what is the Linux compatibility story with that
"something else"?

It should be clear in this removal bug what users should be using
instead of pptp as a Windows-compatible VPN.

** Changed in: pptpd (Ubuntu)
   Status: New => Incomplete

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Incomplete

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  IPSec OpenVPN Strongswan are much better alternatives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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] Re: Heavy stuttering in Firefox with mutter 45.1/45.2

[Steve Langasek]

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

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

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 2046022] Re: Failed to disable unit: Unit file NetworkManager-wait-online-service.service does not exist.

[Steve Langasek]

The unit is called 'NetworkManager-wait-online.service' not
'NetworkManager-wait-online-service.service'.

** Package changed: plymouth (Ubuntu) => network-manager (Ubuntu)

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  Failed to disable unit: Unit file NetworkManager-wait-online-
  service.service does not exist.

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  when i try to disable network manager wait online service - I get a 
notificaiton saying as below 
  Failed to disable unit: Unit file NetworkManager-wait-online-service.service 
does not exist.

  
  But when i do the analyze blame - i clearly see close to 15 seconds being 
eaten up by the network manager 
  needs attention - since boot speed is pathetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046022/+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] Re: Backport packages for 22.04.4 HWE stack

[Steve Langasek]

Hello Timo, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Jammy)
   Status: Incomplete => Fix Committed

-- 
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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Steve Langasek]

** Changed in: ubuntu-settings (Ubuntu Mantic)
   Status: New => In Progress

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  In Progress

Bug description:
  [SRU Justification]

  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

  [Test case]
  No testing is planned beyond any autopkgtests which may be none (the package 
itself doesn't have any).  This should not be released to -updates on its own, 
but should be staged in -proposed so any future SRUs needed don't fail to copy 
due to out-of-date packages.

  [Where problems may occur]
  It is unlikely but possible that the removal of the raspi binary package from 
this source package will have inadvertently modified the contents of the other 
remaining binary packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Steve Langasek]

** Tags added: block-proposed-mantic

** Description changed:

+ [SRU Justification]
+ 
  In response to LP: #2038964 and due to the timing we have forked ubuntu-
  raspi-settings into a separate source package.
  
  ubuntu-settings must therefore be updated to drop ubuntu-raspi-settings*
  from debian/control as otherwise binary builds of the package will be
  rejected by the archive (if the version number is <= 23.10.6) or will
  wrongly supersede the fixes that have just been uploaded to mantic (if
  the version number is > 23.10.6).
+ 
+ [Test case]
+ No testing is planned beyond any autopkgtests which may be none (the package 
itself doesn't have any).  This should not be released to -updates on its own, 
but should be staged in -proposed so any future SRUs needed don't fail to copy 
due to out-of-date packages.
+ 
+ [Where problems may occur]
+ It is unlikely but possible that the removal of the raspi binary package from 
this source package will have inadvertently modified the contents of the other 
remaining binary packages.

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  [SRU Justification]

  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

  [Test case]
  No testing is planned beyond any autopkgtests which may be none (the package 
itself doesn't have any).  This should not be released to -updates on its own, 
but should be staged in -proposed so any future SRUs needed don't fail to copy 
due to out-of-date packages.

  [Where problems may occur]
  It is unlikely but possible that the removal of the raspi binary package from 
this source package will have inadvertently modified the contents of the other 
remaining binary packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu

[Steve Langasek]

Hello Mate, or anyone else affected,

Accepted mesa into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Mantic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-mantic

-- 
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 2037604] Re: Backport packages for 22.04.4 HWE stack

[Steve Langasek]

The directx-headers part of this is easy because it's just a build-
dependency of mesa, but mesa itself is a big delta to a library that
affects all users of the graphics stack: unlike the kernel, which has
both GA and HWE versions where the user can opt out of the rolling
kernel updates on the LTS, there is only one mesa package, so the impact
of any regressions is higher.

I see that the current bug description is in line with the previous
update, LP: #2019212; and of course, with respect to hardware
enablement, this is an SRU we're going to want to take; but I think it
would be best if there were a more explicit test case than just "Install
the new mesa on various hw".   Do we expect this new mesa to be tested
on all certified hardware before it's released to -updates?  Is there a
feedback mechanism for us to *know* if Certification finds regressions
on some of the certified platforms?  Is any effort made to check for
regressions on non-certified hardware?

** Changed in: mesa (Ubuntu Jammy)
   Status: New => Incomplete

-- 
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:
  Incomplete
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]
  Install the new mesa on various hw, see that everything still works like 
before or better.

  [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 2037604] Re: Backport packages for 22.04.4 HWE stack

[Steve Langasek]

Hello Timo, or anyone else affected,

Accepted directx-headers into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/directx-
headers/1.610.2-2~ubuntu0.22.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: directx-headers (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
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:
  New
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]
  Install the new mesa on various hw, see that everything still works like 
before or better.

  [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 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Steve Langasek]

I'd really recommend not open new bug tasks for further source packages
on a bug like this; we clearly aren't going to remove any of those other
packages from mantic now...

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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

Re: [Desktop-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Steve Langasek]

On Tue, Nov 07, 2023 at 05:34:02PM -, Dave Jones wrote:
> Thanks for the quick review! Could someone set up a "mantic" branch

Done.

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039328] Please test proposed package

[Steve Langasek]

Hello Dimitri, or anyone else affected,

Accepted ubuntu-meta into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
meta/1.524.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Update ubuntu-meta with promotions done between last ubuntu-meta build
  & release

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Committed
Status in ubuntu-meta source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * ubuntu-seeds were changed since last meta update
   * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes 
done before release

  [ Test Plan ]

   * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to
  mantic install newly recommended packages.

  [ Where problems could occur ]

   * This is automatically generated change based on ubuntu-seeds commit
  [1].

   * Theoretically, regressions would occur if new desktop-minimal-recommends
     dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools):
     - have issues on install during release-upgrade;
     - have issues on regular system usage (after installed).

  [ Other Info ]

   * ubuntu-meta was not uploaded during final freeze, to prevent
  rebuilding all images as changes affect arm64 only, which is a brand
  new release image

   * protection-domain-mapper [2] and qrtr [3] moved from universe to main in 
Mantic.
   * flash-kernel is/was already in main.

  [1] 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a
  [2] 
https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory
  [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release

[Steve Langasek]

ubuntu-meta sponsored to noble, but no bug ref in changelog, so marking
this fix released for noble.

** Changed in: ubuntu-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-meta (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-mantic

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

Title:
  Update ubuntu-meta with promotions done between last ubuntu-meta build
  & release

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Committed
Status in ubuntu-meta source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * ubuntu-seeds were changed since last meta update
   * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes 
done before release

  [ Test Plan ]

   * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to
  mantic install newly recommended packages.

  [ Where problems could occur ]

   * This is automatically generated change based on ubuntu-seeds commit
  [1].

   * Theoretically, regressions would occur if new desktop-minimal-recommends
     dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools):
     - have issues on install during release-upgrade;
     - have issues on regular system usage (after installed).

  [ Other Info ]

   * ubuntu-meta was not uploaded during final freeze, to prevent
  rebuilding all images as changes affect arm64 only, which is a brand
  new release image

   * protection-domain-mapper [2] and qrtr [3] moved from universe to main in 
Mantic.
   * flash-kernel is/was already in main.

  [1] 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a
  [2] 
https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory
  [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory

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

Re: [Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service

[Steve Langasek]

On Tue, Oct 24, 2023 at 07:36:16PM -, Jeremy Bícha wrote:
> What are the consequences of delaying NetworkManager's restart until
> reboot?

This is not an option on upgrade from <= 23.04 to >= 23.10 because the
postinst needs the new NetworkManager running for the connections migration.

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

Title:
  network-manager SRU flags system for restart required but also
  restarted the service

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After applying the network-manager SRU in mantic, I get a notification
  that a system restart is required to fully apply updates.

  This immediately raised a question, because I KNOW my network
  connection was restarted when the SRU was installed (I have a VPN that
  did not auto-reconnect).

  And I checked the state of the process - it was definitely restarted
  and is running from the binary currently on disk.

  The network-manager postinst has the following code:

  # request a reboot (NM tears down interfaces on restart
  # which is not the way we want to go)
  [ -x /usr/share/update-notifier/notify-reboot-required ] && \
  /usr/share/update-notifier/notify-reboot-required

  But the service restart is also happening. debian/rules currently has:

  override_dh_installsystemd:
  dh_installsystemd -pnetwork-manager --no-start 
NetworkManager-dispatcher.service NetworkManager-wait-online.service 
nm-priv-helper.service
  dh_installsystemd -pnetwork-manager --no-also NetworkManager.service

  No other systemd overrides. Nothing inhibits the restart of the
  service.

  It needs to be one or the other.  And if we're doing SRUs of network-
  manager, then this is bad UX for users applying their daily updates
  and should be fixed in SRU.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:19:38 2023
  InstallationDate: Installed on 2019-12-23 (1401 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+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

Re: [Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service

[Steve Langasek]

On Tue, Oct 24, 2023 at 04:04:25PM -, Jeremy Bícha wrote:
> I do not believe we have a desktop policy to help us determine when it
> is better to either restart services or notify that a computer restart
> is recommended.

As a user I would prefer to not have my vpn connection drop during a
network-manager upgrade; or, barring that, to have it re-established after
the service is restarted.

And since that's not currently implemented, as a user it would be less
annoying for me if the service was not restarted.

HOWEVER, the default policy is to always restart services on upgrade, and
this policy exists for a reason.  Indeed, Lukas tells me we specifically
need to restart NM on upgrade from lunar to mantic because without a
restart, we can't do the connection migration - so in the most immediately
interesting case a restart is mandatory anyway.

The only system service we make an exception for is dbus because the whole
system loses its mind if dbus goes away.

So I think, given the set of knobs we currently have available for tweaking,
the right answer is to drop the reboot-required bit.

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

Title:
  network-manager SRU flags system for restart required but also
  restarted the service

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After applying the network-manager SRU in mantic, I get a notification
  that a system restart is required to fully apply updates.

  This immediately raised a question, because I KNOW my network
  connection was restarted when the SRU was installed (I have a VPN that
  did not auto-reconnect).

  And I checked the state of the process - it was definitely restarted
  and is running from the binary currently on disk.

  The network-manager postinst has the following code:

  # request a reboot (NM tears down interfaces on restart
  # which is not the way we want to go)
  [ -x /usr/share/update-notifier/notify-reboot-required ] && \
  /usr/share/update-notifier/notify-reboot-required

  But the service restart is also happening. debian/rules currently has:

  override_dh_installsystemd:
  dh_installsystemd -pnetwork-manager --no-start 
NetworkManager-dispatcher.service NetworkManager-wait-online.service 
nm-priv-helper.service
  dh_installsystemd -pnetwork-manager --no-also NetworkManager.service

  No other systemd overrides. Nothing inhibits the restart of the
  service.

  It needs to be one or the other.  And if we're doing SRUs of network-
  manager, then this is bad UX for users applying their daily updates
  and should be fixed in SRU.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:19:38 2023
  InstallationDate: Installed on 2019-12-23 (1401 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+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 2038907] Re: Ubuntu patch incorrect disable the thunderbolt and security panels

[Steve Langasek]

** Changed in: gnome-control-center (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu patch incorrect disable the thunderbolt and security panels

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Mantic:
  Fix Committed

Bug description:
  * Impact

  After an upstream reorganisation the patch to disable the
  microcophone/camera panels incorrectly disable also the rest of the
  device section, including thunderbolt and security which should be
  displayed

  * Testcase

  $ gnome-control-center privacy

  The right page should have a devices section listing thunderbolt (if
  the corresponding hardware is available) and security

  * Regression potential

  The change is a simple tweak to the .ui of the privacy panel, any bug
  would show in that panel. Also the thunderbolt and security panel
  haven't got recent testing due to this issue so they could be buggy
  (but it wouldn't be a regression over having the functionality not
  available)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+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 2040292] [NEW] network-manager SRU flags system for restart required but also restarted the service

[Steve Langasek]

Public bug reported:

After applying the network-manager SRU in mantic, I get a notification
that a system restart is required to fully apply updates.

This immediately raised a question, because I KNOW my network connection
was restarted when the SRU was installed (I have a VPN that did not
auto-reconnect).

And I checked the state of the process - it was definitely restarted and
is running from the binary currently on disk.

The network-manager postinst has the following code:

# request a reboot (NM tears down interfaces on restart
# which is not the way we want to go)
[ -x /usr/share/update-notifier/notify-reboot-required ] && \
/usr/share/update-notifier/notify-reboot-required

But the service restart is also happening. debian/rules currently has:

override_dh_installsystemd:
dh_installsystemd -pnetwork-manager --no-start 
NetworkManager-dispatcher.service NetworkManager-wait-online.service 
nm-priv-helper.service
dh_installsystemd -pnetwork-manager --no-also NetworkManager.service

No other systemd overrides. Nothing inhibits the restart of the service.

It needs to be one or the other.  And if we're doing SRUs of network-
manager, then this is bad UX for users applying their daily updates and
should be fixed in SRU.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 08:19:38 2023
InstallationDate: Installed on 2019-12-23 (1401 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: network-manager
UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

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

Title:
  network-manager SRU flags system for restart required but also
  restarted the service

Status in network-manager package in Ubuntu:
  New

Bug description:
  After applying the network-manager SRU in mantic, I get a notification
  that a system restart is required to fully apply updates.

  This immediately raised a question, because I KNOW my network
  connection was restarted when the SRU was installed (I have a VPN that
  did not auto-reconnect).

  And I checked the state of the process - it was definitely restarted
  and is running from the binary currently on disk.

  The network-manager postinst has the following code:

  # request a reboot (NM tears down interfaces on restart
  # which is not the way we want to go)
  [ -x /usr/share/update-notifier/notify-reboot-required ] && \
  /usr/share/update-notifier/notify-reboot-required

  But the service restart is also happening. debian/rules currently has:

  override_dh_installsystemd:
  dh_installsystemd -pnetwork-manager --no-start 
NetworkManager-dispatcher.service NetworkManager-wait-online.service 
nm-priv-helper.service
  dh_installsystemd -pnetwork-manager --no-also NetworkManager.service

  No other systemd overrides. Nothing inhibits the restart of the
  service.

  It needs to be one or the other.  And if we're doing SRUs of network-
  manager, then this is bad UX for users applying their daily updates
  and should be fixed in SRU.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:19:38 2023
  InstallationDate: Installed on 2019-12-23 (1401 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status

[Steve Langasek]

other connections also had . in the name and had no problem migrating.

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Critical
   Status: New

** Tags added: foundations-todo

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  
  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039503] [NEW] package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit stat

[Steve Langasek]

Public bug reported:

lunar to mantic upgrade, exciting to see output from network-manager
postinst migrating connections to /etc/netplan one by one.  But then:

Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
dpkg: error processing package network-manager (--configure):
 installed network-manager package post-installation script subprocess returned 
error exit status 10

That UUID appears in a file /etc/NetworkManager/system-
connections/UPTOWN.guests that hasn't been touched since 2015.

Contents of the file were:

[connection]
id=UPTOWN.guests
uuid=491fa5c8-68ef-4140-8679-dca422f5c262
type=wifi

[wifi]
ssid=UPTOWN.guests
mode=infrastructure
mac-address=E0:9D:31:09:84:54

[ipv6]
method=auto

[ipv4]
method=auto


I've removed it from disk and the migration continued to completion.

Then I got another failure on:

[connection]
id=belkin.1e4.guests
uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
type=802-11-wireless

[802-11-wireless]
ssid=belkin.1e4.guests
mode=infrastructure
mac-address=00:24:D7:1F:EA:20

[ipv6]
method=auto

[ipv4]
method=auto

Is it unhappy because of the . in the names?

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Oct 16 16:12:43 2023
ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2019-12-23 (1393 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: network-manager
Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Critical
 Status: New

** Affects: network-manager (Ubuntu Mantic)
 Importance: Critical
 Status: New


** Tags: amd64 apport-package foundations-todo mantic need-duplicate-check

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  
  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  

[Desktop-packages] [Bug 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries

[Steve Langasek]

2023-10-14T01:44:00.468542-04:00 anadon gdm-password]: 
pam_unix(gdm-password:session): session opened for user anadon(uid=1000) by 
(uid=0)
2023-10-14T01:44:00.473683-04:00 anadon systemd-logind[1169]: New session 6 of 
user anadon.
2023-10-14T01:44:00.522860-04:00 anadon (systemd): 
pam_unix(systemd-user:session): session opened for user anadon(uid=1000) by 
(uid=0)
2023-10-14T01:44:00.658692-04:00 anadon gdm-password]: gkr-pam: unlocked login 
keyring
2023-10-14T01:44:01.673108-04:00 anadon gnome-keyring-daemon[3237]: The PKCS#11 
component was already initialized
2023-10-14T01:44:01.673392-04:00 anadon gnome-keyring-daemon[3560]: 
discover_other_daemon: 1
2023-10-14T01:44:01.674538-04:00 anadon gnome-keyring-daemon[3237]: The Secret 
Service was already initialized
2023-10-14T01:44:01.674742-04:00 anadon gnome-keyring-daemon[3562]: 
discover_other_daemon: 1
2023-10-14T01:44:01.677463-04:00 anadon gnome-keyring-daemon[3563]: 
discover_other_daemon: 1
2023-10-14T01:44:09.242277-04:00 anadon PackageKit: uid 1000 is trying to 
obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
2023-10-14T01:44:09.243637-04:00 anadon PackageKit: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
2023-10-14T01:44:10.632860-04:00 anadon gdm-password]: 
pam_unix(gdm-password:session): session closed for user anadon
2023-10-14T01:44:10.643754-04:00 anadon systemd-logind[1169]: Session 6 logged 
out. Waiting for processes to exit.
2023-10-14T01:44:10.644366-04:00 anadon systemd-logind[1169]: Removed session 6.

This appears to show a successful login with gdm.  So if launching the
graphical session fails afterwards, that must be an issue with gdm or
some other downstream component.  Reassigning.

** Package changed: pam (Ubuntu) => gdm3 (Ubuntu)

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

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

Title:
  On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM
  entries

Status in Ubuntu:
  New
Status in apparmor package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  New

Bug description:
  Last time I hacked around a bug like this, it had portions in PAM,
  apparmor, Seahorse, and Gnome so this time I'd like someone more
  focused on broad stability to look at things.

  The problem is simple.  Before the upgrade to 23.10, I could log in
  using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org"
  WMs.  Now I can't.  I can still login using XFCE and TTY.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2039340/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into mantic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:23.10.11
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-mantic

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 

[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Steve Langasek]

** Package changed: ubuntu-settings (Ubuntu) => ubuntu-raspi-settings
(Ubuntu)

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-raspi-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2038964/+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 2039104] [NEW] ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Steve Langasek]

Public bug reported:

In response to LP: #2038964 and due to the timing we have forked ubuntu-
raspi-settings into a separate source package.

ubuntu-settings must therefore be updated to drop ubuntu-raspi-settings*
from debian/control as otherwise binary builds of the package will be
rejected by the archive (if the version number is <= 23.10.6) or will
wrongly supersede the fixes that have just been uploaded to mantic (if
the version number is > 23.10.6).

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Affects: ubuntu-settings (Ubuntu Mantic)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New


** Tags: foundations-todo

** Also affects: ubuntu-settings (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-settings (Ubuntu Mantic)
 Assignee: (unassigned) => Dave Jones (waveform)

** Tags added: foundations-todo

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

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