laney@raleigh> git diff upstream/6.4.0 upstream/6.9.0 -M05 --
src/network/default.xml src/network/default.xml.in
diff --git a/src/network/default.xml b/src/network/default.xml.in
similarity index 38%
rename from src/network/default.xml
rename to src/network/default.xml.in
index
Public bug reported:
I'm upgrading libvirt-daemon-system from 6.6.0-1ubuntu4 to
6.9.0-1ubuntu1. I got a conffile prompt on this file, and to me it's
quite mysterious.
I suppose some part of libvirt added the delta for me automatically, and
now that the file changed upstream (will add that info
Christian raised this with us just now - I think we should consider
taking a look at this.
Looking at
http://autopkgtest.ubuntu.com/packages/libreoffice/hirsute/arm64
http://autopkgtest.ubuntu.com/packages/libreoffice/hirsute/armhf
the tests are basically OK but one of the uicheck-* ones ends
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785262
Title:
arm64 autopkgtests are flaky
To manage notifications about this bug go to:
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => hugh chao (hugh712)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => hugh chao (hugh712)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been sponsored to the Focal NEW queue now, thanks.
** Changed in: Ubuntu Focal
Status: New => Fix Committed
** Changed in: Ubuntu Focal
Assignee: (unassigned) => Bin Li (binli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
: Confirmed => In Progress
** Changed in: gparted (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903159
Title:
package gparted
D-Bus
activation.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because
** Changed in: ubiquity (Ubuntu Focal)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892040
Title:
US keyboard layout even if a non english
The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent
I verified 3.38.1-1ubuntu2~20.10.1 and 3.36.2-0ubuntu2 and they both
worked for me, and I didn't notice any regressions.
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy
** Tags added: verification-done verification-done-focal
verification-done-groovy
Issue here I think is that we use per-session overrides for the majority
of our Ubuntu customisations, and these don't apply to greeter sessions.
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package in groovy-proposed is a no-change backport of
20.10.3-0ubuntu1.
But nevertheless, I've verified the fix with 20.10.3-0ubuntu0.20.10.1
installed now. The grey gorilla appears fine.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done
I think maybe sssd needs to learn how to set the environment in
"session" mode. I did ask some people at Canonical who know about this
project, hopefully they will have some advice soon. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think anything which causes gvfs to start "early enough" (before
gnome-session has a chance to upload the environment to systemd) will
trigger this problem.
So anything which starts from e.g. default.target, or maybe there are
things like ibus which are started outside of systemd's control.
I
I was running libmutter-7-0 3.38.1-1ubuntu1. I could reproduce the
initial bug of not being able to launch Chromium from the snap. After
upgrading to 3.38.1-2ubuntu1, now I can launch it fine.
Additionally, ss shows that Xwayland is listening on the abstract socket
too.
laney@nightingale> ss
I have re-verified the uploads with the animal.
** Attachment added: "Screenshot from 2020-10-29 10-44-09.png"
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1901361/+attachment/5428951/+files/Screenshot%20from%202020-10-29%2010-44-09.png
** Tags removed: verification-needed
I checked the SRU (20.10.3-0ubuntu20.10.1, weird version) and this
wallpaper appears now.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: raspi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901861
Title:
Failed to set the language after the initial OEM setup for Ubuntu
Desktop on Raspberry Pi
To manage
Sorry, we don't do that. The current default greyscale wallpaper only is
shown there, and this happens via ubuntu-wallpapers.xml. The reason is
that we found that if we show them all (if you have multiple ubuntu-
wallpapers-* installed) then it's very hard to tell between the
different wallpapers,
btw, as per the exception (approved yesterday by Brian):
"The aging requirement is not applied for releasing to -updates /
-security."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901361
Title:
I just updated the test case with the new one we came up with on
https://wiki.ubuntu.com/StableReleaseUpdates#distro-info-data
All looks good to me - see the attached screenshot.
** Description changed:
(copied from LP: #1874843)
H has a name. distro-info needs an update.
SRU Test:
All uploaded to the queues, cheers.
** Description changed:
+ [ Description ]
+
+ Clicking on a blank spot on the featured snaps page can lead to a crash.
+
+ [ QA ]
+
+ 1. With a new user, or by running `/usr/libexec/gnome-initial-setup
--existing-user`, launch g-i-s.
+ 2. Advance through
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901548
Title:
gnome-initial-setup SIGSEGV in snapd_snap_get_name()
To manage notifications about this bug go to:
cal)
Status: New => In Progress
** Changed in: gnome-initial-setup (Ubuntu Groovy)
Status: New => In Progress
** Changed in: gnome-initial-setup (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: gnome-initial-setup (Ubuntu Focal)
Assignee: (unassigned)
(gnome-initial-setup:69424): InitialSetup-WARNING **: 11:35:06.795: Failed to
send report: metrics from this machine have already been reported and can be
found in: /home/laney/.cache/ubuntu-report/ubuntu.20.10
[New Thread 0x337fdb60 (LWP 69455)]
[Thread 0x337fdb60 (LWP 69455) exited]
I looked at the code. I think in on_app_clicked() (in the distro patch)
we need to check the child is a snap tile, or do nothing if not.
Will check this tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
at least to fix the invalid cast, but it seems likely this could lead to
a crash too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901548
Title:
Segfault on arm
To manage notifications about
This is uploaded now to hirsute (the new in-development release) and
groovy (it's in the review queue, look out for a message to test when
it's accepted).
Thanks a lot for reporting.
** Changed in: ubuntu-wallpapers (Ubuntu)
Status: New => Fix Committed
--
You received this bug
Yeah, thanks for duping that.
This is uploaded now to hirsute (the new in-development release) and
groovy (it's in the review queue, look out for a message to test when
it's accepted).
** Attachment added: "greyscale.png"
** Description changed:
+ [ Description ]
+
+ I forgot to update the symlink for the greyscale default gorilla
+ wallpaper and so it doesn't show up in the wallpaper chooser.
+
+ [ Fix ]
+
+ Fix the symlink.
+
+ [ QA ]
+
+ Right click on the desktop, ideally on a clean system so you don't
e..."
and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)
** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
Status: New => In Progress
** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
Assignee: (unassigned) =>
Thanks a lot. It's not exactly a duplicate - there are two bugs here :(
** Summary changed:
- ubuntu 20.10 background
+ Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from
wallpaper chooser
** Also affects: ubuntu-wallpapers (Ubuntu Groovy)
Importance: Undecided
** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901353
Title:
Ubuntu Default Greyscale Wallpaper Sym Link
Bah, thanks, sorry about that.
** Also affects: ubuntu-wallpapers (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
Status: New => Triaged
** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
Assignee: (unassigned) => Iai
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901043
Title:
No sound in ubiquity-dm with nomodeset
To manage notifications about this bug go to:
ah I see, OK - I will upload, thanks!
can you update the test case to say that this version of alsa-utils is
needed please? maybe provide a PPA link for people to install it with,
until that is accepted into focal?
** Changed in: alsa-lib (Ubuntu Focal)
Status: Incomplete => Fix Committed
We've deployed a fix from Steve to include this for BIOS boots only. So
partially fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899615
Title:
No "Memory test" boot menu entry
To manage
I don't see the same problem on the Focal ISO - do we need to fix this
in Focal?
** Changed in: alsa-lib (Ubuntu Focal)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It was done deliberately, to "subtly" highlight the RPi desktop work. :)
** Changed in: ubiquity (Ubuntu)
Status: New => Won't Fix
** Changed in: ubiquity (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Indeed, we need to respin the ISOs for this.
We did not rebuild the squashfs earlier, because we forgot/didn't know
that they contain apt indexes for restricted. So they got out of sync
with the pool (where the drivers are fetched from during installation),
and apt got sad when it couldn't reach
Removing 455 from groovy to groovy-proposed to fix (2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh groovy install with Secure
Boot
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh groovy install with Secure
laney@dev> ./change-override --suite groovy --component main
python3-octavia-lib
~/dev/canonical/release/ubuntu-archive-tools
Override component to
New shim-signed is now on the latest images (20201021).
I'm still not clear what happened when enabling Broadcom from the
installer since it all looks fine to me. Perhaps you could try and let
us know what doesn't work with detailed steps to reproduce? (but
hopefully it does work)
--
You
I think the second part (apt install not showing the prompt on next
boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8.
But I'm not quite sure about your initial part where the installer
didn't do the same. I can make that happen if I tick to install
proprietary drivers and
Yeah, fossfreedom, can you tell us what you ticked on the 'install third
party drivers' page?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - does not work
I think SRUing would be OK for this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900642
Title:
sssd won't start
To manage notifications about this bug go to:
** Changed in: shim-signed (Ubuntu Groovy)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898729
Title:
shim can end up being removed
** Changed in: ubiquity (Ubuntu Groovy)
Assignee: Łukasz Zemczak (sil2100) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892040
Title:
US keyboard layout even if
laney@dev> ./change-override --suite groovy --component restricted
linux-firmware-raspi2 ~/dev/canonical/release/ubuntu-archive-tools
Override component to restricted
linux-firmware-raspi2 2-0ubuntu2 in groovy arm64: multiverse/misc/optional/100%
-> restricted
linux-firmware-raspi2 2-0ubuntu2
laney@dev> ./change-override --suite groovy --component restricted pi-bluetooth
~/dev/canonical/release/ubuntu-archive-tools
Override component to restricted
pi-bluetooth 0.1.15ubuntu1 in groovy arm64: multiverse/misc/optional/100% ->
restricted
pi-bluetooth 0.1.15ubuntu1 in groovy
(if so, other builds from now onwards should be good)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900304
Title:
The "Prepare for shipping to end user" icon is not shown on desktop on
legacy
Please try with this Ubuntu ISO:
http://cdimage.ubuntu.com/ubuntu/daily-live/20201019.1/
we think it should be better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900304
Title:
The "Prepare
(ricotz indicated on IRC that they had done some testing - usually I
would like to see that detailed in the bug)
** Changed in: libreoffice (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No problem from the RT either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899456
Title:
[UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)
To manage notifications about this bug go to:
I subscribed the desktop team to the bugs.
I'm assigning the security team now per comment #2 (thanks for the
review).
** Changed in: malcontent (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you
ted. So basically any theme change which affects
the default desktop will need to go through the process.
(Unless Gunnar is hinting here that there aren't any such screenshots in
which case maybe we should tweak the freeze definition.)
--
Iain Lane [ i...@oranges
Jeremy synced this - and I hope also tested it!
** Changed in: pitivi (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897729
Title:
FeatureFreeze
That does sound useful and worth scheduling I think. I didn't know about
that until now!
I'll try to find some time soon to go back to the release I installed
from and take a look there, per Steve's suggestion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Cheers Steve. Nope, -proposed is not enabled.
Yes, it happened - it was the result of an explicit autoremove on my
part though after I had dist-upgraded to current focal-updates. I should
have noticed that this was happening and stopped it, granted. :)
Attached is the snippet of apt's term.log
I've marked apt as affected because it ships
/etc/apt/apt.conf.d/01autoremove but I suppose each of the affected
packages could also supply their own snippets.
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I just did a set of package updates in focal that ended up with shim
shim-signed mokutil being autoremoved.
I rebooted without noticing, and had to manually recover the system
thereafter. :(
Julian says there was a period of time where these were marked auto. I
suppose that
Public bug reported:
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
I'd like to use it in our new raspberry pi images where we don't have
cloud-init installed. We're already using systemd-growfs, but
I think it should be fine, providing someone does some (light) testing
of the package in an Ubuntu environment to make sure it basically works.
We decided on temporary removal because the Debian maintainer indicated
that this new release was due soon, and we could then re-include pitivi
once it
Already said on IRC, but mentioning here for other RT members:
I'd like to see (1) an analysis of the risks of this update, and (2) a
description of what testing you've done, please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu Groovy)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: mutter (Ubuntu Focal)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah, sorry, I don't think that's a reproducer for the bug. You killed
dbus, gdm and everything else, and they obligingly died on you. :)
My feeling is that this bug is about a deadlock that somehow happens
when dbus and/or systemd are reloaded, possibly at the same time. It
looks like dbus stops
Right, yes, please do go ahead. It was pointed out before that this
would be desirable after we switched away from -legacy due to the nature
of the fixes.
I had thought from the diff of debian/tests/control that the test
coverage of the nft backend was being reduced, but then I took a look at
OK, I understand that the impact is limited for groovy since we don't
build most of the relevant images there. Feel free to go ahead then, but
please do make sure that the ubuntu-cpc images continue to work.
** Changed in: ubuntu-image (Ubuntu)
Status: New => Confirmed
--
You received
** Changed in: xdg-desktop-portal-kde (Ubuntu)
Status: New => Fix Released
** Changed in: xdg-desktop-portal-gtk (Ubuntu)
Status: New => Fix Released
** Changed in: xdg-desktop-portal (Ubuntu)
Status: New => Fix Released
** Changed in: weston (Ubuntu)
Status: New =>
It's still right. I'm going to remove 0.1.7-1 from groovy now. We could
remove g-r-d from the archive altogether if that's required for some
reason. Personally I like it as a reminder to bring it back (there's a
link to this issue) when we can.
We now have pipewire 0.3 in Ubuntu, and so for the
Yeah, makes sense. Happy to approve this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896475
Title:
[FFe] Migrate to pipewire-0.3
To manage notifications about this bug go to:
OK, go for it!
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895060
Title:
[FFe] apparmor 3 upstream release
To manage
Just to confirm, your intention (barring bugs) is that there should be
no breakage for existing apparmor profiles and consumers of the
rewritten tools?
If so, I think this should still be fine at this stage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK by me, please go ahead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896397
Title:
[UIFe] Tweak Arabic font
To manage notifications about this bug go to:
I've uploaded, thanks.
But the regression potential section needs improving, "None" isn't
enough. Please improve it to discuss where people should focus their
attention / testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: oem-priority/focal
Importance: Undecided
Status: New
** Changed in: oem-priority/focal
Status: New => Invalid
** Also affects: network-manager (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New
For reference:
laney@dev> ./change-override --suite groovy --component main fonts-noto
Override component to main
fonts-noto 20200323-1build1 in groovy amd64: universe/fonts/optional/100% ->
main
fonts-noto 20200323-1build1 in groovy arm64: universe/fonts/optional/100% ->
main
fonts-noto
Thanks for this. Really interesting issue, sorry it's taken a while to
respond.
Gunnar, do you have any thoughts on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866038
Title:
By default
Agreed that taking the unit which upstream has validated is more
sensible than backporting. Thanks for the detailed report. I think the
only thing which I would like to see in future is you saying that (and
how) you've tested it manually and spotted no regressions.
But go ahead this time.
--
201 - 300 of 6667 matches
Mail list logo
