> Cloud-init users on these releases that wish to see no apparmour warnings
> might locally include this rule themselves via:
>
> echo " /bin/true Uxr," > /etc/apparmor.d/local/sbin.dhclient
Note for other users finding their way here via googling for error
messages: On jammy (22.04) at least,
Hopefully an ubuntu-release-upgrader workaround will be in place soon.
But in a sense this is an ubuntu-meta matter as well. The code in my
merge proposal sets the "Sans" font temporarily, which in lunar means
that either DejaVu Sans or Noto Sans will be used in the UI during the
upgrade (unless
This bug was fixed in the package mesa - 23.2.0~rc4-1ubuntu1
---
mesa (23.2.0~rc4-1ubuntu1) mantic; urgency=medium
* Merge from Debian. (LP: #2036611)
* control, rules: Stay on llvm 15 until bindgen update has landed.
mesa (23.2.0~rc4-1) unstable; urgency=medium
* New
Looks like it's related to this update:
https://launchpad.net/ubuntu/+source/mesa/23.2.0~rc4-1ubuntu1
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from
cogl_gl_create_timestamp_query() from
On 2023-09-26 22:52, Steve Langasek wrote:
> Trying to think in terms of robust general solutions to this problem,
> what if update-manager were to notice when fonts were upgraded, and
> when they are, shut down the GUI connection and reinitialize it?
> This might require saving a bit of state
On Tue, Sep 26, 2023 at 09:38:21PM -, Gunnar Hjalmarsson wrote:
> If I was in a nitpicking mode I would mention that the unreadable
> character problem also affects the desktop itself and possible open
> programs (even if the latter is advised against). So it's not obvious to
> me that the
You have been subscribed to a public bug:
crash after update
wayland session is not accessible anymore
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2037210
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This bug was fixed in the package initramfs-tools - 0.142ubuntu14
---
initramfs-tools (0.142ubuntu14) mantic; urgency=medium
* mkinitramfs: Skip compression support check if /boot/config-${version}
is missing (LP: #2018171)
-- Benjamin Drung Tue, 26 Sep 2023 00:49:57 +0200
I think one thing that could be improved here is the error message. The
error message I get when running the software updater that tells me I
don't have enough space on /boot is suggesting `sudo apt autoremove`
(which doesn't do anything because the default policy I am using keeps
the running
@Nick: That would be an improvement indeed. Guess you abandon /tmp then.
;)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Trying to think in terms of robust general solutions to this problem, what
if update-manager were to notice when fonts were upgraded, and when they
are, shut down the GUI connection and reinitialize it? This might require
saving a bit of state information in update-manager in order to be able to
[Expired for rsyslog (Ubuntu) because there has been no activity for 60
days.]
** Changed in: rsyslog (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Upstream has closed the issue, but I think they have misunderstood the
bug report.
The problem is that contrary to standard resolvers, systemd-resolved is
returning SERVFAIL for this case instead of NXDOMAIN.
Nobody is asking for the query to be forwarded, only for the response
code to be right.
For the near term, I am working on adapting Gunnar's existing work in a
way that we restore the font on the next boot after the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
@bdrung:
$ grep -v '^$\|#' /etc/initramfs-tools/initramfs.conf
/etc/initramfs-tools/conf.d/*
/etc/initramfs-tools/initramfs.conf:MODULES=most
/etc/initramfs-tools/initramfs.conf:BUSYBOX=auto
/etc/initramfs-tools/initramfs.conf:COMPRESS=zstd
/etc/initramfs-tools/initramfs.conf:DEVICE=
Fixed upstream after 1.8.9.
** Changed in: iptables (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2033663
Title:
iptables
It looks it was a problem in iptables, not iptables-persistent.
** Changed in: iptables-persistent (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
Is this still an issue on a newer Ubuntu (22.04 or later)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1738403
Title:
iptables-save duplicates all rules related to
I updated the title to better reflect the status.
** Summary changed:
- iptables-restore is missing -w option
+ [bionic/18.04 only - fixed in newer ubuntu] iptables-restore is missing -w
option
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Bug watch added: bugzilla.netfilter.org/ #1707
http://bugzilla.netfilter.org/show_bug.cgi?id=1707
** Also affects: iptables via
http://bugzilla.netfilter.org/show_bug.cgi?id=1707
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Is this still an issue for you on a newer Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1150153
Title:
TPROXY error 110 "Connection timed out" on specific sites
I updated the title to better reflect the status.
Note that cosmic and disco, noted in the first post, are already in End of Life.
** Summary changed:
- Packaged version of iptables doesn't provide --random-fully flag.
+ [bionic/18.04 only - fixed in newer ubuntu] iptables doesn't provide
I'm running systemd:amd64 249.11-0ubuntu3.10 from jammy-updates on
Ubuntu 22.04.3 LTS.
--
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/2037399
Title:
Processes keep
Hi, extensions options are available on iptables-extensions man page.
Can you check that this is what you need?
** Changed in: iptables (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Is this issue still reproducible on a newer Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1476041
Title:
iptables-save duplicates libvirt and ufw rules on
This has nothing to do with python-debian. The package that isn't
upgraded is dh-python, but the query is actually about whatever UI is
being used to upgrade.
** Package changed: python-debian (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch
Upgrade error not related to python-debian; this is from an interrupt
apt run.
** Package changed: python-debian (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
** Description changed:
In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
where if a service, started earlier than devices are processed by udev,
does `systemctl daemon-reload`, the system shuts down. This is due to
devices for mounted filesystem temporarily taken dead,
** Changed in: ubuntu-meta (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2037425
** Changed in: cairo (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2037186
Title:
Update cairo to 1.18.0
Status in
I was hit this bug and it turned out that for me the best fix was to
start /usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-
agent-1 before using the software-properties-gtk application.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
*I turn off the ¨timer¨ service and the ¨news¨ service.*
*i disable them with systemctl:*
*systemctl disable "the services"*
*then i stop to get the error.*
*the method you show me is not working, i try that as well.*
*It was a long time ago, I already solved this issue a couple of
months
Public bug reported:
I have a number of Ubuntu 22.04 installations on various computers. In
the last month, I have seen more and more log messages like the
following from different systems:
```
systemd[1]: apache2.service: Unit process 70257 (apache2) remains running after
unit stopped.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/2037417
Title:
mantic arm64 images are
Public bug reported:
ubuntu-server in Mantic pulls in zfs userspace packages and systemd
services are automatically enabled, which means zfs kernel modules are
automatically loaded at boot, for everybody. On Raspberry Pi, this
results in +5MB of additional memory consumption which is not
** Changed in: ubuntu-meta (Ubuntu Mantic)
Status: New => In Progress
** Changed in: ubuntu-meta (Ubuntu Mantic)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~dbungert/ubuntu-seeds/+git/ubuntu/+merge/452156
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2037425
Title:
I have done some debugging, but I'm at a loss for what to do next.
Booting with 'apparmor=0' did not help.
Here's what the mounts look like:
# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
journalctl -b --no-pager
** Attachment added: "kopter-journal.log"
https://bugs.launchpad.net/maas-images/+bug/2037417/+attachment/5704620/+files/kopter-journal.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
The last working maas image had kernel 6.3.0-7-generic, the first one to
fail has 6.5.0-5-generic.
--
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/2037417
Title:
mantic
42 matches
Mail list logo
