系统信息：
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
当我运行时snap list，出现以下异常：
错误：无法列出快照：无法添加授权：用户：未知用户 ID 1532788159
我也无法打开 Firefox 或 snap 商店。
创建timidity.service文件和相关符号链接以便在系统重启时自动启动服务后，我重新启动系统并输入以下输入：
sudo systemctl status timidity
输出：
× timidity.service - TiMidity++ Daemon
Loaded: loaded (/lib/systemd/system/timidity.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-10-07 16:34:46 CEST; 50s ago
Process: 635 ExecStart=/usr/bin/timidity -iA Os (code=exited, status=1/FAILURE)
Main PID: 635 (code=exited, status=1/FAILURE)
CPU: 31ms
ott 07 16:34:46 netcom-Vostro-15-3510 systemd[1]: Started TiMidity++ Daemon.
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: jack_client_new: deprecated
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: Cannot connect to server socket err = No such file or directory
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: Cannot connect to server request channel
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: jack server is not running or cannot be started
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: Couldn't open output device
ott 07 16:34:46 netcom-Vostro-15-3510 systemd[1]: timidity.service: Main process exited, code=exited, status=1/FAILURE
ott 07 16:34:46 netcom-Vostro-15-3510 systemd[1]: timidity.service: Failed with result 'exit-code'.
我的用户名与该群组相关联audio。
符号链接：
/usr/lib/systemd/system/multi-user.target.wants/timidity.service
服务：
/usr/lib/systemd/system/timidity.service
包含：
[Unit]
Description=TiMidity++ Daemon
After=sound.target
Requires=sound.target
[Service]
ExecStart=/usr/bin/timidity -iA Os
Type=simple
[Install]
WantedBy=multi-user.target
我还尝试将“timidity.service”文件更改为以下内容：
[Unit]
Description=TiMidity++ Daemon
After=pulseaudio.service
Requires=pulseaudio.service
[Service]
ExecStart=/usr/bin/timidity -iA Os
Type=simple
[Install]
WantedBy=multi-user.target
但再次重启系统后，错误仍然相同。
尝试在系统已启动的情况下从终端手动启动服务，服务正确启动。
我做错什么了？
刚刚升级到 24.04.1 LTS，但我的 emacs 配置文件无法再加载。出现此错误：
文件丢失：无法打开加载文件，没有此文件或目录，关联
似乎 lisp 再也找不到“assoc”了。在从 22LTS 升级之前，这个功能还有效。
GNU Emacs 29.3（build 1，x86_64-pc-linux-gnu，GTK+ 版本 3.24.41，cairo 版本 1.18.0）于 2024-04-01 发行，由 Debian 修改
uname -a Linux BBalien 6.8.0-45-generic #45-Ubuntu SMP PREEMPT_DYNAMIC 星期五 8 月 30 日 12:02:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
我正在安装 redis，遇到 php8.3-fpm 安装错误。以下是相关的安装消息：
apt install redis-server
...
...
Setting up php8.3-fpm (8.3.6-0ubuntu0.24.04.2) ...
NOTICE: Not enabling PHP 8.3 FPM by default.
NOTICE: To enable PHP 8.3 FPM in Apache2 do:
NOTICE: a2enmod proxy_fcgi setenvif
NOTICE: a2enconf php8.3-fpm
NOTICE: You are seeing this message because you have apache2 package installed.
Job for php8.3-fpm.service failed because a timeout was exceeded.
See "systemctl status php8.3-fpm.service" and "journalctl -xeu php8.3-fpm.service" for details.
invoke-rc.d: initscript php8.3-fpm, action "restart" failed.
× php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager
Loaded: loaded (/usr/lib/systemd/system/php8.3-fpm.service; enabled; preset: enabled)
Active: failed (Result: timeout) since Sun 2024-10-06 13:52:03 CEST; 16ms ago
Docs: man:php-fpm8.3(8)
Process: 285882 ExecStart=/usr/sbin/php-fpm8.3 --nodaemonize --fpm-config /etc/php/8.3/fpm/php-fpm.conf (code=exited, status=0/SUCCESS)
Process: 285889 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/8.3/fpm/pool.d/www.conf 83 (code=exited, status=0/SUCCESS)
Main PID: 285882 (code=exited, status=0/SUCCESS)
CPU: 90ms
Oct 06 13:50:33 Ubuntu-2404-noble-amd64-base systemd[1]: Starting php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager...
Oct 06 13:52:03 Ubuntu-2404-noble-amd64-base systemd[1]: php8.3-fpm.service: start operation timed out. Terminating.
Oct 06 13:52:03 Ubuntu-2404-noble-amd64-base systemd[1]: php8.3-fpm.service: Failed with result 'timeout'.
Oct 06 13:52:03 Ubuntu-2404-noble-amd64-base systemd[1]: Failed to start php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager.
dpkg: error processing package php8.3-fpm (--configure):
installed php8.3-fpm package post-installation script subprocess returned error exit status 1
Setting up libjemalloc2:amd64 (5.3.0-2build1) ...
Setting up liblzf1:amd64 (3.6-4) ...
Setting up redis-tools (5:7.0.15-1build2) ...
Setting up redis-server (5:7.0.15-1build2) ...
Created symlink /etc/systemd/system/redis.service → /usr/lib/systemd/system/redis-server.service.
Created symlink /etc/systemd/system/multi-user.target.wants/redis-server.service → /usr/lib/systemd/system/redis-server.service.
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.3) ...
Errors were encountered while processing:
php8.3-fpm
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Systemctl 和 yournalctl 消息并不是特别具有描述性 - 只是说 php8.3-fpm 无法启动，结果为“超时”。
错误似乎出在dpkg处理上php8.3-fpm：installed php8.3-fpm package post-installation script subprocess returned error exit status 1
内容/var/lib/dpkg/info/php8.3-fpm.postinst：
#!/bin/sh
set -e
if [ -e /usr/share/apache2/apache2-maintscript-helper ]; then
. /usr/share/apache2/apache2-maintscript-helper
php_enable() {
# Don't enable PHP FPM by default when Apache 2 is installed
apache2_msg notice "NOTICE: Not enabling PHP 8.3 FPM by default."
apache2_msg notice "NOTICE: To enable PHP 8.3 FPM in Apache2 do:"
apache2_msg notice "NOTICE: a2enmod proxy_fcgi setenvif"
apache2_msg notice "NOTICE: a2enconf php8.3-fpm"
apache2_msg notice "NOTICE: You are seeing this message because you have apache2 package installed."
return 1
}
else
php_enable() {
# Don't enable PHP FPM by default when Apache 2 is not installed
return 1
}
fi
if [ "$1" = "triggered" ] && [ "$2" = "/etc/php/8.3/fpm/conf.d" ]; then
invoke-rc.d php8.3-fpm restart
fi
CONFDIR=/etc/php/8.3/fpm/conf.d
if [ "$1" = "configure" ]; then
phpini="/etc/php/8.3/fpm/php.ini"
if [ "fpm" = "cli" ]; then
ucf /usr/lib/php/8.3/php.ini-production.fpm $phpini
else
ucf /usr/lib/php/8.3/php.ini-production $phpini
fi
ucfr php8.3-fpm $phpini
if [ -e /usr/lib/php/php-maintscript-helper ]; then
. /usr/lib/php/php-maintscript-helper
mods=$(phpquery -M -v 8.3)
for mod in $mods; do
php_invoke enmod 8.3 fpm $mod
done
fi
if [ -n "$2" ] && dpkg --compare-versions "$2" lt "7.0.3-2~"; then
rm -f /etc/php/8.3/fpm/conf.d/20-opcache.ini;
fi
fi
# Automatically added by dh_apache2/UNDECLARED
if php_enable; then
if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
. /usr/share/apache2/apache2-maintscript-helper
for conf in php8.3-fpm ; do
apache2_invoke enconf $conf || exit 1
done
fi
fi
# End automatically added section
# Automatically added by dh_systemd_enable/13.14.1ubuntu5
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
# The following line should be removed in trixie or trixie+1
deb-systemd-helper unmask 'php8.3-fpm.service' >/dev/null || true
# was-enabled defaults to true, so new installations run enable.
if deb-systemd-helper --quiet was-enabled 'php8.3-fpm.service'; then
# Enables the unit on first installation, creates new
# symlinks on upgrades if the unit file has changed.
deb-systemd-helper enable 'php8.3-fpm.service' >/dev/null || true
else
# Update the statefile to add new symlinks (if any), which need to be
# cleaned up on purge. Also remove old symlinks.
deb-systemd-helper update-state 'php8.3-fpm.service' >/dev/null || true
fi
fi
# End automatically added section
# Automatically added by dh_installinit/13.14.1ubuntu5
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -x "$(command -v systemd-tmpfiles)" ]; then
systemd-tmpfiles ${DPKG_ROOT:+--root="$DPKG_ROOT"} --create php8.3-fpm.conf || true
fi
fi
# End automatically added section
# Automatically added by dh_installdeb/13.14.1ubuntu5
dpkg-maintscript-helper rm_conffile /etc/init/php8.3-fpm.conf 7.4.3-4\~ php8.3-fpm -- "$@"
# End automatically added section
# Automatically added by dh_installinit/13.14.1ubuntu5
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/etc/init.d/php8.3-fpm" ]; then
update-rc.d php8.3-fpm defaults >/dev/null
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
invoke-rc.d php8.3-fpm $_dh_action || exit 1
fi
fi
# End automatically added section
exit 0
不熟悉 dpkg 的功能，但exit 1会出现在两个位置。第一个出现在读取 apache conf 文件时。我已删除 apache2，因此这个不再会触发。第二个只是表示启动/重启失败。
有什么提示可以说明问题所在吗？这似乎超出了我的技能水平。
附加信息：运行systemctl status php8.3-fpm.service回报
× php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager
Loaded: loaded (/usr/lib/systemd/system/php8.3-fpm.service; enabled; preset: enabled)
Active: failed (Result: timeout) since Mon 2024-10-07 11:34:21 CEST; 1min 33s ago
Docs: man:php-fpm8.3(8)
Process: 334032 ExecStart=/usr/sbin/php-fpm8.3 --nodaemonize --fpm-config /etc/php/8.3/fpm/php-fpm.conf (code=exited, status=0/SUCCESS)
Process: 334035 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/8.3/fpm/pool.d/www.conf 83 (code=exited, status=0/SUCCESS)
Main PID: 334032 (code=exited, status=0/SUCCESS)
CPU: 98ms
Oct 07 11:32:51 Ubuntu-2404-noble-amd64-base systemd[1]: Starting php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager...
Oct 07 11:34:21 Ubuntu-2404-noble-amd64-base systemd[1]: php8.3-fpm.service: start operation timed out. Terminating.
Oct 07 11:34:21 Ubuntu-2404-noble-amd64-base systemd[1]: php8.3-fpm.service: Failed with result 'timeout'.
Oct 07 11:34:21 Ubuntu-2404-noble-amd64-base systemd[1]: Failed to start php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager.
此外，手动启动服务并/usr/sbin/php-fpm8.3 --nodaemonize --fpm-config /etc/php/8.3/fpm/php-fpm.conf返回
NOTICE: fpm is running, pid 334206
NOTICE: ready to handle connections
NOTICE: systemd monitor interval set to 10000ms
... no more messages
表示 fpm 已成功启动，但 systemd 可能存在问题？我是否遇到了不匹配的 PID 编号？
我刚刚按照以下步骤重新编译了 Ubuntu Jammy HWE 内核 6.8.0-45：
# Clone Ubuntu stock Kernel repo
git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
cd jammy
git checkout Ubuntu-hwe-6.8-6.8.0-45.45_22.04.1
# Build deps
sudo apt build-dep linux linux-image-unsigned-`uname -r`
sudo apt install build-essential libncurses-dev bison flex libssl-dev libelf-dev fakeroot libncurses-dev gawk flex bison openssl libssl-dev dkms libelf-dev libudev-dev libpci-dev libiberty-dev autoconf llvm dwarves
# Clean all
fakeroot debian/rules clean && make ARCH=x86 mrproper && git clean -fd && git restore . && git clean -fd && git restore .
# do custom changes
code debian.hwe-6.8/changelog # Append custom version
code include/linux/uts.h # Modify UTS_SYSNAME
# Update Debian configs
chmod a+x debian/rules && chmod a+x debian/scripts/* && chmod a+x debian/scripts/misc/*
fakeroot debian/rules clean
fakeroot debian/rules editconfigs
# Start build
fakeroot debian/rules binary-headers binary-generic
我想知道如何才能重新编译单个“ iwlwifi.ko ”模块而不重新编译整个内核。
我尝试通过运行以下命令从内核源的根目录执行标准重新编译：
make -j$(nproc) M=drivers/net/wireless/intel/iwlwifi modules
但是当我试图插入这个时我得到了：
> sudo insmod drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
insmod: ERROR: could not insert module drivers/net/wireless/intel/iwlwifi/iwlwifi.ko: Invalid parameters
并dmesg说：
[10754.522405] BPF: [139328] ENUM x509_key_exit
[10754.522410] BPF: size=4 vlen=34
[10754.522410] BPF:
[10754.522411] BPF: Invalid name
[10754.522412] BPF:
[10754.522413] failed to validate module [iwlwifi] BTF: -22
我猜想一定有一种方法可以利用该fakeroot debian/rules机制，只需重新编译一个模块，而无需清除所有内容并重新构建整个内核。
感谢您的支持。
Ansible，安装XRoad时lxd报错：Attribute Error: NoneType has no attribute "items" lead to lxd_container.py
我尝试使用 Ansible 和 LXD 安装 XRoad，步骤如下：
sudo snap install lxd
lxd init
sudo apt update
sudo apt install software-properties-common
sudo add-apt-repository --yes --update ppa:ansible/ansible
sudo apt install ansible
ansible-playbook hosts -i hosts/lxd_hosts.txt xroad_init.yml
我收到此错误：
Attribute Error: NoneType has no attribute "items" leading to lxd_container.py
ansible-loop-var item: xroad-lxd-cs
Localhost ok=1 failed=1
第一次我执行几乎完全相同的步骤时，没有出现任何错误。现在，当我尝试在另一台虚拟机（Ubuntu）上安装 Xroad 时，出现了此错误。
我试过：
- 重新安装 LXD、Ansible（不同版本）
- 安装 Python 3.12
- apt 更新 + 升级
- 从桥接网络更改为 NAT
- 重新安装 Ubuntu，安装不同版本的 Xroad
错误图片：
每次我启动/重新启动计算机时，它都会运行fsck，但我不知道为什么。
如果我启动到 Ubuntu USB 驱动器，并在我的 Linux 分区上手动运行fsck，它就会清理干净。
以下是我的超级块。我尝试更改“最大安装数”和“检查间隔”，但行为没有变化。
知道为什么会发生这种情况吗？
$ sudo tune2fs -l /dev/nvme0n1p6
tune2fs 1.47.0 (5-Feb-2023)
Filesystem volume name: Ubuntu
Last mounted on: /
Filesystem UUID: f0db2226-e28d-46dd-9b5a-457c87987ed2
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 40845312
Block count: 163380224
Reserved block count: 8169011
Overhead clusters: 2844802
Free blocks: 57597994
Free inodes: 40012689
First block: 0
Block size: 4096
Fragment size: 4096
Group descriptor size: 64
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stride: 4
RAID stripe width: 32
Flex block group size: 16
Filesystem created: Fri Sep 24 20:06:49 2021
Last mount time: Sun Oct 6 17:47:34 2024
Last write time: Sun Oct 6 18:01:39 2024
Mount count: 5
Maximum mount count: 23
Last checked: Sun Oct 6 10:00:35 2024
Check interval: 0 (<none>)
Lifetime writes: 10 TB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
First orphan inode: 17714152
Default directory hash: half_md4
Directory Hash Seed: 7e1d3c28-3106-4408-8132-4b574d84a675
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0xce551aef
我有一台索尼 vaio，装有 ubuntu 22.4 mate
if I press m it shows 0
if I press u it shows 4
和其他几封信
此文本由 ONBOARD 编写，请帮忙
所以今天早些时候，我决定通过为恢复模式（GNU Grub）添加密码来稍微提高我的 Ubuntu 22.04 设备的安全性。我阅读了几篇博客，并一步一步地遵循它们。完成后，我重新启动系统进行测试，却发现我已被锁定在设备之外。我无法启动任何选项，除非它提示我输入用户名和密码。我不知道为什么会发生这种情况，但经过一番研究，我意识到我忘记设置加密密码，而我只执行了指定脚本的最后部分，即让系统在每次启动恢复模式时提示您输入用户名和密码。现在，由于未知的 grub 密码，我被锁定在设备之外。如果您没有为 grub 设置密码，是否有默认密码或其他东西？
当我通过 Flatpak 安装应用程序时，该应用程序会安装，但您只能通过终端打开它。
像这样，flatpak run org.gnome.World.PikaBackup
我知道有一篇关于此的帖子，但有没有更简单的选项？比如一个设置或一个命令可以帮助解决这个问题？我希望我的 Flatpak 应用显示在 Dock 中。