** Summary changed:
- Update and seed wsl-pro-service in the WSL images
+ [FFe] Update and seed wsl-pro-service in the WSL images
** Description changed:
This is a new package for this release. It’s only functional with a
Windows agent which is not publically released and under beta for
Public bug reported:
This is a new package for this release. It’s only functional with a
Windows agent which is not publically released and under beta for now.
As the end of the beta will be after the 24.04 release, we want to get
as close as possible to the current code level, knowing that
Public bug reported:
Tested with 124-1ubuntu1 on noble
1. Create 3 users on the machine:
- sudo-user1, part of sudo group
- sudo-user2, part of sudo group
- normal-user, not part of the sudo group
2. Login with normal-user
3. Try to execute pkexec or any other command prompting for polkit
->
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: software-properties (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
[ Impact ]
* It is not possible to upgrade or re-install python-apt using pip from
the git+ssh://git.launchpad.net/ubuntu/+source/python-apt git repo if
already installed and if wheel installed too.
* On initial install it also is assigned version `0.0.0` which is
Thanks all. Marking as "Won't Fix" and marked MP as Rejected.
** Changed in: ubuntu-meta (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
With only snapd snap preseeded I get boot times very similar to
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.757s (kernel) + 12.458s (userspace) = 16.216s
graphical.target reached after 12.061s in userspace.
```
Which shows we are still taking a boot time hit of ~1.5 seconds...
> * boot times w/ and w/o preseeded snaps
Without preseeded snaps:
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.609s (kernel) + 11.026s (userspace) = 14.636s
graphical.target reached after 10.642s in userspace.
```
With preseeded snapd and core22 snaps:
```
ubuntu@cloudimg:~$
@vorlon
> Also, statically seeding a particular base snap is bad form, as soon
as lxd upgrades its base you lose your performance benefit and have to
play catch-up in a stable release.
yes I don't like this either. Even if we do change it later to core24
then the expectations people have for
Thank you for the detail sdeziel
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Title:
Always preseed core and snapd snap in server seed
Status in
> "other cloud cases that have preseeded snaps" (thinking like ec2 or
oracle that have snapped cloud agent
This isn't something we need to worry about as there will be no change
in this case. If any agent snaps are preseeded then so too will a core
snap and snapd snap.
--
You received this bug
> 15 seconds vs 30 seconds, on a thing that won't affect most cloud
customers
I'll see if I can find the data to back this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
If we don't preseed a core snap and snapd it feels like we're failing to
prioritise the performance of snaps on server/cloud.
But if we acknowledge that knowing that we are prioritising boot speed
then that's fine and we can add it to the noble release notes.
--
You received this bug
Good points
I'll measure boot speed with and without core snap preseeded and add it
here.
time to initialize any snap was my goal but with lxd as an example as it
is such a popular snap.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
in the server seed @
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/tree/server#n69
[1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status: New
Philip Roche (philroche)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051346
Title:
No longer preseed LXD snap to allow for LXD 5.20 release
Status in ubuntu-meta p
Public bug reported:
With LXD 5.20 there is a license change to AGPL and it has been decided
to no longer seed the snap in Ubuntu 24.04 and later and instead seed
the lxd-installer package instead.
This bug is to track the work of making that change in the server seed @
> a) You state that some policy says that no ports other than 22 should
be open, which policy is that? Does it apply only to cloud images, or is
it an Ubuntu policy in general
This policy is detailed @
https://wiki.ubuntu.com/Security/Features#ports
> Default installations of Ubuntu must have no
> a) You state that some policy says that no ports other than 22 should
be open, which policy is that? Does it apply only to cloud images, or is
it an Ubuntu policy in general?
I will try find the referenced policy.
> b) This is in mantic release at the moment, and switching that option
back to
cloud minimized and non minimized images have now been tested with
6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite
which was failing and which is the test suite which prompted this whole
thread. +1
--
You received this bug notification because you are a member of Ubuntu
I have also successfully verified that -proposed amd64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host with older hardware (ThinkPad T460
with 6th gen intel i5 which is the same hardware which we were able to
reproduce the issue on
@xnox I have successfully verified that -proposed arm64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host. See
https://people.canonical.com/~philroche/20231003-mantic-minimal-
proposed-kernel/ for cloud-init logs, some debug output and
Sorry for making you so hard work... I am using now, since 2023 /04...
Ubuntu 23.04... Which works very well on my Asus rog... Thank you so
much to do what you do Best regards G. Roche
Envoyé par AOL sur Android
Le mar., août 29, 2023 à 12:13, Benjamin Drung<1641...@bugs.launchpad.
@Bryce, @RAOF: thanks for the notice! I feel we should then reuse this
MIR to file a new template with our modern MIR rules (Note that the
initial demand was made in 2011!)
I’m thus marking it as incomplete until this is DONE, feel free to redirect
this request directly to the team who will own
** Changed in: grub2 (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1867007
Title:
zfs-initramfs fa
statically linked, in a limited
environment where busybox-static was running to a dynamically linked,
opened one. As discussed during the MIR meeting, this would need a
security assessment.
** Changed in: busybox (Ubuntu)
Assignee: Didier Roche (didrocks) => Ubuntu Security Team (ub
** Description changed:
- When a user is logged in to the Ubuntu desktop, a power button event
- will cause the user to be prompted to choose if they'd like to proceed
- with a shutdown. However, if the system is sitting at a greeter screen,
- a power button event will instead attempt a suspend
We are going to backport it to focal. Groovy, as being EOL in a couple
of months, doesn’t work any SRU work, removing the task.
** No longer affects: ubuntu-settings (Ubuntu Groovy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
ile not found
[-Wmissing-profile]". Those warning could potentially spread to all binaries
using this build. Can you check with upstream about those?
** Changed in: libdeflate (Ubuntu Hirsute)
Assignee: Didier Roche (didrocks) => Sebastien Bacher (seb128)
--
You received
** Changed in: libdeflate (Ubuntu Hirsute)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1908502
Title:
[
** Description changed:
+ [Impact]
+
+ * Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
+ * The option is available on grub and will let you with a broken system,
partially cloned.
+
+ [Test Case]
+
+ * Boot
We will backport your patch to previous releases soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in
Thanks for the confirmation :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in
** Changed in: libgweather (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU] Update libgweather to
I reapplied your debian/changelog directly and pushed to focal (pending
approval). Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU]
Hey Amr and thanks for making ubuntu better.
Do you mind double checking your patch?
Trying to apply it on 3.36.0-1, I get those chunks failing to apply
(tried both your .diff and .diff.gz):
patching file debian/changelog
patching file libgweather/gweather-weather.c
patching file
This patch was worked with upstream and even merged in systemd master.
Howwever, after a month, Lennart decided to revert it because he strongly
thinks that no feedback on fsck is needed because "everyone have fast SSD
disks". (frustrating experience after working for a good 3 months getting
Note: from what I see above, the issue is on the plymouth new
integration (I think it’s xnox that changed it) modifying the logic
displaying the cancelling message. Maybe worth digging there?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Tried with both manufacturer and gutenprint driver:
1. plug an epson stylus photo rx560 via usb
2. add the driver (manufacturer first, retried with gutenprint) autodetected
our gtk ubuntu specific application.
3. Tried to print with multiple apps: the task is queued and
I will have a look (I don’t remember if the grub task is due to the
grub.cfg generation or to grub code itself), but TBH, this is low
priority on my list (downgrading the bug task priority as such, as this
is a multi-system corner-case)
** Changed in: systemd (Ubuntu)
Importance: Medium => Low
ZFS installation without ZSys installed is equivalent to non ZFS
installation without ZSys. userdel calls ZSys which does the cleanup. If
you don’t have it, nothing will change from today’s behavior.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
+ [Impact]
+ * Deleting users were preserving corresponding ZFS user datasets, without
marking them for cleanup.
+ * This is covered by dedicated use cases.
+
+ [Test Case]
+ 1. Ensure you have a foo user:
+ 2. Run userdel --remove foo
+ 3. Check that
** Changed in: shadow (Ubuntu)
Importance: Undecided => Medium
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Also affects: shadow (Ubuntu Focal)
I
** Summary changed:
- Collect unmatched bootfs-datasets on all userdata
+ Collect deleted users
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
d => High
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
This is probably because your bpool is not in the zfs cache file.
Either reinstall from the beta image which has a fix in the installer, or:
- clean up any files and directories (after unmounting /boot/grub and
/boot/efi) under /boot (not /boot itself)
- zpool import bpool
- zpool set cachefile=
Hey Balint. I just added the task post ZFS upload (the upload was
yesterday and I added the task this morning) so indeed, there is some
work needed, part of it being in systemd.
Basically, systemd isn’t capable of mounting datasets when pool names are
duplicated on a machine
zfs-mount-generator
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1867007
Title:
zfs-initramfs fails with
Public bug reported:
?? on update
PC GL753VD ASUS
I7 7700 Ram 8 gb
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.133ubuntu13
ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
Uname: Linux 5.4.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
@Daniel, however, this creates "interesting" issues, like when you have a
pulseaudio server on the network. Even if your laptop is connected before the
user session, it will always switch to the server, even if you reverted on this
decision at previous reboot.
However what I describe above
(in unapproved)
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in
Here is the change to the ubuntu desktop seed as an example:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/commit/?h=eoan=00192c2d530e6b9a636ac0dcd754c4a80a2319e5.
Ubiquity upload is on the way.
--
You received this bug notification because you are a member of Ubuntu
Touch
Subscribed infinity for tracking the release. Look at the commit why
it's not (yet) added to live-common.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739
Title:
Public bug reported:
Move those 2 to the live seed to have them available in the installer.
Mark them then manually installed in the installer if needed. Then,
ubiquity will purge them if not used.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects:
** Also affects: ubuntu-mate-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847431
Title:
Installing ZFS
Public bug reported:
We need to:
* seed zfs-initramfs
* remove apt install from ubiquity zfs script.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta
** Summary changed:
- [FFe] Ubiquity with zsys install option
+ [FFe] Ubiquity with zfs install option
** Description changed:
Part of the 19.10 feature announcement is zfs experimental support in
the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
+1 on the MIR side
** Changed in: gupnp-av (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp-av in Ubuntu.
https://bugs.launchpad.net/bugs/1785629
Title:
[MIR] gupnp-av
Thanks a lot Łukasz! The MIR is available at
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1839271, the MIR
part has been acked, it's pending a security review for now.
Anyway, let's proceed with this so that we can test it early in the
wild, thanks again!
--
You received this bug
attaching shadow build logs
** Attachment added: "shadow_4.5-1.1ubuntu4_amd64.build"
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1842902/+attachment/5287475/+files/shadow_4.5-1.1ubuntu4_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hey Alex! Thanks for looking at it.
Sure, I've added some checks for open/dup2 (and exiting the child).
On execl, I've kept the similar logic than the rest of the code, meaning:
- don't check for execl return value.
- if something bad happen, execl returns.
- we go on the next line which is a
Public bug reported:
Part of the zsys spec is creating/associating one user dataset for each
HOME user.
As zsys is an official experimentation for 19.10, we would like to
include this feature in a safe way, and reachable for any tool creating
users (adduser, gnome-control-center, ubiquity…).
Public bug reported:
With the default configuration (nothing changed), I see in the
development version of ubuntu (disco) that unattended-upgrade is now
updating every package first thing after boot.
As you can see below, it didn't update packages from the security
pocket, but all packages in
Let's turn those as incomplete to get off the list until we get over
them again (probably next cycle).
** Changed in: gupnp-av (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742714
Title:
MIR: mesa-vulkan-drivers FFE: install by default
** Changed in: gupnp-av (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp-av in Ubuntu.
https://bugs.launchpad.net/bugs/1785629
Title:
[MIR] gupnp
** Changed in: gupnp (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp in Ubuntu.
https://bugs.launchpad.net/bugs/1799974
Title:
[MIR] gupnp
Sta
** Changed in: gssdp (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp in Ubuntu.
https://bugs.launchpad.net/bugs/1799977
Title:
[MIR] gssdp
Sta
Thanks! Do you mind listing the exact binary package list which should
then be promoted?
Agreed with you on the autopkgtests. This could have helped if vala were
to regressed the lib build, but unsure this is really needed as a
separate autopkgtests.
So, +1 for me, the security team should feel
Thanks! Do you mind listing the exact binary package list which should
then be promoted?
I would have appreciated the simple nitpick to be fixed while you were
fixing the other issues, but as said, not a requirement…
Agreed with you on the autopkgtests. This could have helped if vala were
to
** Attachment added: "crash after update on ubuntu 18.10"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1734106/+attachment/5215372/+files/IMG_20181122_124810_DRO.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Ubuntu crashes after update on nov 22 <<< On 4 18.0 12
impossible to restart //
can open on recovery ;ode <<< 1st part and thenm crashs see picture on
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
** Changed in: gssdp (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp in Ubuntu.
https://bugs.launchpad.net/bugs/1799977
Title:
[MIR] gssdp
Sta
** Changed in: gupnp (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp in Ubuntu.
https://bugs.launchpad.net/bugs/1799974
Title:
[MIR] gupnp
Sta
Tests are actually ran during package build. So, good in that regard.
Should it ran as autopkgtests though?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp-av in Ubuntu.
https://bugs.launchpad.net/bugs/1785629
Title:
* -doc package: I think we should promote it as well in main, if the -dev is
promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first
is lynx, in universe, www-browser is a virtual package not fullfiled?). In
addition, it ships the doc in devhelp format (despite symlink
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1795410
Title:
cannot bring up window menu via keybinding
I've generated a report with a version pre 7.3, then, upgrade apport and
report it with 7.4 and I didn't trigger any crash.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you
Are you sure this is due to the above patch, can you try without it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1691678
Title:
Scrollbars escape the bottom and right
Ok, so the current fix in UNAPPROVED will prevent that at least ;)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1791324
Title:
I installed it on bionic and confirmed that on a default configuration,
the new settings is taken.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
e Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-meta (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1783571
Title:
Set Yaru as default
As a reminder, ubuntu-settings is failing due to a meson issue:
https://github.com/mesonbuild/meson/issues/3914.
The stack has been tested locally and everything works well, including
transition with removal of older alternatives and fallback to plan Shell
for GDM without the theme installed.
**
yaru MIR is https://bugs.launchpad.net/ubuntu/+source/yaru-
theme/+bug/1783600
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
Note: Need as well Yaru 18.10.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1783571
Title:
Set Yaru as default
Status in ubuntu-settings package in Ubuntu:
Public bug reported:
Set Yaru as default ubuntu 18.10 theme.
** Affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~didrocks/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/350879
--
You
Are you sure that your configuration was still set to manual and not
"never"? (there is a timeout bug in whoopsie-preferences which reset the
condition to "never" if g-c-c is kept opened).
I just tried with the -proposed version, generated a crash which can be
reported (note as well that some
Interesting, I was sure we upstreamed completely systemd-fsckd. Anyway,
+1 for me, let me assign to xnox who is doing most of systemd uploads
nowdays so that he attaches it to next upload.
Many thanks!
** Changed in: systemd (Ubuntu)
Assignee: Didier Roche (didrocks) => Dimitri John Led
Thanks for submitting this patch and sorry for the time to review it!
The patch looks good to me, I would love though to get that directly
upstream rather than us carrying a distro-patch for a small issue like
this, do you mind doing a PR there? https://github.com/systemd/systemd/
** Changed in:
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-settings (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-settings (Ubuntu)
Importance: Undecided => Medium
** Changed i
** Also affects: ubuntu-settings (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1782190
Title:
Set
Thanks! I indeed didn't try the server side, I don't see how this is a
new issue though compared to apport-noui.service? The same service files
start/restart/stop rules are just moved to apport package via apport-
autoreport.service. So, if there is a race on install until the next
reboot, the
** Description changed:
[ Impact ]
A lot of users are bother by the number of whoopsie dialog. We introduced on
"G-C-C privacy option don't allow sending manual report" bug
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a
way for users to change from always
.*) directly.
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubun
Public bug reported:
The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
It's blocking randomly on different tests.
All tests that are stucked, implements closing a request via a timeout
(and then, executing
1 - 100 of 375 matches
Mail list logo
