[Desktop-packages] [Bug 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
Ok, this was introduced upstream somewhere between 2.36.0 (jammy release) and 2.44.0 (jammy-updates). webkit2gtk now detects whether gbm_bo_create_with_modifiers2 exists at build time; if so, it uses them. This is not a problem for the main archive, as the libgbm that mesa provides includes those symbols, but some proprietary drivers include their own libgbm (notably, here, the ARM MALI drivers) and this change has accidentally and silently broken the effective driver ABI for Ubuntu 22.04. In this case here it seems like it will be easy enough to patch the code to dynamically resolve gbm_bo_create_with_modifiers2 - the upstream code already has an implementation for where this is not available at build time. That's not an archive-wide solution, though. It's not *entirely* obvious to me whether this should be considered an SRU regression - I'm inclined to think so, but I don't hold that opinion strongly. I'll take the temperature of the SRU team on this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2063476 Title: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 Status in gnome-control-center package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Cannot run gnome-control-center due to missing symbol lookup. Please see the output of the console: ``` ubuntu@kria:~$ gnome-control-center -h gnome-control-center: symbol lookup error: /lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Thu Apr 25 16:57:26 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Yes, please make sure the flaky tests are marked as such in the autopkgtests. SRUs are not released until either the test passes or the package version is marked as badtest in the britney hints. (A retry has caused it to pass on armhf) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051738] [NEW] Suspend button does not respond to mouse click, only touchcreen
Public bug reported: So, this is pretty weird. In the Shell quick settings panel (the one accessed by clicking on the wifi/bluetooth/sound/battery part of the top bar), in the Shutdown submenu, the "Suspend" button - and *only* the Suspend button - does not respond to mouse clicks. I cannot use it to suspend the system with either the touchpad or an external mouse. The other buttons in that menu respond to mouse clicks, and the Suspend button responds when I use the touchscreen to tap it. I've attached a screencast in an attempt to demonstrate this (although it obviously doesn't show when I'm actually clicking the mouse). This behaviour has been going on for a while, at least the whole Mantic cycle, but maybe longer. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 09:21:31 2024 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-26 (949 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.2-0ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screencast of failing to click on the suspend button" https://bugs.launchpad.net/bugs/2051738/+attachment/5743692/+files/Screencast%20from%202024-01-31%2009-26-10.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051738 Title: Suspend button does not respond to mouse click, only touchcreen Status in gnome-shell package in Ubuntu: New Bug description: So, this is pretty weird. In the Shell quick settings panel (the one accessed by clicking on the wifi/bluetooth/sound/battery part of the top bar), in the Shutdown submenu, the "Suspend" button - and *only* the Suspend button - does not respond to mouse clicks. I cannot use it to suspend the system with either the touchpad or an external mouse. The other buttons in that menu respond to mouse clicks, and the Suspend button responds when I use the touchscreen to tap it. I've attached a screencast in an attempt to demonstrate this (although it obviously doesn't show when I'm actually clicking the mouse). This behaviour has been going on for a while, at least the whole Mantic cycle, but maybe longer. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 09:21:31 2024 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-26 (949 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.2-0ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
Hello Daniel, or anyone else affected, Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This is a regression introduced upstream in mutter 45.1 (8f27ebf8), although it only hurts the triple buffering patch so that's where it's fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Ah, jbicha had already retriggered the autopkgtests, and they now pass. Huzzah! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Status in evince source package in Jammy: Fix Released Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Retriggered the autopkgtest to use the correct apparmor version; let's see if that fixes things. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: Fix Committed Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
OOoooh, right. This is releasable, and has a sensible changelog, it's
just that LP isn't showing the full changes file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Fix Released
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
It seems that it's already been retried once in the main archive. I note
that your PPA builds *without* -proposed enabled, whereas the archive
will build *with* -proposed enabled - possibly this is why it fails in
the archive and succeeds in your PPA?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028082] Re: Update glib to 2.76.4
Hello Jeremy, or anyone else affected, Accepted glib2.0 into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.76.4-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030959] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: Fix Released Bug description: [ Impact ] Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur (giving the frame clock an opportunity to measure lower GPU usage). This is different to the recent bug fix that probably caused it: Bug 2023766: * only occurs when moving over animated GUIs. * never recovers or corrects itself. * was spatial jittering at full frame rate. * reduced the frame rate of the GUI below it. This bug: * only occurs when moving over non-animated GUIs. * does recover and correct itself. * is stuttering at seemingly half frame rate, but perfect spatially. * does not reduce the frame rate of the the GUI below. I think the reason we only see this in 42 (jammy) is because that predates the change in the triple buffering algorithm to scale based on "dynamic max render time" alone. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. [ Test Plan ] 1. Stress GNOME Shell maximally by repeatedly entering/leaving the overview and/or scrolling the app grid. 2. Stop suddenly and wiggle the mouse over some part of the desktop that DOES NOT respond to mouse movement. Such as the wallpaper or some blank grey space next to the app grid. Expect: The mouse cursor does not get stuck in half frame rate. [ Where problems could occur ] In desktop frame timing since the clutter frame clock is being changed. Although risk is minimal since we're just reverting to the pre-July state of that code. [ Other Info ] The patch being dropped was found to not really be required in GNOME 42: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/comments/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
gdm3 looks good to me, but I haven't accepted it yet as it depends on the gnome-settings-daemon patches and I think it's best to resolve those questions before accepting gdm3 into -proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: Incomplete Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
> Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. Do I read the gnome-settings-daemon patches correctly, and this actually just entirely drops support for auth via NSS? So the regression potential is that if someone has set up auth via a custom system nss database, this *will* break login for them? (Unrelatedly, patches like smartcard-Use-autopointers.patch and smartcard-manager-Use-mutex-auto-lockers-when-convenient.patch are the sort of refactoring patches that we prefer not to see in SRUs. I don't think they're a blocker, but they make reviewing more difficult) ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: Incomplete Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2034105] Update Released
The verification of the Stable Release Update for xserver-xorg-video- amdgpu has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: Fix Committed Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Released Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] appstream-glib can't handle em or code tags, breaking Flathub
Ooof, double oops. That's the *flatpak* version they've described, not
the appstream-glib version they've tested.
Nathan Teodosio: could you (or someone else) double-check that this is
fixed specifically by appstream-glib 0.7.16-1ubuntu2 in Focal?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/2023215
Title:
[SRU] appstream-glib can't handle em or code tags, breaking Flathub
Status in appstream-glib package in Ubuntu:
Fix Released
Status in appstream-glib source package in Focal:
Fix Committed
Status in appstream-glib source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* Currently, any application that is using modern AppStream metadata
containing / tags in their description, and that is still using the
deprecated appstream-glib will fail to parse this data.
* Unfortunately, this affects some high-visibility applications now, like
Flatpak, which are unable to perform proper searches. See
https://github.com/flatpak/flatpak/issues/5434 for reference.
* This kind of issue may potentially affect more tools as well.
[ Test Plan ]
1. Open a terminal and run
sudo apt install flatpak
2. Then run
flatpak remote-add --if-not-exists flathub
https://flathub.org/repo/flathub.flatpakrepo
3. Run
flatpak search meld
The broken output may look something like:
F: Failed to parse
/var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error
on line 1960 char 29: already set '
Organic Maps is a free Android & iOS offline maps app for travelers,
tourists, hikers, and cyclists.
It uses crowd-sourced OpenStreetMap data and is developed with love by
' and tried to replace with ' ('
No matches found
4. Install the updated appstream-glib packages.
5. Restart your computer then log back in.
6. Open a terminal and run
flatpak search meld
The working output looks something like
Name DescriptionApplication ID Version Branch
Remotes
Meld Compare and merge your files org.gnome.meld 3.22.0 stable
flathub
[ Where problems could occur ]
* The reverse-dependencies for appstream-glib in Ubuntu Jammy are:
flatpak-tests
unity
libmalcontent-ui-0-0
libappstream-glib-dev
gir1.2-appstreamglib-1.0
appstream-util
flatpak
* Flatpak should continue to work, and there should be no new errors
in GNOME/Unity.
[ Other Info ]
* None. Updating this should mainly help Flatpak users and should
have no ill effects on any other component of the OS.
* This issue was fixed upstream in appstream-glib 0.8.1 which is
available in Ubuntu 22.10 and newer releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/2023215/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] appstream-glib can't handle em or code tags, breaking Flathub
Oops! Looks like the last commenter meant to set this into the
verification-done state, rather than -failed, as they've got correct
output.
Fixing and releasing.
** Tags removed: verification-failed-focal verification-needed
** Tags added: verification-done-focal
** Tags removed: verification-done-focal
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/2023215
Title:
[SRU] appstream-glib can't handle em or code tags, breaking Flathub
Status in appstream-glib package in Ubuntu:
Fix Released
Status in appstream-glib source package in Focal:
Fix Committed
Status in appstream-glib source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* Currently, any application that is using modern AppStream metadata
containing / tags in their description, and that is still using the
deprecated appstream-glib will fail to parse this data.
* Unfortunately, this affects some high-visibility applications now, like
Flatpak, which are unable to perform proper searches. See
https://github.com/flatpak/flatpak/issues/5434 for reference.
* This kind of issue may potentially affect more tools as well.
[ Test Plan ]
1. Open a terminal and run
sudo apt install flatpak
2. Then run
flatpak remote-add --if-not-exists flathub
https://flathub.org/repo/flathub.flatpakrepo
3. Run
flatpak search meld
The broken output may look something like:
F: Failed to parse
/var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error
on line 1960 char 29: already set '
Organic Maps is a free Android & iOS offline maps app for travelers,
tourists, hikers, and cyclists.
It uses crowd-sourced OpenStreetMap data and is developed with love by
' and tried to replace with ' ('
No matches found
4. Install the updated appstream-glib packages.
5. Restart your computer then log back in.
6. Open a terminal and run
flatpak search meld
The working output looks something like
Name DescriptionApplication ID Version Branch
Remotes
Meld Compare and merge your files org.gnome.meld 3.22.0 stable
flathub
[ Where problems could occur ]
* The reverse-dependencies for appstream-glib in Ubuntu Jammy are:
flatpak-tests
unity
libmalcontent-ui-0-0
libappstream-glib-dev
gir1.2-appstreamglib-1.0
appstream-util
flatpak
* Flatpak should continue to work, and there should be no new errors
in GNOME/Unity.
[ Other Info ]
* None. Updating this should mainly help Flatpak users and should
have no ill effects on any other component of the OS.
* This issue was fixed upstream in appstream-glib 0.8.1 which is
available in Ubuntu 22.10 and newer releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/2023215/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
Hello Kai-Chuan, or anyone else affected, Accepted xserver-xorg-video-amdgpu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/22.0.0-1ubuntu0.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. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034105] Proposed package upload rejected
An upload of xserver-xorg-video-amdgpu to jammy-proposed has been rejected from the upload queue for the following reason: "This looks good, but you've included two slightly different versions of the patch? Please re-upload with just one :)". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966167] Update Released
The verification of the Stable Release Update for yaru-theme has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Released Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979037] Update Released
The verification of the Stable Release Update for yaru-theme has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979037 Title: Monitor numbers are almost invisible in an Ubuntu/Yaru session Status in Yaru Theme: New Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in yaru-theme source package in Jammy: Fix Released Bug description: [ Impact ] Monitor numbers (displayed in the top left corner of each screen while in the Screen Display settings) are almost invisible in an Ubuntu/Yaru session. But they are big and bold in a GNOME (Adwaita) session. Both using Wayland. [ Test case ] Run: env XDG_RUNTIME_DIR=/tmp/.test.runtime XDG_SESSION_TYPE=wayland \ MUTTER_DEBUG_NUM_DUMMY_MONITORS=2 \ GNOME_SHELL_SESSION_MODE=ubuntu \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode In the nested shell, open Settings, go to Display panel The display OSDs should properly show Now repeat on the Appearance panel too [ Regression potential ] Nothing really, other OSDs may have wrong theming, but it's basically impossible To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1979037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992688] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020834] Please test proposed package
Hello Matthew, or anyone else affected, Accepted adsys into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~20.04.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- 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 Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path.
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Hello Matthew, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04.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: adsys (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy ** Changed in: adsys (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Hello Matthew, or anyone else affected, Accepted adsys into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2ubuntu0.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: adsys (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: In Progress Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit
[Desktop-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2019212 Title: Backport packages for 22.04.3 HWE stack Status in mesa package in Ubuntu: Invalid Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) [Test case] Install the new mesa on various hw configs, check 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 23.0.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021948] Re: New bugfix release 23.0.4
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Lunar: Fix Committed Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [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/2021948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020682] Re: Release adsys 0.12.0
Now an ubuntu-release thread: https://lists.ubuntu.com/archives/ubuntu- release/2023-June/005650.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020682 Title: Release adsys 0.12.0 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Incomplete Status in adsys source package in Lunar: New Bug description: ADSys is part of the enterprise desktop offerings and customers are requesting the new version to be released for 22.04 LTS. [Impact] * ADSys depends on Go 1.20, so the golang-1.20 package must be backported to 22.04 as well. * The new version has some features that are heavily requested by enterprise customers running the LTS. [Test Plan] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5. AD user should be able to log in (https://github.com/ubuntu/adsys/wiki/2.-Prerequisites); 2. Install admx and adml files on your AD controller (https://github.com/ubuntu/adsys/wiki/3.-AD-Setup); 3. Configure some Group Policies in the AD server (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO); 4. Install ADSys, reboot the machine and login in as an AD user; 5. Ensure that the configuration done in the AD server is reflected on the Ubuntu machine; [Where problems could occur] * ADSys can prevent authentication of AD users if some policies can't be applied; * For local users, no impact will occur; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020682/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020682] Re: Release adsys 0.12.0
I see that we've done this sort of wholesale backport once before, but this doesn't seem like it falls under the "other safe cases" part of the SRU criteria: https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases It seems like this should have a more formal process? I don't see any special case documentation on the wiki, nor can I find it discussed on ubuntu-release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020682 Title: Release adsys 0.12.0 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Incomplete Status in adsys source package in Lunar: New Bug description: ADSys is part of the enterprise desktop offerings and customers are requesting the new version to be released for 22.04 LTS. [Impact] * ADSys depends on Go 1.20, so the golang-1.20 package must be backported to 22.04 as well. * The new version has some features that are heavily requested by enterprise customers running the LTS. [Test Plan] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5. AD user should be able to log in (https://github.com/ubuntu/adsys/wiki/2.-Prerequisites); 2. Install admx and adml files on your AD controller (https://github.com/ubuntu/adsys/wiki/3.-AD-Setup); 3. Configure some Group Policies in the AD server (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO); 4. Install ADSys, reboot the machine and login in as an AD user; 5. Ensure that the configuration done in the AD server is reflected on the Ubuntu machine; [Where problems could occur] * ADSys can prevent authentication of AD users if some policies can't be applied; * For local users, no impact will occur; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020682/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
Hello Angel, or anyone else affected, Accepted gnome-shell into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Committed Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020277] Re: Update gnome-shell to 44.1
Hello Jeremy, or anyone else affected, Accepted gnome-shell into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020277 Title: Update gnome-shell to 44.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Committed Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS It is also believed to fix at least one crash issue reported as LP: #2016007 but without a clear test case, that bug is not included in this SRU verification. Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) This update requires mutter 44.1 (LP: #2020225). This was done with bumped dependencies in debian/control. gnome-shell 44.1 could be run with mutter 44.1 but it led to build test failures. Also, mixing different versions of mutter & gnome-shell is not supported upstream. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1
While the discussion about the test plan is ongoing https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/58 I'm happy to accept this with the currently documented test plan and the test plans on all the associated bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
Hello Nathan, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012717] Re: GNOME 44 multi-monitor screen freeze when resuming from sleep
Hello Daniel, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] Using multiple monitors in a Wayland session, one or both may freeze when resuming from sleep. [ Test Plan ] 1. Log into a Wayland session. 2. Set up gnome-shell to span two monitors. 3. Wait for the monitors to sleep. 4. Wiggle the mouse to wake them. 5. Move the mouse between both monitors. 6. Verify that the mouse appears on both monitors and neither are frozen. [ Where problems could occur ] This fix affects frame scheduling so problems could always occur in the form of other screen freezes and frame rate issues. [ Original report ] Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed
Hello Daniel, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
Hello Tim, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Re: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04
Hello Daniel, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017137 Title: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1
Hello Jeremy, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015962] Proposed package upload rejected
An upload of ayatana-indicator-messages to lunar-proposed has been rejected from the upload queue for the following reason: "Rejecting from the queue as this is still missing SRU information, and that should notify someone who cares :). The diff itself looks fine, although the it now also needs fixing in mantic and the lunar upload needs a non- conflicting version number. Please feel free to reupload with those fixed.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015955] Re: gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listener() from meta_wayland_keyboard_set_focus() from meta_wayland_seat_set_input_focus()
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015955/+attachment/5663166/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015955 Title: gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listener() from meta_wayland_keyboard_set_focus() from meta_wayland_seat_set_input_focus() Status in mutter package in Ubuntu: Confirmed Bug description: GNOME Shell reliably crashes when I drag a (buggy) Wayland client from a scale-1 output to a scale-2 output. The client bug is: https://github.com/wez/wezterm/issues/2445#issuecomment-1502516313 - it will set (and commit) a buffer_scale of 2 while having a buffer with dimensions not a multiple of 2 committed in some circumstances. GNOME Shell (correctly) sends a protocol error, and disconnects the client. However, when dragging the window from a scale-1 output to a scale-2 output with the mouse, gnome-shell will kill the client with a protocol error, but then immediately crash. I've tested killing a gnome-text-editor client with SIGTERM while moving the window with the mouse, and that *doesn't* kill gnome shell, so this doesn't appear to be just a matter of a client disconnecting while their window is currently mouse-dragged. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.9+bcachefs.git20230406.7889026b-1.1-generic 6.2.9 Uname: Linux 6.2.9+bcachefs.git20230406.7889026b-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 14:17:29 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 GsettingsChanges: InstallationDate: Installed on 2021-11-02 (525 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/chris ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/home/chris/.cargo/bin/nu XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 () UpgradeStatus: Upgraded to lunar on 2022-11-17 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015543] Re: Update to the upstream 1.12.1 bugfix version
It looks like (for Jammy, at least) there is an in-archive consumer of libwpebackend-fdo-1.0-1 - cog. We need at least a minimal smoke test for SRU verification, and that should suffice. I don't have a Jammy system handy, and cog isn't in the archives post-Jammy - could someone please cook up a minimal test case using cog? ** Also affects: wpebackend-fdo (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: wpebackend-fdo (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpebackend-fdo in Ubuntu. https://bugs.launchpad.net/bugs/2015543 Title: Update to the upstream 1.12.1 bugfix version Status in wpebackend-fdo package in Ubuntu: Fix Released Status in wpebackend-fdo source package in Jammy: Incomplete Bug description: * Impact The update fixes memory handling issues which could potential have security implication. It was requested by the MIR team on https://bugs.launchpad.net/ubuntu/+source/wpebackend- fdo/+bug/1973033/comments/11 as we need to promote the package for incoming webkitgtk security updates Fedora issues an update on similar concern https://bodhi.fedoraproject.org/updates/FEDORA-2022-f98ab9f311 * Testcase Unfortunately it's not easy to test wpebackend-fdo since the project has no tests nor demo utility. The backend is used mostly by webkitgtk but the current archive version is built without that option. It is a requirement for newer webkitgtk series though and such for incoming security update (since newer webkitgtk series are rolled out as security updates) * Regression potential The changes are small fixes for memory management issues but if those were wrong then it could lead to rendering issues or crashes in webkitgtk clients once webkitgtk is build with libwpe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/2015543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016441] Re: Scrolling with the mouse wheel beyond the top or bottom causes gnome-control-center to exit
Aha! This *is* an artefact of something strange on my system; namely, I was starting gnome-control-center from a terminal emulator packaged as a snap; as such, it has a LD_LIBRARY_PATH specified, which was partially overriding library resolution. Weird that this manifests as the application cleanly exiting, but 路♀️ ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2016441 Title: Scrolling with the mouse wheel beyond the top or bottom causes gnome- control-center to exit Status in gnome-control-center package in Ubuntu: Invalid Bug description: Attempting to scroll with the scroll wheel beyond the bounds of the content (so, scrolling up when at the top or scrolling down when at the bottom of a list) causes gnome-control-center to exit cleanly (not crash) with exit code 1. There do not appear to be any interesting messages when running it from the command line, with --verbose: chris ~ gnome-control-center --verbose ♥ 10:37 10:37:36.4308 Gtk[103396]: WARNING: Unknown key gtk-button-images in /home/chris/.config/gtk-4.0/settings.ini 10:37:36.4309 Gtk[103396]: WARNING: Unknown key gtk-menu-images in /home/chris/.config/gtk-4.0/settings.ini 10:37:36.4310 Gtk[103396]: WARNING: Unknown key gtk-toolbar-style in /home/chris/.config/gtk-4.0/settings.ini ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.9+bcachefs.git20230406.7889026b-1.1-generic 6.2.9 Uname: Linux 6.2.9+bcachefs.git20230406.7889026b-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 17 10:33:23 2023 InstallationDate: Installed on 2021-11-02 (530 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2022-11-17 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016441] [NEW] Scrolling with the mouse wheel beyond the top or bottom causes gnome-control-center to exit
Public bug reported: Attempting to scroll with the scroll wheel beyond the bounds of the content (so, scrolling up when at the top or scrolling down when at the bottom of a list) causes gnome-control-center to exit cleanly (not crash) with exit code 1. There do not appear to be any interesting messages when running it from the command line, with --verbose: chris ~ gnome-control-center --verbose ♥ 10:37 10:37:36.4308 Gtk[103396]: WARNING: Unknown key gtk-button-images in /home/chris/.config/gtk-4.0/settings.ini 10:37:36.4309 Gtk[103396]: WARNING: Unknown key gtk-menu-images in /home/chris/.config/gtk-4.0/settings.ini 10:37:36.4310 Gtk[103396]: WARNING: Unknown key gtk-toolbar-style in /home/chris/.config/gtk-4.0/settings.ini ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.9+bcachefs.git20230406.7889026b-1.1-generic 6.2.9 Uname: Linux 6.2.9+bcachefs.git20230406.7889026b-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 17 10:33:23 2023 InstallationDate: Installed on 2021-11-02 (530 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2022-11-17 (150 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2016441 Title: Scrolling with the mouse wheel beyond the top or bottom causes gnome- control-center to exit Status in gnome-control-center package in Ubuntu: New Bug description: Attempting to scroll with the scroll wheel beyond the bounds of the content (so, scrolling up when at the top or scrolling down when at the bottom of a list) causes gnome-control-center to exit cleanly (not crash) with exit code 1. There do not appear to be any interesting messages when running it from the command line, with --verbose: chris ~ gnome-control-center --verbose ♥ 10:37 10:37:36.4308 Gtk[103396]: WARNING: Unknown key gtk-button-images in /home/chris/.config/gtk-4.0/settings.ini 10:37:36.4309 Gtk[103396]: WARNING: Unknown key gtk-menu-images in /home/chris/.config/gtk-4.0/settings.ini 10:37:36.4310 Gtk[103396]: WARNING: Unknown key gtk-toolbar-style in /home/chris/.config/gtk-4.0/settings.ini ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.9+bcachefs.git20230406.7889026b-1.1-generic 6.2.9 Uname: Linux 6.2.9+bcachefs.git20230406.7889026b-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 17 10:33:23 2023 InstallationDate: Installed on 2021-11-02 (530 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2022-11-17 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement
Hello Robert, or anyone else affected, Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.4-0ubuntu2 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: glib2.0 (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007746] Re: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver
Hello Mustafa, or anyone else affected, Accepted xorg-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.20.13-1ubuntu1~20.04.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: xorg-server (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2007746 Title: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: Fix Committed Bug description: [ Impact ] * Microsoft Azure NV-series instances with NVidia GRID drivers started to experience xserver crashes while following Microsoft's official guide to installing Nvidia drivers [1]. * Root cause analysis showed that it was due to having a device with BusID "PCI:0@:0:0", where domain id is >= 32767 while the hyperv_drm kernel module is loaded. * Removing either the BusID specification or unloading the hyperv_drm kernel module seems to fix the crash. * The crash is happening while X.server is trying to enumerate PCI devices. X.server dereferences a NULL pointer while trying to access to the PCI device info. * The reason why it only happens while the hyperv_drm kernel module is loaded is that the hyperv_drm module does not expose PCI hardware information since it's a virtual device. * The upstream patch [2] addresses the issue and it's confirmed that the xserver with the patch does not experience the crash. * Ubuntu Focal `xorg-server` package does not include the patch [2] at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6). [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 [ Test Plan ] Part (a) is quoted from Microsoft's official guide [1]. Part (a): * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU - e.g. `NV36adms A10` * Install updates, required tooling, and the desktop environment: - sudo apt-get update - sudo apt-get upgrade -y - sudo apt-get dist-upgrade -y - sudo apt-get install build-essential ubuntu-desktop -y - sudo apt-get install linux-azure -y * Disable nouveau kernel driver: # Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: blacklist nouveau blacklist lbm-nouveau * Reboot the VM, re-connect, and then stop X server: - sudo reboot # wait for the reboot, reconnect, and continue: - sudo systemctl stop lightdm.service * Download and install the NVidia GRID driver: - wget -O NVIDIA-Linux-x86_64-grid.run https://go.microsoft.com/fwlink/?linkid=874272 - chmod +x NVIDIA-Linux-x86_64-grid.run - sudo ./NVIDIA-Linux-x86_64-grid.run - # When the setup asks whether you want to run the nvidia-xconfig utility to update your X configuration file, select Yes. * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf - sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf * Edit /etc/nvidia/grid.conf - sudo nano /etc/nvidia/grid.conf # Append the following lines: IgnoreSP=FALSE EnableUI=FALSE # Remove this line if present: FeatureType=0 # And save. * Reboot the VM Part (b): * Ensure that the hyperv_drm kernel module is loaded: - sudo modprobe hyperv_drm * Use the attached xorg.conf file to override /etc/X11/xorg.conf file * try to start the `xserver`: - sudo startx *
[Desktop-packages] [Bug 2002926] Update Released
The verification of the Stable Release Update for vte2.91 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/2002926 Title: GNOME Console doesn't copy last line Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Kinetic: Fix Released Bug description: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2002926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Can anyone do the verification for kinetic? Releasing this for 22.04 is
blocked waiting on successful testing for 22.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006756] Update Released
The verification of the Stable Release Update for pango1.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Released Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003335] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2003335 Title: [SRU] libreoffice 7.3.7 updates for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 https://wiki.documentfoundation.org/ReleasePlan/7.3 * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) https://bugs.documentfoundation.org/show_bug.cgi?id=150011 * Fix bug in copying table where we need to create a primary key * Don’t set language to none on defined styles (tdf#126657, tdf#145104) https://bugs.documentfoundation.org/show_bug.cgi?id=126657 https://bugs.documentfoundation.org/show_bug.cgi?id=145104 [ * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) https://bugs.documentfoundation.org/show_bug.cgi?id=150682 DROPPED from this SRU ] [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/amd64/libr/libreoffice/20230118_041112_1de9d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/arm64/libr/libreoffice/20230117_123847_1a3af@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/armhf/libr/libreoffice/20230117_105914_aa586@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/ppc64el/libr/libreoffice/20230117_111546_c7e43@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/s390x/libr/libreoffice/20230117_150924_08154@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950282] Update Released
The verification of the Stable Release Update for libmbim has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2003176] Please test proposed package
Hello Mustafa, or anyone else affected, Accepted metacity into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/metacity/1:3.44.0-1ubuntu1 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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: Fix Committed Status in metacity source package in Jammy: Fix Committed Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Hello Mustafa, or anyone else affected, Accepted metacity into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/metacity/1:3.36.1-1ubuntu1 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: metacity (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: metacity (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: Fix Committed Status in metacity source package in Jammy: Fix Committed Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003335] Re: [SRU] libreoffice 7.3.7 updates for jammy
Hello Rico, or anyone else affected, Accepted libreoffice into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.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: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2003335 Title: [SRU] libreoffice 7.3.7 updates for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 https://wiki.documentfoundation.org/ReleasePlan/7.3 * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) https://bugs.documentfoundation.org/show_bug.cgi?id=150011 * Fix bug in copying table where we need to create a primary key * Don’t set language to none on defined styles (tdf#126657, tdf#145104) https://bugs.documentfoundation.org/show_bug.cgi?id=126657 https://bugs.documentfoundation.org/show_bug.cgi?id=145104 [ * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) https://bugs.documentfoundation.org/show_bug.cgi?id=150682 DROPPED from this SRU ] [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/amd64/libr/libreoffice/20230118_041112_1de9d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/arm64/libr/libreoffice/20230117_123847_1a3af@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/armhf/libr/libreoffice/20230117_105914_aa586@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/ppc64el/libr/libreoffice/20230117_111546_c7e43@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/s390x/libr/libreoffice/20230117_150924_08154@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1999008] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/ubuntu/+source/xorg-server/+bug/1999008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Looks like the DEP8 test is flaky; it has failed with previous non-xorg- server packages as well, and I've just retried it and it has passed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/ubuntu/+source/xorg-server/+bug/1999008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003335] Re: [SRU] libreoffice 7.3.7 updates for jammy
Is there a way to make the the shortcut change only apply on layouts where this is a problem? I think this is close enough to deliberately introducing a regression (“my keyboard shortcut doesn't work anymore”) that it's inappropriate for an SRU as-is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2003335 Title: [SRU] libreoffice 7.3.7 updates for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 https://wiki.documentfoundation.org/ReleasePlan/7.3 * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) https://bugs.documentfoundation.org/show_bug.cgi?id=150011 * Fix bug in copying table where we need to create a primary key * Don’t set language to none on defined styles (tdf#126657, tdf#145104) https://bugs.documentfoundation.org/show_bug.cgi?id=126657 https://bugs.documentfoundation.org/show_bug.cgi?id=145104 * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) https://bugs.documentfoundation.org/show_bug.cgi?id=150682 [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/amd64/libr/libreoffice/20230118_041112_1de9d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/arm64/libr/libreoffice/20230117_123847_1a3af@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/armhf/libr/libreoffice/20230117_105914_aa586@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/ppc64el/libr/libreoffice/20230117_111546_c7e43@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/s390x/libr/libreoffice/20230117_150924_08154@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003335] Re: [SRU] libreoffice 7.3.7 updates for jammy
Mostly looks ok, but ubuntu-0001-tdf-150682-Change-shortcut-of- inserting-Math-objects.patch doesn't seem like an appropriate change for an SRU. By my understanding this will change the shortcut for "insert math object" on everyone's system. Is my understanding correct? If so, I think this behaviour change is inappropriate for an SRU. Additionally, the linked bug refers to the shortcut being problematic *on Windows*; is this actually a problem for Ubuntu users? Finally, ubuntu-0005-make-ValueTransfer-easier-to-understand.patch looks (from a brief skim) like a refactoring patch which is not expected to make any functional difference; is this the case? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2003335 Title: [SRU] libreoffice 7.3.7 updates for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 https://wiki.documentfoundation.org/ReleasePlan/7.3 * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) https://bugs.documentfoundation.org/show_bug.cgi?id=150011 * Fix bug in copying table where we need to create a primary key * Don’t set language to none on defined styles (tdf#126657, tdf#145104) https://bugs.documentfoundation.org/show_bug.cgi?id=126657 https://bugs.documentfoundation.org/show_bug.cgi?id=145104 * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) https://bugs.documentfoundation.org/show_bug.cgi?id=150682 [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/amd64/libr/libreoffice/20230118_041112_1de9d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/arm64/libr/libreoffice/20230117_123847_1a3af@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/armhf/libr/libreoffice/20230117_105914_aa586@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/ppc64el/libr/libreoffice/20230117_111546_c7e43@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/s390x/libr/libreoffice/20230117_150924_08154@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003833] Re: colord migration blocked by impossible depends on argyll
I'm not sure Argyll is going to be MIR-able; could we instead demote colord-sensor-argyll to universe? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/2003833 Title: colord migration blocked by impossible depends on argyll Status in colord package in Ubuntu: New Bug description: colord recently re-enabled argyll support. Unfortunately since argyll is in universe and colord is in main, this is causing an 'impossible depends' migration error for colord. colord-sensor-argyll/amd64 in main cannot depend on argyll in universe Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64 colord (1.4.6-2) unstable; urgency=medium * debian/control: - Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355) - Bump Standards-Version to 4.6.1 (no changes needed) * debian/rules: * debian/control: * debian/not-installed: - Re-enable Argyll support. Argyll no longer appears in danger of being removed from the archive. * debian/copyright: - Fix misspelling of Richard Hughes' name - Drop no-longer-necessary Files: stanzas - Include full license details of data/profiles -- Christopher James Halse Rogers Tue, 01 Nov 2022 11:02:35 +0100 There is a MIR for argyll (LP: #821883) which could be a solution for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2003833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
Hello Bram, or anyone else affected, Accepted fonts-noto-color-emoji into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts-noto-color- emoji/2.038-0ubuntu1 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: fonts-noto-color-emoji (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 This update requires the nototools update to be accepted as a build dependency LP: #1990681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998765] Update Released
The verification of the Stable Release Update for libnl3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Released Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Hello errors.ubuntu.com, or anyone else affected, Accepted xorg-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.6 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: xorg-server (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/ubuntu/+source/xorg-server/+bug/1999008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Hello errors.ubuntu.com, or anyone else affected, Accepted xorg-server into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: xorg-server (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Confirmed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/ubuntu/+source/xorg-server/+bug/1999008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000423] Re: "Alternate Characters Key" UI not reflecting current choice
Hello Gunnar, or anyone else affected, Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu0.22.04.6 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: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2000423 Title: "Alternate Characters Key" UI not reflecting current choice Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Status in gnome-control-center source package in Kinetic: Won't Fix Bug description: [ Impact ] When you set an "Alternate Characters Key", only two of the available options — "None" and "Right Alt" — are correctly reflected in the UI. If you select some of the other options, the UI tells you that "None" is selected. The xkb-options dconf value is correct, though. As an example: If I pick Right Ctrl, xkb-options is correctly changed to ['lv3:ralt_alt', 'lv3:switch']. So it looks like it parses lv3:ralt_alt instead of lv3:switch, and incorrectly concludes that the current value is "None". [ Test Plan ] * Install gnome-control-center from jammy-proposed. * Go to Settings -> Keyboard -> Alternate Characters Key and pick some other option but "None" or "Right Alt". * Make sure that the option you selected is correctly reflected in the UI. [ Where problems could occur ] This is a targeted fix which only affects a specific control in Settings. Considering the current broken state, I'd say that the risk is minimal that the change would make it worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2000423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
llvm-toolchain-15 will presumably need to be promoted to main in jammy- proposed/-updates, yes? I'm not familiar with the process of backporting NEW packages into main; presumably because it's in main in lunar that'll be ok, but I'd like to check with the MIR team that my assumption is correct. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Fix Committed 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: Fix Committed 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. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
Right, but as far as the archive is concerned, libdrm-tegra0 itself is unused :) What code *does* use libdrm-tegra0, and how sure are we that it doesn't use those symbols (even accidentally)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Fix Committed 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: Fix Committed 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. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
spirv-headers is build-depended on by several packages; could we do test-rebuilds of those as a part of verification, please. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Fix Committed 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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted spirv-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/spirv- headers/1.6.1+1.3.216.0-1~ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: spirv-headers (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Fix Committed 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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
I know it doesn't have any rdepends in the archive, but this includes a libdrm-tegra0 ABI break without bumping SONAME; what sort of consumers of libdrm-tegra0 are likely to exist? What risk mitigations could we implement? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted directx-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/directx- headers/1.606.4-1~ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: directx-headers (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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
Hello errors.ubuntu.com, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.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: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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) [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998893] Re: NV reverse prime HDMI has no output
Hello Kai-Chuan, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.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: mesa (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997360] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted libqmi into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.32.0-1ubuntu0.22.10.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: libmbim (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997360] Re: Update from git snapshot to stable 1.20
These seem reasonable, particularly if there's later HWE updates to be made. I assume the Cert lab has some of the hardware to test on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997360] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted libmbim into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.28.0-1~ubuntu22.10.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997360] Re: Update from git snapshot to stable 1.20
Hello Sebastien, or anyone else affected, Accepted modemmanager into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.10.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic ** Changed in: libqmi (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Kinetic: Fix Committed Status in libqmi source package in Kinetic: Fix Committed Status in modemmanager source package in Kinetic: Fix Committed Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998893] Re: NV reverse prime HDMI has no output
Is there a particular reason why we should take the PCI-ID removals? They seem safe enough, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998893] Proposed package upload rejected
An upload of mesa to jammy-proposed has been rejected from the upload queue for the following reason: "Looks like there's unintentional changes in src/mesa/formats.csv". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972977] Proposed package upload rejected
An upload of mesa to jammy-proposed has been rejected from the upload queue for the following reason: "Looks like there's unintentional changes in src/mesa/formats.csv". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/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: In Progress 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) [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Fix Released Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] 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-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985856] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985856 Title: Update Mutter to 42.5 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988625] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988625 Title: Left-over cursor visible on second screen Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. [ Test Plan ] 1. Set up a dual-monitor system using open source graphics drivers only. 2. Log into a Wayland session (usually just "Ubuntu"). 3. Wiggle the mouse between the two monitors. Expect: The mouse pointer never gets left behind and frozen on the previous monitor. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] This sounds like (Fix Released) #1724977, but seems to happen on extra screens. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: Fix Committed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gnome-shell source package in Kinetic: Fix Released Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993809] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993809 Title: Update gnome-shell to 42.5 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.4 Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- I also cherry-picked a fix from kinetic: gsettings org.gnome.settings-daemon.peripherals.mouse no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop trying to report customizations for that gsettings schema. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993308] Re: Update gnome-calendar to 43.1
Hello Jeremy, or anyone else affected, Accepted gnome-calendar into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- calendar/43.1-0ubuntu1 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-calendar (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 Status in gnome-calendar package in Ubuntu: Fix Committed Status in gnome-calendar source package in Kinetic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990456] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971632] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1971632 Title: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Jammy: Fix Released Bug description: * Impact On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. * Test case Connect a bluetooth headset to the computer, try to change the active profile. The selection should be reflected and the quality match, the pairing and service should be stable * Regression potential The changes are in the bluetooth a2dp/sbc functions so any potential regression would impact the connectivity with bluetooth devices using an a2dp profile (aptX, SBC, AAC). Check with different devices using the previously listed profiles. Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22
[Desktop-packages] [Bug 1987523] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1987523 Title: Pulsaudio crashes once BT microphone is connected Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Fix Released Bug description: * Impact When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. * Test case - Connect a bluetooth headset to the computer - Try to change the profile to HFP from the desktop settings or the pulseaudio cli -> the profile should get correctly selected, the service shouldn't crash * Regression potential The changes are in the functions handling mSBC packets which handle bluetooth HFP codecs, so any regression would concern bluetooth devices using that profile. --- When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: [51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at ../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). Aborting. Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash report... Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie Aug 24 13:44:24 p14s systemd[1]: Started crash report submission. Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: /var/lock/whoopsie/lock Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully. Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk I've identified the upstream fix for this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e I've built packages with the fix and can confirm that it does solve the problem. Packages are available at: https://launchpad.net/~ivoks/+archive/ubuntu/pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982330] Update Released
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1982330
Title:
Cannot apply policies from uppercase class path like "MACHINE"
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
Fix Committed
Status in adsys source package in Jammy:
Fix Committed
Bug description:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g.
Machine), but they are uppercase (e.g. MACHINE). This prevents any
GPOs from being applied.
This is a common occurence with GPOs created by Microsoft, like the
Default Domain Policy.
[Test Plan]
Reproduction:
* Mark the Default Domain Policy as active for the client, and set some
Ubuntu policy entries.
* Restart and/or manually sync the client machine.
* Observe the log message indicating that parsing the GPO failed:
Policy "Default Domain Policy" doesn't have any policy for class
"user" open
/var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol:
no such file or directory
* Observe that the Ubuntu policies were not applied.
To confirm the bug is fixed, repeat the steps above after applying the
fix, and the policies should be applied.
[Where problems could occur]
* Fixing this bug will allow adsys to parse, and possibly fail when
applying policies from an uppercase path, whereas before it silently
ignored them. Fixes for these potential bugs have also been submitted.
[Other Info]
The issue was initially reported on GitHub:
https://github.com/ubuntu/adsys/issues/346
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982330/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962170] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Tests are failing with the samba version in jammy. We want people using focal be able to upgrade to newer samba and still be compatible with adsys. [Test Plan] 1. Ensure that DEP8 tests are passing once uploaded to proposed and ready to be migrated [Where problems could occur] The functionalities failing are only on tests running (DEP8 or tests during package builds), but we want to be able to run our tests with newer versions of samba on focal too without regressing existing testsuite. -- The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961458] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1961458 Title: chown of script directory and contents Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Potential security issues in ApplyPolicy due to race when scripts are enabled. [Test Plan] 1. Attach your machine to Ubuntu Advantage to get script support. 2. Add a script to one GPO for user login/logout 3. Login as an user, starting a new user session (no session should be currently running for that given user). 4. Check the permissions are following what is described from the discussion below. [Where problems could occur] Script support was added recently, and it needs Ubuntu Advantage enablement to be activated. However, to this day, there is still no official ubuntu-advantage-desktop-daemon packaged on focal. ./internal/policies/scripts/scripts.go ApplyPolicy() unsafe owner changes: Changing the scripts directory owner allows any user processes to create symbolic links within, and then they can take ownership of any file on writable mounts. If the files must be owned by the user, the best way is to switch to the user's uid before creating the files. fchown(2) of the file descriptor before closing it should also work. I lose track of what's happening around the "Running machine startup scripts" -- it looks to me like adsys is also *executing* the scripts that were moments ago given to the user to modify. It is not safe for root to run user-owned files. Does the user *have* to own the directory and scripts? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962510] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Fix some flaky tests to ensure that future SRUs are easier to release [Test Plan] 1. Have the package build (tests are running) and that DEP8 tests are passing. [Where problems could occur] The fix is only impacting some tests that were flaky and asking for a rerun. Fixes are only located in this test code to make them more reliable and less racy, even in VM environments. - adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961459] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1961459 Title: adsys pam issues Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Memory leaks in adsys pam modules. [Test Plan] 1. Install SRU version of adsys 2. Login as an user 3. Ensure that you can still login successfully. [Where problems could occur] Login can be disabled due to the PAM module crashing. There is only one code path leading to that, so easy to detect. -- These may not be security issues but it's possible I overlooked something; since they live in a security boundary I thought it worth reporting with a bit of hassle. If you'd rather work on this in the open, feel free to open this. pam_adsys.c update_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to work but I don't think that's how that API is supposed to be used pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982342] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982342 Title: Cannot parse policies with empty values Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] In addition to empty data, some Microsoft policy entries happen to have empty values as well. See the following entry: // [key;value;type;size;data] : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. This fails hard when parsing, returning an `empty value` error, rendering the remaining policies unparsable. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not support policy entries with empty values, we must still be able to parse them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982343] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982343 Title: Cannot parse policy entries with unsupported types Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Policies with unsupported types are currently unable to be parsed. Even if Ubuntu doesn't support these types we should still be able to parse the Microsoft ones - otherwise we are unable to apply any of the GPOs. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu supports a limited subset of types, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982345] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982345 Title: Cannot parse policy entries with no data Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] The Default Domain Policy for Computers has a bunch of SystemCertificates keys with no data which adsys fails to parse. Here are some examples: Software\Policies\Microsoft\SystemCertificates\ACRS\Certificates Software\Policies\Microsoft\SystemCertificates\ACRS\CRLs Software\Policies\Microsoft\SystemCertificates\ACRS\CTLs Software\Policies\Microsoft\SystemCertificates\CA\Certificates Software\Policies\Microsoft\SystemCertificates\CA\CRLs Software\Policies\Microsoft\SystemCertificates\CA\CTLs Software\Policies\Microsoft\SystemCertificates\Disallowed\Certificates Software\Policies\Microsoft\SystemCertificates\Disallowed\CRLs Software\Policies\Microsoft\SystemCertificates\Disallowed\CTLs Software\Policies\Microsoft\SystemCertificates\DPNGRA\Certificates When examined with a hex editor, these look like the following: : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. The last field of the [key;value;type;size;data] stanza is entirely empty (semicolon succeeded immediately by a closing brace) whereas we expect a null character. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not have policy entries with no data, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy for Computers on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/384 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982351] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982348] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982348 Title: Describe if a key requires an Ubuntu Pro subscription Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Before applying policies, adsys checks for the existence of an Ubuntu Pro subscription. If not found, all keys with the exception of dconf keys are filtered, as they require Ubuntu Pro. Annotate the generated ADMX/ADML files with this information. [Test Plan] * Open the Group Policy Management Editor * Navigate to User Configuration > Administrative Templates > Ubuntu > Session Management > User Scripts > Logoff scripts * The description should contain the following line: An Ubuntu Pro subscription on the client is required to apply this policy. [Where problems could occur] This is a purely visual change that only impacts generated XML files. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982349] Update Released
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1982349
Title:
Manage energy profile settings
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
Fix Committed
Status in adsys source package in Jammy:
Fix Committed
Bug description:
[Impact]
Adsys cannot currently manage GSettings power management keys, such
as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
* Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
* Double click on the last entry: Whether to hibernate ...
* Enable it, set the value to "hibernate"
* On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
* Observe the logs that indicate the parsing of the dconf key:
DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
* Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
This code is located in the dconf policy application manager and
restricted to it. The negative impact in case of a new bug will be
seen by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982347] Update Released
The verification of the Stable Release Update for adsys has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982347 Title: Username is case sensitive when applying policies on login Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] Reproduction: * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases * Observe multiple files created at /var/cache/adsys/policies With the fix applied, remove *all* cached policies at /var/cache/adsys/policies and attempt to login with different case combinations of the AD account, e.g.: administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz As root, check the contents of /var/cache/adsys/policies - you should only see a lowercase entry: administra...@warthogs.biz [Where problems could occur] Target name normalization is exercised by the code that dumps policies applied for a given user, and by the code that updates or creates a policy for a given user. If this happens to cause a bug, it will render the core part of adsys unusable. We believe this is highly unlikely given that in some cases, adsys already used the lowercase variant of the username to apply and display policies. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990456] Re: xorg reports bogus 1600x1024 resolution
Hello Yao, or anyone else affected, Accepted xorg-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.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: xorg-server (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-515 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-515/515.65.01-0ubuntu0.20.04.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- 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: nvidia-graphics-drivers-515 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987038] Re: Fix slow refresh rate when AMD GPU screen in reverse prime mode
Hello Kai-Heng, or anyone else affected, Accepted xserver-xorg-video-amdgpu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/22.0.0-1ubuntu0.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: xserver-xorg-video-amdgpu (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1987038 Title: Fix slow refresh rate when AMD GPU screen in reverse prime mode Status in HWE Next: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Focal: Confirmed Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Status in xserver-xorg-video-amdgpu source package in Kinetic: Fix Released Bug description: [Impact] When AMD GPU is a GPU screen using reverse prime and its the only display, the fresh rate is very slow. [Fix] Enable present extension for GPU screen so it can be a viable CRTC to be selected. [Test] On a I+A laptop and external displays are routed to AMDGPU, disable internal display like closing lid can observe the issue. With the fix applied, the external display becomes very smooth. [Where problems could occur] I personally don't see why GPU screen can't use present extension, but this is Xorg so there might be some arcane reasons I didn't think of. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
