[Bug 2095536] Re: [MIR] ubuntu-x1e-settings

[Christian Ehrhardt]

Only ubuntu-x1e-settings itself had the arch switch

$ rmadison -u ubuntu -s plucky-proposed hwe-qcom-x1e-meta ubuntu-x1e-settings ubuntu-x1e-settings-nogrub 
 hwe-qcom-x1e-meta          | 25.04.3 | plucky-proposed/universe | all
 hwe-qcom-x1e-meta          | 25.04.4 | plucky-proposed/universe | all
 ubuntu-x1e-settings        | 25.04.3 | plucky-proposed/universe | amd64, armhf, ppc64el, riscv64
 ubuntu-x1e-settings        | 25.04.4 | plucky-proposed/universe | source, arm64
 ubuntu-x1e-settings-nogrub | 25.04.3 | plucky-proposed/universe | all
 ubuntu-x1e-settings-nogrub | 25.04.4 | plucky-proposed/universe | all

matches excuses

old binaries left on amd64: ubuntu-x1e-settings (from 25.04.3)
missing build on armhf: ubuntu-x1e-settings (from 25.04.3)
missing build on ppc64el: ubuntu-x1e-settings (from 25.04.3)
missing build on riscv64: ubuntu-x1e-settings (from 25.04.3)

Removing those so that 25.04.4 could move

./remove-package -m "LP: #2095536 ubuntu-x1e-settings is only meant for arm64" -s plucky-proposed --version 25.04.3 -a amd64 -a armhf -a ppc64el -a riscv64 --binary ubuntu-x1e-settings
Removing packages from plucky-proposed:
	ubuntu-x1e-settings 25.04.3 in plucky amd64
	ubuntu-x1e-settings 25.04.3 in plucky armhf
	ubuntu-x1e-settings 25.04.3 in plucky ppc64el
	ubuntu-x1e-settings 25.04.3 in plucky riscv64
Comment: LP: #2095536 ubuntu-x1e-settings is only meant for arm64
Remove [y|N]? y
4 packages successfully removed.

With that done and the MIR approved let us also fix the component mismatch.
I do see live-common seed -> ubuntu-x1e-settings which itself needs ubuntu-x1e-settings-nogrub.
But I do not see a dep onto hwe-qcom-x1e-meta.
As it would therefore drop out again let us for now only promote these.

./change-override --component main --suite plucky-proposed ubuntu-x1e-settings-nogrub
Override component to main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky amd64: universe/misc/optional/100% -> main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky arm64: universe/misc/optional/100% -> main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky armhf: universe/misc/optional/100% -> main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky i386: universe/misc/optional/100% -> main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky ppc64el: universe/misc/optional/100% -> main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky riscv64: universe/misc/optional/100% -> main
ubuntu-x1e-settings-nogrub 25.04.4 in plucky s390x: universe/misc/optional/100% -> main
Override [y|N]? y
7 publications overridden.

./change-override --component main --suite plucky-proposed --binary-and-source ubuntu-x1e-settings
Override component to main
ubuntu-x1e-settings 25.04.4 in plucky: universe/misc -> main
ubuntu-x1e-settings 25.04.4 in plucky arm64: universe/misc/optional/100% -> main
Override [y|N]? y
2 publications overridden.


If there is anything missing or wrong or worth to sort out with hwe-qcom-x1e-meta, comment and set this back to incomplete so we see it in the MIR meeting.


** Changed in: ubuntu-x1e-settings (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-x1e-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2095536

Title:
  [MIR] ubuntu-x1e-settings

Status in ubuntu-x1e-settings package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  Currently in universe

  [Rationale]
  Very much like we did with the Lenovo Thinkpad X13s for 24.10 [1] I would
  like to add support for some of the new Snapdragon X Elite laptops in
  our coming release. Because arm64 is a bit special we need to ship a
  settings package containing tweaks and configs that make the installer
  "just work".

  This is based on the work I did for our Snapdragon Ubuntu concept
  image [2].

  [Security]
  I don't expect any security impact. The package is mostly config files
  and should only affect this specific hardware.

  [Quality assurance]
  For now we will have to test manually. There are multiple developers who
  have access to hardware so that should not get in the way.

  [UI standards]

  [Dependencies]

  [Standards compliance]

  [Maintenance/Owner]
  Owned by the Foundations team.

  [Background information]
  The package provides 3 binary packages.

  - hwe-qcom-x1e-meta: This is picked up by "ubuntu-drivers --recommended" in subiquity and pulls
    in ubuntu-x1e-settings
  - ubuntu-x1e-settings: A full set of configs needed to make a installation work. This includes
    statically configured kernel command line parameters that would regress other devices
  - ubuntu-x1e-settings-nogrub: A safe subset of ubuntu-x1e-settings without the kernel command line.
    On our live media we want those to be set at runtime depending on which device we boot on to prevent
    regressions

  >  please explain and give rationale for the "snap channels" in
  >  debian/ubuntu-x1e-settings.postinst, as this seems to be swapping out the
  >  whole stacks of GNOME/Mesa, which might lead to a different experience than
  >  stock Ubuntu.
  >  => snap refresh --channel adreno/stable --no-wait gnome-42-2204
  >  => snap refresh --channel beta/kisak --no-wait mesa-2404

  Since this is pretty new hardware we are facing problems with the
  dependency bundling model in snaps. Mesa in particular is problematic
  because it is closely tied to the hardware and kernel.

  The hardware this package enables is not supported in mesa prior to
  24.10, so the "default experience" would be that nothing works. We
  work around this by switching the main mesa provider snaps to channels
  built against a working mesa version.

  Since core24 there is a dedicated mesa snap to handle those kinds of situations, for core22 we have to hijack the gnome snap which supplies mesa for some core
  apps like the snap store or firefox (which segfault otherwise).

  This "workaround" will have to remain until those snaps switch to a
  base that is new enough to support the hardware out of the box
  (core26) or until we have a way to support newer hardware in older
  snap base versions (e.g. use system mesa). Once core24 is widely in
  use we can drop the workaround for core22.

  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/+bug/2074078
  [2] https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-x1e-settings/+bug/2095536/+subscriptions