[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-10 Thread Tim Holmes-Mitra
I've tested the proposed mesa + hwe kernel and as far as I can tell it's
working well. I believe my Z16 is navi 2nd generation and it has an iGPU
and dGPU both AMD (600M series and RX 6500 respectively). What I tested:

- firefox you tube videos (with both DRI_PRIME=0 and 1)
- steam deb running dota and quake2 (with both DRI_PRIME=0 and 1)
- desktop is hardware rendered with the iGPU and working well
- multi-monitor (2 external 4k monitors)

Let me know if there's anything else I should add or test.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()

2023-10-05 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037497

Title:
  gnome-shell crashed with SIGSEGV at NULL from end_query() from
  cogl_gl_create_timestamp_query() from
  cogl_onscreen_egl_swap_buffers_with_damage()

Status in Mesa:
  New
Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in mesa package in Fedora:
  Confirmed

Bug description:
  crash after update
  wayland session is not accessible anymore

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 05:52:26 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-26 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users
  separator:

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


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


[Touch-packages] [Bug 1923052] Re: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session

2023-09-21 Thread Tim Holmes-Mitra
Not a release blocker.

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1923052

Title:
  screen reader does not read ubiquity window after it is launched in
  "Try Ubuntu" session

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Confirmed
Status in at-spi2-core source package in Jammy:
  Incomplete
Status in orca source package in Jammy:
  Incomplete
Status in ubiquity source package in Jammy:
  Confirmed
Status in at-spi2-core source package in Mantic:
  Incomplete
Status in orca source package in Mantic:
  Incomplete
Status in ubiquity source package in Mantic:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions


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


[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

2023-09-21 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug 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 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


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


[Touch-packages] [Bug 2019939] Re: Outdated documentation about NetworkManager keyfiles

2023-09-21 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  Outdated documentation about NetworkManager keyfiles

Status in debian-handbook package in Ubuntu:
  Won't Fix
Status in dhcpcanon package in Ubuntu:
  Won't Fix
Status in fai package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  Fix Committed
Status in scap-security-guide package in Ubuntu:
  New
Status in wifi-qr package in Ubuntu:
  New

Bug description:
  The affected packages contain documentation or examples about
  NetworkManager keyfiles, which might not be appropriate anymore on
  Ubuntu, since the Netplan integration was enabled in NetworkManager
  (starting with Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+subscriptions


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