[Touch-packages] [Bug 1996494] Re: CVE-2022-2309: NULL Pointer Dereference allows attackers to cause a denial of service (or application crash)
Thanks a lot for the fixes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1996494 Title: CVE-2022-2309: NULL Pointer Dereference allows attackers to cause a denial of service (or application crash) Status in libxml2 package in Ubuntu: Fix Released Bug description: NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn’t be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered. Reference: https://ubuntu.com/security/CVE-2022-2309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1996494/+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 1823985] Re: isc-dhcp-server can't load leases file with apparmor enabled
[Expired for isc-dhcp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: isc-dhcp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1823985
Title:
isc-dhcp-server can't load leases file with apparmor enabled
Status in isc-dhcp package in Ubuntu:
Expired
Bug description:
I can't start isc-dhcp-server with apparmor enabled.
I set a custom leases file in the dhcpd.conf:
lease-file-name "/test/var/lib/dhcp/dhcpd.leases";
and created a custom apparmor profile for that in
/etc/apparmor.d/local/usr.sbin.dhcpd:
/test/var/lib/dhcp/dhcpd{,6}.leases* lrw,
But when I try to start I see the following errors from dhcpd:
Internet Systems Consortium DHCP Server 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Config file: /etc/dhcp/dhcpd.conf
Database file: /test/var/lib/dhcp/dhcpd.leases
PID file: /run/dhcp-server/dhcpd.pid
Can't open /test/var/lib/dhcp/dhcpd.leases for append.
If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging..
exiting.
And in the messages log I can see errors like this:
Apr 9 17:07:03.601 myhost dhcpd[27361]: Can't open
/test/var/lib/dhcp/dhcpd.leases for append.
Apr 9 17:07:03.601 myhost dhcpd[27361]:
Apr 9 17:07:03.601 myhost dhcpd[27361]: If you think you have received this
message due to a bug rather
Apr 9 17:07:03.601 myhost dhcpd[27361]: than a configuration issue please
read the section on submitting
Apr 9 17:07:03.601 myhost dhcpd[27361]: bugs on either our web page at
www.isc.org or in the README file
Apr 9 17:07:03.601 myhost dhcpd[27361]: before submitting a bug. These
pages explain the proper
Apr 9 17:07:03.601 myhost dhcpd[27361]: process and the information we find
helpful for debugging..
Apr 9 17:07:03.601 myhost dhcpd[27361]:
Apr 9 17:07:03.601 myhost dhcpd[27361]: exiting.
Apr 9 17:07:03.603 myhost kernel: audit: type=1400
audit(1554822423.596:221): apparmor="DENIED" operation="capable"
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1
capname="dac_override"
Apr 9 17:07:03.603 myhost kernel: audit: type=1400
audit(1554822423.596:221): apparmor="DENIED" operation="capable"
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1
capname="dac_override"
After disabling apparmor for dhcpd everything works as expected:
ln -s /etc/apparmor.d/usr.sbin.dhcpd /etc/apparmor.d/disable/
apparmor_parser -R /etc/apparmor.d/usr.sbin.dhcpd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1823985/+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 1916931] Re: omshell returns inconsistent results or segfaults
[Expired for isc-dhcp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: isc-dhcp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Expired Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+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 1989410] Re: Not able to connect to hotspot because of WPA2 WPA3 security
I have been facing same problem by hotspot on netplan.
And WPA is also not working.
Please see attached image.
but downgrade(wpasupplicant=2:2.9.0-21build1) is working.
This problem is just Ubuntu 22.
Please kindly fix this problem.
** Attachment added: "スクリーンショット 2022-12-12 10.44.14.png"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1989410/+attachment/5635317/+files/%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88%202022-12-12%2010.44.14.png
--
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/1989410
Title:
Not able to connect to hotspot because of WPA2 WPA3 security
Status in wpa package in Ubuntu:
New
Bug description:
Both security WPA2 and WPA3 displaying on the security section due to
this not able to connect the hotspot.
Same device and firmware working properly in ubuntu 20.04 OS, But in
ubuntu 22.04 we are facing this issue.
"nmcli dev wifi" on client side:
On Ubuntu 20.04:
IN-USE
SSID ubuntu_new_golden
MODE Infra
CHAN 1
RATE 130Mbit/s
SECURITY WPA2
On Ubuntu 22.04:
IN-USE
SSID ubuntu_new_golden
MODE Infra
CHAN 1
RATE 130Mbit/s
SECURITY WPA2 WPA3
Only difference we can see is SECURITY
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libwpa-client-dev 2:2.10-6ubuntu2
Uname: Linux 5.19.0-rpl-ww37bkc x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 15 12:23:41 2022
Dependencies:
InstallationDate: Installed on 2022-09-10 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1989410/+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 1998893] Re: NV reverse prime HDMI has no output
Verify on GAI5-DVT1.1-D9_202211-30857. Intel graphic ID [8086:a78b] 1. enable proposed 2. update mesa to 22.0.5-0ubuntu0.2 3. reboot 4. check the xorg log, that the glamoregl can be loaded successfully. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar
Thx for reviewing, uploading and the fix! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1998470 Title: re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: Triaged Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. https://launchpad.net/ubuntu/+source/zlib/+changelog The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar
Uploaded. One fix, you commented in debian/changelog about removing --crc32-vx from debian/rules, but didn't actually do so. So I made that change before uploading. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1998470 Title: re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: Triaged Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. https://launchpad.net/ubuntu/+source/zlib/+changelog The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
** Description changed: [Impact] - lima driver is missing from riscv64, but we also need to disable JIT - which then means using non-llvmpipe swrast. JIT for riscv64 is buggy and - should be fixed in a future llvm release. + lima driver is missing from riscv64, but in order to enable it we need + to disable anything that uses JIT on riscv64: swrast for vulkan, and + draw-use-llvm for gallium. + + JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -- 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/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: [Impact] lima driver is missing from riscv64, but in order to enable it we need to disable anything that uses JIT on riscv64: swrast for vulkan, and draw-use-llvm for gallium. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37
[Touch-packages] [Bug 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
** Description changed: + [Impact] + + lima driver is missing from riscv64, but we also need to disable JIT + which then means using non-llvmpipe swrast. JIT for riscv64 is buggy and + should be fixed in a future llvm release. + + [Test case] + + Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and + that it works. + + [Where things could go wrong] + + This is a new driver for the architecture, so there's little chance of + breakage. + + -- + "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -- 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/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: [Impact] lima driver is missing from riscv64, but we also need to disable JIT which then means using non-llvmpipe swrast. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37
[Touch-packages] [Bug 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
** Also affects: mesa (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) 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/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
vanvugt: any way to verify this 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+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 1998893] Re: NV reverse prime HDMI has no output
kchsieh: please verify this bugfix -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1999336] Re: New bugfix release 22.2.5
** Description changed: - WIP + [Impact] + + Update Mesa to the latest bugfix release of the 22.2.x series for + kinetic, and backport it to jammy for 22.04.2 image. + + diffstat: + 177 files changed, 2100 insertions(+), 617 deletions(-) + 191 commits + + [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. -- 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/1999336 Title: New bugfix release 22.2.5 Status in mesa package in Ubuntu: New Status in mesa source package in Kinetic: New Bug description: [Impact] Update Mesa to the latest bugfix release of the 22.2.x series for kinetic, and backport it to jammy for 22.04.2 image. diffstat: 177 files changed, 2100 insertions(+), 617 deletions(-) 191 commits [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/1999336/+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 1999336] [NEW] New bugfix release 22.2.5
Public bug reported: WIP ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Kinetic) 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/1999336 Title: New bugfix release 22.2.5 Status in mesa package in Ubuntu: New Status in mesa source package in Kinetic: New Bug description: WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1999336/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
** Also affects: spirv-headers (Ubuntu) Importance: Undecided Status: New ** Changed in: spirv-headers (Ubuntu) Status: New => Invalid ** Description changed: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 + spirv-headers + - needed by s-l-t-15 + spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap - Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building - [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: In Progress Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: New Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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
