** Summary changed:
- Why is the full xorg package being installed in Mantic?
+ Why is the full xorg package being installed in Noble?
** Tags removed: lunar
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The amdgpu kernel driver here doesn't seem to be from Ubuntu so we can't
track its bugs here.
Please consider uninstalling the drivers that are presumably from AMD,
then reboot and report new bugs to Ubuntu for any issues you find.
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New =>
Thanks for the bug report. Please try logging into Wayland instead.
There is a menu in the corner of the login screen where you can select
Ubuntu (which is Wayland) or Ubuntu on Xorg.
Also it looks like your kernel driver amdgpu/6.2.4-1683306.22.04 did not
come from Ubuntu so please also try
[Expired for isc-dhcp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: isc-dhcp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
[Expired for casper (Ubuntu) because there has been no activity for 60
days.]
** Changed in: casper (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** 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/2045196
Title:
two monitors have night light, one does not
Status in xorg package
You have been subscribed to a public bug:
Two monitors have night light, one does not. It's on a scheduler
(although I don't think the scheduler is turning it off properly once
it's on, either) for sunset and sunrise. Including a screen shot. Tried
turning it off and on again in display settings
@kerneldude - do you know if MITRE ever assigned a CVE for this?
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
The verification of the Stable Release Update for apparmor has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package apparmor - 2.13.3-7ubuntu5.3
---
apparmor (2.13.3-7ubuntu5.3) focal; urgency=medium
* apparmor.preinst: recursively remove cache directories during a
upgrade. (LP: #2032851)
-- Georgia Garcia Tue, 10 Oct 2023
09:20:12 -0300
** Changed in:
** Changed in: ubuntu-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1801762
Title:
Dual-signed things should be
** Description changed:
Ubuntu 20.04, Linux Mint 20.3, amd64
network-manager 1.22.10-1ubuntu2.3
+
+ $ nmcli -v
+ nmcli tool, version 1.22.10
I wanted to script nmcli to make configuration of WiFi of IoT device
easy but it is not an easy task. I assume this is a bug in nmcli design,
** Description changed:
Ubuntu 20.04, Linux Mint 20.3, amd64
network-manager 1.22.10-1ubuntu2.3
I wanted to script nmcli to make configuration of WiFi of IoT device
easy but it is not an easy task. I assume this is a bug in nmcli design,
not specific to Ubuntu...
The problem.
** Description changed:
Ubuntu 20.04, Linux Mint 20.3, amd64
network-manager 1.22.10-1ubuntu2.3
I wanted to script nmcli to make configuration of WiFi of IoT device
easy but it is not an easy task. I assume this is a bug in nmcli design,
not specific to Ubuntu...
The problem.
** Description changed:
Ubuntu 20.04, Linux Mint 20.3, amd64
network-manager 1.22.10-1ubuntu2.3
I wanted to script nmcli to make configuration of WiFi of IoT device
easy but it is not an easy task. I assume this is a bug in nmcli design,
not specific to Ubuntu...
The problem.
** Description changed:
Ubuntu 20.04, Linux Mint 20.3, amd64
network-manager 1.22.10-1ubuntu2.3
I wanted to script nmcli to make configuration of WiFi of IoT device
easy but it is not an easy task. I assume this is a bug in nmcli design,
not specific to Ubuntu...
The problem.
Public bug reported:
Ubuntu 20.04, Linux Mint 20.3, amd64
network-manager 1.22.10-1ubuntu2.3
I wanted to script nmcli to make configuration of WiFi of IoT device
easy but it is not an easy task. I assume this is a bug in nmcli design,
not specific to Ubuntu...
The problem. IoT devices with WiFi
This bug was fixed in the package gst-plugins-bad1.0 - 1.16.3-0ubuntu1.1
---
gst-plugins-bad1.0 (1.16.3-0ubuntu1.1) focal-security; urgency=medium
[ Luís Infante da Câmara ]
* SECURITY UPDATE: Heap buffer overflow in dvdspu (LP: #2035585)
-
Note to future mdeslaur: re-mashing the retry button will eventually
result in the test passing and the build succeeding.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
*** This bug is a duplicate of bug 1043298 ***
https://bugs.launchpad.net/bugs/1043298
** This bug has been marked a duplicate of bug 1043298
more information about errors on update failure
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
*** This bug is a duplicate of bug 2032851 ***
https://bugs.launchpad.net/bugs/2032851
Hi Herb!
The fix is already on the way and should be available to you soon. Meanwhile,
as a workaround, you can remove the /etc/apparmor.d/cache/e10c1cf9.0 directory
with
rm -r
Since the mentioned commit will be in v255, this will be fixed for Noble
when we ship v255. Nothing to do there. I'm just going to mark "invalid"
for systemd for that reason.
For Jammy, Lunar, and Mantic, we can SRU this change in systemd-hwe.
** Changed in: systemd (Ubuntu)
Status: New
Public bug reported:
Investigate why systemds fails for amd64 and armhf.
For amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20231127_110919_522a6@/log.gz
Armfh https://autopkgtest.ubuntu.com/results/autopkgtest-
*** This bug is a duplicate of bug 2032851 ***
https://bugs.launchpad.net/bugs/2032851
Hi Georgia,
Your response is greatly appreciated.
Long story short:
I have a beautiful dual-boot Ubuntu setup now.
I have a 22.04 and an 18.04 on a 500gig hard drive.
Really working well.
Thanks.
Fixed in v0.107 https://github.com/canonical/netplan/releases/tag/0.107
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Also affects: systemd-hwe (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd-hwe (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Mantic)
** Changed in: heimdal (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2036253
Title:
FTBFS: missing strl* symbols fail the
** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The first container reboot fails because seeding takes too long (which
is bug 1878225). Then the hack kicks in and a second image build is
attempted with also fails. The hack masks the problematic services
9811s Created symlink /etc/systemd/system/snapd.service → /dev/null.
9817s Created symlink
How about directly sending a SIGSEGV or a SIGABRT to a working
teamviewer process using kill(1) ? That's what I usually do when I test
apport crash reporting code, this might trigger the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
2023-11-29T11:00:34.713689+00:00 mantic-test systemd[1]: Reached target
cloud-init.target - Cloud-init target.
2023-11-29T11:00:34.713731+00:00 mantic-test systemd[1]: Startup finished in
5.934s.
2023-11-29T11:00:34.766612+00:00 mantic-test systemd[1]: dmesg.service:
Deactivated successfully.
Ok that's not it. It looks like a container reboot takes longer than 1
min with newer kernels resulting in a timeout error and subsequent
failure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
>From my limited testing, it looks like it was introduced in 6.5.0-10.10.
--
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/2038433
Title:
systemd autopkgtest regression on
So the workaround for the above in systemd/debian/tests/tests-in-lxd is
problematic?
--
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/2038433
Title:
systemd autopkgtest
Oh -> bug 1878225
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in
Is seems the container fails to boot. From a bad run:
9109s autopkgtest [10:39:17]: test tests-in-lxd: [---
9145s 2023-11-28T10:39:50Z INFO Waiting for automatic snapd restart...
9259s lxd 5.19-8635f82 from Canonical** installed
9288s Creating autopkgtest-prepare-jhI
9475s
Looks like we should backport https://salsa.debian.org/vim-
team/vim/-/commit/16884ac6857d1499839649f061b966e276122666
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1968912
38 matches
Mail list logo
