[Touch-packages] [Bug 1973477] Re: unable to upgrade to xubuntu

2022-05-16 Thread Timo Aaltonen
the missing firmware warning is not the reason, it's erroring because of
klibc-utils

** Package changed: linux-firmware (Ubuntu) => klibc (Ubuntu)

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

Title:
  unable to upgrade to xubuntu

Status in klibc package in Ubuntu:
  Incomplete

Bug description:
  W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module 
r8169
  Errors were encountered while processing:
   klibc-utils
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 16:59:41 2022
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InstallationDate: Installed on 2022-04-20 (24 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1973477/+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 1971712] Re: Add support for Intel DG2

2022-05-13 Thread Timo Aaltonen
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1972721] Re: Include gtk3 changes needed for mutter 42.1

2022-05-13 Thread Timo Aaltonen
Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.33-1ubuntu2 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: gtk+3.0 (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 Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1972721

Title:
  Include gtk3 changes needed for mutter 42.1

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 
apps like gedit, it's not possible to scroll past the cursor position.

  The mutter issue with more details is
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2261

  We need to update mutter 42.1 since it includes a lot of bug fixes.

  GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and
  gtk4) will better comply with the Wayland specifications.

  The gtk4 bug is LP: #1972722

  Test Case
  -
  Install the updated gtk3 packages.
  Use gedit to open a long text file.
  Scroll down past the page break.
  The document should scroll normally.

  What Could Go Wrong
  ---
  Ideally, GNOME would have done a new GTK3 release for this issue. They will 
eventually, but it seems better for Ubuntu to be proactive and not further 
delay the mutter/gnome-shell 42.1 releases.

  These commits are cherry-picks from the stable branch
  https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/

  NOTE
  
  To avoid a temporary mismatch related to phased updates, we want this update 
to be 100% phased before releasing mutter 42.1 to jammy-updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1972721/+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 1973270] Re: json-c please mark package as multiarch

2022-05-13 Thread Timo Aaltonen
Hello Gianfranco, or anyone else affected,

Accepted json-c into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/json-c/0.15-3~ubuntu1.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: json-c (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 Ubuntu
Touch seeded packages, which is subscribed to json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1973270

Title:
  json-c please mark package as multiarch

Status in json-c package in Ubuntu:
  Fix Released
Status in json-c source package in Jammy:
  Fix Committed
Status in json-c source package in Kinetic:
  Fix Released

Bug description:

  [Impact]

  People using multi-arch to build for different architectures

  [Test Plan]

   * Install json-c on M-A environment

  [Where problems could occur]

  * Specially now that we don't have anymore real i386 env

  [Other Info]
   
   json-c (0.15-3) unstable; urgency=medium
 * Mark dev package as M-A: same (Closes: #1009805)
   - thanks Tomeu Vizoso for the hint.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1973270/+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 1971712] Re: Add support for Intel DG2

2022-05-11 Thread Timo Aaltonen
** Description changed:

  [Impact]
  
  Ubuntu 22.04 does not support Intel DG2-based hw which is released later
  this year.
- 
  
  [Fix]
  
  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package
  
- 
  [Test case]
  
  Boot a system with a DG2-based GPU, check that native graphics drivers
- are used
+ are used.
  
+ Test mesa also on gen9-gen12 GPU's to verify that there are no
+ regressions even though the backports are for DG2.
  
  [What could go wrong]
  
  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which isn't
  installed by default except preinstall machines with this hardware. So
  other users are not affected.

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in linux-oem-5.17 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1959345] Re: vulkaninfo reports error

2022-05-10 Thread Timo Aaltonen
see, remnants of amdgpu-pro ;)

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1615381] Please test proposed package

2022-05-06 Thread Timo Aaltonen
Hello Jarno, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.15 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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: apt (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  APT will try and fail to remove the currently running kernel, when booted 
into an older kernel that is not protected. May wreak some havoc if mixed with 
other operations to the point that apt goes weird and needs manual fixing up.

  [Test case]
  For the SRUs we have included an automated test case that starts with an 
empty autoremove config file, and then checks that the running kernel is 
protected at runtime.

  You can also test manually, but it's not necessary:

  - Install new kernel
  - Reboot into kernel not listed as protected in 01autoremove-kernels
  - Run autoremove

  [Where problems could occur]
  We may more easily run out of space in /boot. hirsute has new autoremoval 
code that runs completely at runtime; but that seems a bit large to SRU after 
only a few weeks in hirsute. Hence, we should protect the current kernel _in 
addition_ to the other kernels, just like unattended-upgrades and 
update-manager do. This increases the risk of filling up /boot compared to 
older apt versions, but is at the same level as unattended-upgrades and 
update-manager.

  [Original bug report]

  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  

[Touch-packages] [Bug 1968154] Please test proposed package

2022-05-06 Thread Timo Aaltonen
Hello Julian, or anyone else affected,

Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.8 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: apt (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  New
Status in apt source package in Focal:
  Fix Committed
Status in unattended-upgrades source package in Focal:
  New
Status in apt source package in Impish:
  Fix Committed
Status in unattended-upgrades source package in Impish:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1615381] Re: apt-get autoremove may remove current kernel

2022-05-06 Thread Timo Aaltonen
Hello Jarno, or anyone else affected,

Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.8 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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 removed: verification-done verification-done-focal
** Tags added: verification-needed verification-needed-focal

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

** Changed in: apt (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  APT will try and fail to remove the currently running kernel, when booted 
into an older kernel that is not protected. May wreak some havoc if mixed with 
other operations to the point that apt goes weird and needs manual fixing up.

  [Test case]
  For the SRUs we have included an automated test case that starts with an 
empty autoremove config file, and then checks that the running kernel is 
protected at runtime.

  You can also test manually, but it's not necessary:

  - Install new kernel
  - Reboot into kernel not listed as protected in 01autoremove-kernels
  - Run autoremove

  [Where problems could occur]
  We may more easily run out of space in /boot. hirsute has new autoremoval 
code that runs completely at runtime; but that seems a bit large to SRU after 
only a few weeks in hirsute. Hence, we should protect the current kernel _in 
addition_ to the other kernels, just like unattended-upgrades and 
update-manager do. This increases the risk of filling up /boot compared to 
older apt versions, but is at the same level as unattended-upgrades and 
update-manager.

  [Original bug report]

  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 

[Touch-packages] [Bug 1968154] Please test proposed package

2022-05-06 Thread Timo Aaltonen
Hello Julian, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.15 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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 Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1968154

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  New
Status in apt source package in Focal:
  Fix Committed
Status in unattended-upgrades source package in Focal:
  New
Status in apt source package in Impish:
  Fix Committed
Status in unattended-upgrades source package in Impish:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Re: Only keep 2 kernels

2022-05-06 Thread Timo Aaltonen
Hello Julian, or anyone else affected,

Accepted apt into impish-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.3.9ubuntu0.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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: apt (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

** Tags added: verification-needed-focal

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  New
Status in apt source package in Focal:
  Fix Committed
Status in unattended-upgrades source package in Focal:
  New
Status in apt source package in Impish:
  Fix Committed
Status in unattended-upgrades source package in Impish:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8

2022-05-06 Thread Timo Aaltonen
Hello Ilgaz, or anyone else affected,

Accepted openssl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.2 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: openssl (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 Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1968997

Title:
  openssl has catastrophic issues when locale set to TR_UTF8

Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Due to the case comparison differences in the Turkish locale, some routines in
  OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking
  crypto.

  [Test Plan]

  This bug is really easy to trigger:

  sudo locale-gen tr_TR.UTF-8
  LANG=C curl https://ubuntu.com/ > /dev/null # This work
  LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails

  The error is curl: (35) error:0372:digital envelope
  routines::decode error

  [Where problems could occur]

  This patch set is relatively massive, and can cause regressions, as 
illustrated
  by the patch #5 which fixes one such regression. Those regressions would 
likely
  show up as either libssl crashes, in case of uninitialized objects, or as
  algorithm selection failures if somehow the case comparison is buggy.

  [Other Info]
   
  The fix has already been released upstream as part of their 3.0.3 release.

  [Original report]
  I noticed this when I checked "ua status". It alerted me that I should check 
my openssl configuration.

  "ua status
  Failed to access URL: 
https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy
  Cannot verify certificate of server
  Please check your openssl configuration."

  I also figured wget doesn't work with https:// URLs at all.

  On web I found:
  https://github.com/openssl/openssl/issues/18039

  So I changed locale to C_UTF-8

  #locale
  LANG=tr_TR.UTF-8
  LANGUAGE=
  LC_CTYPE="tr_TR.UTF-8"
  LC_NUMERIC=tr_TR.UTF-8
  LC_TIME=tr_TR.UTF-8
  LC_COLLATE="tr_TR.UTF-8"
  LC_MONETARY=tr_TR.UTF-8
  LC_MESSAGES="tr_TR.UTF-8"
  LC_PAPER=tr_TR.UTF-8
  LC_NAME=tr_TR.UTF-8
  LC_ADDRESS=tr_TR.UTF-8
  LC_TELEPHONE=tr_TR.UTF-8
  LC_MEASUREMENT=tr_TR.UTF-8
  LC_IDENTIFICATION=tr_TR.UTF-8
  LC_ALL=
  casaba@ship-macbook:/backups$ sudo locale-gen c
  ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8
  ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8
  ca_ES ca_FR ce_RU crh_UA cv_RU
  ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB
  casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8
  Generating locales (this might take a while)...
C.UTF-8... done
  Generation complete.
  casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8
  casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8

  Now the result is (after logout/login)

  ua status
  SERVICE ENTITLED STATUS DESCRIPTION
  cc-eal yes n/a Common Criteria EAL2 Provisioning Packages
  cis yes n/a Security compliance and audit tools
  esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM)
  fips yes n/a NIST-certified core packages
  fips-updates yes n/a NIST-certified core packages with priority security 
updates
  livepatch yes n/a Canonical Livepatch service

  Enable services with: ua enable 

   Account: il...@fastmail.fm
  Subscription: il...@fastmail.fm

  If Ubuntu 22 ships with current configuration, entire TR will suffer
  considering you can't find http:// downloads anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic 

[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

2022-05-06 Thread Timo Aaltonen
Hello leonpano, or anyone else affected,

Accepted wpa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 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.

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

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1971712] [NEW] Add support for Intel DG2

2022-05-05 Thread Timo Aaltonen
Public bug reported:

[Impact]

Ubuntu 22.04 does not support Intel DG2-based hw which is released later
this year.


[Fix]

Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package


[Test case]

Boot a system with a DG2-based GPU, check that native graphics drivers
are used


[What could go wrong]

The Mesa patches are only for DG2 support, should not affect other
hardware at all. The kernel driver is in a separate package which isn't
installed by default except preinstall machines with this hardware. So
other users are not affected.

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

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

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

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

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

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

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in linux-oem-5.17 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  
  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  
  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used

  
  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1959345] Re: vulkaninfo reports error

2022-05-04 Thread Timo Aaltonen
I've been trying to tell that it's some remnant of amdgpu-pro, and not
something ever shipped by Ubuntu, and that's why the bug is marked as
'invalid'.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

2022-05-04 Thread Timo Aaltonen
the package is mesa-vulkan-drivers, and it ships the correct file for
radeon:

/usr/share/vulkan/icd.d/radeon_icd.x86_64.json

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

2022-05-02 Thread Timo Aaltonen
well I think some parts still remain on your system.. in any case, it
should all work just fine at least on more current releases

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

2022-04-29 Thread Timo Aaltonen
it's looking for amd_icd64.json, and if you google that most hits seem
to suggest amdgpu-pro/amdvlk

so do you have amdvlk installed?

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

2022-04-28 Thread Timo Aaltonen
we as in 'ubuntu'

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

2022-04-28 Thread Timo Aaltonen
you have the amdgpu-pro driver installed, if it's vulkan driver does not
install it's icd file in the correct place, there's nothing we can do
about that

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-06 Thread Timo Aaltonen
udev is built by src:systemd

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-06 Thread Timo Aaltonen
Well, I can reassign to see if the maintainer of systemd/udev could
backport the patch for this.

** Package changed: xf86-input-wacom (Ubuntu) => systemd (Ubuntu)

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

2022-04-05 Thread Timo Aaltonen
** Changed in: xkeyboard-config (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in GNOME Shell:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .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  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-31 Thread Timo Aaltonen
That'll install all updates from proposed? Don't do that. Just use a
clean image and then install the required updates as mentioned in #106

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a 

[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-30 Thread Timo Aaltonen
the gnome-chess crash does

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in Mesa:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966221/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-29 Thread Timo Aaltonen
or do as advised in comment #106

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note 

[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-29 Thread Timo Aaltonen
echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted' >> 
/etc/apt/sources.list
apt update
apt install libx11-6

verify with 'apt-cache policy libx11-6' that you have the correct
version (from proposed), and run your tests.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) 

[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-29 Thread Timo Aaltonen
gnome-chess fails to start as well, but it's crashing also on newer gen
chips (tested on Alder Lake) with the iris driver. What's common is that
it is also fine on wayland.

upstream had a look at the backtrace, but said that there's nothing that
would explain why it fails on xorg

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966221/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)

2022-03-28 Thread Timo Aaltonen
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)

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

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1965563/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2022-03-25 Thread Timo Aaltonen
Hello jeremyszu, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.13 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: alsa-ucm-conf (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  On P620, only single port can work on rear panel. For example, when the 
Line-Out is plugged, the Mic won't work anymore.

  [Fix]
  Use upstream version of UCM to handle port priority correctly, instead of 
separate ports into different profiles.

  [Test]
  Once the UCM is in place, all three ports of rear panel work correctly.

  [Where problems could occur]
  UCM is not a static thing - it's actually interpreted differently at higher 
level. So any change in userspace daemons other than PulseAudio may not like 
the change and can interpret the UCM in another way.

  == Original Bug Report ==
  After backporting following patches from PA and alsa-ucm-conf and then it 
works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-24 Thread Timo Aaltonen
did you enable focal-proposed?

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note 

[Touch-packages] [Bug 1960669] Re: the display doesn't appear after suspend, i915

2022-02-12 Thread Timo Aaltonen
install 'linux-generic-hwe-20.04' and then you'll get a newer kernel

does it fix this?

** Package changed: libdrm (Ubuntu) => linux (Ubuntu)

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

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

Title:
  the display doesn't appear after suspend, i915

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System: Lenovo T470s
  Kernel: 5.4.0-97-generic #110-Ubuntu SMP

  After S3 suspend and resuming the external display doesn't work.
  C-A-F1, C-A-F7 solves the problem.

  The regression appears 2-3 weeks ago after update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960669/+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 1960544] Re: External Monitors Not Detected Anymore

2022-02-10 Thread Timo Aaltonen
you need to update again and run 'apport-collect 1960544'

also, test 21.10 live image to see if it works there

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

Title:
  External Monitors Not Detected Anymore

Status in mesa package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of
  mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm*
  etc.), external displays (here connected via DELL USB Dock) are not
  detected anymore. I had to restore the old version with Timeshift.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1960544] Re: External Monitors Not Detected Anymore

2022-02-10 Thread Timo Aaltonen
that's unlikely, mesa has little to do with driving displays, the kernel
does

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

Title:
  External Monitors Not Detected Anymore

Status in mesa package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of
  mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm*
  etc.), external displays (here connected via DELL USB Dock) are not
  detected anymore. I had to restore the old version with Timeshift.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1956915] Re: New bugfix release 21.2.6

2022-02-09 Thread Timo Aaltonen
this bug is "fix committed" for both focal and impish, meaning the
update is in the respective -proposed pocket.

see comment #5

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1960372] Re: DPMS ignores attempts to DISABLE IT

2022-02-09 Thread Timo Aaltonen
** Package changed: libxcb (Ubuntu) => ubuntu

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

Title:
  DPMS ignores attempts to DISABLE IT

Status in Ubuntu:
  New

Bug description:
  I'm on a fresh installation of Debian, linux image 5.10, with a radeon
  RX580 gpu.

  My computer is not honoring the setting to "never" turn the monitor
  off, in power settings.

  DPMS is still killing the monitor after 10 minutes. It appears bugged.
  I have to manually turn DPMS with a cron job every 5 minutes to make
  sure it "stays off".

  I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER
  AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me???

  How do I completely disable and REMOVE this bugged program "dpms" from
  my system, safely???

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1960372/+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 1956915] Re: New bugfix release 21.2.6

2022-02-09 Thread Timo Aaltonen
the jammy queue has had 21.3.x for weeks now

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1949553] Re: Backport packages for 20.04.4 HWE stack

2022-02-08 Thread Timo Aaltonen
tested on intel TGL-U, WHL, and AMD Radeon 520 Mobile, everything looks
good

** Description changed:

  [Impact]
  
  These are needed for 20.04.4 images.
  
  [Test case]
  
  Boot a daily image, see that it still has the necessary stack installed
  and working.
  
  [What could go wrong]
  
  libdrm: adds some new api, no changes to old stuff
  
- llvm-13: a new package, no regression potential on it's own
- 
  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that point
  
  xserver: a new point-release, 1.20.x series is in deep maintenance mode,
  so there should be little chance of breakage

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1956915] Re: New bugfix release 21.2.6

2022-02-08 Thread Timo Aaltonen
** Tags removed: verification-needed verification-needed-focal 
verification-needed-impish
** Tags added: verification-done verification-done-focal 
verification-done-impish

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1958242] Re: mesa update freeze/crash screen before login

2022-02-08 Thread Timo Aaltonen
please try the latest stable release from

https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

then at least we'd know if it's fixed in 21.3.x

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

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

Title:
  mesa update freeze/crash screen before login

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After updating my laptop after a long trip. It starts to bootm, then
  screen goes black with the mouse pointer hanging over, sddm does not
  start.

  This symptoms I saw them before and were related to mesa libraries. See 
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that.
  But the actual problem seems somewhat different this time.

  Furthermore dmesg shows:

  [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 
7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000]
  [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 
f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 
48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd

  r300_dri.so is from the package libgl1-mesa-dri

  I applied the same workaround I did for the previous time that mesa
  was broken: downgrade to previous mesa version.

  I went to Ctrl+Alt-F2, logged in and:
  **
  sudo apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 
libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 
libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 
libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5

  sudo apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 
libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 
libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 
libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5
  ***

  Now everything works fine. Other than the mentioned mesa packages
  everything else is fully updated.

  === In short something got broken again in mesa 21.2.6, downgrading to
  21.0.3 fixes the issue. ===

  Running Lubuntu 20.04
  Kernel:
  5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 
x86_64 GNU/Linux

  lsb_release -rd:
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

  GPU:
  Advanced Micro Devices [AMD/ATI]
  RS482M [Mobility Radeon Xpress 200]
  driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1958242/+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 1958904] Please test proposed package

2022-01-28 Thread Timo Aaltonen
Hello Andrea, or anyone else affected,

Accepted initramfs-tools into impish-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.140ubuntu6.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958904

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

2022-01-28 Thread Timo Aaltonen
Hello Andrea, or anyone else affected,

Accepted initramfs-tools into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.136ubuntu6.7 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: initramfs-tools (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

** Changed in: initramfs-tools (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-impish

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig

2022-01-27 Thread Timo Aaltonen
looks like it's still unresolved upstream

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  mesa GLX change leads to wine showing GLXBadFBConfig

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes
  both wine and Proton (on an older system that does not have Vulkan..
  SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to
  fire up OpenGL.

  Wine, for Direct3D support it tries to fire up (in order) Vulkan then
  progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even
  1.4 (of course the older the OpenGL the lower supported Direct3D
  version).  Wine does not like getting an error back with the same
  transaction serial number as it sent out.

  See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969
  Mesa issue 3969,  
  The patch there throws in an "XNoOp()" to increment the transaction serial 
number.

  But the patch there caused issues in other apps, per 
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763
  Mes  issue 4763,
  They found XNoOp() increments the serial number, but xcb keeps a "shadow 
copy" of the serial number which is not incremented, causing problems.   
XFlush() increments the serial number, keeps xcb in sync and happy, with no 
real side effects (running XFlush() frequently would slow things down, but this 
code only runs when a GLX context is being created anyway which just doesn't 
happen all that frequently.)

  Please find attached a patch implementing the updated patch suggested
  in issue 4763.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5
  ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Dec  1 18:59:43 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Dell Picasso [1028:0a12]
  InstallationDate: Installed on 2020-05-05 (575 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Inspiron 3505
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash 
nvme_core.io_timeout=300 nosmt vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2021
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.7
  dmi.board.asset.tag: not specified
  dmi.board.name: 0RV9WY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.4.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3505
  dmi.product.sku: 0A12
  dmi.product.version: 1.4.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+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 1574354] Re: playing .mp4 in VLC freezes machine

2022-01-27 Thread Timo Aaltonen
vlc works just fine on several machines here, closing

if you have further issues, open a new bug

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1958554] Re: package libdrm-intel1:amd64 2.4.91-2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevo

2022-01-21 Thread Timo Aaltonen
some transient issue on your system, not a bug in the package

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

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

Title:
  package libdrm-intel1:amd64 2.4.91-2 failed to install/upgrade: Paket
  ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
  nochmal installieren, bevor Sie die Konfiguration versuchen.

Status in libdrm package in Ubuntu:
  Invalid

Bug description:
  I jut got this error message when starting up; I have no further
  information.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libdrm-intel1:amd64 2.4.91-2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jan  9 17:13:47 2022
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GK208B [GeForce GT 730] [10b0:1287]
  InstallationDate: Installed on 2022-01-08 (12 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 7052A9G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.3
  SourcePackage: libdrm
  Title: package libdrm-intel1:amd64 2.4.91-2 failed to install/upgrade: Paket 
ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  nochmal 
installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT47AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HKT47AUS:bd01/10/2012:svnLENOVO:pn7052A9G:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 7052A9G
  dmi.product.version: ThinkCentre M91p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1958554/+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 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output

2022-01-17 Thread Timo Aaltonen
thanks for testing

focal-proposed (and impish) has 21.2.6, so once it lands in updates,
it's also fixed for focal

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

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

Title:
  Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc
  video output

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Hello!

  As reported here
  https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1939447 upgrading
  mesa-vdpau-drivers package from 20.0.4-2ubuntu1 to
  21.0.3-0ubuntu0.2~20.04.1 breaks vlc video hardware acceleration.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vdpau-drivers 21.0.3-0ubuntu0.2~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Aug 11 02:21:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  MachineType: HP HP 245 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=e8820090-c9e5-4245-bcb4-92818bd91e34 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.14
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.08:bd04/21/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.sku: Y9Q66PC#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-12T15:11:08.785042
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+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 1956915] Re: New bugfix release 21.2.6

2022-01-12 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1955566] Re: iris driver doesn't load correctly on intel pci_id 0x4688

2022-01-10 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1949553 ***
https://bugs.launchpad.net/bugs/1949553

focal will get this via impish backport

** This bug has been marked a duplicate of bug 1956915
   New bugfix release 21.2.6

** This bug is no longer a duplicate of bug 1956915
   New bugfix release 21.2.6

** This bug has been marked a duplicate of bug 1949553
   Backport packages for 20.04.4 HWE stack

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

Title:
  iris driver doesn't load correctly on intel pci_id 0x4688

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  [Impact]

   * iris driver doesn't load with pci_id 4688. Instead, it uses llvm.
  we expect the Intel GPU uses iris driver.

  [Test Plan]

   * $ DISPLAY=:0 glxinfo | grep -i opengl
  OpenGL vendor string: Mesa/X.org
  OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
  ...
  OpenGL version string: 3.1 Mesa 21.0.3

   * After applying the fix, it shows:

   * $ DISPLAY=:0 glxinfo | grep -i opengl
  OpenGL vendor string: Intel
  OpenGL renderer string: Mesa Intel(R) Graphics (ADL-S GT1)
  ...
  OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 
(git-d4975a0dbc)

  [Where problems could occur]

   * This patch is backport the PCI ID mapping for enabling iris driver which 
is expected when users have a GPU.
   * If there is any issue occur then we need to fix it with iris driver.

  [Other Info]

   * It already in upstream and we have a platform which using ADL-HX in OEM 
project. Thus, we need to enable iris on it at least on focal.
   * The patch is simple as to add "CHIPSET(0x4688, adl_gt1, "ADL-S GT1", 
"Intel(R) Graphics")" in "include/pci_ids/iris_pci_ids.h".
   * Patch backported from df5b14969f9869f363bcc8b2a564c85aaa481597

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955566/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

2022-01-10 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915

** This bug has been marked a duplicate of bug 1956915
   New bugfix release 21.2.6

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Impish:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1946621/+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 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output

2022-01-10 Thread Timo Aaltonen
So what about impish? Focal will soon get 21.2.x from impish.

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

Title:
  Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc
  video output

Status in mesa package in Ubuntu:
  New

Bug description:
  Hello!

  As reported here
  https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1939447 upgrading
  mesa-vdpau-drivers package from 20.0.4-2ubuntu1 to
  21.0.3-0ubuntu0.2~20.04.1 breaks vlc video hardware acceleration.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vdpau-drivers 21.0.3-0ubuntu0.2~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Aug 11 02:21:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  MachineType: HP HP 245 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=e8820090-c9e5-4245-bcb4-92818bd91e34 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.14
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.08:bd04/21/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.sku: Y9Q66PC#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-12T15:11:08.785042
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

2022-01-10 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915

** This bug has been marked a duplicate of bug 1956915
   New bugfix release 21.2.6

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1950044] Re: REGRESSION with version 21.0.3, please backport 21.2.x to Focal

2022-01-10 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915

** This bug has been marked a duplicate of bug 1956915
   New bugfix release 21.2.6

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

Title:
  REGRESSION with version 21.0.3, please backport 21.2.x to Focal

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,
  I was running into this problem:
  https://bugs.winehq.org/show_bug.cgi?id=50864

  The current workaround is:
  sudo add-apt-repository ppa:savoury1/display && sudo apt upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1950044/+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 1956915] Re: New bugfix release 21.2.6

2022-01-10 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Impish)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Impish:
  New

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1956915] [NEW] New bugfix release 21.2.6

2022-01-10 Thread Timo Aaltonen
Public bug reported:

[Impact]

This is the last point-release of the 21.2.x-series, we should put it in
impish so latest bugfixes would get there, and in focal for 20.04.4
image.

[Test case]

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

[Where things could go wrong]

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

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

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: mesa (Ubuntu Impish)
 Importance: Undecided
 Status: New

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

** Also affects: mesa (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Impish:
  New

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1952083] Re: Add support for Beige Goby

2021-12-02 Thread Timo Aaltonen
sounds like your mirror is not uptodate

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

Title:
  Add support for Beige Goby

Status in amd:
  New
Status in OEM Priority Project:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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

2021-12-01 Thread Timo Aaltonen
The verification of the Stable Release Update for mesa 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 Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1952083

Title:
  Add support for Beige Goby

Status in amd:
  New
Status in OEM Priority Project:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1952083/+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 1949553] Re: Backport packages for 20.04.4 HWE stack

2021-11-24 Thread Timo Aaltonen
see Debian bugs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994873
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994955

we can't keep valgrind enabled, or libdrm.pc would be broken

** Bug watch added: Debian Bug tracker #994873
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994873

** Bug watch added: Debian Bug tracker #994955
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994955

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Incomplete
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1952083] [NEW] Add support for Beige Goby

2021-11-24 Thread Timo Aaltonen
Public bug reported:

Impact]

New hardware support for AMD's Beige Goby needs a commit backported to
mesa. This is only needed on focal, skipping hirsute (no kernel support
there). Fixed in impish and up.

[Test plan]

Install updates, boot a BG machine and check that the desktop has full
hardware acceleration.

[Where problems could occur]

Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
could go wrong.

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

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

** Description changed:

  Impact]
  
  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel support
- there).
+ there). Fixed in impish and up.
  
  [Test plan]
  
  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.
  
  [Where problems could occur]
  
  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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

Title:
  Add support for Beige Goby

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952083/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-23 Thread Timo Aaltonen
Bug 1918855 is fixed in focal and up, so if you still have crashes then
that was not your bug/fix.

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1871959/+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 1950174] Update Released

2021-11-18 Thread Timo Aaltonen
The verification of the Stable Release Update for mesa 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 Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1950174

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87

  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU
  is enabled in WSLg. We’re getting incredibly unlucky because a glx
  drawable is being freed and reallocated with exactly the same heap
  pointers during a resize, which is causing Mesa to think the new
  drawable is already fully initialized when binded to the context, but
  it is not true and only because the new drawable is matching the old
  stale pointer for the previously freed drawable… and as a result the
  context remain invalid and the app is unable to present.

  With the push of WDDMv3 drivers which expose vGPU in WSL, the number
  of users hitting this issue is increasing.

  [Test Case]
  On Windows 11 with WSLg and Ubuntu 20.04

  1. Verify that hardware acceleration is enable either with glxinfo -B or in 
edge with edge://gpu
  2. Install and launch chrome, edge or vscode
  3. Resize the windows repeatedly

  Verification:
  The app must not crash or hang.

  [What could go wrong]

  The patch resets two pointers to NULL in dri_unbind_context(), which
  is correct for that function and can't regress anything else.

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

2021-11-15 Thread Timo Aaltonen
The verification of the Stable Release Update for openssl 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 Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1940656

Title:
  Potential use after free bugs in 1.1.1

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * There have been multiple use-after-free bugs fixed in OpenSSL 1.1.1
  stable branches which have not yet been applied in Focal. They are
  difficult to reproduce, often require an engine to be used, and
  somehow fail, as these use-after-free bugs are all in error conditions
  and error paths. Usually fixing local configuration, and making engine
  available is the right solution. It is however better to return errors
  than crash. These patches are in 1.1.1h+ and openssl-3.

  [Test Plan]

   * The fixes were applied upstream without clear reproducers, or unit
  tests

   * Check that all autopkgtests pass and there no regressions

   * Configure and use openssl with any engine and ensure that it
  continues to work

  [Where problems could occur]

   * There will be behaviour change, such that multithreaded
  applications may now notice Null pointers from the openssl engine
  apis, when previously they saw valid pointers which were freed
  already. Meaning that on connection failures, daemon or application
  shutdowns, different messages might be generated i.e. invalid engine
  context, unallocated methods, instead of crashing with double free.

  [Other Info]

   * Multiple customers are using openssl 1.1.1 with engines these days,
  reporting various issues, it is better to have more resilient openssl
  w.r.t. engine use in case of engine missuse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940656/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

2021-11-10 Thread Timo Aaltonen
fixed in 21.2.5-1 which is in jammy-proposed

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

** Also affects: mesa (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Impish:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1946621/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

2021-11-10 Thread Timo Aaltonen
** Description changed:

  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:
  
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
  
  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
  enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
  is being freed and reallocated with exactly the same heap pointers
  during a resize, which is causing Mesa to think the new drawable is
  already fully initialized when binded to the context, but it is not true
  and only because the new drawable is matching the old stale pointer for
  the previously freed drawable… and as a result the context remain
  invalid and the app is unable to present.
  
  With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
  users hitting this issue is increasing.
  
  [Test Case]
  On Windows 11 with WSLg and Ubuntu 20.04
  
  1. Verify that hardware acceleration is enable either with glxinfo -B or in 
edge with edge://gpu
  2. Install and launch chrome, edge or vscode
  3. Resize the windows repeatedly
  
  Verification:
  The app must not crash or hang.
  
  [What could go wrong]
+ 
+ The patch resets two pointers to NULL in dri_unbind_context(), which is
+ correct for that function and can't regress anything else.

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

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Incomplete

Bug description:
  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87

  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU
  is enabled in WSLg. We’re getting incredibly unlucky because a glx
  drawable is being freed and reallocated with exactly the same heap
  pointers during a resize, which is causing Mesa to think the new
  drawable is already fully initialized when binded to the context, but
  it is not true and only because the new drawable is matching the old
  stale pointer for the previously freed drawable… and as a result the
  context remain invalid and the app is unable to present.

  With the push of WDDMv3 drivers which expose vGPU in WSL, the number
  of users hitting this issue is increasing.

  [Test Case]
  On Windows 11 with WSLg and Ubuntu 20.04

  1. Verify that hardware acceleration is enable either with glxinfo -B or in 
edge with edge://gpu
  2. Install and launch chrome, edge or vscode
  3. Resize the windows repeatedly

  Verification:
  The app must not crash or hang.

  [What could go wrong]

  The patch resets two pointers to NULL in dri_unbind_context(), which
  is correct for that function and can't regress anything else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Timo Aaltonen
** Also affects: mesa (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  New

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1949116/+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 1949553] Re: Backport packages for 20.04.4 HWE stack

2021-11-03 Thread Timo Aaltonen
** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

** Changed in: libdrm (Ubuntu Focal)
   Status: New => In Progress

** Changed in: mesa (Ubuntu Focal)
   Status: New => In Progress

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

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libdrm (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  In Progress
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  In Progress

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1949553] [NEW] Backport packages for 20.04.4 HWE stack

2021-11-03 Thread Timo Aaltonen
Public bug reported:

[Impact]

These are needed for 20.04.4 images.

[Test case]

Boot a daily image, see that it still has the necessary stack installed
and working.

[What could go wrong]

libdrm: adds some new api, no changes to old stuff

llvm-13: a new package, no regression potential on it's own

mesa: a new major release, but we'll pull the final stable release of
21.2.x series, so there shouldn't be any regressions left at that point

xserver: a new point-release, 1.20.x series is in deep maintenance mode,
so there should be little chance of breakage

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

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

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Timo Aaltonen
yes it should, promotion is fine

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  New

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1949116/+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 1940504] Re: Support Alder Lake P graphics

2021-10-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1930188] Please test proposed package

2021-10-08 Thread Timo Aaltonen
Hello Bijay, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.12 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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 Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the 

[Touch-packages] [Bug 1930188] Please test proposed package

2021-10-08 Thread Timo Aaltonen
Hello Bijay, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: pulseaudio (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU 

[Touch-packages] [Bug 1930188] Please test proposed package

2021-10-08 Thread Timo Aaltonen
Hello Bijay, or anyone else affected,

Accepted pulseaudio into hirsute-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:14.2-1ubuntu1.2 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: pulseaudio (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for 

[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

2021-10-08 Thread Timo Aaltonen
Hello Bijay, or anyone else affected,

Accepted alsa-ucm-conf into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.4-2ubuntu1.4 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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 removed: verification-done-hirsute
** Tags added: verification-needed verification-needed-hirsute

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

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic 

[Touch-packages] [Bug 1944107] Re: No archive files for static compilation are included in the -dev package

2021-10-05 Thread Timo Aaltonen
this broke flutter classic snap, and I had to revert the change

** Changed in: libdrm (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
   No archive files for static compilation are included in the -dev
  package

Status in libdrm package in Ubuntu:
  Triaged

Bug description:
  There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not
  possible to compile statically against this library. See attached
  debdiff to solve this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd

2021-10-04 Thread Timo Aaltonen
Note that this will be dropped from the next upload, as LLVM JIT is not
available on riscv64 which means apps crash, see Debian bug #995618.

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

Title:
  Enable riscv64 build of mesa-opencl-icd

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu release: impish
  Package version: 21.2.1-2ubuntu1

  `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so
  is it possible to enable this package as I have done here:
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing-
  archive-extra ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp

2021-09-29 Thread Timo Aaltonen
** Description changed:

  [Impact]
  
  New hardware support for AMD's Yellow Carp need five commits backported
- to mesa and new firmware. This is only needed on focal, skipping
- hirsute/impish (no kernel support there).
+ to mesa and new firmware. This is only needed on focal, skipping hirsute
+ (no kernel support there).
  
  [Test plan]
  
  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.
  
  [Where problems could occur]
  
  The firmware is new, so it will simply add new files to l-f without any
  impact on others.
  
  Mesa adds five commits in total, and while some affect other chips, they
  mostly fix hw bugs or add a helper and such, hard to see what could go
  wrong.

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  New
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2021-09-28 Thread Timo Aaltonen
huh, focal-updates has a much newer mesa which has that commit..

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1945227] [NEW] drm/amdgpu: Add support for Yellow Carp

2021-09-27 Thread Timo Aaltonen
Public bug reported:

[Impact]

New hardware support for AMD's Yellow Carp need five commits backported
to mesa and new firmware. This is only needed on focal, skipping
hirsute/impish (no kernel support there).

[Test plan]

Install updates, boot a YC machine and check that the desktop has full
hardware acceleration.

[Where problems could occur]

The firmware is new, so it will simply add new files to l-f without any
impact on others.

Mesa adds five commits in total, and while some affect other chips, they
mostly fix hw bugs or add a helper and such, hard to see what could go
wrong.

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

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  New
Status in mesa source package in Focal:
  New

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute/impish (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

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

2021-09-27 Thread Timo Aaltonen
The verification of the Stable Release Update for libdrm 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 Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940504

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2021-09-27 Thread Timo Aaltonen
comment #113 still holds, focal needs to be verified first

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To 

[Touch-packages] [Bug 1940504] Re: Support Alder Lake P graphics

2021-09-23 Thread Timo Aaltonen
oh, oem-5.14 was part of this bug :)

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

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940504] Re: Support Alder Lake P graphics

2021-09-23 Thread Timo Aaltonen
ADL-P works with the updated stack, plus linux-oem-5.14 from proposed

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1944107] Re: No archive files for static compilation are included in the -dev package

2021-09-21 Thread Timo Aaltonen
enabled again in 2.4.107-3

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

Title:
   No archive files for static compilation are included in the -dev
  package

Status in libdrm package in Ubuntu:
  New

Bug description:
  There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not
  possible to compile statically against this library. See attached
  debdiff to solve this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+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 1940504] Re: Support Alder Lake P graphics

2021-09-17 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1943906] [NEW] warning about missing firmware is mostly just noise

2021-09-17 Thread Timo Aaltonen
Public bug reported:

Every time an LTS release gets a new backport kernel, we see reports
from concerned users when they see something like this:

W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module 
i915

and since we don't do full backports of linux-firmware this is just
noise for the users. Could there be a way to warn only during the
development phase? That way the missing firmware would more likely get
added for the primary kernel prior to release, but not warn when using a
newer backport/mainline kernel.

(in this case the guc firmware would be pointless to add to l-f, since
while they would be loaded, the feature they add is not enabled by
default)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: initramfs-tools 0.140ubuntu6
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 17 08:47:46 2021
InstallationDate: Installed on 2018-02-06 (1318 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to impish on 2020-09-02 (379 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

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

Title:
  warning about missing firmware is mostly just noise

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Every time an LTS release gets a new backport kernel, we see reports
  from concerned users when they see something like this:

  W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for 
module i915

  and since we don't do full backports of linux-firmware this is just
  noise for the users. Could there be a way to warn only during the
  development phase? That way the missing firmware would more likely get
  added for the primary kernel prior to release, but not warn when using
  a newer backport/mainline kernel.

  (in this case the guc firmware would be pointless to add to l-f, since
  while they would be loaded, the feature they add is not enabled by
  default)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: initramfs-tools 0.140ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 17 08:47:46 2021
  InstallationDate: Installed on 2018-02-06 (1318 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: 

[Touch-packages] [Bug 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

2021-09-16 Thread Timo Aaltonen
** Description changed:

  If mesa is built with -O3 then EGL will fail with:
  
  libEGL warning: DRI2: failed to create any config
  
  this can be easily reproduced by building libepoxy which then runs a
  series of tests.
+ 
+ The same is fine on amd64, and also ppc64el is fine with gcc-10 and -O3.

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  Unknown
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1943818] [NEW] mesa built with -O3 on ppc64el has broken EGL

2021-09-16 Thread Timo Aaltonen
Public bug reported:

If mesa is built with -O3 then EGL will fail with:

libEGL warning: DRI2: failed to create any config

this can be easily reproduced by building libepoxy which then runs a
series of tests.

The same is fine on amd64, and also ppc64el is fine with gcc-10 and -O3.

** Affects: mesa
 Importance: Unknown
 Status: Unknown

** Affects: gcc-11 (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: ppc64el

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #5315
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/5315

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/5315
   Importance: Unknown
   Status: Unknown

** Also affects: gcc-11 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  Unknown
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd

2021-09-08 Thread Timo Aaltonen
the packaging is basically synced from Debian, committed there

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

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

Title:
  Enable riscv64 build of mesa-opencl-icd

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  Ubuntu release: impish
  Package version: 21.2.1-2ubuntu1

  `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so
  is it possible to enable this package as I have done here:
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing-
  archive-extra ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1940504] Re: Support Alder Lake P graphics

2021-09-07 Thread Timo Aaltonen
** Package changed: linux-oem-5.13 (Ubuntu Focal) => linux-oem-5.14
(Ubuntu Focal)

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  New
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940504] Re: Support Alder Lake P graphics

2021-08-25 Thread Timo Aaltonen
** Description changed:

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.
  
  [Impact]
  
  ADL-P machines need to use the native driver.
  
  [Fix]
  
  Backport support from upstream.
  
  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
  
  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.
  
- 
  [Where things could go wrong]
+ For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in mesa source package in Focal:
  New

Bug description:
  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

2021-08-20 Thread Timo Aaltonen
I realize that, but that won't happen before impish has released. And
even then it'll take a while to land, but will happen before 20.04.4
release.

In the meantime you can use a ppa version, there are several to choose
from

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  New

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

2021-08-19 Thread Timo Aaltonen
Besides, 21.1.7 does not have that merge request in it, only
master/21.2-branch do.

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  New

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

2021-08-19 Thread Timo Aaltonen
We just got 21.0.x from Ubuntu 21.04 backported, the next one will be
21.2.x from impish after it has released.

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  New

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940504] Re: Support Alder Lake P graphics

2021-08-19 Thread Timo Aaltonen
** Description changed:

+ NOTE: this is for focal only, hirsute/impish do not and will not have
+ kernel support for this.
+ 
  [Impact]
  
+ ADL-P machines need to use the native driver.
  
  [Fix]
  
+ Backport support from upstream.
+ 
+ libdrm: a single patch from 2.4.107
+ mesa: three commits to add pci-id's and a workaround
+ kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
  
  [Test case]
+ Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.
  
  
  [Where things could go wrong]

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

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

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in mesa source package in Focal:
  New

Bug description:
  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  
  [Where things could go wrong]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940504] Re: Support Alder Lake P graphics

2021-08-19 Thread Timo Aaltonen
** Changed in: libdrm (Ubuntu)
   Status: New => Fix Released

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in libdrm source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in mesa source package in Focal:
  New

Bug description:
  [Impact]

  
  [Fix]


  [Test case]

  
  [Where things could go wrong]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940504] Re: Support Alder Lake P graphics

2021-08-19 Thread Timo Aaltonen
** Summary changed:

- Support Alder Lake P/M graphics
+ Support Alder Lake P graphics

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  New
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in libdrm source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in mesa source package in Focal:
  New

Bug description:
  [Impact]

  
  [Fix]


  [Test case]

  
  [Where things could go wrong]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1940504] [NEW] Support Alder Lake P/M graphics

2021-08-19 Thread Timo Aaltonen
Public bug reported:

[Impact]


[Fix]


[Test case]


[Where things could go wrong]

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

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

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

** Affects: libdrm (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

Title:
  Support Alder Lake P/M graphics

Status in libdrm package in Ubuntu:
  New
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in libdrm source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in mesa source package in Focal:
  New

Bug description:
  [Impact]

  
  [Fix]


  [Test case]

  
  [Where things could go wrong]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

2021-08-19 Thread Timo Aaltonen
that would require a newer libepoxy

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

2021-08-19 Thread Timo Aaltonen
this bug was about iris, if you have some other issue that *requires
iris*, then file a new one

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.

2021-08-13 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [radeon] Horizontal lines of screen corruption after last update.

Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: D8N02UC#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+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 1894973] Re: Better default settings for MESA and GALIUM_HUD

2021-08-13 Thread Timo Aaltonen
** Package changed: mesa (Ubuntu) => ubuntu

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

Title:
  Better default settings for MESA and GALIUM_HUD

Status in Ubuntu:
  New

Bug description:
  I suggest to put these settings in ubuntu-gaming package or something
  similar

  GALLIUM_HUD_VISIBLE=false
  GALLIUM_HUD_TOGGLE_SIGNAL=10
  GALLIUM_HUD_PERIOD=0.1
  
GALLIUM_HUD=.x10.y200.h80.w300.c240.dfps;.x10.y300.h80.w300.c100cpu+GPU-load:100;.x10.y400.h80.w300requested-VRAM+VRAM-usage

  References:
  https://docs.mesa3d.org/envvars.html#gallium-environment-variables

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


  1   2   3   4   5   6   7   8   9   10   >