[Desktop-packages] [Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
I don't see a report so I presume this is OK to release? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020277] 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/2020277 Title: Update gnome-shell to 44.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Released Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS It is also believed to fix at least one crash issue reported as LP: #2016007 but without a clear test case, that bug is not included in this SRU verification. Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) This update requires mutter 44.1 (LP: #2020225). This was done with bumped dependencies in debian/control. gnome-shell 44.1 could be run with mutter 44.1 but it led to build test failures. Also, mixing different versions of mutter & gnome-shell is not supported upstream. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] 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/2020225 Title: Update mutter to 44.1 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.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] 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/2017137 Title: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] 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/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015861] 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/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] 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/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012717] 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/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Using multiple monitors in a Wayland session, one or both may freeze when resuming from sleep. [ Test Plan ] 1. Log into a Wayland session. 2. Set up gnome-shell to span two monitors. 3. Wait for the monitors to sleep. 4. Wiggle the mouse to wake them. 5. Move the mouse between both monitors. 6. Verify that the mouse appears on both monitors and neither are frozen. [ Where problems could occur ] This fix affects frame scheduling so problems could always occur in the form of other screen freezes and frame rate issues. [ Original report ] Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Incomplete Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
> Therefore, the crash is fixed even though there is still a remaining bug. Does this bug need reopening then, or a new bug filed? I leave that up to you - setting Incomplete for now since that's better than Fix Released and this being forgotten. ** Changed in: gnome-shell (Ubuntu Lunar) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Incomplete Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] Update to 0.7.18-2ubuntu0.1 for jammy
I think this should probably be fixed in SRUs together with bug 2006110 and verified together. See my comment 6 there for further comment. -- 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] Update to 0.7.18-2ubuntu0.1 for jammy Status in appstream-glib package in Ubuntu: New Status in appstream-glib source package in Jammy: New 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 ] * Run "flatpak search firefox" - Observe the failure. * Update to the patched version * Run "flatpak search firefox" again, it should work now. [ 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. 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 2006110] Re: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy
Just driving past while someone mentioned it and and trying to help this along. I suggest that you combine this with bug 2023215 and arrange a comprehensive Test Plan which verifies that both issues are fixed as well and that "normal" use cases (whatever they might be - I don't know) aren't regressed. You mentioned that Snaps use them, and we know that Snaps are default on Ubuntu - so it absolutely must be tested that Appstream behaviour hasn't regressed on Snaps as part of the Test Plan, surely? This bug also needs to explain what is actually broken from the user's perspective please - what noisy warning messages where? And the Test Plan should clearly verify that what you're trying to fix is actually fixed. Same for the other bug - rather than "observe the failure" please make it clear what the failure actually is, so somebody following the Test Plan can be confident that it's actually gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy Status in Flatpak: New Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Jammy: Triaged Bug description: The attached debdiff contains two targeted fixes to address noisy warning messages when AppStream is used with newer Flatpak versions. [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components. However, this fix has already been well-tested for over a year. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populated with data. [ Where problems could occur ] * If GNOME Software / KDE Discover still show all applications, everything should be fine, as this is the codepath this change touches. * `apt update` should not emit any warning messages from AppStream. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+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 2006110] Re: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy
Please also adjust the bug title to describe what the actual problem is that you're fixing. Depending on what that is, it may be appropriate to mark one bug as a dupe of the other (or not if they then describe obviously separate things). It's fine if they end up distinct but with a single Test Plan between them, if that's what makes sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy Status in Flatpak: New Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Jammy: Triaged Bug description: The attached debdiff contains two targeted fixes to address noisy warning messages when AppStream is used with newer Flatpak versions. [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components. However, this fix has already been well-tested for over a year. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populated with data. [ Where problems could occur ] * If GNOME Software / KDE Discover still show all applications, everything should be fine, as this is the codepath this change touches. * `apt update` should not emit any warning messages from AppStream. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
Thank you for the report. I noted this in https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter for future updates that rely on the exception. Would it be appropriate to add this Test Plan to future mutter updates that are based on the exception? If so, please could you amend the wiki? Thanks! -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 1970424] Proposed package upload rejected
An upload of gnome-session to jammy-proposed has been rejected from the upload queue for the following reason: "Questions in https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424 oustanding for two months". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1970424 Title: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Jammy: Incomplete Bug description: Impact -- Because ubuntu-desktop-minimal only recommends xdg-desktop-portal-gnome, it is easy for users to accidentally not have it installed. If it (Or another desktop portal backend are not installed), it breaks critical functionality for both the Firefox snap and Chromium snaps. It also breaks countless other snaps. Test Case - 1. ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome 2. It should be possible to uninstall xdg-desktop-portal-gnome and keep xdg-desktop-portal-gtk. (This allows someone to keep using GTK3 and avoid the libadwaita dialogs which may be easier for third party themes.) After installing or uninstall portal packages, you should log out and log back in to make sure the user services get stopped and started correctly. What Could Go Wrong --- This just adds an additional dependency. I believe the portal backends currently open by default in the locale sort order, so xdg-desktop-portal-gnome is preferred if installed, then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg- desktop-portal-wlr. Which coincidentally is the order we would want. How This Was Fixed -- ubuntu-desktop-minimal is a special germinate package and doesn't accept alternate dependencies. An alternate dependency is needed because we want to allow people to use a different portal backend and the easiest way to use a different portal backend is to install the backend you want and uninstall the ones you don't want. Therefore, we are handling this with a dependency in ubuntu-session. We are also doing this with gnome-session since that's a popular alternative for people who want a vanilla GNOME experience. Original Bug Report --- With ubuntu 22.04 firefox comes as snap package by default. it is not possible to open any file dialog. save graphics as, save html page, import certificate never opens a file dialog. firefox is completly useless without that file dialog. (the root case is ubuntu uses snap) further: in snap store firefox has no icon and it's called firefox not "Firefox". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424/+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 1987678] Proposed package upload rejected
An upload of jansson to jammy-proposed has been rejected from the upload queue for the following reason: "Questions in https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678 remain unresolved after many months". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Backport jansson 2.14 to jammy from kinetic Status in jansson package in Ubuntu: Fix Released Status in jansson source package in Jammy: Incomplete Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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] Re: SRU gjs 1.72.4 to jammy
** Description changed: [ 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 - Gjs applications (such as GNOME Maps, GNOME Characters, GNOME - Weather...) and GNOME Shell and its components and extensions should - continue working. + 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). -- 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 Committed 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 2023572] Re: SRU gjs 1.72.4 to jammy
This looks good. Accepting, but subject to test plan review. See https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/61?u=rbasak. It's probably worth waiting on SRU verification until the test plan is approved. ** Tags added: verification-needed verification-needed-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/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 Committed 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 2023572] Please test proposed package
Hello Marco, or anyone else affected, Accepted gjs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.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 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 Committed 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 2012978] Re: Memory leak
Hello Vladimir, or anyone else affected,
Accepted gjs into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.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: gjs (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 Committed
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 2024248] Re: Update gnome-remote-desktop to 42.8
Accepting, thanks. FTR, I think it's fine to have made improvements in testing without a separate SRU bug. I have reviewed this change and testing looks objectively better now. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024248 Title: Update gnome-remote-desktop to 42.8 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.8 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+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 2024248] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.8-0ubuntu0.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 gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024248 Title: Update gnome-remote-desktop to 42.8 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.8 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+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 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
I'm accepting as this question can be resolved after accept but before release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a 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/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+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 2024238] Re: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.8-0ubuntu0.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: gnome-remote-desktop (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024238 Title: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e097eda971e1f65f9170b00258037980eee90aca 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/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024238/+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 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
(and it's a current topic in the ubuntu-release@ thread, so sort of unresolved generally) ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a 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/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+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 2024240] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.8-0ubuntu0.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 gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a 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/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+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 2024197] Update Released
The verification of the Stable Release Update for gnome-remote-desktop 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-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024197 Title: Update gnome-remote-desktop to 44.2 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 44 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 23.04 release, 44.0: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/44.0...44.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
I think it's OK to skip Kinetic if you don't want to proceed with it. However, what are the implications of that severe regression for the QA process for other releases? Are there QA gaps that could also affect a release into Jammy, for example? Is it worth investigating the Kinetic failure further - not necessarily for the Kinetic release, but to consider if there are any implications that might cause a regression in Jammy? ** Tags added: regression-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. 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, an
[Desktop-packages] [Bug 2023571] 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/2023571 Title: Update to gjs 1.76.2 and SRU it Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Lunar: Fix Released Bug description: [ Impact ] There is a new bugfix release in the stable series associated with GNOME 44 https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.2/NEWS [ Test case ] Complete the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu (it is used by even GDM, the login screen). Smaller bugs could interrupt people's workflows. This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+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 2023766] Re: Mouse cursor stutters over GUI elements that are animated
Accepting into Jammy. I can see that the code changes appear already present in lunar-proposed. Please could you confirm the status of the fix in lunar-updates please, so we can avoid introducing a regression when users upgrade? On test plans, I see both this bug and the other one will be individually tested, but what's the plan to ensure that other behaviour in mutter isn't regressed? https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter exists, so would following that be appropriate, or do you want to do something else to verify this? ** Changed in: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2023766] Please test proposed package
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-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hello Fabio, 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-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Status in mutter source package in Lunar: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] When running GNOME on the Xdcv X11 server, changing the display scale in Settings and then clicking 'Revert Settings' instead of 'Keep Changes' does not revert the settings. [ Test Plan ] Very complicated; see comment #8. [ Where problems could occur ] In the list of available graphics modes in Xorg sessions on jammy only (an equivalent fix already exists in later Ubuntu releases). [ Original Description ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]:
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Releasing this to Jammy is blocked on understanding what happened with Kinetic. Not necessarily for the Kinetic release, but I think we should understand what happened first in case it has implications for Jammy. ** Tags removed: verification-done-focal verification-done-jammy verification-needed-kinetic ** Tags added: verification-failed-kinetic verification-needed-focal verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. 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 cha
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Thank you for the detailed analysis! So to make sure I understand: we think adsys 0.9.2 was broken in Kinetic all along due to some problem at the Kerberos end. You isolated this issue to outside adsys using ldbsearch. This issue with ldbsearch does not occur with Jammy. So you're confident that the problem isn't something that is being introduced by adsys. Is my understanding correct? If so then there might be implications for a standing SRU exception for adsys but not for this particular bugfix SRU in Jammy, so if you can confirm please then I think this fix can be released to Jammy and to Focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: 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 The
[Desktop-packages] [Bug 2024248] Re: Update gnome-remote-desktop to 42.9
Thank you for the verification jenhsun! There was also a plan to carry out testing as documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop. See the plan in the bug description above. Was this done? If so, please document that and flip the tag back. ** Tags removed: verification-done verification-done-jammy ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024248 Title: Update gnome-remote-desktop to 42.9 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.9 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+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 2028312] Re: does not support spec 1.5
Thank you for the report. It would be smoothest if upstream released a version with that change. I see that is requested in https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues/69 ** Bug watch added: Debian Bug tracker #1041654 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041654 ** Also affects: desktop-file-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041654 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues #69 https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues/69 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 Status in desktop-file-utils package in Ubuntu: New Status in desktop-file-utils package in Debian: Unknown Bug description: This package's code is a bit behind from the upstream code. In 2022, code was committed to support 1.5: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/56d220dd679c7c3a8f995a41a27a7d6f3df49dea When trying to validate .desktop files in Ubuntu that are running 1.5, I am getting errors. I am running Ubuntu 23.04 desktop-file-utils 0.26-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+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 2007379] Please test proposed package
Hello Gunnar, or anyone else affected, Accepted im-config into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/im- config/0.50-2ubuntu22.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 im-config in Ubuntu. https://bugs.launchpad.net/bugs/2007379 Title: Set GTK_IM_MODULE in Ubuntu on Xorg sessions Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Jammy: Fix Committed Status in im-config source package in Kinetic: Won't Fix Status in im-config package in Debian: Fix Released Bug description: [ Impact ] gnome-settings-daemon underwent a code refactoring before the release of version 42 as regards the IBus integration on x11. Initially there was the striking bug #1969637, but also with that one fixed, an issue due to the refactoring remains. These steps illustrate the problem: * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you only can input latin letters * Log out and log in again * Find that you now can input Chinese as expected The need for the last relogin is an inconvenience and a regression compared to how it worked before gnome-settings-daemon 42. The proposed upload makes im-config set the GTK_IM_MODULE variable to 'ibus' for Ubuntu on Xorg sessions, which makes it work as smoothly as it did previously. [ Test Plan ] * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Install im-config from jammy-proposed * Reboot and log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you instantly can input Chinese [ Where problems could occur ] This means that we — again — make im-config interfere with the IM configuration on GNOME desktops. Via bug #1893551 we kind of did the opposite in order to reduce the frequency of ibus crashes. But the situation now is different: - This is more narrow-scoped and limited to x11 - The upstream GNOME code has undergone significant changes - The measure is greenlighted by the upstream IBus maintainer (I think Fedora does it too) But with that said, I'm going to be attentive to the frequency of ibus crashes going forward. [ Other Info ] I prefer to skip kinetic for these reasons: - Not so much time left before EOL - Low importance - A jammy user with an IBus IM already set up, and who upgrades to kinetic, won't encounter a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/2007379/+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 2007379] Re: Set GTK_IM_MODULE in Ubuntu on Xorg sessions
Gunnar, I suspect you know more about this area than anyone else in Ubuntu at the moment. So accepting on the basis that you think it makes sense to make this change. I do agree that the bug is significant enough for SRU. But please could you expand the Test Plan to check for inadvertent regressions to unaffected users of Xorg? ** Changed in: im-config (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 im-config in Ubuntu. https://bugs.launchpad.net/bugs/2007379 Title: Set GTK_IM_MODULE in Ubuntu on Xorg sessions Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Jammy: Fix Committed Status in im-config source package in Kinetic: Won't Fix Status in im-config package in Debian: Fix Released Bug description: [ Impact ] gnome-settings-daemon underwent a code refactoring before the release of version 42 as regards the IBus integration on x11. Initially there was the striking bug #1969637, but also with that one fixed, an issue due to the refactoring remains. These steps illustrate the problem: * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you only can input latin letters * Log out and log in again * Find that you now can input Chinese as expected The need for the last relogin is an inconvenience and a regression compared to how it worked before gnome-settings-daemon 42. The proposed upload makes im-config set the GTK_IM_MODULE variable to 'ibus' for Ubuntu on Xorg sessions, which makes it work as smoothly as it did previously. [ Test Plan ] * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Install im-config from jammy-proposed * Reboot and log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you instantly can input Chinese [ Where problems could occur ] This means that we — again — make im-config interfere with the IM configuration on GNOME desktops. Via bug #1893551 we kind of did the opposite in order to reduce the frequency of ibus crashes. But the situation now is different: - This is more narrow-scoped and limited to x11 - The upstream GNOME code has undergone significant changes - The measure is greenlighted by the upstream IBus maintainer (I think Fedora does it too) But with that said, I'm going to be attentive to the frequency of ibus crashes going forward. [ Other Info ] I prefer to skip kinetic for these reasons: - Not so much time left before EOL - Low importance - A jammy user with an IBus IM already set up, and who upgrades to kinetic, won't encounter a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/2007379/+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 2011415] Re: /usr/bin/software-properties-gtk:AttributeError:on_pktask_finish:net_status_changed
Could you please confirm that this fix isn't relevant for releases after Focal - ie. that the necessary API exists in Jammy onwards? It may be that you implied this already, but the bug status isn't set separately and I can't find anything that states this unambiguously so I want to make sure it isn't being accidentally missed. ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Focal) Status: New => Incomplete ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2011415 Title: /usr/bin/software-properties- gtk:AttributeError:on_pktask_finish:net_status_changed Status in software-properties package in Ubuntu: Incomplete Status in software-properties source package in Focal: Incomplete Bug description: * Impact The change from the previous revision to handle connectivity change use an API not available on focal and trigger an exception * Test case - detach the system from ubuntu pro if it's attached - open software-properties - go the ubuntu pro tab - click on 'enable ubuntu pro' - while the dialog is open disconnect and reconnect the network - change the selection from manual token to PIN the UI should update and no error should be triggered Check also that the error reports stop for the new version (url referenced below) * Regression potential If the callback were not working as expected the UI could end up not responding to status change or not accepting the PIN or token entered, validate that the different methods still work as expected to register -- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.9.11, the problem page at https://errors.ubuntu.com/problem/22525c20f3bbf4ac03854d8a844e8d5f746b2959 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/software-properties/+bug/2011415/+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 1970424] Re: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome
> What Could Go Wrong Adding a dependency can cause unintended side effects. For example, users may now (directly or indirectly) pull in a package that conflicts with something else they have installed. Have you looked for these? Does the alternative provided definitely cover all cases? > I believe the portal backends currently open by default in the locale sort order, so xdg-desktop-portal-gnome is preferred if installed, then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg-desktop- portal-wlr. Which coincidentally is the order we would want. Could this therefore cause user behaviour to change as a higher priority backend is dropped in? Again, has this been analysed? It might all be fine, but these are the sorts of things that I think need documented analysis in the "What could go wrong" section. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1970424 Title: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Jammy: In Progress Bug description: Impact -- Because ubuntu-desktop-minimal only recommends xdg-desktop-portal-gnome, it is easy for users to accidentally not have it installed. If it (Or another desktop portal backend are not installed), it breaks critical functionality for both the Firefox snap and Chromium snaps. It also breaks countless other snaps. Test Case - 1. ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome 2. It should be possible to uninstall xdg-desktop-portal-gnome and keep xdg-desktop-portal-gtk. (This allows someone to keep using GTK3 and avoid the libadwaita dialogs which may be easier for third party themes.) After installing or uninstall portal packages, you should log out and log back in to make sure the user services get stopped and started correctly. What Could Go Wrong --- This just adds an additional dependency. I believe the portal backends currently open by default in the locale sort order, so xdg-desktop-portal-gnome is preferred if installed, then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg- desktop-portal-wlr. Which coincidentally is the order we would want. How This Was Fixed -- ubuntu-desktop-minimal is a special germinate package and doesn't accept alternate dependencies. An alternate dependency is needed because we want to allow people to use a different portal backend and the easiest way to use a different portal backend is to install the backend you want and uninstall the ones you don't want. Therefore, we are handling this with a dependency in ubuntu-session. We are also doing this with gnome-session since that's a popular alternative for people who want a vanilla GNOME experience. Original Bug Report --- With ubuntu 22.04 firefox comes as snap package by default. it is not possible to open any file dialog. save graphics as, save html page, import certificate never opens a file dialog. firefox is completly useless without that file dialog. (the root case is ubuntu uses snap) further: in snap store firefox has no icon and it's called firefox not "Firefox". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424/+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 1970424] Re: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome
Marking as Incomplete for the benefit of SRU reviewers. Please set back once my questions are answered. ** Changed in: gnome-session (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1970424 Title: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Jammy: Incomplete Bug description: Impact -- Because ubuntu-desktop-minimal only recommends xdg-desktop-portal-gnome, it is easy for users to accidentally not have it installed. If it (Or another desktop portal backend are not installed), it breaks critical functionality for both the Firefox snap and Chromium snaps. It also breaks countless other snaps. Test Case - 1. ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome 2. It should be possible to uninstall xdg-desktop-portal-gnome and keep xdg-desktop-portal-gtk. (This allows someone to keep using GTK3 and avoid the libadwaita dialogs which may be easier for third party themes.) After installing or uninstall portal packages, you should log out and log back in to make sure the user services get stopped and started correctly. What Could Go Wrong --- This just adds an additional dependency. I believe the portal backends currently open by default in the locale sort order, so xdg-desktop-portal-gnome is preferred if installed, then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg- desktop-portal-wlr. Which coincidentally is the order we would want. How This Was Fixed -- ubuntu-desktop-minimal is a special germinate package and doesn't accept alternate dependencies. An alternate dependency is needed because we want to allow people to use a different portal backend and the easiest way to use a different portal backend is to install the backend you want and uninstall the ones you don't want. Therefore, we are handling this with a dependency in ubuntu-session. We are also doing this with gnome-session since that's a popular alternative for people who want a vanilla GNOME experience. Original Bug Report --- With ubuntu 22.04 firefox comes as snap package by default. it is not possible to open any file dialog. save graphics as, save html page, import certificate never opens a file dialog. firefox is completly useless without that file dialog. (the root case is ubuntu uses snap) further: in snap store firefox has no icon and it's called firefox not "Firefox". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement
In the meantime, please could you confirm what [sorry, that's ambiguous; I mean *how*] you tested? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement
Thanks. I agree and I've added a hint. This should hopefully clear the flag on the next (Jammy) britney run. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011415] Re: /usr/bin/software-properties-gtk:AttributeError:on_pktask_finish:net_status_changed
> bug added by the previous revision Tagging regression-update then, FTR, for future regression risk analysis. > That fix isn't relevant for releases after Focal; The necessary API exists for Jammy onwards. OK thanks. Then the correct bug task status for Jammy onwards is Invalid or maybe Fix Released, so I'll change that. ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Invalid ** Tags added: regression-update ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2011415 Title: /usr/bin/software-properties- gtk:AttributeError:on_pktask_finish:net_status_changed Status in software-properties package in Ubuntu: Invalid Status in software-properties source package in Focal: Fix Committed Bug description: * Impact The change from the previous revision to handle connectivity change use an API not available on focal and trigger an exception * Test case - detach the system from ubuntu pro if it's attached - open software-properties - go the ubuntu pro tab - click on 'enable ubuntu pro' - while the dialog is open disconnect and reconnect the network - change the selection from manual token to PIN the UI should update and no error should be triggered Check also that the error reports stop for the new version (url referenced below) * Regression potential If the callback were not working as expected the UI could end up not responding to status change or not accepting the PIN or token entered, validate that the different methods still work as expected to register -- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.9.11, the problem page at https://errors.ubuntu.com/problem/22525c20f3bbf4ac03854d8a844e8d5f746b2959 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/software-properties/+bug/2011415/+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 2004475] 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/2004475 Title: Archive type selection drop-down in archive creation window is clipped Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: Fix Released Bug description: Impact -- (see LP: #2013338 for nautilus 42.6 SRU for jammy, which should fix this) When you try to change type of the archive that you'd like to create the drop-down list is clipped from the left, which contains most important information about the type that you try to select. At the same time archive creation window has a fixed size and cannot be resized. See screenshot. Upstream bug: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 Test Case - Log into "Ubuntu on Xorg". Run nautilus, right-click on any file or folder, and select Compress... In the newly opened Create Archive dialog, click on the file extension so that a popup menu is opened. The expected behaviour is that the popup would display correctly and in full. With this bug present, the popup appears clipped/cropped. To reproduce the bug, might need to set the screen resolution low, or enable Accessibility > Seeing > Large Text from gnome-control-center. -- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 16:40:30 2023 InstallationDate: Installed on 2020-11-24 (799 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2023-01-18 (14 days ago) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2004475/+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 2013338] 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/2013338 Title: Update nautilus to 42.6 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 42 series: https://gitlab.gnome.org/GNOME/nautilus/-/blob/42.6/NEWS 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 --- See the test case from LP: #2004475 and verify the bug is fixed with 42.6. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013338/+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 2058687] 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/2058687 Title: [SRU] libreoffice 7.6.6 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of 39 bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 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_76/1898/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/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 39 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: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+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 2059756] Re: [SRU] adsys 0.14.1
Currently the version of adsys in Mantic is 0.13.1ubuntu0.1, which is lower than the version in Jammy Unapproved. What's your plan for Mantic and/or users upgrading to Mantic please? -- 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/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Status in adsys source package in Mantic: Confirmed Status in golang-1.22 source package in Mantic: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will
[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1
OK, thanks. I guess we can review the Jammy upload for now then on the assumption that the Mantic upload won't have substantial changes until it arrives in the queue. -- 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/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Status in adsys source package in Mantic: Confirmed Status in golang-1.22 source package in Mantic: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled othe
[Desktop-packages] [Bug 2064656] Re: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` mul
From #ubuntu-release, Jeremy suggested that this needs doing before the language packs are generated for 24.04.1. ** Changed in: gsettings-desktop-schemas (Ubuntu Noble) Milestone: None => ubuntu-24.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2064656 Title: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT , ru_RU, Indonesian (id) and maybe other locales Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in gsettings-desktop-schemas source package in Noble: In Progress Bug description: Impact -- The systemd journal gets a lot of warnings about an incorrect translation for the default Ubuntu Desktop when used with certain languages including Georgian, Indonesian, Lithuanian, and Russian. This issue is much worse if someone has enabled the show Seconds option in the top bar clock. This issue is being fixed by packaging the new bugfix release of gsettings-desktop-schemas 46.1. There were only translation updates in this release. https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/compare/46.0...46.1 Test Case - 1. Open a terminal and run sudo apt install language-pack-gnome-lt 2. Close the terminal 3. Open the Settings app (gnome-control-center) 4. In the side bar, click System, then Date & Time. Turn on Seconds. 5. Close the Settings app. 6. Open the Language Support app. You can click Remind me later if you see a warning that says "The language support is not installed completely." 7. Drag Lietuvių to the top of the list. 8. Log out 9. Log back in. 10. Open a terminal and run journalctl -f. You should not see any of the clock-format warnings mentioned in the Original Bug Report below. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for gsettings-desktop-schemas. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Because gsettings-desktop-schemas is included in Ubuntu language packs, this issue is actually only fixed with a language pack update. Ubuntu currently only updates language packs shortly before Ubuntu LTS point releases. Therefore, we will need to push this update without being able to verify the Test Case first. Original Bug Report --- After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that gnome-shell was spamming errors at the rate of 12 lines every second: geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:19 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. My locale is lt_LT.UTF-8, but this issue appears also in ru_RU, id (Indonesian) and maybe other locales. This is caused by a mistaken translation of the quote characters in "'24h'" which is used as the default value for a particular gsettings key. Specifically, this translation: https://translations.launchpad.net/ubuntu/noble/+source/gsettings-desktop-schemas/+pots/gsettings-desktop-schemas/lt/232/
[Desktop-packages] [Bug 2072772] Re: The package is build without malcontent
Hello Sebastien, or anyone else affected, Accepted gnome-control-center into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:46.3-0ubuntu0.24.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2072772 Title: The package is build without malcontent Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Fix Committed Bug description: * Impact The package is currently built with malcontent disabled because the package was in universe. The corresponding MIR is now approved, including for Noble (lp: #1892456). The package got promoted in Oracular already. The malcontent library is needed to provide parental control integration with something OEM partners need (new regulations make the feature mandatory to sell new devices in France starting this summer, other countries are following) * Test case - log as an admin user - install malcontent-gui (we don't plan to install it by default due to depends issues but oem will) - create another non admin user (if there isn't already one existing) - start gnome-control-center - switcht to the users panel - select the other users in the right pane -> a 'parental control' entry should be displayed * Regression potential The option is just display an entry to start the malcontent-gui interface. A problem would only impact the users panel, if the patch was wrong it could be impact on the layout of that page or showing that item when it shouldn't * Other information We will need to promote the malcontent source and libmalcontent-0-0 binary. Since we can't promote things in release it means we will need to coordinate with an archive admin to copy the package in noble- updates and promote it there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+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 2064762] Re: Update gnome-control-center to 46.3
Hello Jeremy, or anyone else affected, Accepted gnome-control-center into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:46.3-0ubuntu0.24.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Noble) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2064762 Title: Update gnome-control-center to 46.3 Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Fix Committed Bug description: Impact -- There was a new bugfix release in the stable 46 series. https://gitlab.gnome.org/GNOME/gnome-control-center/-/compare/46.0...46.3 https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.3/NEWS Test Case 1 --- Install the update. Make sure that gnome-control-center continues to run well. Test Case 2 --- Install gnome-session Log out. Click your name on the login screen. Click the gear in the bottom right corner and choose GNOME. Finish logging in. Make sure that gnome-control-center continues to run well. This test case is because some of our Ubuntu customizations only show in the Ubuntu session, not other sessions like vanilla GNOME. Test Case 3 --- Open gnome-control-center Click the last item in the left sidebar named About Click Device Name. Type in a different name for your computer. Press Enter. The Rename Device dialog should close and your new computer name should take effect. Test Plan - We started drafting the corresponding testplan on https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeControlCenter We will use the SRU verification as an opportunity to complete the wikipage, documenting what was tested and setting a basis for the next updates What Could Go Wrong --- gnome-control-center is used by Ubuntu Desktop and Edubuntu. It is a critical app for viewing and changing a huge variety of settings for these desktops. gnome-control-center is part of GNOME Core and has a microrelease exception for Ubuntu stable release updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064762/+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 2077654] Re: Race condition on builders result in 100% fail rate
> +# Race condition may happen and the test fails. This only happens in
> Jammy containers.
> +# Disable the test for now.
> +return
I don't think it's appropriate to disable a test without an analysis
that considers what it was testing, how to mitigate the gap created by
disabling the test or an explanation of why it isn't necessary to run
the test.
We also need to make arrangements to ensure that a future SRU or
security update of this package will make the same mitigation.
In the lack of such an analysis or a proper fix, if it only sometimes
fails, wouldn't it be better to just retry a few times to land the SRU?
--
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/2077654
Title:
Race condition on builders result in 100% fail rate
Status in ubuntu-drivers-common package in Ubuntu:
New
Status in ubuntu-drivers-common source package in Jammy:
New
Bug description:
[ Impact ]
ADT testing fails on arm builders
[ Test Plan ]
Run ADT tests in PPA or locally with:
PYTHONPATH=. python3 tests/run
test_ubuntu_drivers.DetectTest.test_system_driver_packages_force_install_nvidia
The error message to look for is:
==
FAIL: test_system_driver_packages_force_install_nvidia
(test_ubuntu_drivers.DetectTest)
system_driver_packages() force install config points to an older version.
--
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/mock.py", line 1379, in patched
return func(*newargs, **newkeywargs)
File
"/home/ubuntu/ubuntu-drivers-common-0.9.6.2~0.22.04.6~ppa0/tests/test_ubuntu_drivers.py",
line 1479, in test_system_driver_packages_force_install_nvidia
self.assertFalse('nvidia-driver-510' in res_wrong_json)
AssertionError: True is not false
[ Where problems could occur ]
during ADT testing on builders
[ Other Info ]
Cause unknown. It sometimes fails when locally on x86 machine but only in
Jammy container. Jammy package ran in Noble container does not fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2077654/+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 2077646] Re: revert RLIMIT_NOFILE set and test
SRU review: it looks like the test being disabled was first introduced in 1:0.9.5.1 and was related to an FTBFS fix. However, it doesn't seem to be testing the actual payload, but its own test setup. I don't see a way that disabling this test would cause a false negative, so it appears to be a no-op from an SRU perpsective, so I'm allowing the change for SRU purposes. However, note that this isn't fixed in the development release, so you're diverging things here. -- 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/2077646 Title: revert RLIMIT_NOFILE set and test Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Jammy: New Status in ubuntu-drivers-common source package in Noble: New Status in ubuntu-drivers-common source package in Oracular: New Bug description: change to builder config in RLIMIT_NOFILE resulted in one of the tests to fail. The original value of 1024 is now changed to 65535. ADT test framework in u-d-c is intended to rise this value to 8180, but only if it was lower than that. Then it checks that the limit is set to 8180. After the change to the builder config, the tests fail because the value is higher than 8180, but the subsequent test is still performed. Testing framework became too dependent on builder's internal config. [ Impact ] ADT testing fails, resulting in package build failures in PPA [ Test Plan ] Run ADT tests at package build time, or locally with: PYTHONPATH=. python3 tests/run test_ubuntu_drivers The message that we are looking for is: == FAIL: test_max_open_file_descriptors (test_ubuntu_drivers.DetectTest) max_open_file_descriptors -- Traceback (most recent call last): File "/<>/tests/test_ubuntu_drivers.py", line 209, in test_max_open_file_descriptors self.assertEqual(soft, 8180) AssertionError: 65536 != 8180 [ Where problems could occur ] during ADT testing [ Other Info ] Caused by commit: commit 95ab52ae6a00f1cd75bd842486849c0bdb74c71c Author: Alberto Milone Date: Mon Mar 7 13:38:19 2022 +0100 Change maximum open files limit for the shell This patch is no longer needed and can be reverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2077646/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
From IRC (#ubuntu-release): 13:14 tjaalton: for bug 2060268, are there any cases where the udev rule would be triggered but is the wrong thing to do? How certain are we on that point? 13:14 tjaalton: presumably the Test Plan should specify testing on particular hardware? That needs adjusting. But also, because of the previous question, do we need to be testing on multiple hardware? 13:15 tjaalton: or maybe against multiple nvidia driver versions - we ship multiple, right? -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+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 2071877] Proposed package upload rejected
An upload of libmbim to noble-proposed has been rejected from the upload queue for the following reason: "Rejecting as agreed with @kchsieh, pending the full SRU.". -- 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/2071877 Title: Support sending AT commnad by mbim-cli for Compal WWAN module Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libmbim source package in Noble: Incomplete Bug description: [ Impact ] * Add a service to make mbim-cli be able to send AT command to Compal WWAN module DW5826e through mbimcli [ Test Plan ] * On the platform with Compal SDX12 WWAN module with ID: usb:v413Cp8217 usb:v413Cp8218 * Open terminal Ctrl + Alt + t * Try command $ sudo mbimcli -d /dev/cdc-wdm0 -p --compal-query-at-command=AT * Output: AT OK * Without the patch it will show error: Unknown options --compal-query-at-command=AT [ Where problems could occur ] * It adds new mbim service for supporting Compal module, there is no existing service modification. * The mbim relies on transaction task to handle sending AT command to the modem. It will send the command asynchronously, if there is a bug or system issue in GLib, the AT command may not send to modem successfully. [ Other Info ] * Upstream commit: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/commit/c275e4f1422291b933464880c37bd9cfd14b5bca To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2071877/+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 2077746] Re: GNOME Shell crashes when recording a session with fractional scaling and using a custom cursor
I'm rejecting two uploads for Noble because they collide between bug 2077746 and bug 2025006 (amongst others). Please coordinate and re- upload just one SRU at once (possibly squashing multiple fixes together as you wish). ** Changed in: mutter (Ubuntu Noble) Status: In Progress => Triaged -- 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/2077746 Title: GNOME Shell crashes when recording a session with fractional scaling and using a custom cursor Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Noble: Triaged Bug description: [ Impact ] When recording a session or sharing it, and a custom cursor is used, then GNOME Shell crashes as soon as the cursor is painted Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3978 [ Test case ] - Enable fractional scaling to something that is not an integer scaling (e.g. 150%, 175%...) - Start recording or sharing your session - E.g. Can use https://screenrecorderonline.net/ - Open this page (firefox) https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commit/ff3c8fbbc1d14 Hover on an image - Open GIMP and use the color picker in your screen - The custom cursor should show properly and gnome shell should record it without crashing [ Regression potential ] The cursor is not show or it has the wrong scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2077746/+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 2025006] Re: Monitor colour profile is randomly not applied
I'm rejecting two uploads for Noble because they collide between bug 2077746 and bug 2025006 (amongst others). Please coordinate and re- upload just one SRU at once (possibly squashing multiple fixes together as you wish). ** Changed in: mutter (Ubuntu Noble) Status: In Progress => Triaged -- 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/2025006 Title: Monitor colour profile is randomly not applied Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Noble: Triaged Status in mutter source package in Oracular: Fix Committed Bug description: [ Impact ] Colour profiles fail to apply at random times in Wayland sessions. Either when enabled in Settings>Color, or when logging into a new session. [ Workaround ] Switch VTs away and back to your login, usually with Ctrl+Alt+F3, Ctrl+Alt+F2. The correct colour profile is now more likely to be applied. [ Test Plan ] 1. Log into a Wayland session. 2. Open Settings > Color. 3. Select your primary monitor and 'Add profile'. 4. Add a whole-screen profile that will visibly change the screen like 'D50'. 5. Verify the new profile does not have the ⓘ icon next to it. 6. Repeatedly swap between enabling the new file, and enabling the old automatic profile. 7. Verify the screen colour temperature changes EVERY TIME that the ✓ check mark moves. [ Where problems could occur ] KMS property management in Wayland sessions has been redesigned for this fix, which includes colour management, night light, and hardware privacy screens. So there is a risk of unexpected behaviour in any of those features. Since KMS properties are applied atomically on most machines, this could also affect screen refresh performance. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2025006/+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 2077654] Re: Race condition on builders result in 100% fail rate
OK, but how does this relate to the upload in Jammy unapproved that
disables the test outright?
--
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/2077654
Title:
Race condition on builders result in 100% fail rate
Status in ubuntu-drivers-common package in Ubuntu:
New
Status in ubuntu-drivers-common source package in Jammy:
New
Bug description:
[ Impact ]
ADT testing fails on arm builders
[ Test Plan ]
Run ADT tests in PPA or locally with:
PYTHONPATH=. python3 tests/run
test_ubuntu_drivers.DetectTest.test_system_driver_packages_force_install_nvidia
The error message to look for is:
==
FAIL: test_system_driver_packages_force_install_nvidia
(test_ubuntu_drivers.DetectTest)
system_driver_packages() force install config points to an older version.
--
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/mock.py", line 1379, in patched
return func(*newargs, **newkeywargs)
File
"/home/ubuntu/ubuntu-drivers-common-0.9.6.2~0.22.04.6~ppa0/tests/test_ubuntu_drivers.py",
line 1479, in test_system_driver_packages_force_install_nvidia
self.assertFalse('nvidia-driver-510' in res_wrong_json)
AssertionError: True is not false
[ Where problems could occur ]
during ADT testing on builders
[ Other Info ]
Cause unknown. It sometimes fails when locally on x86 machine but only in
Jammy container. Jammy package ran in Noble container does not fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2077654/+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 2037274] 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/2037274 Title: [SRU] libreoffice 7.5.7 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.7 is in its seventh bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.7_release * Version 7.5.6 is currently released in lunar. For a list of fixed bugs compared to 7.5.6 see the list of bugs fixed in the release candidates of 7.5.7 (that's a total of 14 bugs): https://wiki.documentfoundation.org/Releases/7.5.7/RC1#List_of_fixed_bugs 7.5.7 RC1 is identical to the 7.5.7 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/1697/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15171690/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20230925_122613_dc43d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20230925_154920_2e924@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20230926_164913_a0855@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20230925_123824_567d4@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20230925_131148_33d08@/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 14 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: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274/+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 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
Thank you for contributing this fix! Could you please expand on the Test Plan? For manual testing, what are the exact steps that a user would perform, what results would indicate that the bug is present, and what results would indicate that the bug is fixed? For example, I don't see a command to run in https://github.com/qpdf/qpdf/issues/1050, or the expected results if the bug is fixed. For automated testing, you said the tests aren't included in the patch. Why not? Could we include them instead, and therefore increase confidence in the correctness of the fix? > qpdf has a rigorous test suite This is great, but is this test suite run as part of the package build and publication process in Ubuntu? If not, how could we arrange to run the test suite against the Ubuntu build of the package that includes this patch to ensure that we aren't regressing unaffected users in providing this update? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: New Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050 Corresponding debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Debian stable release approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 To manage notifications about this bug go to: https://bugs.launchpad.net/qpdf/+bug/2039804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lis
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
> The patch doesn't include the new test cases, but it does include all the old ones, which should demonstrate that there is no regression. OK, but doesn't that just leave a problem behind for the next person who tries to do an SRU to this package? Can't we just include the tests? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: New Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely goo
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
** Summary changed: - SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 + Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Hello Jay, or anyone else affected, Accepted qpdf into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qpdf/11.5.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: qpdf (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: qpdf (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: obje
[Desktop-packages] [Bug 2039804] Please test proposed package
Hello Jay, or anyone else affected, Accepted qpdf into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qpdf/11.3.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to fi
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Thank you for the discussion. On balance I think what you've said makes sense and it's not worth going further, but I think it's important to have the trade-offs and choices documented here and that's done now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Triaged Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rig
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
The development release isn't open yet. We will need to sync across from Debian when it opens. I am subscribed to this bug. Feel free to ping me here if it's not been done in a few weeks. ** Changed in: qpdf (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Triaged Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be repr
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
I understand that qpdf in Noble will auto-sync when Noble opens. ** Changed in: qpdf (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Committed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Could someone also test the proposed fix for Lunar please, and report the version tested? Otherwise releasing the fix for Jammy will result in users being regressed if upgrading from Jammy to Lunar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
> It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. It might be worth running a binary debdiff for SRU verification then, against the binary packages built in proposed, to ensure that the change only contains what we expect? ** Changed in: ubuntu-settings (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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: Fix Committed Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Please test proposed package
Hello Steve, or anyone else affected, Accepted ubuntu-settings into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/23.10.5.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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: Fix Committed Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2045043] 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/2045043 Title: Update fonts-noto-color-emoji for Unicode 15.1 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Released Status in fonts-noto-color-emoji source package in Mantic: 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.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle [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 LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. 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] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2045043/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
The removal of pptpd seems like something that should be release noted to me, to give enquiring users somewhere to refer to. ** 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 network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 1973084] Re: transmission-daemon high RAM usage
** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2045667] 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/2045667 Title: Update gnome-shell to 45.2 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.2/NEWS 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 -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045667/+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 2007702] Re: [SRU] Deb version numbering is misleading
Rejecting from the Unapproved queues as Steve's request above has not been addressed in over a month. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007702 Title: [SRU] Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Incomplete Status in chromium-browser source package in Jammy: Incomplete Status in chromium-browser source package in Lunar: Incomplete Status in chromium-browser source package in Mantic: Incomplete Bug description: [Impact] For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
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-0ubuntu7 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 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Mutter failed to build, only once, on jammy amd64: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. [ Test Plan ] Build mutter. [ Where problems could occur ] More build failures or accidentally depending on meson features that don't exist in jammy. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
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-0ubuntu7 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 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Mutter's test cases fail on jammy since Mesa got updated: mutter:cogl+cogl/conform / framebuffer-get-bits [ Test Plan ] Build mutter and run its tests (done automatically during packaging) [ Where problems could occur ] More tests fail. [ Other Info ] 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―
[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-0ubuntu7 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 removed: verification-done verification-failed-jammy ** Tags added: verification-needed 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-0ubuntu7 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 removed: verification-failed-jammy ** 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 (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058136] Re: Sync udisks2 2.10.1-6 (main) from Debian unstable (main)
Thank you for working on this! > Can I suggest ubuntu adds the debian delta as well as the ubuntu delta patch as part of this sync & merge Sorry, I don't follow. It looks like lp-2037569-skip- bd_part_get_disk_spec.patch is part of the Ubuntu delta uploaded in ubuntu1. A sync would drop this, but you tested a build that still includes it? If so, why are you requesting a sync? What am I missing? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2058136 Title: Sync udisks2 2.10.1-6 (main) from Debian unstable (main) Status in udisks2 package in Ubuntu: New Bug description: Please sync udisks2 2.10.1-6 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as it confuses GObject's type loading cache: "cannot register existing type 'UDisksDaemon'". (Patch also applied to Debian packaging git, can be synced next time). (LP: #2040488) * Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a device and that device has partitions. (LP: #2037569) * Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a device and that device has partitions. (LP: #2037569) The existing ubuntu noble-proposed FTBFS The -Wl, -Bsymbolic-functions is part of debian as per the -6 changelog entry I did a grab-merge of udisks then built with both the debian tests-Fix-targetcli_config.json.patch and the ubuntu lp-2037569-skip-bd_part_get_disk_spec.patch - using sbuild this successfully builds in noble-proposed. Can I suggest ubuntu adds the debian delta as well as the ubuntu delta patch as part of this sync & merge Changelog entries since current noble version 2.10.1-1ubuntu3: udisks2 (2.10.1-6) unstable; urgency=medium [ Martin Pitt ] * Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as it confuses GObject's type loading cache: "cannot register existing type 'UDisksDaemon'". Ubuntu enables this linker flag by default, no-op for Debian. (LP: #2040488) [ Michael Biebl ] * Drop python3-distutils Depends from debian/tests/control. No longer needed since 2.10.0. (Closes: #1065991) * Build-depend on pkgconf instead of pkg-config -- Michael Biebl Mon, 11 Mar 2024 23:19:45 +0100 udisks2 (2.10.1-5) unstable; urgency=medium * tests: Fix targetcli_config.json. Not all attributes are available anymore in newer kernel versions. -- Michael Biebl Wed, 10 Jan 2024 12:28:58 +0100 udisks2 (2.10.1-4) unstable; urgency=medium * Stop moving files from /usr/sbin to /sbin. With merged-/usr being mandatory, this is no longer necessary. -- Michael Biebl Mon, 27 Nov 2023 05:40:54 +0100 udisks2 (2.10.1-3) unstable; urgency=medium * Replace udev Build-Depends with systemd-dev. The new systemd-dev package ships udev.pc and systemd.pc which provides the paths for udevdir/systemdsystemunitdir/tmpfilesdir. -- Michael Biebl Mon, 20 Nov 2023 23:51:36 +0100 udisks2 (2.10.1-2) unstable; urgency=medium * Move systemd services files and udev rules to /usr. Add a corresponding versioned Build-Depends on debhelper (>= 13.11.6) to ensure we have a recent enough dh_installsystemd. -- Michael Biebl Sat, 21 Oct 2023 14:39:24 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2058136/+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 2003735] 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/2003735 Title: [SRU] libreoffice 7.4.4 updates for kinetic Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Fix Released Status in libreoffice source package in Lunar: Fix Released Bug description: [Impact] * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1 * It includes one crash fix for https://bugs.documentfoundation.org/show_bug.cgi?id=153059 https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1&id=ef02234e55c1ca0890b6882fb2d9a33328cbb88e * This SRU will cherry-pick this specific patch only. [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/1604/ * 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 * Test plan for this crash fix 1. Open a new writer document 2. Insert a page break 3. Go to page 1 and click on the header 4. Go to page 2 and click on the header button -> Crash [Regression Potential] * This is well defined and upstream tested patch to fix a specific crash. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2003735/+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 1987631] Re: Screencast only records one second
regression-updates based on duplicate report https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995358 ** Tags added: regression-update -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
@vanvugt what about pipewire in Jammy? Based on the duplicate report, isn't this a regression in Jammy? -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1996148] Please test proposed package
Hello Robie, or anyone else affected, Accepted pipewire into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pipewire/0.3.48-1ubuntu3 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. ** Package changed: gnome-shell (Ubuntu) => pipewire (Ubuntu) ** Changed in: pipewire (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1996148 Title: pipewire update to 0.3.48-1ubuntu2 resulted in regressions Status in pipewire package in Ubuntu: Invalid Status in pipewire source package in Jammy: Fix Committed Bug description: The SRU in bug 1985057 resulted in regression reports, including bug 1987631, currently marked as duplicates bug 1993912 and bug 1995358, and possibly bug 1994928. It's clear that we need to revert, but I don't want the metadata to close all of those regression bugs since it isn't clear that they will definitely be resolved with the revert. So this is a meta-bug to track the revert itself, to ensure that the original bug remains open after the revert lands. I will change Seb's upload to refer to this bug instead. Hopefully this is the most helpful arrangement to keep bug statuses and tooling clean and accurate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1996148/+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 1996148] [NEW] pipewire update to 0.3.48-1ubuntu2 resulted in regressions
Public bug reported: The SRU in bug 1985057 resulted in regression reports, including bug 1987631, currently marked as duplicates bug 1993912 and bug 1995358, and possibly bug 1994928. It's clear that we need to revert, but I don't want the metadata to close all of those regression bugs since it isn't clear that they will definitely be resolved with the revert. So this is a meta-bug to track the revert itself, to ensure that the original bug remains open after the revert lands. I will change Seb's upload to refer to this bug instead. Hopefully this is the most helpful arrangement to keep bug statuses and tooling clean and accurate. ** Affects: pipewire (Ubuntu) Importance: Undecided Status: Invalid ** Affects: pipewire (Ubuntu Jammy) Importance: Undecided Status: Fix Committed ** Tags: regression-update verification-needed verification-needed-jammy ** Tags added: regression-update ** Description changed: The SRU in bug 1985057 resulted in regression reports, including bug - 1987631, currently marked as duplicates bug 1993912 and 1995358, and + 1987631, currently marked as duplicates bug 1993912 and bug 1995358, and possibly bug 1994928. It's clear that we need to revert, but I don't want the metadata to close all of those regression bugs since it isn't clear that they will definitely be resolved with the revert. So this is a meta-bug to track the revert itself, to ensure that the original bug remains open after the revert lands. I will change Seb's upload to refer to this bug instead. Hopefully this is the most helpful arrangement to keep bug statuses and tooling clean and accurate. ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Invalid ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1996148 Title: pipewire update to 0.3.48-1ubuntu2 resulted in regressions Status in pipewire package in Ubuntu: Invalid Status in pipewire source package in Jammy: Fix Committed Bug description: The SRU in bug 1985057 resulted in regression reports, including bug 1987631, currently marked as duplicates bug 1993912 and bug 1995358, and possibly bug 1994928. It's clear that we need to revert, but I don't want the metadata to close all of those regression bugs since it isn't clear that they will definitely be resolved with the revert. So this is a meta-bug to track the revert itself, to ensure that the original bug remains open after the revert lands. I will change Seb's upload to refer to this bug instead. Hopefully this is the most helpful arrangement to keep bug statuses and tooling clean and accurate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1996148/+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 1985057] Re: Camera output freeze when using pipewiresrc
Thanks. I accepted the upload but changed the bug reference to point to bug 1996148 instead, since landing the revert shouldn't close this bug. I'll reopen this bug since the revert reverts it. ** Changed in: pipewire (Ubuntu Jammy) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1985057 Title: Camera output freeze when using pipewiresrc Status in OEM Priority Project: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in pipewire source package in Jammy: Triaged Bug description: [Impact] On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can reproduce it too. [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is in upstream from 0.3.52 to 0.3.56, and there is no regression found, so the risk is low. [Other Info] Upstream commits: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985057/+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 1987631] Re: Screencast only records one second
Possibly fixed in jammy-proposed with bug 1996148. If this fixes this for you, please let us know. -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987678] Re: Backport jansson 2.14 to jammy from kinetic
OK, so to make sure I understand: nothing in the archive is directly affected by this bug. But if a user builds their own thing with both jansson and json-c, then the symbol conflict arises. I think this is still fine in principle to SRU, but I would like your out-of-archive component (vvas) tested against the proposed pocket as part of the SRU verification please, and your confirmation that the problem is fixed, before we release it. Separately, above I asked: > On the specific fix, there is quite a bit of noise here. Did you consider cherry-picking the symbol versioning change only? I think this should be safe and not an ABI break, but I'm not that familiar in this area. Is there something I'm missing - why is a backport required instead? I think this question is still outstanding. Why can we not make the minimal necessary changes? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Backport jansson 2.14 to jammy from kinetic Status in jansson package in Ubuntu: Fix Released Status in jansson source package in Jammy: Incomplete Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1987678] Re: Backport jansson 2.14 to jammy from kinetic
> 3) the other minor changes in the new upstream release all seemed conservative fixes addressing simple issues that seemed LTS worthy (some even seemed to border on improving the security of some functions) The catch is that these changes then need individual review and consideration as to whether they are acceptable, including by the SRU team. The default is that we expect each change to be individually tested, too, unless the upstream meets the quality criteria detailed at https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases. Is this the case here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Backport jansson 2.14 to jammy from kinetic Status in jansson package in Ubuntu: Fix Released Status in jansson source package in Jammy: Incomplete Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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] Re: Update gnome-characters to 43.1
Thank you for the verification, and for leaving the note about glib2.0. I think this package is fine to release, but I believe it's blocked on the verification and autopkgtest failure analysis of glib2.0 in bug 1999098? Otherwise AIUI the package would become uninstallable? -- 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 Committed 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] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Thank you for working on this! What's the plan for Kinetic? Please see: https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases If the goal is to make Sinhala text more readable on Ubuntu, please could you make that an additional part of the Test Plan, instead of only checking the order of output in a font listing? I appreciate that would be subjective, but I think that with the screenshots given, asking someone who can read Sinhala to just verify it's a substantial improvement and matches expectations would be much better than not doing that at all. In working to fix this we should ensure that we've actually achieved the intended goal, rather than an intermediary technical step. > Where problems could occur It sounds like font metrics are changing, so text might wrap differently, resulting in it no longer fitting, or change the size of windows, etc, in various user interface elements. It sounds like it's worth the change, but please look out for this during testing. ** Changed in: language-selector (Ubuntu Jammy) Status: In Progress => Incomplete -- 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: Incomplete 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-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. [ 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. :) [ 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.launch
[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Thank you for the updates! It looks like you responded appropriately to all of my points, but I'd like to clarify one thing about version numbers and Kinetic. > If a user with an updated jammy (including this fix) upgrades to kinetic, they will still have version 0.219.1 of the language-selector-* packages, since the version string in kinetic is lower. So no regression. If you're not intending to fix Kinetic, then we'll need to use a different package version for Jammy. We generally avoid the version situation you describe, since that makes it difficult to reliably issue an update for users for the package in Kinetic. Consider if a security update were then required, for example. It would be possible to fix, but only if someone were to notice the unusual situation first. And it's confusing for Kinetic users to be on a different package version depending on whether or not they upgraded from Jammy or not. That situation means there are more combinations of interactions with other packages that might lead to different behaviours and different bugs. So we avoid it. Using a "compliant" version for the Jammy SRU, the original point about regressions on upgrade still stands, but see https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases for instructions and policy for this situation. It may still acceptable if you insist on not updating Kinetic. But we will want to adjust the version string for Jammy. -- 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: In Progress Status in language-selector source package in Kinetic: Won't Fix 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-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/th
[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Hello Aurora, or anyone else affected, Accepted language-selector into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/language- selector/0.219.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: language-selector (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic ** Changed in: language-selector (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 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 Committed 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 peo
[Desktop-packages] [Bug 2000551] Please test proposed package
Hello Aurora, or anyone else affected, Accepted language-selector into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/language- selector/0.219.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 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 Committed 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 detail
[Desktop-packages] [Bug 2077741] Re: No default background set for GNOME-Greeter
Accepting. I see that the change is scoped to "[org.gnome.desktop.background:GNOME-Greeter]" so I guess there's low likelyhood of impact outside that, but for testing, to what extent do we need to consider other flavours that use gnome-greeter? ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2077741 Title: No default background set for GNOME-Greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Committed Bug description: [ Impact ] While using Gnome-Initial-Setup launched from GDM (when no user > 1000 is present on the machine), no background is set on GNOME-Greeter, leading to a solid blue background wallpaper. Gnome-Initial-Setup is currently used on OEM shipped devices to provide a first user setup flow. We plan to also use it for a Raspberry Pi first user flow. We have received lots of feedback that the solid blue background is not in line with the Flutter installer and looks like an error occurred / the wallpaper failed to load. By updating /usr/share/glib-2.0/schemas/10_ubuntu- settings.gschema.override with: ``` # for GDM/DM # FIXME: move to :Ubuntu-Greeter once upstream supports this, see LP: #1788 [org.gnome.desktop.interface:GNOME-Greeter] gtk-theme = 'Yaru' icon-theme = 'Yaru' cursor-theme = 'Yaru' font-name = 'Ubuntu 11' monospace-font-name = 'Ubuntu Mono 13' font-antialiasing = 'rgba' [org.gnome.login-screen] logo='/usr/share/plymouth/ubuntu-logo.png' + [org.gnome.desktop.background:GNOME-Greeter] + picture-uri = 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + picture-uri-dark = 'file:///usr/share/backgrounds/ubuntu-wallpaper-d.png' + show-desktop-icons = false ``` I was able to add in one. This will help improve the GIS installer flow for Raspberry Pi we plan to support in 24.10 and the OEMs ubuntu-settings: Installed: 24.04.3 Ubuntu version: 24.04 LTS [ Test Plan ] To test this change, you can follow the test plan for Gnome-Initial- Setup up to the point where you have launched the GDM Gnome-Initial- Setup session and Gnome-Initial-Setup has appeared. You should see the default Ubuntu wallpaper, not a solid blue wallpaper, behind Gnome- Initial-Setup. https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup [ Where problems could occur ] If the path to the wallpaper is invalid, the session reverts to its blue background, returning to its current state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077741/+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 2077741] Please test proposed package
Hello Matthew, or anyone else affected, Accepted ubuntu-settings into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/24.04.5 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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-settings in Ubuntu. https://bugs.launchpad.net/bugs/2077741 Title: No default background set for GNOME-Greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Committed Bug description: [ Impact ] While using Gnome-Initial-Setup launched from GDM (when no user > 1000 is present on the machine), no background is set on GNOME-Greeter, leading to a solid blue background wallpaper. Gnome-Initial-Setup is currently used on OEM shipped devices to provide a first user setup flow. We plan to also use it for a Raspberry Pi first user flow. We have received lots of feedback that the solid blue background is not in line with the Flutter installer and looks like an error occurred / the wallpaper failed to load. By updating /usr/share/glib-2.0/schemas/10_ubuntu- settings.gschema.override with: ``` # for GDM/DM # FIXME: move to :Ubuntu-Greeter once upstream supports this, see LP: #1788 [org.gnome.desktop.interface:GNOME-Greeter] gtk-theme = 'Yaru' icon-theme = 'Yaru' cursor-theme = 'Yaru' font-name = 'Ubuntu 11' monospace-font-name = 'Ubuntu Mono 13' font-antialiasing = 'rgba' [org.gnome.login-screen] logo='/usr/share/plymouth/ubuntu-logo.png' + [org.gnome.desktop.background:GNOME-Greeter] + picture-uri = 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + picture-uri-dark = 'file:///usr/share/backgrounds/ubuntu-wallpaper-d.png' + show-desktop-icons = false ``` I was able to add in one. This will help improve the GIS installer flow for Raspberry Pi we plan to support in 24.10 and the OEMs ubuntu-settings: Installed: 24.04.3 Ubuntu version: 24.04 LTS [ Test Plan ] To test this change, you can follow the test plan for Gnome-Initial- Setup up to the point where you have launched the GDM Gnome-Initial- Setup session and Gnome-Initial-Setup has appeared. You should see the default Ubuntu wallpaper, not a solid blue wallpaper, behind Gnome- Initial-Setup. https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup [ Where problems could occur ] If the path to the wallpaper is invalid, the session reverts to its blue background, returning to its current state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077741/+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 920257] Re: Support for MTU 1500 for pppoe (RFC 4638)
Ubuntu has 2.4.6-3ubuntu1 in Vivid, which is greater than 2.4.5+git20130610-1 so I presume this is fixed now. ** Changed in: ppp (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/920257 Title: Support for MTU 1500 for pppoe (RFC 4638) Status in ppp package in Ubuntu: Fix Released Bug description: My ISP (AAISP.org.uk) support PPPoE connections with MTU of 1500 (using mini jumbo frames) as pre RFC 4638 however the version of PPPoE included doesn't allow for setting the MTU larger than 1492. there is a patch (from May/Aug 2010) in the upstream ppp codebase (Patch named "rp-pppoe: allow MTU to be increased up to 1500") is there a chance of getting this patch applied? Additional info: http://tools.ietf.org/html/rfc4638 http://git.ozlabs.org/?p=ppp.git;a=commit;h=fd1dcdf758418f040da3ed801ab001b5e46854e7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/920257/+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 1416875] Re: apache-2.4.10 dies in reload
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reassinging to redland-bindings as you've identified the problem to be there. Sorry, I don't have instructions to give you to collect a core dump for Apache specifically. ** Package changed: apache2 (Ubuntu) => redland-bindings (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland-bindings in Ubuntu. https://bugs.launchpad.net/bugs/1416875 Title: apache-2.4.10 dies in reload Status in redland-bindings package in Ubuntu: New Bug description: net3# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic Different than https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/669005 which has to do with php5-curl. I deinstalled php5-curl + had no effect. Using trace8 provides no additional detail. Unable to get apache to generate a core dump, even after reading many articles + trying many command line incantations. Someone tell me how to get a core dump + I'll post the stack trace of failure. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redland-bindings/+bug/1416875/+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 1416651] Re: Please merge inkscape 0.91-1 from Debian unstable (main)
> ctually, it'll probably be cleaner to hold on for a short time until the Debian maintainer has released the package in the Unstable branch... Are you sure that the Debian maintainer is planning to do this? Since Debian is in freeze, it's often easier to not upload something to unstable that will not go into the release. I presume that this new release doesn't meet the jessie freeze policy. I'd also presume that the Debian maintainer plans to upload the experimental version to unstable eventually, so I think the divergence will disappear. Unless you know otherwise? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1416651 Title: Please merge inkscape 0.91-1 from Debian unstable (main) Status in inkscape package in Ubuntu: Triaged Status in inkscape package in Debian: New Bug description: Inkscape community proudly announces the 0.91 release of Inkscape! Please update Ubuntu 15.04 packages to the latest stable Inkscape version. Packages for Uuntu 14.x, 12.04 and 15.04 are available at ppa:inkscape.dev/stable - see https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable This release marks the culmination of a multi-year effort to switch to a new internal graphics rendering engine, Cairo. This brings performance enhancements and more accurate rendering of drawings. A new Trace Pixel Art feature enables creation of vector art from bitmaps, sprites, and icons. A new Symbols Library provides reusable graphics elements - you can even read in Visio symbol libraries. New Snapping options and improved Snap preferences make it easier to quickly place items in the alignments you need. The tools for arranging objects offer several new ways to position the elements of a drawing. Tons of other little improvements have been made across all the other tools as well. Several new file formats are supported, including FXG, SIF and HTML5 export; and VSD and CDR import. EMF/WMF are now readable and writable for all platforms. And XCF, PDF, EPS, and PS+LaTeX support are improved. Inkscape has a rich Extension ecosystem, which is well known for bringing clever, cool, and innovative new ideas. Over a dozen new extensions are added in this release, including an Isometric Grid Generator, a Bitmap Cropper, a Text Extractor and a Text Merger, an HSL Adjuster, a Font Replacer, a Voronoï Diagram Creator, and more. The above barely scratches the surface of all the new stuff included in this release. For the full story, including examples and screenshots, please see our detailed Release Notes: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1416651/+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
