[Desktop-packages] [Bug 2038811] Re: NetworkManager crashes when updating wpa-eap connections
Can we get proper SRU information on this bug? Thank you! ** Also affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Mantic) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2038811 Title: NetworkManager crashes when updating wpa-eap connections Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Triaged Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager. This problem was most recently seen with package version 1.44.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 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/netplan.io/+bug/2038811/+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 2062564] Re: [FFe] Seed pemmican
This is the final bits for raspi, shame the FFe is so late. That being said... we already had it during Beta so, +1. ** Changed in: pemmican (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged -- 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/2062564 Title: [FFe] Seed pemmican Status in pemmican package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Triaged Bug description: [ Impact ] Add pemmican to raspi server and desktop images in order that Pi 5 users can be notified if/when overcurrent or undervolt events occur (potentially resulting in brownout, data-corruption, and all manner of other symptoms typically caused as a result of undervolt). [ Test Plan ] On all supported models of Pi: * Boot the image with pemmican installed * Ensure boot proceeds normally with package installed and that no warnings appear On the Pi 5 specifically: * Boot the image normally * Ensure boot proceeds normally with package installed and that no warnings appear * Using bench power-supply to back-feed the Pi, lower voltage until brownout occurs * Reboot and ensure undervolt warning is shown * Shutdown and boot with PSU that cannot negotiate 5A * Ensure deficient PSU warning is shown On the Pi 5 desktop image specifically: * Boot desktop image * Attach USB load tester and raise current draw until USB ports fail * Ensure overcurrent warning is displayed [ Regression Potential ] Quite low given all the tests noted above have already been performed on all supported models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
** Changed in: mesa (Ubuntu Noble) Status: Fix Released => Triaged -- 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/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)
I have accepted the new mesa upload that should fix at least the vmware issues. -- 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/2061118 Title: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in open-vm-tools package in Ubuntu: Invalid Status in gtk4 source package in Noble: Triaged Status in mesa source package in Noble: Triaged Status in open-vm-tools source package in Noble: Invalid Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2060548] Re: [FFe] Update and seed wsl-pro-service in the WSL images
As per our earlier discussion, +1 on this. It's late but the risk is low and confidence is high. You can proceed. ** Changed in: wsl-pro-service (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged -- 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/2060548 Title: [FFe] Update and seed wsl-pro-service in the WSL images Status in ubuntu-meta package in Ubuntu: Triaged Status in wsl-pro-service package in Ubuntu: Triaged Bug description: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. It also fixes a vulnerability by depending on latest Go and latest x/net/http. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Hello Kai-Heng, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu6 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: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New 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] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu6 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: mutter (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 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 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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Hello Kai-Heng, 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-0ubuntu4 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: In Progress => 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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
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-0ubuntu4 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: In Progress => 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/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: In Progress 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 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 2037604] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Released Status in mesa source package in Jammy: Fix Released Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~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 2051068] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
Timo, can you verify this? -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~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 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release
If the impact on first-time start is acceptable by the server team (which seems to be the case), this looks like a reasonable ask. -- 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/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: New Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2042796] 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/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small Status in Mutter: Fix Released Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Bug description: [ Impact ] Touchscreen touches at the left or bottom edges (within 20px) of the screen are not treated as mouse clicks. Icons only get highlighted, not launched. [ Test Plan ] 0. Find a touchscreen. 1. Set Ubuntu Dock in Panel mode (the default mode) if not already. 2. Touch as close to the edge of the screen as possible. Aim for the gap between the icon and the edge of the screen. Expect: The app launch animation occurs for each tap. Icons aren't just highlighted. [ Where problems could occur ] Anywhere in touchscreen gesture tracking or even regular touchscreen usage. As this bug demonstrates, the former is able to interfere with even simple touchscreen actions. [ Workaround ] Size the Ubuntu Dock adequately large so it is unlikely the user will touch less than 20 pixels from the edge of the screen. [ Original description ] On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2040153] Update Released
The verification of the Stable Release Update for network-manager 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2040153 Title: Network Manager will not remove Netplan YAMLs when connections are deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: In Progress Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Fix Released Bug description: [ Impact ] Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete Network Manager connections persistently. That means that, when the connection is deliberately deleted by the user, it will re-appear when the system is rebooted or netplan apply is executed. This is happening because the systemd service unit is setting the property "ProtectSystem" to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. When connections are deleted, libnetplan will try to open its YAML files with writing permissions and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd so the Network Manager's daemon will be able to write to that directory. This upload also improves the autopkgtests related to Netplan. Network Manager will be started by systemd, which ensures we are testing in the same environment conditions used by a desktop installation. It also adds a few more instances of connections deletions so we can test a bit more that YAML files are being removed. It also adds all the dependencies required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). [ Test Plan ] Launch a new Mantic VM: $ lxc launch ubuntu:mantic --vm Install network-manager and ubuntu-settings: # apt install network-manager ubuntu-settings Run Netplan # netplan apply Create a dummy connection via nmcli: # nmcli con add type dummy connection.interface-name dummy0 Check a new YAML will be created in /etc/netplan Delete the connection with nmcli # nmcli con del dummy-dummy0 Check the YAML WAS NOT removed from /etc/netplan You will see the error below in the NetworkManager's journal netplan_delete_connection: Cannot write output state: Read-only file system Add the PPA containing the fix and run the same test described above # add-apt-repository ppa:danilogondolfo/network-manager # apt update # apt upgrade Check that the YAML will be created when the connection is added and deleted and the connection is removed. [ Where problems could occur ] As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager runs, we are not expecting any regression. As for the changes in the autopkgtest related to Netplan, they are passing on all architectures. Autopkgtests amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz ppc64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz s390x - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz armhf - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz [ Other Info ] --- Original description --- When a connection is deleted using any NM facility, libnetplan is failing to delete the YAML file. Because of that, the connection will be recreated when "netplan generate" runs again. This is probably being caused by a combination of two things. First, the NM's systemd unit has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When
[Desktop-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status
Hello Steve, or anyone else affected, Accepted network-manager into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.44.2-1ubuntu1.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- 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: network-manager (Ubuntu Mantic) Status: In Progress => 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: Fix Committed Status in network-manager source package in Mantic: Fix Committed Bug description: [ Impact ] * A failure to query nmcli will fail the network-manager.postinst maintainer script (using "set -e") * This will make the package installation/upgrade fail * The fix catches the error on "ORIG_NAME=$(nmcli --get-values connection.id con show "$UUID")" and skips the corresponding keyfile with a warning message [ Test Plan ] $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file [connection] id=aaaUPTOWN uuid=491fa5c8-68ef---dca422f5c262 type=wifi [wifi] ssid=aaaUPTOWN mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN* $ sudo nmcli con reload $ ls -la /etc/NetworkManager/system-connections/ total 32 drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./ drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../ -rw--- 1 root root 199 Oct 17 17:05 UPTOWN.guests -rw--- 1 root root 191 Oct 17 17:46 aaaUPTOWN # Install network-manager from proposed $ apt update && apt install -t mantic-proposed network-manager # version 1.44.2-1ubuntu1.1 # Verify you don't see an error like this, breaking the pkg install Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 # Verify you see a migration log like this and the package installation is successful: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to NetworkManager. Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan $ echo $? 0 # Verify the good profile got migrated, while the bad one remains: $ sudo grep -RH UPTOWN /etc/netplan/ /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml: "aaaUPTOWN": /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml: name: "aaaUPTOWN" /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: "aaaUPTOWN" $ ls -la /etc/NetworkManager/system-connections/ insgesamt 28 drwxr-xr-x 2 root root 12288 Okt 17 18:03 . drwxr-xr-x 7 root root 12288 Okt 17 17:46 .. -rw--- 1 root root 199 Okt 17 17:05 UPTOWN.guests [ Where problems could occur ] * This is touching NetworkManager's maintainer script * Breaking it could lead to a broken/unconfigured NetworkManager package * This could render a machine's networking unusable * It could break distribution upgrades on package install/configure failure [ Other Info ] * Linting was used to
[Desktop-packages] [Bug 2032812] Re: [FFe] libreoffice 7.6.x for mantic
Hey Rico! Do we have a rough estimation on when the 7.6.x of interest will be available? I'm usually not fond of giving +1's to blanket FFe's like this, as the timing also is very important to whether an FFe will be accepted or not. I would be generally okay with this, but if it gets too close to release, it would be a no. Do we know more? I see the rc in the PPA FTBFS on armhf. I'd prefer to defer decision until we have the release ready. ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- 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/2032812 Title: [FFe] libreoffice 7.6.x for mantic Status in libreoffice package in Ubuntu: Incomplete Bug description: Libreoffice releases are quite in sync with the Ubuntu release schedule and every Ubuntu release receives its new "major" update. This cycle there are a few issues. As precaution to prevent breaking the archive and blocking transitions the upload is delayed until further notice. Hereby I am asking for permission to upload libreoffice 7.6.x for 23.10/mantic when it is ready. The package will be prepared at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice- prereleases/+packages?field.name_filter=_filter=published_filter=mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2032812/+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 2027671] Re: [SRU] libreoffice 7.5.5 for lunar
Hello Rico, or anyone else affected, Accepted libreoffice into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.5-0ubuntu0.23.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- 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: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2027671 Title: [SRU] libreoffice 7.5.5 for lunar Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.5 is in its fifth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.5_release * Version 7.5.4 is currently released in lunar. For a list of fixed bugs compared to 7.5.4 see the list of bugs fixed in the release candidates of 7.5.5 (that's a total of 70 bugs): https://wiki.documentfoundation.org/Releases/7.5.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.5/RC2#List_of_fixed_bugs 7.5.5 RC2 is identical to the 7.5.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_75/1589/ * 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/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15016907/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230718_033443_f8aa9@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230714_103204_cba01@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230714_150913_425f2@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230714_061923_700ec@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230715_114537_85189@/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 minor release with a total of 70 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described
[Desktop-packages] [Bug 2020834] Proposed package removed from archive
The version of adsys in the proposed pocket of Kinetic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 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: Confirmed 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. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about this bug go to:
[Desktop-packages] [Bug 2020834] Proposed package removed from archive
The version of adsys in the proposed pocket of Kinetic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 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: Confirmed 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. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about this bug go to:
[Desktop-packages] [Bug 2020834] Proposed package removed from archive
The version of adsys in the proposed pocket of Kinetic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: adsys (Ubuntu Kinetic) Status: Fix Committed => Confirmed -- 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: Confirmed 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. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage
[Desktop-packages] [Bug 2020834] Proposed package removed from archive
The version of adsys in the proposed pocket of Kinetic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 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: Confirmed 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. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about this bug go to:
[Desktop-packages] [Bug 2023913] 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/2023913 Title: Release gnome-shell 42.9 to Jammy 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.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional 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 -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. WARNING --- Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+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] Re: Ubuntu Dock icons not clickable at the edge of the screen
I see this bug also affects gnome-shell-extension-ubuntu-dock, but in jammy-proposed I only see yaru-theme. Is the gnome-shell-extension- ubuntu-dock package needed for this to go forward? -- 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 Committed 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 2012978] Update Released
The verification of the Stable Release Update for gjs 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gjs source package in Kinetic: Won't Fix Bug description: [ Impact ] High Memory Usage 3.1gb in 2h after reboot [ Test case ] Run: env G_SLICE=always-malloc valgrind --leak-check=full \ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \ gjs -c "const GLib=imports.gi['GLib'];function leak(){const l=GLib.Variant['new']('i',1)};leak();imports.system.gc();" No leak should be detected Running more installed tests under valgrind should output no leaks (unless those caused by gobject-introspection): sudo apt install gjs-tests env GJS_DEBUG_TOPICS= valgrind --leak-check=full \ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \ /usr/libexec/installed-tests/gjs/minijasmine \ /usr/libexec/installed-tests/gjs/js/testGIMarshalling.js There may be only two leaks caused by gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one after a ObjectInstance::prop_setter_impl call (these are leaks in the test library that are expected with gobject-introspection 42, but fixed in later versions). env GJS_DEBUG_TOPICS= valgrind --leak-check=full \ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \ /usr/libexec/installed-tests/gjs/minijasmine \ /usr/libexec/installed-tests/gjs/js/testRegress.js No leak expected [ Regression potential ] Gjs applications (including gnome Shell) using GVariant may misbehave --- ProblemType: BugDistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 2023572] Update Released
The verification of the Stable Release Update for gjs 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of 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 Released 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 1991022] Update Released
The verification of the Stable Release Update for speech-dispatcher 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 speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Released Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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 1971984] Please test proposed package
Hello Ubucolors, or anyone else affected, Accepted pcsc-lite into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pcsc- lite/1.9.5-3ubuntu1 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 pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Fix Committed Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Please test proposed package
Hello Ubucolors, or anyone else affected, Accepted pcsc-lite into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pcsc- lite/1.9.9-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: pcsc-lite (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 pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Fix Committed Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Re: pcscd.socket is disabled after installation
Hello Ubucolors, or anyone else affected, Accepted pcsc-lite into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pcsc- lite/1.9.9-1ubuntu0.23.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- 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: pcsc-lite (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Changed in: pcsc-lite (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Fix Committed Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 2023746] Update Released
The verification of the Stable Release Update for modemmanager 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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
As I don't see anything actionable right now, and there's been no movement since my last ping, I'll remove the ubuntu-sponsors subscription. Please re-add that in case any additional sponsoring is needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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
Hello Matthias, or anyone else affected, Accepted appstream-glib into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/appstream- glib/0.7.16-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: appstream-glib (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed 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 firefox 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 1966413] Re: [SRU] --no-oem option is broken
The concern about people possibly relying on the old broken behavior of --no-oem is valid, but in this case I think the option itself is 'clear enough' in meaning that if anyone relied on --no-oem not doing anything, it's a bit on them. Accepted. -- 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/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/bin/ubuntu-drivers", line 376, in greet config.no_oem = install_oem_meta NameError: name 'install_oem_meta' is not defined ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-drivers-common
[Desktop-packages] [Bug 1966413] Please test proposed package
Hello eoli3n, or anyone else affected, Accepted ubuntu-drivers-common into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.6.2~0.22.04.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- 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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File
[Desktop-packages] [Bug 1966413] Re: [SRU] --no-oem option is broken
Hello eoli3n, or anyone else affected, Accepted ubuntu-drivers-common into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.7.1.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- 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: ubuntu-drivers-common (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Changed in: ubuntu-drivers-common (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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after
[Desktop-packages] [Bug 2014954] Proposed package upload rejected
An upload of libmbim to jammy-proposed has been rejected from the upload queue for the following reason: "Bug provides a newer SRU debdiff for this upload.". -- 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/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2020604] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Invalid Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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] Update Released
The verification of the Stable Release Update for appstream-glib 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 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: In Progress 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 firefox 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 2013235] 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/2013235 Title: Drag and Drop not working in Qt-Applications on Gnome 44 Status in Kdenlive: Invalid Status in Mutter: Fix Released Status in OpenShot Video Editor: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact == Drag and drop items within Qt applications not working since upgrade to Ubuntu Lunar developmental release. The items can be picked up then the cursor changed to the "forbid" sign and no further interaction to the app. Confirmed affected apps: 3d Slicer, Krita. Test Case = 1. Start from Ubuntu 23.04 (the default desktop not KDE or Kubuntu) 2. Open a terminal and run sudo apt install krita 3. Install the updated mutter packages then log out and log back in. 4. Run Krita 5. Click New File. Then click Create 6. Select the rectangle from the left sidebar. Draw a rectangle on the canvas. 7. In the menu, select Layer > New > Add Paint Layer 8. Select the ellipse/circle from the left sidebar. Draw an ellipse on the canvas. 9. In the right sidebar, drag Paint Layer 1 on top of Paint Layer 2 so that they switch places. This should work with the updated mutter packages but does not work with mutter 44.0 or mutter 44.1. What Could Go Wrong === This fix is included in the upstream mutter 44.2 release so see the master bug for that update: https://launchpad.net/bugs/2022951 To manage notifications about this bug go to: https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2022951] 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/2022951 Title: Update mutter to 44.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.2/NEWS This is basically a prerequisite for GNOME Shell 44.2 LP: #2022961 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 Other Info -- This also includes an update of the triple buffering patch to add one commit to fix a potential crash with resuming from suspend. That triple buffering patch is maintained in a targeted mutter 44 branch by Canonical Desktop engineer Daniel. I was unable to easily reproduce the crash so I didn't include LP: #2020652 in the SRU changelog. I dropped 2 patches to mark some tests as flaky since mutter seems to build reliably enough on Debian and Ubuntu without those patches. Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 44.2 to require mutter >= 44.2 (even though GNOME Shell 44.2 appears to run ok with Mutter 44.1). I believe the only way to make the dependency relationship work the other way (not allow Mutter 44.2 with GNOME Shell 44.1) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2022951/+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 2022889] 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/2022889 Title: [SRU] libreoffice 7.5.4 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Released Bug description: [Impact] * LibreOffice 7.5.4 is in its forth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.4_release * Version 7.5.3 is currently released in lunar. For a list of fixed bugs compared to 7.5.3 see the list of bugs fixed in the release candidates of 7.5.4 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_75/1460/ * 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/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14936260/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230605_142135_2b00f@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230605_113325_1478c@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230605_085103_17f17@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230605_092012_906e0@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230605_104011_2ff4a@/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 minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2022889/+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 2023417] Update Released
The verification of the Stable Release Update for nautilus 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well Test Case 2 --- 1. Install the update 2. Run pkill nautilus to ensure all open nautilus windows are closed 3. Open Nautilus 4. Click Ctrl+N to open a second Nautilus window 5. In the first Nautilus window, open the Preferences dialog. This dialog is modal to this window (can't be moved away from centered in the window). Close Preferences. Close this window. 6. In the second Nautilus window, open the Preferences dialog. The preferences dialog should be modal to the window (and it should not crash). https://gitlab.gnome.org/GNOME/nautilus/-/issues/2986 Test Case 3 --- 1. Install the update 2. Open a terminal and run sudo apt install gnome-sushi 3. Open Nautilus 4. Open the preferences dialog and turn on Expandable Folders in List View. Close the preferences dialog. 5. Press Ctrl+l to focus the address bar and enter /usr/share 6. Use the space bar to open the Sushi previewer on one of the folders 7. With the Sushi preview window open, use the down arrow keys to navigate down to other folders. Keep going down until you go beyond the first page of results in Nautilus. The main nautilus window should scroll down to show these results focused. https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1221 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires gtk4 4.10.4 (LP: #2023031) This update drops 4 cherry-picked patches that have been applied in the new release It also cherry-picks 3 patches from the stable gnome-44 branch (future nautilus 44.3). It also includes a patch included in 44.2 but dropped from 44.2.1 because it was not clear how long it would take for gtk4 4.10.4 to be released. But gtk 4.10.4 was released only a few hours later. https://gitlab.gnome.org/GNOME/nautilus/-/commit/e193b2ce5d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023417/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
Hello Laider, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.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. ** Tags added: verification-needed verification-needed-jammy -- 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/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1965208] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+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 1974293] Update Released
The verification of the Stable Release Update for gjs 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gjs source package in Kinetic: Won't Fix Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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 1983130] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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/1983130 Title: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Dash to dock hides when a right-click menu is closed, even if there's no need for it. [ Test case ] 1. From settings -> Appearance: Enable dock auto-hide 2. Open a window, ensuring the dock is visible 3. Right click on a dock icon, and then click outside the menu to close it 4. The dock should be visible again and not hide (unless is expected) [ Regression potential ] The dock does not hide after closing the menu if a window is below it --- Description: Ubuntu 22.04 LTS Release: 22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983130/+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 1992847] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+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 1979096] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released Bug description: [ Impact ] Search [ Test case ] 1. From settings: a. Enable non-fractional scaling of 200% b. Show the dock on the left side c. Enable dock auto-hide 2. Hit Super key and search for any result 3. Hitting Enter key or clicking on an application icon should launch it [ Regression potential ] App grid has wrong sizes or not properly visible --- The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: BugDistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 2017420] Update Released
The verification of the Stable Release Update for libheif 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 eog in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Released Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Is there anything that still needs to be done here? Are we waiting for backports to earlier series? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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
Also, since I don't know the adsys codebase, how does the automated testing story for it look like? Does it have a thorough test suite? Autopkgtests? -- 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 2012371] Re: [FFe] ubuntu-proxy-manager and adsys
This bug is mentioned from the adsys SRU .changes file but does not provide an SRU template. As this seems to reference a new feature (and new dependency), I would like to see this properly tested with a regression potential section filled in. Also, this upload seems to add a Suggests: ubuntu-proxy-manager for jammy but there is no ubuntu-proxy-manager in jammy (and no upload in the queue). ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: adsys (Ubuntu Jammy) Status: New => Incomplete -- 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/2012371 Title: [FFe] ubuntu-proxy-manager and adsys 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: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. Installing the ubuntu-proxy-manager package on its own has no impact to the system. To benefit from its functionality adsys has to be upgraded and correctly configured. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+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 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
Hello Marian, or anyone else affected, Accepted libheif into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libheif/1.14.2-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- 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: libheif (Ubuntu Lunar) Status: New => 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 eog in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Committed Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2020682] Re: Release adsys 0.12.0
Please see https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371 - please address the concerns written there before we proceed with this SRU. ** Changed in: adsys (Ubuntu Jammy) Status: New => Incomplete -- 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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
Resurrected the removed upload into bionic-proposed. After some discussion we decided not to remove autopkgtest regression fix uploads from -proposed for series that are transitioning to ESM as they might be useful as a base for any ESM follow up uploads. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code
[Desktop-packages] [Bug 1782984] Proposed package removed from archive
The version of libx11 in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Won't Fix Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at
[Desktop-packages] [Bug 1782984] Proposed package removed from archive
The version of libx11 in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Won't Fix Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at
[Desktop-packages] [Bug 1782984] Proposed package removed from archive
The version of libx11 in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Won't Fix Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at
[Desktop-packages] [Bug 1782984] Proposed package removed from archive
The version of libx11 in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. ** Changed in: libx11 (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Won't Fix Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and
[Desktop-packages] [Bug 1966413] Re: --no-oem option is broken
** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Status: New => Won't Fix -- 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/1966413 Title: --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: New Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: New Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File
[Desktop-packages] [Bug 1733321] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase
[Desktop-packages] [Bug 1733321] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase
[Desktop-packages] [Bug 1733321] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase
[Desktop-packages] [Bug 1733321] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase
[Desktop-packages] [Bug 1733321] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. ** Changed in: network-manager (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package
[Desktop-packages] [Bug 1733321] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase
[Desktop-packages] [Bug 1983794] Update Released
The verification of the Stable Release Update for libcanberra 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 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 Released 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 1983794] Re: Evolution not deleting autosave files
Seeing that kinetic will go EOL next month, I'll conditionally skip the requirement for kinetic to be verified before this can go out. Releasing. -- 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 Released 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 2019751] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell source package in Lunar: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released Bug description: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+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 2019994] Update Released
The verification of the Stable Release Update for gnome-calendar 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-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2019994 Title: Update gnome-calendar to 44.1 Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/44.1/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default in Ubuntu Desktop, Edubuntu, and Ubuntu Cinnamon. 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/2019994/+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 1973470] Update Released
The verification of the Stable Release Update for apport 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 xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: Fix Released Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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] Re: firefox deb not installed
Brian promised to update the description with the required SRU information. On this note I have accepted the upload into jammy- proposed. -- 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 Committed Bug 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 1992688] Re: firefox deb not installed
Hello Brian, or anyone else affected, Accepted ubuntu-meta into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.481.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. ** Tags added: verification-needed verification-needed-jammy -- 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 Committed Bug 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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
We have decided this is a zero-day SRU, we already tested it and we'll release it as-is. -- 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: In Progress 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 1987976] Re: firefox black window on wayland
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in Release Notes for Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976] Re: firefox black window on wayland
Gunnar, thanks for reporting on this bug. A quick question: since the original issue got reported in 2022 before kinetic release, what was the status for this in 22.10? Was this also broken there? It's important for us to know if this is a regression or not. Also, with a visible workaround (re-running firefox), my recommendation would be to release note it, and maybe only include it in case we will need to do a full respin of all desktop RC images for 23.04. -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 2009767] Please test proposed package
Hello Kai-Chuan, 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.4-2ubuntu1.7~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. -- 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/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher.
[Desktop-packages] [Bug 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
Unfortunate that this can't be fixed with a targetted fix. The good part is that we anyway do xorg-server MRE's for HWE stack updates for LTSes - and if Timo feels comfortable enough to sponsor this backport for jammy, that's already a good clue for me. ** Changed in: xorg-server (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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+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 2009481] Re: FFE: mesa 23.0.1
Shame 23.0.1 has no release notes so far, but I browsed through the changes in 23.0.0. Let's get this in - we need that for the Beta. ** Changed in: mesa (Ubuntu) Status: New => Triaged -- 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/2009481 Title: FFE: mesa 23.0.1 Status in mesa package in Ubuntu: Triaged Bug description: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. diffstat: git diff mesa-22.3.6..mesa-23.0.0 | diffstat | tail -1 2493 files changed, 710212 insertions(+), 170014 deletions(-) commits: git log1 mesa-22.3.6..mesa-23.0.0 | wc -l 3157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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 1993621] 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/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 2007331] 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2009481] Re: FFE: mesa 23.0.1
I think it makes sense to go with 23.0.1 indeed, we'll probably update it regardless. A bit unfortunate that this didn't happen earlier, but it's outside of our control. I'd still like to see the list of changes for 23.0.0 + 23.0.1, but let's consider this a pre-ACK for the FFe. -- 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/2009481 Title: FFE: mesa 23.0.1 Status in mesa package in Ubuntu: Incomplete Bug description: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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] Update Released
The verification of the Stable Release Update for metacity 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 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 Released 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 1990677] Update Released
The verification of the Stable Release Update for fonts-noto-color-emoji 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 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 Released 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 2002510] Update Released
The verification of the Stable Release Update for bbswitch 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 bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: Fix Released Status in bbswitch source package in Jammy: Fix Released Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
@mdeslaur yes, basically all stable-series daily builds always build with -proposed enabled. The reason for that is that we want people to be able to test proposed updates in images in case its needed for validation. We always enable -proposed for those as one of the steps *after* we release an LTS version. Devel series dailies however always build with -proposed *disabled*. Anyway, please give me a sign when this update is good to go. Can I safely release kinetic at least? Should this go to -security? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
Apparently since we switched to mozjs102, the jammy image builds FTBFS because mozjs102 is in universe. I see it's in main for all the other series so after a few checks I'll promote it to main in jammy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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] Update Released
The verification of the Stable Release Update for directx-headers 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 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 Released Status in libdrm source package in Jammy: Fix Released Status in llvm-toolchain-15 source package in Jammy: Fix Released Status in mesa source package in Jammy: Fix Released Status in spirv-headers source package in Jammy: Fix Released Status in spirv-llvm-translator-14 source package in Jammy: Fix Released Status in spirv-llvm-translator-15 source package in Jammy: Fix Released 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 2000423] Update Released
The verification of the Stable Release Update for gnome-control-center 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-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 Released 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 1995137] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: Fix Released Bug description: [Impact] lima driver is missing from riscv64, but in order to enable it we need to disable anything that uses JIT on riscv64: swrast for vulkan, and draw-use-llvm for gallium. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+subscriptions -- Mailing list: https://launchpad.net/~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 1999336] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1999336 Title: New bugfix release 22.2.5 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Kinetic: Fix Released Bug description: [Impact] Update Mesa to the latest bugfix release of the 22.2.x series for kinetic, and backport it to jammy for 22.04.2 image. diffstat: 177 files changed, 2100 insertions(+), 617 deletions(-) 191 commits [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1999336/+subscriptions -- Mailing list: https://launchpad.net/~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 1999098] Update Released
The verification of the Stable Release Update for glib2.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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1999098 Title: Update glib to 2.74.3 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Kinetic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/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 autopgktest 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 Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. 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 -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so they are functionally equivalent. Ubuntu 23.04 will get newer glib versions before 23.04 is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+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 1999100] Update Released
The verification of the Stable Release Update for gnome-characters 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-characters in Ubuntu. https://bugs.launchpad.net/bugs/1999100 Title: Update gnome-characters to 43.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Kinetic: Fix Released Bug description: NOTE TO SRU TEAM Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop and Ubuntu Budgie. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1999100/+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 2000551] Update Released
The verification of the Stable Release Update for language-selector 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 language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Released Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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] Re: libnl3 3.4.0 doesn't work with WCN3980
Hello Robert, or anyone else affected, Accepted libnl3 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnl3/3.4.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- 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: libnl3 (Ubuntu Focal) Status: New => 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 libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Committed 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 1991761] Re: Backport packages for 22.04.2 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/22.2.5-0ubuntu0.1~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 -- 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: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed 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: Fix Committed 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 2001911] Re: [SRU] libreoffice 7.4.4 for kinetic
Hello Rico, or anyone else affected, Accepted libreoffice into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.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: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2001911 Title: [SRU] libreoffice 7.4.4 for kinetic Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Kinetic: Fix Committed Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * Version 7.4.2 is currently released in kinetic and 7.4.3 in kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.4 (that's a total of 114 bugs): https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_74/1542/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/amd64/libr/libreoffice/20230106_232736_1d62c@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/arm64/libr/libreoffice/20230107_123110_dfe59@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/armhf/libr/libreoffice/20230107_140034_7d823@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/ppc64el/libr/libreoffice/20230107_011032_e9378@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/s390x/libr/libreoffice/20230112_013620_d1bce@/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 minor release with a total of 114 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * 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:
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-15 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-15/1:15.0.6-3~ubuntu0.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: llvm-toolchain-15 (Ubuntu Jammy) Status: In Progress => 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: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed 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: Fix Committed 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