I forgot to say, the above was after updating systemd to
249.11-0ubuntu3.9
--
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/2009743
Title:
networkd: classless routes served
Here is the requested log. The sequence of operations was:
sudo systemctl restart systemd-networkd
sudo networkctl forcerenew bond0
Sylvain's diagnostic seems to have hit the nail on the head. I see the
following messages in the log:
bond0: DHCP: requested route destination 10.88.88.0/24 is in
click to see https://alsyedconstruction.com/when-do-you-close-on-a-new-
construction-home/
--
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/1922414
Title:
ssh-agent fails to
I also see it on Ubuntu MATE Jammy.
Will the fix come from Xorg,
or should we add LightDM to the affected projects list?
--
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/1922414
Hi Nick,
I disagree with this filesystem name space pollution.
UNIX has a SPACE as parameter separator.
UNIX has a SLASH as filesystem directory separator
DOS has a BACKSLASH as filesystem directory separator
nowadays are directory_names and file_names with SPACES, causing problems
with CLI
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Hi Athos,
Thanks for the review.
Please pause this SRU. There are currently issues that need clarification from
Intel. I will reopen it and update the "[ Where problems could occur ]" section
once the issue is clarified. Thank you.
** Changed in: oem-priority
Status: In Progress =>
Could you refer to some documentation on this restriction (especially -
what actions are allowed/restricted)?
In addition - what was the reason of DROP behaviour? All known to me
system restrictions behave as REJECT - i.e. restricted action gets an
immediate result instead on being stuck until
** Changed in: mesa-amber (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2019212
Title:
Backport packages for 22.04.3 HWE
101 - 109 of 109 matches
Mail list logo