Yes, based on your link this 'work around' disables new cgroups.
: "If for some reason you need to keep the legacy cgroup v1 hierarchy, you
can select it via a kernel parameter at boot time:
systemd.unified_cgroup_hierarchy=0"
however, it at least allows a working session.
on another point:
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Missing depends on whoopsie.
+ whoopsie used in dbus config without depends
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
[ Impact ]
* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.12.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/OpenLDAPUpdates.
[ Major Changes ]
* See the list
Due to a ping on IRC I wanted to summarize the situation here as it
seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out
why and how to fix it)
- if it doesn't work at least fail
-6ubuntu2 is the version that will get to Jammy (22.04), 9ubuntu1 is the
version currently in the devel series (future Kinetic, 22.10).
In general it is preferable to use the version compiled for your current
series, even though using the one in -devel might make sense in a
testing context, as
No it's not fixed, the upstream gdk-pixbuf task got closed because they
don't want to accept new loaders in source so it needs to be fixed in
another component.
We should probably push to integrate it as a new package at some point
but there hasn't been high demand for it so far and it's not
It's still an issue, can we get a fix please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1823098
Title:
/etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf
Status
Tested 249.11-0ubuntu3.3 and DuplicateAddressDetection is now honored as
expected. No other issues were observed.
--
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/1964494
I've tested systemd 249.11-0ubuntu3.3 from jammy-proposed, all looking good!
$ apt list systemd
Listing... Done
systemd/jammy-proposed,now 249.11-0ubuntu3.3 amd64 [installed]
# 1: only "libssl3" is added as a binary dependency (as expected) plus some new
"Suggests":
$ apt-cache depends systemd
** Bug watch added: Red Hat Bugzilla #1941170
https://bugzilla.redhat.com/show_bug.cgi?id=1941170
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1941170
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I think I misunderstood the first time I looked at the upstream issue.
We have the commit that reverts the regressing commit, but not the
follow-on patch (which was not backported to the v259-stable branch).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Please note that nomachine technical support provided me with a
workaround. It works, but I don't understand the implications. This
fixed the problem with xubuntu 22.04. The support notes says it works
for ubuntu 22. 04 as well
In my case I added the kernel setting to GRUB_CMDLINE_LINUX which was
Debian 11's ifupdown 0.8.36 does not contain the /etc/network/if-
up.d/resolved script that contains the DOMAINS=DOMAINS line.
The equivalent functionality in Debian comes from /etc/network/if-
up.d/000resolvconf from the resolvconf package.
(I don't know if these are standard or if these are
was solved in 0.99.beta20-1
** Changed in: libcaca (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925467
Title:
was solved in 0.99.beta20-1
** Changed in: libcaca (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925468
Title:
The issue is now being discussed also on
https://lists.ubuntu.com/archives/ubuntu-devel/2022-June/042116.html
--
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/1972159
Title:
A monitor going blank and then coming back almost always means that a
stable signal (enough bandwidth) can't be maintained.
You should start by trying to replace the DisplayPort cable, or at least
re-plugging the one you have. If that doesn't solve it then to at least
prove the theory please try
Thank you for your bug report. wpa 2.10, which is the version included
in the current Ubuntu serie, has been released in january where the
patch you reference is from 2020, so yes it is included. Could you
perhaps report the issue on gnome-n-d gitlab?
** Changed in: wpa (Ubuntu)
Importance:
@Sebastian, the SRU needs to be verified for the fix to move to updates,
maybe you could help testing the proposed version to help there?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
In case there's more than just that amdgpu kernel crash happening please
also run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
reassigning to miredo then since it seems to be an issue due to this
component
** Package changed: network-manager (Ubuntu) => miredo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I've sponsored/uploaded both the Jammy and Kinetic debdiffs. Kinetic is
accepted, jammy-proposed has to go through SRU.
Removing Sponsors as there is nothing more to sponsor here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
EDS generates instances for recurring events starting at midnight with
an UNTIL date incorrectly. Specifically, using
e_cal_client_generate_instances() or
e_cal_recur_generate_instances_sync() generates an instance one day
after the UNTIL date. This bug was introduced with
** Patch added: "1-1814301-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5597063/+files/1-1814301-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
@tim-ruchardson unified_cgroup_hierarchy=1 is exactly what I want to
enable, and I reported the problem in #1956942, where there is a
reference to https://lists.ubuntu.com/archives/ubuntu-
devel/2021-August/041598.html
the default is hierarchy=unified.
Also, in my configuration docker is using
Thank you for the bug report, upstreamed fixed it for 3.44.3+ so it will
be fixed in Ubuntu when that version lands
** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => Low
** Changed in: evolution-data-server (Ubuntu)
Status: New => Triaged
** Changed in:
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Milestone: None => 2.22.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Public bug reported:
As seen in https://bugs.launchpad.net/ubuntu/+source/obs-
studio/+bug/1978414 with ApportVersion: 2.21.0-0ubuntu2.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook
symb['add_info'](report, ui)
File
This bug still persists. Ubuntu MATE 20.04.4, network-manager
1.22.10-1ubuntu2.3
--
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/1008213
Title:
Missing depends on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
I've proposed the change to Debian: https://salsa.debian.org/sdeziel-
guest/quassel/-/merge_requests/1
--
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/1814302
Title:
31 matches
Mail list logo
