[Expired for apt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
It is not a typical configuration to have both services running.
It makes sense to have both services running, IF you have configured
separate network interfaces to be managed by each. But this is a very
uncommon configuration.
The expectation is that the services are dynamically enabled only
re: "you should not have both services running"
Is this documented somewhere? What software or script, during system
installation, is meant to ensure this? I have not seen warnings emitted
from postinst (as added for /etc/network/interfaces) or service start.
--
You received this bug
This bug was fixed in the package systemd - 253.5-1ubuntu6
---
systemd (253.5-1ubuntu6) mantic; urgency=medium
* debian/tests: Depends: tzdata-legacy for upstream-{1,2} (LP: #2035778)
File: debian/tests/control
Hi, we were seeing similar issues when bootstrapping AWS EC2 hosts in
our service. We applied the patch provided in upstream internally and it
indeed resolved the filesystem resize errors we previously encountered.
It would be helpful to also backport the patch in Ubuntu and make it
generally
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
The gnome-shell crash is easily reproducible by choosing Try Ubuntu when
using a mantic desktop legacy image.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036440/+attachment/5703615/+files/journal.txt
--
You received this bug notification
*** This bug is a duplicate of bug 2036358 ***
https://bugs.launchpad.net/bugs/2036358
** This bug has been marked a duplicate of bug 2036358
systemd wait-online now times out after jammy and lunar upgrade
--
You received this bug notification because you are a member of Ubuntu
Touch
I am also seeing this on Ubuntu 20.04.3 LTS Server. apt upgrade of systemd
"(249.11-0ubuntu3.9, 249.11-0ubuntu3.10)" results in:
Sep 22 22:25:27 mail systemd-networkd-wait-online[420]: Timeout occurred while
waiting for network connectivity.
Sep 22 22:25:27 mail systemd[1]:
Thanks for the tip. Not sure why both were enabled but disabling
systemd-networkd.service fixes the long wait during boot for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service.
Just a note that the pin prompt works under Ubuntu 23.04 after
installing ssh-askpass-gnome. Yubico - Security Key C NFC used.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
I have verified the fix using systemd 249.11-0ubuntu3.11 from jammy-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:jammy jammy
Creating jammy
Starting jammy
nr@six:~$ lxc exec jammy bash
Within the container, after enabling -proposed:
I have verified the fix using systemd 252.5-2ubuntu3.2 in lunar-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:lunar lunar
Creating lunar
Starting lunar
nr@six:~$ lxc exec lunar bash
In the container, after enabling -proposed:
Given that this is required for hardware support, rc3 is tested already
in Debian and other distros, Mantic is an interim release, and also
taking into account Timo's familiarity with the package (see
d/changelog), I'm +1 with this request. I also tested the PPA packages
and they worked fine for
i386 build fixed by a new upstream bugfix
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic
** Bug watch added: github.com/lwindolf/liferea/issues #1306
https://github.com/lwindolf/liferea/issues/1306
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
(In reply to Thomas Zajic from comment #56)
> Is this the same bug that is being discussed here?
No, because the problem here is specific to GTK 4 and has been around
for years. That is, since you didn't have this problem with 2.40, this
bug is not your bug.
You're probably hitting either bug
Hi, seems like I'm a bit late to the party, but anyways ... I recently
reported a bug against liferea (a GTK3 based RSS reader using WebkitGTK
as an HTML rendering engine), where the HTML preview frame would appear
empty with the newly released webkitgtk-2.42.0, while with
webkitgtk-2.40.5 (and
As discussed with the wider security team, we have decided not to push
ahead with this change for mantic and instead will look to enable it
very early in the 24.04 devel cycle . Marking as invalid and
unsubscribing the release team.
** Changed in: apparmor (Ubuntu)
Status: New => Won't Fix
20 matches
Mail list logo
