I'm not sure what the intended configuration of these two packages is.
On one (older) lunar system I find neither installed. On a fresh lunar
install however I find pipewire-alsa but no pulseaudio. Neither package
is seeded so it seems either of those configurations is valid.
They do definitely
https://forum.ubuntu.org.cn/viewtopic.php?t=493946这是修改的方法， 可以先看一下。
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2016950
Title:
ubuntu 23.o4 新安装ssh默认端口修改不成功
Status in
昨天试了发布的正式版，不管是桌面版还是Server的版本，通过修改sshd_config文件来改默认22端口都是失败的，
不知道是什么原因，不能每次都修改socket的文件吧， 关键是还有别的安全方面的东西需要配置的。
** Changed in: openssh (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
By default, /etc/systemd/logind.conf sets HandlePowerKey to poweroff. This is
a terrible default, because this poweroff action does not ask for any
confirmation whatsoever, encouraging data loss. The power key does get pressed
inadvertently from time to time:
- It's
This just happened while I was watching Twitch, had Amazon open, and
just opened Disney+
And it happened multiple times in multiple minutes
** Attachment added: "journal_230420.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2016435/+attachment/5665959/+files/journal_230420.txt
--
Public bug reported:
Upgrading from 18.04 to 20.04.
No space left on /boot.
Solved by changing compression from lz4 to xz and regenerating before reboot.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 5.4.0-147.164-generic
The issue I experienced here, with ~0 bytes free on /boot, produces a
more clear "no space left" error than other initramfs-tools post-
installation bugs.
See Df.txt;
/dev/sda1 238924232193 0 100% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2017182
Title:
package initramfs-tools 0.136ubuntu6.7 failed to
Like #3 experienced, logs seems to make it plausible that this is caused
by inadequate storage on /boot.
See Df.txt;
/dev/sda1 240972190591 37940 84% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic
Error 24 :
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/sdb2 241965 197598 31875 87% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
Error 24 : Write error : cannot write compressed
This one is different from other initramfs-tools post-installation
errors. /boot is on / which has plenty of space, but update-initramfs is
missing /boot/initrd.img-5.4.0-37-generic.new.
See Df.txt;
/dev/sda5 436953712 8324136 406363876 3% /
/dev/sda1 523248 4523244 1%
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/sda1 240972 192901 35630 85% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-39-generic
Error 24 : Write error : cannot write
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/md0 235691 183367 35848 84% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
Error 24 : Write error : cannot write compressed block
E:
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/sda1 240972 191360 37171 84% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-45-generic
Error 24 : Write error : cannot write compressed block
E:
This seems to be caused by bad installation state of package initramfs-
tools-core which should have provided file /usr/share/initramfs-
tools/scripts/functions together with /usr/sbin/mkinitramfs tool.
See end of DpkgTerminalLog.txt;
update-initramfs: Generating
This particular issue seems to be caused by a mismatch between a
specific software suspend partition being specified in ininitramfs-tools
config and the available partitions. Not inadequate storage on /boot.
See end of DpkgTerminalLog.txt;
update-initramfs: Generating
The plan is for MAAS to enable apparmor for Lunar onwards. Older
releases were always deployed without apparmor and I think changing this
would be dangerous, as we don't know how many customers are relying on
the current behaviour.
--
You received this bug notification because you are a member
On Mon, Apr 17, 2023 at 01:30:11PM -, Nick Rosbrook wrote:
> Odd. Does `systemctl show --propoerty=RuntimeMaxUSec session-2.scope`
> show the same thing, or something different?
For a current session, which is session-93.scope, I see in the file:
RuntimeMaxSec=1h 38min 56s
And from
@Andreas
Replying about the accountsservice part, we got some issues resolved
there before the release but the bug here is a different problem then
the one addressed in accountsservice 22.08.8-1ubuntu7.
The issue is in the indicator codebase and the right fix is what has
been uploaded for
No. Issue is resolved for me now since I have deleted /etc/resolv.conf
and a link to /run/systemd/resolve/stub-resolv.conf was created. The
upgrade then completed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Summarizing this bug from an SRU POV
We need https://launchpad.net/ubuntu/+source/indicator-
messages/13.10.1+18.10.20180918-0ubuntu5 in lunar. Previous upload of
0ubuntu4 failed to migrate/build (see comment #24), and I guess 0ubuntu5
arrived too late for the release.
We also have
Tested with kernel 5.4.0-149.166 in focal. Test plan works Ok.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Lunar kernel will need SRU to be fixed up.
And separately, we could check if we can get rid of apparmor=0 for all
supported releases or not, in next mass release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Now about those bugs, it is true that apparmor and overlayfs used to not
play along.
Depending on support matrix we can attempt to turn apparmor back on.
Equally it is buggy that Ubuntu kernel does not work with apparmor
turned off.
It would be nice to investigate if we can at least enable
I confirm this dirty hack makes MAAS successfully deploy Lunar:
--- a/src/provisioningserver/kernel_opts.py
+++ b/src/provisioningserver/kernel_opts.py
@@ -111,9 +111,6 @@ def compose_purpose_opts(params):
"cc:{'datasource_list': ['MAAS']}end_cc",
# Read by cloud-init.
MAAS started to set `apparmor=0` to fix
https://bugs.launchpad.net/maas/+bug/1677336 due to
https://bugs.launchpad.net/maas/+bug/1408106
This seems to no longer affect Lunar (and probably a few releases before
that)
--
You received this bug notification because you are a member of Ubuntu
Touch
I can confirm @xnox's findings with my maas server deploying lunar.
Adding `apparmor=1` to the settings/configuration/kernel-parameters
allows for a successful deployment with the lunar 6.2.0-20.20 kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Is your system still in this state? If so what does ls -alh
/etc/resolv.conf show? This error is weird, because this `cp` in the
systemd-resolved.postinst is guarded by checks to see if
/etc/resolv.conf is already a symlink to /run/systemd/resolve/stub-
resolv.conf...
Setting up systemd-resolved
** Tags removed: need-duplicate-check
--
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/2017169
Title:
package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade:
** Description changed:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which I
don't believe was part of the 20230319 serial. I don't have access to
the maas server, so I can't directly check any log
Public bug reported:
updating to new release of ubuntu took issue with a modified
/etc/systemd/resolved.conf
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: systemd-resolved 252.5-2ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2016908
and then change the status of the bug to 'Confirmed'.
If, due to the
horay i managed to reproduce it locally.
** Also affects: linux (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/2016908
We talked about it and agreed on the following changes:
- don't patch the libnssckbi.so library path anymore, as that one is working in
the original code
- for libnsspem.so, use a debian architecture macro that respects cross
compiles and uses the target arch instead of the host one.
--
You
We discussed fixes to the maas bootloader builds and as a result, we
have a new maas bootloader which should have the latest shim and grub:
http://images.maas.io/ephemeral-v3/candidate/bootloaders/uefi/amd64/20230420.0/
I manually copied these to my test maas, it did not resolve the issue
(or
As I understand it, libnsspem.so is the one in the "wrong" place:
/usr/lib/$ARCH/nss/libnsspem.so
A quick apt-file search on lunar shows that is the only package that
puts something in /usr/lib/$ARCH/nss.
I appended this config to my ~/.pki/nssdb/pkcs11.txt file to test search
paths:
I am annoyed that i cannot reproduce this locally outside of MAAS.
--
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/2016908
Title:
Unable to deploy hosts with lunar images
Adding the language-selector package, since many fontconfig files
affecting Chinese rendering are provided by language-selector-common.
** Also affects: language-selector (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
One thought is to ask why we still install the fonts-arphic-uming
package when installing Chinese (Simplified as well as Traditional).
Probably it is of historical reasons from the time before Noto existed.
But let's consider that to be a matter of its own. Even if AR PL UMing
is available, Noto
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: krb5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2017149
Title:
package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed
Public bug reported:
Unknown
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.12
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
AptOrdering:
> Instead, `add-apt-repository` should call `getArchiveSubscriptionURL`
(not `getArchiveSubscriptionURLs`)
this doesn't seem to work correctly.
For example:
In [25]: lp.me.getArchiveSubscriptionURLs()
Out[25]:
@Gunnar Hjalmarsson:
I have attached the screenshot at
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/2
+ Both Firefox and snap-store are displayed with UMing
+ The webpage in Firefox is displayed with UMing
+ Non-snap applications uses Noto
** Summary changed:
-
@Shengjing Zhu: Can you confirm that it's only in snap applications you
see UMing instead of Noto? Btw, is it limited to Snap Store, or is the
FF snap affected as well?
Also: Is Noto used as expected
- when browsing web sites with Chinese contents
- in the desktop itself, e.g. Settings
**
Public bug reported:
[ Impact ]
VA-API decoding doesn't work on DCN 3.1.4.
Mesa 22.2.5 includes all the code to support it but is missing the chip ID.
The device ID was included in upstream mesa 22.3.1.
[ Test Plan ]
* Verify that VA-API works using "mpv" or a similar tool that uses VA-API
*
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fontconfig (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
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.
I think we all understand the direction here, Jeremy. You don't care
about non-paying users.
I'm not sure what being an Ubuntu Member means any more but what the
point if part of that isn't speaking out when there's a problem, and I
have to say that removing freedoms from users is about as big a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Package changed: apport (Ubuntu) => apport-symptoms (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2016712
Title:
Sound/audio related problems option never
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I tried to reproduce this behavior, but got bug #2017120 instead.
Relevant failure there:
Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio
daemon running, or not running as session daemon.
Public bug reported:
1. ubuntu-bug
2. Sound/audio related problems
Then you get a dialog: "PulseAudio seems to have crashed. Do you with to
report a bug?"
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic
The problem has gone away and direct scanout is working. Now I get 60
FPS fullscreen.
I can only imagine direct scanout wasn't being used for some reason
because if I disable that then I can synthesise this bug again. But
under those circumstances it's really bug 2017097.
** Changed in: glmark2
Kernel side:
kernel/sys.c::SYSCALL_DEFINE5(prctl, int, option,...):
{
struct task_struct *me = current;
unsigned char comm[sizeof(me->comm)];
long error;
error = security_task_prctl(option, arg2, arg3, arg4, arg5);
if (error != -ENOSYS)
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/2017090
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hi, indeed I forget the store is also snap.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076
Title:
default Chinese font is ugly
Status in fontconfig package in
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS
+ [raspi] glmark2-wayland --fullscreen stutters visually while reporting
hundreds of FPS
--
You received this bug
It looks like this issue mostly affects Snap apps.
Please see the font config debug output attached.
** Attachment added: "font config debug output"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5665442/+files/fc-debug.log
--
You received this bug
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/2017076
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
上午做了一下测试发现， 修改/etc/systemd/system/ssh.socket.d/listen.conf这个文件确实可以修成功，
但是修改sshd_config文件还是没有效果。另4月18号的镜像在thinkpad T14 Gen2的机器上安装新系统，装完后发现启动失败
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2017083
Title:
package linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
@enr0n: Thanks for your help.
I've deleted my old comment because I messed up the output of the
container.
Here are the outputs of your test script. Output of the host:
hostsystem ~ # bash /tmp/test.sh
cgroupsv1
Output of the container:
container ~ $ bash /tmp/test.sh
hybrid
So, there is a
We should let Noto CJK has higher priority.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076
Title:
default Chinese font is ugly
Status in fontconfig package in
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5665408/+files/2023-04-20_14-14.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
Public bug reported:
After installs Ubuntu 23.04 with Chinese language selected, the default
font is chosen to AR PL UMing CN, which is very ugly.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: fontconfig 2.14.1-3ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux
69 matches
Mail list logo
