While retries on DNS resolution failures does not work for cloud-
init.service for environments running NetworkManager.service (desktop
live ISOs), I have found that the retries work where systemd-networkd is
bringing up network config (server live ISOs). This is because cloud-
init.service is
Can you take a photo of the problem?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
This bug was fixed in the package systemd - 252.5-2ubuntu2
---
systemd (252.5-2ubuntu2) lunar; urgency=medium
* network/dhcp4: accept local subnet routes from DHCP (LP: #2004478)
File:
debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch
This is/was a common issue on AMD systems. I think the 5.14 OEM kernel
here is missing this fix:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1344#note_932943
But if it's still happening in later kernels then it might be related
to:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470
This issue with NetworkManager.service and systemd is reminiscent of the
related feature request against systemd-networkd
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912 that also
points out the ordering issues.
--
You received this bug notification because you are a member of
I have HP EliteBook 860 G9. The earliest kernel version where ALC245
worked with speakers is 6.1.8 (Arch Linux 2023.02.01).
dmesg | grep -i speaker
[ 26.424223] input: PC Speaker as /devices/platform/pcspkr/input/input12
[ 28.118123] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245:
The attachment "isc-dhcp-apparmor-scripts-disable-fix.debdiff" seems to
be a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment,
Also affected. Downgrading to 2.9 worked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1972790
Title:
Can't connect to hotspot created on ubuntu
Status in wpa package in
TLDR: My earlier suggestion to retry in cloud-init.service while
awaiting DNS is not viable when thinking about NetworkManager.
NetworkManager.service is After=sysinit.target due to After=dbus.service
and cloud-init.service is Before=sysinit.target. NetworkManager is the
only service bringing up
The fix/commit is applied in v5.12, thus available on Jammy
(v5.15-based).
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
~/git/linux$ git describe --contains 4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
I can confirm Dan's validation that After=systemd-resolved.service doesn't buy
us anything here because, although systemd-resolved.service is up,
NetworkManager.service && NetworkManager-wait-online.service don't finish
bringing link up for related network devices until After=dbus.service
Debdiff in the attached enables dhclient to execute dhclient with -sf
/bin/true
** Patch added: "isc-dhcp-apparmor-scripts-disable-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+attachment/5654529/+files/isc-dhcp-apparmor-scripts-disable-fix.debdiff
--
You
Public bug reported:
In some cases, it may be desirable to disable dhclient scripts. By
default /sbin/dhclient-script is used, and some others are allowed by
the apparmor profile.
Without Apparmor, disabling hook scripts can be accomplished with flags
-sf /bin/true, but with apparmor enabled
Found this guy, thanks him -
https://launchpad.net/~ubuntuhandbook1/+archive/ubuntu/libgweather
--
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/1918044
Title:
(Update
Good day.
As I understand, I should somehow change libgweather to 3.36.2. Is there any
instruction manual for that? I can see some tarball in repo
https://download.gnome.org/sources/libgweather/3.36/libgweather-3.36.2.tar.xz
but have no idea how to proceed.
--
You received this bug
I'm also going back to the tabular network state printed out by in
cloud-init.service shows: that the primary network interface is still
down at this point in boot, which it shouldn't be. cloud-init should be
waiting on the presence of link up before starting it's cloud-
init.service (network boot
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2011615
Title:
BIOS
Status in xorg package in Ubuntu:
New
Bug description:
You have been subscribed to a public bug:
It seems to me that BIOS has driver problem.
When booting the error BIOS message it is showed every time.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-37.38-generic 5.19.17
Uname: Linux
Public bug reported:
Commands like this:
rsync -a host.example.org:\{this,that} .
have worked for decades, in multiple Ubuntu versions, but were broken by the
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type
that command).
(To be clear, the backslash there
Focal is in soft freeze atm, once the soft freeze is lifted this should
land
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1964636
Title:
Incorrect handling of apparmor
Focal is in soft freeze atm, once that is lifted this should land
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1993353
Title:
Add posix message queue IPC mediation
The verification passed for jammy:
```
william@william-Latitude-E7470 ~ apt-cache policy udev
udev:
Installed: 249.11-0ubuntu3.7
Candidate: 249.11-0ubuntu3.8
Version table:
*** 249.11-0ubuntu3.8 500
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64
Packages
Is this issue blocked by something?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1728130
Title:
Policy needs improved feature versioning to ensure it is correctly
Is there something blocking the release for focal?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1964636
Title:
Incorrect handling of apparmor `bpf` capability
Status
Is there something blocking the release for focal? Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1993353
Title:
Add posix message queue IPC mediation
Status in
Thank you all for your attention on this bug.
Sorry my earlier comment on this bug was ill-informed and incorrect. I'm able
to reproduce this as well through the server installer qemu/kvm based installs
as well so I can confirm as well that this isn't/wasn't NetworkManager and
I played with a two variation of dropping in some after directives, but
obtained similar failing results where the network state was not what
cloud-init wanted at the time it started.
@Chad - what's your thoughts on some service reordering?
--
You received this bug notification because you are
*** This bug is a duplicate of bug 2011313 ***
https://bugs.launchpad.net/bugs/2011313
** This bug has been marked a duplicate of bug 2011313
gnome-control-center crashes after launch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
FWIW you can test this out by adding a drop-in config:
$ cat > /etc/systemd/system/cloud-init.service.d/10-after-systemd-resolved.conf
<< EOF
[Service]
After=systemd-resolved.service
EOF
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2011575
Title:
Cursor used during log in after boot still on screen after log in
You have been subscribed to a public bug:
After booting up my laptop and logging in, the cursor that is used
during the log in phase just freezes on the spot it last was after
pressing the enter key to log in and stays there the whole usage time.
It only disappears when I restart or shut down the
It appears we have the following *ordering* relationship between
systemd-resolved.service, cloud-init.service, network.target, and
network-online.target:
network-online.target
/ \
/.. \
/.\
This bug was fixed in the package gnome-shell-extension-appindicator -
53-1
---
gnome-shell-extension-appindicator (53-1) experimental; urgency=medium
* New upstream release
* appIndicator: Wait for style change if no stage is set
* appIndicator: Reuse already imported
This bug was fixed in the package sysvinit - 3.06-2ubuntu1
---
sysvinit (3.06-2ubuntu1) lunar; urgency=medium
* Merge with Debian unstable (LP: #2007421). Remaining changes:
- When building for Ubuntu, skip all binaries except for sysvinit-utils
- Fix absence of
** Tags added: focal jammy kinetic lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1735002
Title:
Allow configuring Wi-Fi MAC Randomization feature from GUI
Attached the wrong debdiff. 2022g-0ubuntu0.16.04+esm1 is the correct
one.
** Patch added: "tzdata_2022g-0ubuntu0.16.04+esm1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5654400/+files/tzdata_2022g-0ubuntu0.16.04+esm1.debdiff
--
You received this bug
Attached debdiff for xenial and also pushed to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata
** Patch added: "tzdata_2022g-0ubuntu0.18.04.debdiff"
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654393/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I attached some logs that might be useful. After checking it again I
realized that the syslog timestamps are a little off when compared to
the systemd journal.
As shown in the timeline.txt (attached), cloud-init and systemd-resolved
are starting at the same time.
So the name resolution might not
** Attachment added: "timeline.txt"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654394/+files/timeline.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "systemd_journal.txt"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654392/+files/systemd_journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
See: https://bugs.launchpad.net/bugs/1890177
I am opening a new ticket because I believe there may have been a
regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still
see this issue.
/etc/rsyslog.d/90-google.conf:
# Google Compute Engine default console
** Changed in: rsync (Ubuntu Jammy)
Status: New => Invalid
** Changed in: rsync (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: rsync (Ubuntu Lunar)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This bug was fixed in the package backintime - 1.2.1-3ubuntu0.3
---
backintime (1.2.1-3ubuntu0.3) jammy-security; urgency=medium
* Fix compatibility with rsync security update (LP: #2009756)
- debian/patches/rsync_compat.patch: fix changes to argument protection
in
This bug was fixed in the package backintime - 1.3.2-0.1ubuntu0.2
---
backintime (1.3.2-0.1ubuntu0.2) kinetic-security; urgency=medium
* Fix compatibility with rsync security update (LP: #2009756)
- debian/patches/rsync_compat.patch: fix changes to argument protection
in
** Changed in: netplan
Status: New => Invalid
--
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/2008952
Title:
DNS failure while trying to fetch user-data
Status in
No crash reports from gnome-shell 44 yet. I'm hopeful this was fixed
by/around the same time as https://gitlab.gnome.org/GNOME/gnome-
shell/-/commit/1559f03a82317e06aa0596bf12feb8b761a58f52
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Maybe we need some additional systemd service ordering, to make systemd-
resolved start before calling into the DHCP client, so that it can
properly receive the DNS servers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The upstream PR has been merged and we got the new glib serie in Lunar
so assuming it's fixed there
** Changed in: glib2.0 (Ubuntu Lunar)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The #1 gnome-shell crash in 23.04 is currently:
https://errors.ubuntu.com/problem/fa3beeb1c25d862ecb2a0900c2b2519503a6109d
which actually sounds like this bug. See also bug 2011429.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
50 matches
Mail list logo
