[Bug 2080004] Re: Shotwell bug - Out of memory #5123
Hello Jon, or anyone else affected, Accepted shotwell into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shotwell/0.32.6-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/2080004 Title: Shotwell bug - Out of memory #5123 To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/2080004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2025006 Title: Monitor colour profile is randomly not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2025006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2077746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064762 Title: Update gnome-control-center to 46.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064762/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012388] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2012388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019776] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2019776 Title: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2019776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039543] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059819] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2067610] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2067610 Title: GNOME Shell qrcode generator may create invalid QR code images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2067661] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2067661 Title: Login Qr code text is not readable in the lockscreen when using a light theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2068080] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2068080 Title: Updating password from authd does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2068912] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2068912 Title: Authd based authentication fields cannot be translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2069381] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2069381 Title: GNOME Shell doesn't try to start ibus-daemon on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069381/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2069559] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2069559 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() from st_widget_get_paint_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2069559/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072703] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2072703 Title: Update to GNOME Shell release 46.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072710] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2072710 Title: Qrcode-based authentication requires manual ack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072710/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072711] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2072711 Title: Qrcode based authentication does not allow to request a new login code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072714] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2072714 Title: Qrcode authentication dialog should show the login code as separate item To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072714/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072716] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2072716 Title: Key navigation in login / lockscreen choice list does not fully work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072718] Proposed package upload rejected
An upload of gnome-shell to noble-proposed has been rejected from the upload queue for the following reason: "GNOME MRE not valid for gnome- shell as discussed in bug". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2072718 Title: Switching authentication mode with authd may leave old messages or fields around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This change was reverted, so I'm reopening the bug task for Noble. See main tracking bug 2064672 and regression bug 2072811 for details. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This change was reverted, so I'm reopening the bug task for Noble. See main tracking bug 2064672 and regression bug 2072811 for details. ** Changed in: apparmor (Ubuntu Noble) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072742] Re: [SRU] Backport gnome-calendar 46.1
Looks like this falls under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME but please get into the habit of stating that in the SRU documentation. Otherwise you're going to face delays while SRU team members who do not know the background query the upload because it appears to be missing information. ** Description changed: Impact -- This is a new Gnome Calendar release, which contains mostly translation updates but also changes to key binding handling. Here is the news file: https://download.gnome.org/sources/gnome- calendar/46/gnome-calendar-46.1.news Test plan - https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar Regression potential Particular key bindings (particularly of dialog windows) could stop to work. + + Other information + - + + This falls under the GNOME microrelease exception already approved by + the SRU team. See https://wiki.ubuntu.com/StableReleaseUpdates/GNOME for + the background. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2072742 Title: [SRU] Backport gnome-calendar 46.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2072742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1996927] Re: [SRU] Nautilus send mail not working
I've not looked into this in detail yet, but just passing by: > The original logic must remain unaltered for the case nautilus-sendto is not installed. Assuming your analysis identified to be a risk and that's why you mentioned it, surely this is a scenario that should be part of your Test Plan? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996927 Title: [SRU] Nautilus send mail not working To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1996927/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042844] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2042844 Title: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2042844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059818] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059819] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Thank you for the analysis. I've triggered a retest against migration- reference/0 then. That should reset the baseline and remove the flag. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054510 Title: Incomplete screen redraws in virtual machines running Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2045667 Title: Update gnome-shell to 45.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Oh, wait. You are just fixing the race condition? Please the SRU documentation then. Right now I read "We should drop it in favour of using simpledrm with fbdev emulation layer" which is very misleading as to what you're actually proposing to do. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Oh, this? > When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. In that case, why can you not revert the kernel config change in the HWE backport to Jammy? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
> it will expose the race condition to GDM What race condition, please? If this is the justification for the proposed SRU, then I'd expect to see that explained, but I don't see any explanation. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028082] Re: Update glib to 2.76.4
There's an open question on glib2.0 and the GNOME MRE here: https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/65?u=rbasak -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters over GUI elements that are animated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters over GUI elements that are animated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.2 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 the object having b
> 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 Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020277 Title: Update gnome-shell to 44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2004475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2013338 Title: Update nautilus to 42.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013338/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1996148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1996148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1984266] Update Released
The verification of the Stable Release Update for epiphany-browser has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1984266 Title: Update epiphany-browser to 42.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1984266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1985128] Re: GDM fails to activate the login session in AWS Workspaces
Hello Marco, or anyone else affected, Accepted gnome-shell into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/42.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: gnome-shell (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1985128 Title: GDM fails to activate the login session in AWS Workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1985304] Please test proposed package
Hello Marco, or anyone else affected, Accepted gnome-shell into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/42.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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1985304 Title: Update GNOME Shell to 42.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1985304] Re: Update GNOME Shell to 42.4
> Verify that they can all be enabled without showing an error. IIRC the original request was to ensure that the extensions actually work (ie. a basic smoke test), not just that they can be enabled without error. I'll adjust your Test Plan accordingly. Really the Test Plan should be approved once by the SRU team and then documented on the wiki, so that we don't bikeshed each invididual one every SRU. I suggested this in https://discourse.ubuntu.com/t/scope-of- gnome-mru/18041/48 but there doesn't seem to be any progress on this. So sorry to be bikeshedding this here, but until those remaining steps are done, that's how it is. ** Description changed: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.4/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.2 Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. + Verify that the basic functionality of each extension works as expected. 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 ** Changed in: gnome-shell (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1985304 Title: Update GNOME Shell to 42.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964795] Please test proposed package
Hello Paul, or anyone else affected, Accepted gnome-keyring into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- keyring/40.0-3ubuntu3 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 Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1964795 Title: gnome-keyring-daemon crashed with signal 7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1964795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964795] Re: gnome-keyring-daemon crashed with signal 7
FTR, the upstream commit is here: https://gitlab.gnome.org/GNOME/gnome- keyring/-/commit/a17707681f35b73a5ecd8ca60a5ff950c790df39 ** Changed in: gnome-keyring (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1964795 Title: gnome-keyring-daemon crashed with signal 7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1964795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1978838] Re: Couldn't connect to accessibility bus
Hello Sebastien, or anyone else affected, Accepted evince into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evince/42.3-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: evince (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1978838 Title: Couldn't connect to accessibility bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1978838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Update Released
The verification of the Stable Release Update for gvfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
Thank you for taking the time to do this! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
Thank you for working with us to try and get a test plan for Ubuntu together. How about this: 1) I'll accept the package (1.44.1-1ubuntu1.1) into focal-proposed. 2) You test using your Ubuntu VM as best as you can to ensure that the package hasn't regressed for Ubuntu users. 3) You verify the package fixes your race on Mint as pragmatically you've found no practical way to test on Ubuntu. 4) If we're good on both verifications, I'll publish the update to focal-updates. Does this plan work for you? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
Is there nobody using Ubuntu itself who will be able to help test at all? Is anyone willing to fire up an Ubuntu live image to help test it there? If so, maybe it's worth seeing if the race reproduces in a live environment on Ubuntu first? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
> I guess the goal there would just be to say the issue occurred X times in Y hours on 1.44.1-1ubuntu1, and zero times in Z hours on -proposed. I think something like that would be fine, yes. I'm not sure about using Mint for the test though. Are there any direct users of Ubuntu who could test in this fashion? If no direct Ubuntu users appear to be affected, then the race could be manifesting due to some difference in Mint, at which point there'd be limited benefit for the regression risk cost of making a change for direct Ubuntu users in a stable release. But if direct Ubuntu users _are_ affected, then I would expect at least one of them to be able to step up and help us test. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
The patch and upload look good. Thanks! > To my knowledge, there is not a 100% reproducer for gvfs from userspace as this is a probable lock-ordering issue in lower-level code. https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the underlying glib issue. I appreciate the difficulty, and we can be pragmatic about not requiring 100% verification. But then what exactly is the test plan? How do you propose to verify that the issue is at least _likely_ to be fixed before we release the fix into focal-updates? What steps, if any, are you proposing to take, exactly? Are you proposing not to test it at all? Or just to test that basic functionality in the affected areas still work, and if so, what would that cover exactly? Or are you going to attempt to trigger the race and if unsuccessful some number of times then call it good? Or some combination? I'd like for expectations to be clear, and the plan agreed, before accepting this into focal-proposed. Once a test plan (or lack thereof) is agreed, then +1 to accept this into focal-proposed. ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #1941 https://gitlab.gnome.org/GNOME/glib/-/issues/1941 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947553] Update Released
The verification of the Stable Release Update for gnome-panel has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1947553 Title: wrong panel size 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1947553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Thanks Dariusz. Are you intending to fix gnome-shell-extension-desktop-icons in Focal also then, to restore the behaviour? If so, then shouldn't these be uploaded together with a Breaks clause to make sure users get both at the same time? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
According to the upstream bug, the change was necessary to work correctly with the desktop shell extension. Won't reverting the change risk integration issues with extensions, including the ones we ship by default? Shouldn't this be detailed in "Where problems could occur", and mitigation integrated into the Test Plan? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
Hello Peter, or anyone else affected, Accepted gnome-shell-extension-desktop-icons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/20.04.0-3~ubuntu20.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938747] Re: [SRU] can't adjust output volume through volume-slider after changing output-device
Hello Hui, or anyone else affected, Accepted gnome-control-center into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.36.5-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1938747 Title: [SRU] can't adjust output volume through volume-slider after changing output-device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Hello Mario, or anyone else affected, Accepted gnome-control-center into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.38.5-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938747] Re: [SRU] can't adjust output volume through volume-slider after changing output-device
> can I think if this intentional? ...can I *check* if this is intentional? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1938747 Title: [SRU] can't adjust output volume through volume-slider after changing output-device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938747] Please test proposed package
Hello Hui, or anyone else affected, Accepted gnome-control-center into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.38.5-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1938747 Title: [SRU] can't adjust output volume through volume-slider after changing output-device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938747] Re: [SRU] can't adjust output volume through volume-slider after changing output-device
The Focal upload is missing the fix for bug 1795483 which there's a task for. The Hirsute upload includes fixes for both. Accepting the Hirsute upload. Before I accept the Focal upload, can I think if this intentional? I can accept the current upload if you want, but then the fix for bug 1795483 will get blocked until that SRU is done. ** Changed in: gnome-control-center (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1938747 Title: [SRU] can't adjust output volume through volume-slider after changing output-device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
I noticed that newer uploads in Impish for -ng provide: + gir1.2-clutter-gst-3.0, + gir1.2-gtkclutter-1.0, Are these needed for the -ng SRU to Hirsute? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
** Description changed: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. + [racb] Since single click code is also being adjusted, please test that single clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 ** Description changed: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. - [racb] Since single click code is also being adjusted, please test that single clicking behaviour has not changed. + [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. + [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Please test proposed package
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.36.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.38.1-3ubuntu3.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936303] Please test proposed package
Hello Kai-Heng, or anyone else affected, Accepted gnome-settings-daemon into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.36.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1936303 Title: [SRU] Debounce multiple rfkill events To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936303] Re: [SRU] Debounce multiple rfkill events
Hello Kai-Heng, or anyone else affected, Accepted gnome-settings-daemon into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.38.1-3ubuntu3.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-hirsute ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1936303 Title: [SRU] Debounce multiple rfkill events To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
