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://wi
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
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
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 testi
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 te
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-extens
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 Ubu
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-extens
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-extens
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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 Ubu
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
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
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
inform
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?
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 th
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 th
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 th
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/b
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://wik
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.
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.
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.
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 encount
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
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
> 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 subsc
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
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
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.u
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.
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
individu
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 regr
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:/
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://wi
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
** 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 (su
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
De
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!
--
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 Pla
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 regres
> 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)
S
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 encount
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 r
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 r
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 r
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 r
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 r
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 r
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 encount
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 wi
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
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
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 s
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
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
> 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 belie
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
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 i
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://
@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
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.launchpa
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 en
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.
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.
> 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 onc
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
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
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://wi
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 reg
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:
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 pa
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
> 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
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
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 encount
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 m
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 integrate
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
reposit
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 n
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 th
> 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 vo
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
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 wi
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-exten
** 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 n
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 th
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
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
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 testi
1 - 100 of 231 matches
Mail list logo
