AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

  • 主页
  • 系统&网络
  • Ubuntu
  • Unix
  • DBA
  • Computer
  • Coding
  • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / unix / 问题

问题[linux-mint](unix)

Martin Hope
ehwlt
Asked: 2025-04-23 18:30:12 +0800 CST

Mint:软件包损坏,apt/Synaptic 想要删除一半的系统

  • 10

我想安装 ausweisapp 的当前版本,它需要 Mint 21.3 仓库中没有的软件包或版本,所以我开始手动安装这些软件包及其依赖项。第三个是 libzstd1_1.5.4。之前已经安装了它的一个旧版本,现在两个都坏了。如果我尝试删除其中一个,Synaptic 和apt-get install -f许多其他软件包都会被删除,比如系统一半的软件包。Aptitude:一样。

我怎样才能只删除我手动安装的软件包而不删除其他任何东西?


sudo apt install libzstd1{,:i386}=1.4.8+dfsg-3build1返回:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libzstd1:i386 is already the newest version (1.4.8+dfsg-3build1).
The following packages were automatically installed and are no longer required:
  libhttp-parser2.9 libqt5qmlmodels5 libqt5qmlworkerscript5 libqt5quick5 libqt5quickcontrols2-5 libqt5quicktemplates2-5 libqt5websockets5
  qml-module-qt-labs-platform qml-module-qtgraphicaleffects qml-module-qtqml qml-module-qtqml-models2 qml-module-qtqml-statemachine qml-module-qtquick-controls
  qml-module-qtquick-controls2 qml-module-qtquick-layouts qml-module-qtquick-templates2 qml-module-qtquick-window2 qml-module-qtquick2
Use 'sudo apt autoremove' to remove them.
The following packages will be DOWNGRADED:
  libzstd1
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 7 not upgraded.
2 not fully installed or removed.
Need to get 0 B/324 kB of archives.
After this operation, 62.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
dpkg: warning: downgrading libzstd1:amd64 from 1.5.4+dfsg2-5 to 1.4.8+dfsg-3build1
(Reading database ... 686126 files and directories currently installed.)
Preparing to unpack .../libzstd1_1.4.8+dfsg-3build1_amd64.deb ...
Unpacking libzstd1:amd64 (1.4.8+dfsg-3build1) over (1.5.4+dfsg2-5) ...
dpkg: error processing archive /var/cache/apt/archives/libzstd1_1.4.8+dfsg-3build1_amd64.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libzstd1/changelog.Debian.gz', which is different from other instances of package libzstd1:amd64
Errors were encountered while processing:
 /var/cache/apt/archives/libzstd1_1.4.8+dfsg-3build1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

输出dpkg:

~ $: sudo dpkg --purge libzstd1_1.5.4
dpkg: warning: ignoring request to remove libzstd1_1.5.4 which isn't installed

~ $: sudo dpkg --purge libzstd1      
dpkg: dependency problems prevent removal of libzstd1:amd64:
 systemd depends on libzstd1 (>= 1.4.0).
 squashfs-tools depends on libzstd1 (>= 1.4.0).
 rsync depends on libzstd1 (>= 1.4.0).
 plocate depends on libzstd1 (>= 1.4.0).
 mesa-vulkan-drivers:amd64 depends on libzstd1 (>= 1.4.0).
 mesa-vdpau-drivers:amd64 depends on libzstd1 (>= 1.4.0).
 mesa-va-drivers:amd64 depends on libzstd1 (>= 1.4.0).
 libxatracker2:amd64 depends on libzstd1 (>= 1.4.0).
 libtiff5:amd64 depends on libzstd1 (>= 1.4.0).
 libsystemd0:amd64 depends on libzstd1 (>= 1.4.0).
 libsereal-encoder-perl:amd64 depends on libzstd1 (>= 1.4.0).
 libsereal-decoder-perl depends on libzstd1 (>= 1.4.0).
 libqt5core5a:amd64 depends on libzstd1 (>= 1.4.0).
 libosmesa6:amd64 depends on libzstd1 (>= 1.4.0).
 libkmod2:amd64 depends on libzstd1 (>= 1.4.0).
 libgl1-mesa-dri:amd64 depends on libzstd1 (>= 1.4.0).
 libflatpak0:amd64 depends on libzstd1 (>= 1.4.0).
 libcurl4:amd64 depends on libzstd1 (>= 1.4.0).
 libcurl3-gnutls:amd64 depends on libzstd1 (>= 1.4.0).
 libboost-iostreams1.74.0:amd64 depends on libzstd1 (>= 1.4.0).
 libarchive13:amd64 depends on libzstd1 (>= 1.4.0).
 libapt-pkg6.0:amd64 depends on libzstd1 (>= 1.4.0).
 kmod depends on libzstd1 (>= 1.4.0).
 gfortran-11 depends on libzstd1 (>= 1.4.0).
 gcc-12 depends on libzstd1 (>= 1.4.0).
 gcc-11 depends on libzstd1 (>= 1.4.0).
 g++-11 depends on libzstd1 (>= 1.4.0).
 flatpak depends on libzstd1 (>= 1.4.0).
 dpkg depends on libzstd1 (>= 1.4.0).
 cpp-12 depends on libzstd1 (>= 1.4.0).
 cpp-11 depends on libzstd1 (>= 1.4.0).
 btrfs-progs depends on libzstd1 (>= 1.4.0).

dpkg: error processing package libzstd1:amd64 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libzstd1:amd64
linux-mint
  • 2 个回答
  • 477 Views
Martin Hope
Chris Rogers
Asked: 2025-04-03 19:28:09 +0800 CST

您能将笔记本电脑上的 Linux Mint 安装更换到 Raspberry Pi 5 吗?

  • 7

在决定全力以赴、清除笔记本电脑驱动器并在我的旧笔记本电脑上全新安装 Linux Mint(Windows 11 不支持)之后,我成为了 Linux 的新用户。

这台笔记本电脑现在已经报废了,我开始更喜欢 Linux Mint 而不是 Microsoft Windows。因此,我决定购买配备 8GB RAM 和 NVMe 帽的 Raspberry Pi 5。

我认为我不需要像安装 Microsoft Windows 那样从头开始安装。那么,我是否可以通过适配器将笔记本电脑的 SATA 驱动器连接到 USB 连接器,并使用它来启动我的旧 Linux Mint 设置,还是需要将 SATA 驱动器内容克隆到 SD 卡或 NVMe 驱动器?

linux-mint
  • 1 个回答
  • 156 Views
Martin Hope
ItHertz
Asked: 2025-03-31 08:51:10 +0800 CST

为什么升级 linux mint 后涉及 libtiff 的 magick 命令会失败?

  • 5

我最近升级到了 Linux Mint 22.1 Cinnamon,ImageMagick 脚本现在抛出一个错误:

magick: symbol lookup error: /usr/local/lib/libMagickCore-7.Q16HDRI.so.10: undefined symbol: TIFFFieldDataType, version LIBTIFF_4.0

我/usr/local/lib注意到这libMagickCore-7.Q16HDRI.so.10是一个指向的符号链接libMagickCore-7.Q16HDRI.so.10.0.0

我从 synaptic 安装的 ImageMagick 版本。我不记得我是否曾尝试从 synaptic 之外安装版本。

magick -version
Version: ImageMagick 7.1.0-43 Q16-HDRI x86_64 8718d6292:20220709 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI OpenMP(4.5) 
Delegates (built-in): fontconfig freetype jbig jng jpeg lcms lzma pangocairo png tiff x xml zlib
Compiler: gcc (9.4)

magick -list format
TIFF* rw+   Tagged Image File Format (LIBTIFF, Version 4.5.1)
TIFF64* rw+   Tagged Image File Format (64-bit) (LIBTIFF, Version 4.5.1)

我已经安装libtiff-dev libtiff5-dev并libtiff6

在网上搜索此问题时,我随机尝试遵循以下建议conda uninstall libtiff,但只返回

PackagesNotFoundError: The following packages are missing from the target environment:
  - libtiff 

如果您能提供任何关于如何解决此问题的想法,我们将不胜感激。

linux-mint
  • 2 个回答
  • 40 Views
Martin Hope
user2661923
Asked: 2025-03-16 02:33:47 +0800 CST

了解 apt-get build-dep 过程

  • 6

在本问题末尾添加了附录,以回应 Stephen Kitt 的回答。


交叉发布:在渐近线(sourceforge)论坛上发布帖子没有什么乐趣。

在这篇文章中,我描述了我尝试执行该apt-get build-dep命令以及执行该apt-update命令时进行的实验。我想了解导致这些错误的原因,以及是否有补救措施(使用提取的源代码)。

在 Linux Mint 22 中,我安装了 VirtualBox 7 并创建了一个 Linux Mint 22 客户机,用于实验。在客户机中,我首先安装了 TexLive,然后从其源代码成功安装了 Latex 插件 Asymptote 3.00。为此,我必须首先安装以下软件包:

freeglut, cmake, libx11-dev, bison, flex, libgl1-mesa-dev, libglu1-mesa-dev  zlib1g-dev

这次实验成功后,我恢复了刚安装 TexLive 并提取 Asymptote 3.00 源代码后拍摄的 VirtualBox 快照。作为第二次实验,我尝试简化该过程。有人建议我可以通过以下命令让单个安装处理依赖项:

apt-get build-dep asymptote 
./configure
make all
make install

根据初步研究,我sudo xed使用以下行更新了 \etc\apt\sources.list:

deb-src file:/home/steve/Downloads/asymptote-3.00 unstable main contrib 

然后我导航到 /home/steve/Downloads/asymptote-3.00 并执行sudo apt-get build-dep asymptote。此操作失败并显示以下消息:

$ sudo apt-get build-dep asymptote
Reading package lists... Done
E: You must put some 'deb-src' URIs in your sources.list

为了进行调查,我随后执行sudo apt update了

Get:1 file:/home/steve/Downloads/asymptote-3.00 unstable InRelease
Ign:1 file:/home/steve/Downloads/asymptote-3.00 unstable InRelease
Get:2 file:/home/steve/Downloads/asymptote-3.00 unstable Release
Err:2 file:/home/steve/Downloads/asymptote-3.00 unstable Release
File not found - /home/steve/Downloads/asymptote-3.00/dists/unstable/Release (2: No such file or directory)
...

根据以上apt update报告,我将sudo apt-get build-dep asymptote附加的行替换为以下内容后重试:

deb-src file:/home/steve/Downloads/asymptote-3.00

这产生了

$ sudo apt-get build-dep asymptote
E: Malformed entry 8 in list file /etc/apt/sources.list (Suite)
E: The list of sources could not be read.
E: Malformed entry 8 in list file /etc/apt/sources.list (Suite)
E: The list of sources could not be read.

再次调查,我重新执行sudo apt update,结果

$ sudo apt update
E: Malformed entry 8 in list file /etc/apt/sources.list (Suite)
E: The list of sources could not be read.

进一步调查,asymptote 3.0 目录的完整子目录列表如下:

backports           examples                patches                         
base                gc                      prc             
build-scripts       gl-matrix-2.4.0-pruned  tests           
cmake-preset-files  GUI                     thirdparty_impl 
cmake-scripts       libatomic_ops           tinyexr         
cudareflect         LspCpp                  webgl           
cxxtests            misc                    windows         
doc 

附录
我对 Stephen Kitt 的答案进行了测试验证。

读完他的回答并重新加载(之前的)VirtualBox 快照后,我发现而deb不是deb-src条目已经包含在内/etc/apt/sources.list.d/official-source-repositories.list。

我已经确定在这种情况下,该apt-get build-dep asymptote命令不起作用。必须将deb-src条目添加到 中\etc\apt\sources.list。根据他的回答,我将这五个deb-src条目添加到 中\etc\apt\sources.list。

然后,我执行了menu : software-sources : enable-source-code-repositories : update-cache。

然后我执行了apt update。

然后,我导航到提取的代码的目录asymptote并执行apt-get build-dep asymptote命令。

据推测,这工作得很好(即我在 10 分钟后中止,因为 VirtualBox 处理很慢,并且该过程增加了额外的 1+ gb 的包装)。

根据 Stephen Kitt 的回答中的评论,我重新执行了整个实验,但有一个例外:我没有将所有 5deb-src行都添加到中\etc\apt\sources.list,而是只添加了deb-src http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse行。

这似乎也运行得很好。同样,出于同样的原因,我在 10 分钟后中止了 VirtualBox 的运行。

总的来说,这对我来说是一次很棒的学习经历。

linux-mint
  • 1 个回答
  • 42 Views
Martin Hope
Ryan King Art
Asked: 2025-03-13 23:22:20 +0800 CST

以相反顺序在线上传照片(Firefox 和 Linux Mint)

  • 5

我经常在线上传一组照片,例如产品图片或艺术品。最近我注意到 Firefox 会以相反的顺序上传文件夹中的一组照片。我尝试上传照片的每个网站都会发生这种情况。

示例:在 Linux 上的一个文件夹中,我有:

  • 作品1.jpg
  • 作品2.jpg
  • 作品3.jpg

当我将所有照片一起上传时,它会按以下顺序上传:

  • 作品3.jpg
  • 作品2.jpg
  • 作品1.jpg

这很令人沮丧,因为每次上传照片时我都必须手动重新排序。我不记得以前发生过这种情况,只是最近才发生过。

由于这种情况发生在每个网站上,我预计它与 Linux Mint 或 Firefox 有关。

我尝试过的:

我试过按 Control A 键,选择所有照片,然后上传,我还试过选择第一张照片,然后按住 shift 键,选择底部的照片,然后点击上传。我也试过这样做,但方向相反,所以按住 shift 键,选择最后一张照片,然后选择第一张照片。

我也尝试过按名称、修改日期和相反顺序排列 Fire 浏览器中的照片,但照片仍然以相反的顺序上传。

我还尝试将照片重命名为:

  • 001.jpg
  • 002.jpg
  • 003.jpg

但这仍然不能修复上传顺序。

PNG 和 JPG 文件也会出现这种情况。

linux-mint
  • 2 个回答
  • 36 Views
Martin Hope
MiB_Coder
Asked: 2025-03-09 17:59:14 +0800 CST

无法使用 fstab 在启动时挂载 LVM 逻辑卷

  • 5

我在卷组 vgsata 中设置了逻辑卷 lvvm。lvvm 是使用 thin -T 选项创建的:

sudo lvcreate -L 925G -T vgsata/lvvm
lsblk
...
sdc                     8:32   0 931,5G  0 disk  
└─sdc1                  8:33   0 931,5G  0 part  
  ├─vgsata-lvvm_tmeta 252:0    0   116M  0 lvm   
  │ └─vgsata-lvvm     252:2    0   925G  0 lvm   
  └─vgsata-lvvm_tdata 252:1    0   925G  0 lvm   
    └─vgsata-lvvm     252:2    0   925G  0 lvm   

系统启动时,我可以毫无问题地从终端挂载卷:

sudo mount /dev/vgsata/lvvm /VM

但是当我尝试使用 fstab 完成此操作时,通过添加行

/dev/mapper/vgsata-lvvm /VM ext4    defaults    0   2

如果不安装卷,启动过程现在需要多花 1-2 分钟。boot.log我发现了一些与超时相关的问题:

[ TIME ] Timed out waiting for device dev-m…m.device - /dev/mapper/vgsata-lvvm.
[DEPEND] Dependency failed for systemd-fsck…m Check on /dev/mapper/vgsata-lvvm.
[DEPEND] Dependency failed for VM.mount - /VM.
[DEPEND] Dependency failed for local-fs.target - Local File Systems.

我也尝试使用 UUID,但事实上这似乎不是 LVM 的推荐方式,它并没有解决问题。

那么在启动时挂载逻辑卷的最佳方法是什么?还是我在创建精简卷时犯了一个错误?

linux-mint
  • 1 个回答
  • 58 Views
Martin Hope
pedda
Asked: 2025-02-13 09:20:18 +0800 CST

Linux Mint 22:initramfs 的设置问题(luks 加密分区,带有用于 root、home、swap 的 LVM)

  • 9

我的设置:先决条件:

  • 双启动 Windows 10/以前为 Ubuntu 24.04(来自 22.04)
  • 分区表:
    /dev/nvme0n1p7                   202G   96M  202G   1% 
    /ntfs_data
    /dev/nvme0n1p3                   230G   54G  177G  24% 
    /windows
    /dev/nvme0n1p5                   3,0G  288M  2,6G  11% /boot
    /dev/mapper/ubuntu--vg-home      2,8T  1,7T  964G  64% /home
    /dev/nvme0n1p1                   256M  158M   99M  62% 
    /boot/efi
    tmpfs                            1,6G  300K  1,6G   1% /run/user/1000
    /home/xxx/.Private               2,8T  1,7T  964G  64% /home/xxx
    /dev/mapper/usb1TB_202304_crypt  938G  890G  559M 100% 
    /backup1TB
    /backup1TB/home_xxx_bck          938G  890G  559M 100% 
    /backup1TB/home_xxx_bck
    
    我的 SSD 分区表的 gparted 屏幕截图
  • /dev/nvme0n1p6 是配置了 LVM 的 luks 加密设备:
    • 根 (243 GB)
    • 家庭 (2.8 TB)
    • 交换 ( 16 GB)

安装导致initramfs出错的步骤:

我使用了 Linux Mint 22 USB 安装程序(图片下载于 2025 年 1 月)。我设法安装了 LVM2 和 cryptsetup 包以获得 LVM 和 LUKS 的帮助。我在 2022 年在 Ubuntu 22.04 下配置了 LVM,如下所示:

# vgs
  WARNING: Couldn't find device with uuid CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH.
  WARNING: Couldn't find device with uuid I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs.
  WARNING: VG ubuntu-vg is missing PV CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH (last written to /dev/mapper/ubuntu-vg1).
  WARNING: VG ubuntu-vg is missing PV I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs (last written to /dev/mapper/ubuntu-vg2).
  VG        #PV #LV #SN Attr   VSize  VFree   
  ubuntu-vg   3   4   0 wz-pn- <6,01t <180,97g

# pvs
  WARNING: Couldn't find device with uuid CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH.
  WARNING: Couldn't find device with uuid I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs.
  WARNING: VG ubuntu-vg is missing PV CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH (last written to /dev/mapper/ubuntu-vg1).
  WARNING: VG ubuntu-vg is missing PV I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs (last written to /dev/mapper/ubuntu-vg2).
  PV                      VG        Fmt  Attr PSize  PFree   
  /dev/mapper/ubuntu-luks ubuntu-vg lvm2 a--   3,21t <180,97g
  [unknown]               ubuntu-vg lvm2 a-m  <1,40t       0 
  [unknown]               ubuntu-vg lvm2 a-m  <1,40t       0 

# lvs
  LV         VG        Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  backupHome ubuntu-vg -wi-----p-    2,79t                                                    
  home       ubuntu-vg -wi-ao----    2,78t                                                    
  root       ubuntu-vg -wi-ao---- <247,33g                                                    
  swap_1     ubuntu-vg -wi-ao----   16,00g  

我打开了一个 bash,然后打开 LUKS 并将 LVM 设置为活动状态(LVM 以前是在 2022 年的 22.04 下创建的):

# cryptsetup luksOpen /dev/nvmeon1p6 ubuntu-luks
# lvchange -ay ubuntu-vg

然后我启动了安装应用程序,并选择手动模式,在分配分区时,我按照上面所示进行配置,将根和 /dev/nvme0n1p5 格式化为(未加密)/boot 分区。

之后,我启动了新安装的 Linux Mint 22。但有趣的是,除了第一次启动时,启动顺序中的图形密码对话框只弹出一次并解密了 luks,但无法正确分配 LVM 分区。之后甚至找不到或检测到 LUKS 加密卷,在每种情况下,我最终都在繁忙的盒装 initramfs 中等待了很长时间。

在这里我总是必须重复上述两个指令,然后才能退出 initramfs 并继续启动我的系统。

我发现 /etc/crypttab 中没有 crypttab,于是我安装了一个

# cat /etc/crypttab 
# <target name>         <source device>                           <key file>      <options>
# mounted /, /home, swap_1
ubuntu-luks             UUID=b910aded-9314-403f-a350-7892ba95ffd5 none            luks
# mounted as /backupHome LV part1, partial Loading (mustn't be present during boot)
ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks
#ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks,noauto
# mounted as /backupHome LV part2, partial loading (mustn't be present during boot)
ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks
#ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks,noauto
usb1TB_202304_luks      UUID=4c4b603f-9146-4cb0-9621-9aa098ec592c none            luks

# ubuntu-luks             UUID=b910aded-9314-403f-a350-7892ba95ffd5 none            luks  # mounted on /
# ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks,noauto  # mounted as /backupHome, part1
# ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks,noauto  # mounted as /backupHome, part2

和 /etc/fstab:

# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system>                           <mount point>   <type>  <options>                 <dump>  <pass>
/dev/mapper/ubuntu--vg-root               /               ext4    errors=remount-ro         0       1
# /boot was on /dev/nvme0n1p5 during installation
UUID=712868f5-29cc-429a-b535-375a3d868fa3 /boot           ext4    defaults                  0       2
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=E079-2792                            /boot/efi       vfat    umask=0077                0       1
/dev/mapper/ubuntu--vg-home               /home           ext4    defaults                  0       2
# /ntfs_data was on /dev/nvme0n1p7 during installation
UUID=3B269E2A1843CA0B                     /ntfs_data      ntfs    defaults,umask=007,gid=46 0       0
# /windows was on /dev/nvme0n1p3 during installation
UUID=4C30FF1730FF06AC                     /windows        ntfs    defaults,umask=007,gid=46 0       0
/dev/mapper/ubuntu--vg-swap_1             none            swap    sw                        0       0
/dev/mapper/ubuntu--vg-backupHome         /backupHome     ext4    defaults,nofail           0       2

然后我更新了 initramfs $ sudo update-initramfs -k all -c

现在我永久修复了 luks 加密(因此对话框每次启动时都会出现,就像描述的一样)但是 lvm 的激活 $ lvchange -ay ubuntu-vg 不是在 initramfs 中完成的!

我如何才能实现最后一步——激活 LV 组?

  • 注意:作为 USB 驱动器的备份 lvm 媒体通常在启动期间不存在!
    # mounted as /backupHome LV part1, partial Loading (mustn't be present during boot)
    ubuntu-luks_backupHome1  UUID=xxx none            luks
    #ubuntu-luks_backupHome1 UUID=xxx none            luks,noauto
    # mounted as /backupHome LV part2, partial loading (mustn't be present during boot) 
    ubuntu-luks_backupHome2  UUID=xxx none            luks
    #ubuntu-luks_backupHome2 UUID=xxx none            luks,noauto
    

[编辑 101502013]:今天它启动时出现类似以下错误

/sbin/lvchange not found

在 initramfs 中。我发现在 中有一个不同之处initrams,那就是lvm的命令(如lvs, pvs, vgs, lvchange, lvcreate等)仅使用主命令lvm作为前缀。我还发现在/sbin中initramfs只有一个符号链接,即奇怪的别名 lvm -> vgchange,似乎在应用链接后 arg0 变成了 arg1。这是我接下来尝试的方法,将此链接放入 initramfs 中。

[EDIT2] 我首先将 lvm 启动和激活脚本放入 local-top,然后放入 init-bottom,最后放入 local-bottom,并相应地更新了 initramfs, update-initramfs -k all -c 但没有任何成功,LUKS 已解密,但脚本要么未运行,要么运行得太早,每次它最终都会出现在 initramfs 控制台及其 busybox 中。当我手动执行脚本并退出时,它每次都会继续启动。但这非常不舒服,而且由于时间滞后很多,因此同样耗时,它不是执行脚本,而是无休止地重复产生此输出行:

mdadm: No array found in config file or automatically

这是我的脚本的实际位置:

# tree /etc/initramfs-tools/
/etc/initramfs-tools/
├── conf.d
│   └── cryptsetup
├── hooks
├── initramfs.conf
├── modules
├── scripts
│   ├── init-bottom
│   ├── init-premount
│   ├── init-top
│   ├── local-bottom
│   │   └── lvm
│   ├── local-premount
│   ├── local-top
│   ├── nfs-bottom
│   ├── nfs-premount
│   ├── nfs-top
│   └── panic
└── update-initramfs.conf

14 directories, 5 files

该脚本看起来可以执行如下:

#!/bin/sh
# Check and activate LVM volumes regardless of input arguments

# Log the intention to activate LVM volumes
echo "Activating LVM volumes..." > /dev/console

# Activate the volume group
if /sbin/vgchange -ay ubuntu-vg; then
    echo "Logical volume group ubuntu-vg successfully activated." > /dev/console
    /sbin/lvm lvchange -ay ubuntu-vg --activationmode partial
else
    echo "Failed to activate logical volume group ubuntu-vg." > /dev/console
fi

在这期间,我压缩了一个 initrd 映像以查看 cryptsetup 命令的运行位置,但它似乎有点复杂: unmkinitramfs -v initrd.img-6.8.0-53-generic /tmp/initrd 然后我搜索了cryptsetup :

# find /tmp/initrd/ -type f -iname "*" -exec grep -Hn "cryptsetup " {} \;
grep: /tmp/initrd/main/usr/sbin/cryptsetup: binary file matches
grep: /tmp/initrd/main/usr/lib/x86_64-linux-gnu/libcryptsetup.so.12.10.0: binary file matches
grep: /tmp/initrd/main/usr/lib/x86_64-linux-gnu/libmount.so.1.1.0: binary file matches
/tmp/initrd/main/usr/lib/cryptsetup/functions:320:        if [ -e "$CRYPTTAB_OPTION_header" ] && /sbin/cryptsetup isLuks -- "$CRYPTTAB_OPTION_header"; then
/tmp/initrd/main/usr/lib/cryptsetup/functions:324:        if /sbin/cryptsetup isLuks -- "$s"; then
/tmp/initrd/main/usr/lib/cryptsetup/functions:366:    /sbin/cryptsetup -T1 \
/tmp/initrd/main/usr/lib/cryptsetup/functions:396:    /sbin/cryptsetup -T1 \
/tmp/initrd/main/usr/bin/cryptroot-unlock:89:# birth date) of the cryptsetup process with same $CRYPTTAB_NAME.
/tmp/initrd/main/usr/bin/cryptroot-unlock:118:  # find the cryptsetup process with same $CRYPTTAB_NAME
/tmp/initrd/main/usr/bin/cryptroot-unlock:173:      echo "cryptsetup: cryptsetup failed, bad password or options?" >&2
/tmp/initrd/main/scripts/local-top/cryptroot:127:    # our `cryptroot-unlock` script searches for cryptsetup processes
/tmp/initrd/main/scripts/local-top/cryptroot:164:            cryptsetup_message "ERROR: $CRYPTTAB_NAME: cryptsetup failed, bad password or options?"
/tmp/initrd/main/scripts/local-top/cryptroot:177:                /sbin/cryptsetup remove -- "$CRYPTTAB_NAME"

**有什么想法吗?我做错了什么,或者可以做些什么不同的事情?**

linux-mint
  • 1 个回答
  • 53 Views
Martin Hope
pedda
Asked: 2025-02-13 00:30:21 +0800 CST

Linux Mint 22:HP Envy 13 aq1176ng-RDP 上仅有声音,但没有耳机或扬声器

  • 5

首先:通过 RDP(远程桌面连接)虚拟声音 iE NoMachine运行良好,只有内置扬声器和耳机没有声音。声音驱动程序(声音开放固件由 github 源 v2.2(在最近的 v2.12 之前)安装)。声卡是英特尔snd_hda_intel。

在此处输入图片描述

我关注了网络上关于 Linux Mint 或 Ubuntu 22 的几个链接,它们总是类似这样的:

  • 安装 ALSA
  • 重新安装音响系统并重新启动 alsa
  • (重新)安装管线
  • 安装并配置 hdajackretask(我认为这是最没有希望的方法)

包括重新启动 alsa,

# dmesg | grep snd
[  659.315312] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[  659.315388] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[  659.678692] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[  659.678695] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[  659.678697] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[  659.678698] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[  659.678699] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[  659.678699] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

获取系统信息(最后两行音频):

# inxi -SMA
System:
  Host: HP-ENVY-Laptop-13-aq1176ng Kernel: 6.8.0-52-generic arch: x86_64
    bits: 64
  Desktop: Cinnamon v: 6.4.6 Distro: Linux Mint 22.1 Xia
Machine:
  Type: Laptop System: HP product: HP ENVY Laptop 13-aq1xxx
    v: Type1ProductConfigId serial: 8CG0165VNF
  Mobo: HP model: 86AE v: 83.18 serial: PJEKT1DHCDM061 UEFI: Insyde v: F.22
    date: 11/24/2023
Audio:
  Device-1: Intel Comet Lake PCH-LP cAVS driver: sof-audio-pci-intel-cnl
  API: ALSA v: k6.8.0-52-generic status: kernel-api

启动过程中‘snd’的日志重新硬化结果对我来说看起来很好:

$ journalctl -b -x | grep -i snd
Oct 17 19:15:17 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
Oct 17 19:15:17 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

到目前为止还没有结果。唯一可行的是,如果你通过 NoMachine 连接,声音就会传输到远程计算机。

所以我认为声音是产生的,但在操作系统抽象层到硬件之间的某个地方存在问题。我恳求您提供想法或解决方案(树)!

[编辑]

aplay-l输出

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

lspci 输出:

# lspci
00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi
00:14.5 SD Host controller: Intel Corporation Comet Lake PCH-LP SCS3
00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller
00:15.1 Serial bus controller: Intel Corporation Comet Lake Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller
00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH-LP cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller
02:00.0 3D controller: NVIDIA Corporation GP108BM [GeForce MX250] (rev a1)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]

dmesg|grep audio的输出

# dmesg |grep audio
[   15.060429] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[   15.060582] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[   15.060596] sof-audio-pci-intel-cnl 0000:00:1f.3: enabling device (0000 -> 0002)
[   15.060801] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   15.060876] sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   15.067813] sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode
[   15.108086] sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5
[   15.108092] sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[   15.108097] sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[   15.113689] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[   15.113694] sof-audio-pci-intel-cnl 0000:00:1f.3:  Firmware file:     intel/sof/sof-cml.ri
[   15.113697] sof-audio-pci-intel-cnl 0000:00:1f.3:  Topology file:     intel/sof-tplg/sof-hda-generic-2ch.tplg
[   15.116471] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[   15.116474] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[   15.116481] sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[   15.216153] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[   15.216160] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[   15.236595] sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0
[   15.257684] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   15.257692] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   15.257695] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   15.257697] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[   15.257699] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[   15.257701] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19
[ 4302.743485] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 4302.743565] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 4302.744012] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[ 4302.744080] sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 4302.750643] sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode
[ 4302.764441] sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5
[ 4302.764450] sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[ 4302.764457] sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[ 4302.766353] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[ 4302.766357] sof-audio-pci-intel-cnl 0000:00:1f.3:  Firmware file:     intel/sof/sof-cml.ri
[ 4302.766358] sof-audio-pci-intel-cnl 0000:00:1f.3:  Topology file:     intel/sof-tplg/sof-hda-generic-2ch.tplg
[ 4302.768019] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 4302.768022] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.768029] sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[ 4302.880559] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 4302.880569] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.881182] sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.897218] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[ 4302.897226] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 4302.897229] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 4302.897232] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[ 4302.897233] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[ 4302.897235] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

[编辑 3] Alsamixer 的图片。如果设备在列中的数字周围是绿色,则表示设备已静音,反之亦然?另外还有声卡列表,实际上是默认声卡和 sof-hda-default。 在此处输入图片描述 但在 alsamixer 中更改音量或静音不会改变扬声器中缺失的声音,并且所做的更改在启动后不会保留: 在此处输入图片描述

linux-mint
  • 1 个回答
  • 89 Views
Martin Hope
user153245
Asked: 2025-02-02 17:37:20 +0800 CST

Linux Mint 主机上的 Qemu/KVM 中的 Windows 10 客户机没有声音

  • 6

我在 Linux Mint 22 机器上用 Qemu/kvm 安装了 Windows 10。一切正常,但 Windows 没有声音。不过,当我使用 Remmina 通过 RDP 连接到 Windows 时,Windows 声音正常。

我想直接听到 Windows 声音(而不是通过 RDP 会话)。我该如何解决?

更新 客户的 xml 配置文件如下:

<domain type='kvm'>
  <name>win10</name>
  <uuid>febb531c-95f7-4022-bdd6-46363978364e</uuid>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
      <libosinfo:os id="http://microsoft.com/win/10"/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>4</vcpu>
  <os>
    <type arch='x86_64' machine='pc-q35-8.2'>hvm</type>
    <bootmenu enable='yes'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv mode='custom'>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
    </hyperv>
    <vmport state='off'/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='2'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
    <timer name='hypervclock' present='yes'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' discard='unmap'/>
      <source file='/home/user/Qemu/QEMU-VMs/win-10/win10.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <boot order='2'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/user/Software/virtio-win-0.1.262.iso'/>
      <target dev='sdc' bus='sata'/>
      <readonly/>
      <boot order='3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0x15'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0x16'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0x17'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/>
    </controller>
    <controller type='pci' index='9' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='9' port='0x18'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='10' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='10' port='0x19'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/>
    </controller>
    <controller type='pci' index='11' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='11' port='0x1a'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/>
    </controller>
    <controller type='pci' index='12' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='12' port='0x1b'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/>
    </controller>
    <controller type='pci' index='13' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='13' port='0x1c'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/>
    </controller>
    <controller type='pci' index='14' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='14' port='0x1d'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <interface type='network'>
      <mac address='52:54:00:68:9d:5b'/>
      <source network='default'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='spice' autoport='yes'>
      <listen type='address'/>
      <image compression='off'/>
    </graphics>
    <graphics type='vnc' port='-1' autoport='yes'>
      <listen type='address'/>
    </graphics>
    <sound model='ich9'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
    </sound>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='2'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='3'/>
    </redirdev>
    <watchdog model='itco' action='reset'/>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>

更新2 以下是的输出$ inxi -A:

Audio:
  Device-1: Intel CM238 HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.8.0-52-generic status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active
linux-mint
  • 2 个回答
  • 127 Views
Martin Hope
Elder Geek
Asked: 2025-01-14 04:41:22 +0800 CST

为什么 lastlog 显示每个用户从未登录过?

  • 5

当我运行lastlog输出时,系统上的每个用户都显示为**Never logged in**

me@me-Z370-HD3P:~$ lastlog
Username         Port     From             Latest
root                                       **Never logged in**
daemon                                     **Never logged in**
bin                                        **Never logged in**
sys                                        **Never logged in**
sync                                       **Never logged in**
games                                      **Never logged in**
man                                        **Never logged in**
lp                                         **Never logged in**
mail                                       **Never logged in**
news                                       **Never logged in**
uucp                                       **Never logged in**
proxy                                      **Never logged in**
www-data                                   **Never logged in**
backup                                     **Never logged in**
list                                       **Never logged in**
irc                                        **Never logged in**
gnats                                      **Never logged in**
nobody                                     **Never logged in**
systemd-network                            **Never logged in**
systemd-resolve                            **Never logged in**
messagebus                                 **Never logged in**
systemd-timesync                           **Never logged in**
syslog                                     **Never logged in**
_apt                                       **Never logged in**
tss                                        **Never logged in**
rtkit                                      **Never logged in**
systemd-coredump                           **Never logged in**
kernoops                                   **Never logged in**
uuidd                                      **Never logged in**
cups-pk-helper                             **Never logged in**
lightdm                                    **Never logged in**
tcpdump                                    **Never logged in**
speech-dispatcher                           **Never logged in**
avahi-autoipd                              **Never logged in**
usbmux                                     **Never logged in**
nm-openvpn                                 **Never logged in**
geoclue                                    **Never logged in**
dnsmasq                                    **Never logged in**
pulse                                      **Never logged in**
_flatpak                                   **Never logged in**
avahi                                      **Never logged in**
saned                                      **Never logged in**
colord                                     **Never logged in**
fwupd-refresh                              **Never logged in**
hplip                                      **Never logged in**
me                                         **Never logged in**
sssd                                       **Never logged in**

“last” 输出不一致(我也是)。为什么会有差异?

me@me-Z370-HD3P:~$ last
me       tty7         :0               Fri Jan 10 19:15    gone - no logout
reboot   system boot  5.15.0-130-gener Fri Jan 10 19:15   still running
me       tty7         :0               Fri Jan 10 19:11 - 19:12  (00:01)
reboot   system boot  5.15.0-130-gener Fri Jan 10 19:10 - 19:12  (00:01)
me       tty7         :0               Mon Jan  6 14:50 - 15:44 (4+00:53)
reboot   system boot  5.15.0-130-gener Mon Jan  6 14:15 - 15:44 (4+01:28)
me       tty7         :0               Fri Jan  3 08:04 - 14:14 (3+06:10)
reboot   system boot  5.15.0-126-gener Thu Jan  2 21:04 - 14:14 (3+17:10)
me       tty7         :0               Thu Jan  2 08:56 - 21:03  (12:07)
reboot   system boot  5.15.0-126-gener Wed Jan  1 16:19 - 21:03 (1+04:44)
me       tty7         :0               Wed Jan  1 12:40 - 13:54  (01:14)
reboot   system boot  5.15.0-126-gener Wed Jan  1 12:40 - 13:54  (01:14)
me       tty7         :0               Mon Nov 25 16:46 - 12:39 (36+19:52)
reboot   system boot  5.15.0-126-gener Mon Nov 25 16:46 - 12:39 (36+19:52)
me       tty7         :0               Tue Nov 19 16:57 - 16:45 (5+23:47)
reboot   system boot  5.15.0-126-gener Tue Nov 19 16:57 - 16:45 (5+23:48)
me       tty7         :0               Thu Nov 14 13:37 - 16:56 (5+03:19)
reboot   system boot  5.15.0-125-gener Thu Nov 14 12:15 - 16:56 (5+04:41)
me       tty7         :0               Wed Nov 13 11:30 - 12:14 (1+00:44)
reboot   system boot  5.15.0-125-gener Wed Nov 13 09:19 - 12:14 (1+02:55)
me       tty7         :0               Tue Nov 12 17:20 - 09:14  (15:54)
reboot   system boot  5.15.0-125-gener Tue Nov 12 17:19 - 09:14  (15:54)
reboot   system boot  5.15.0-125-gener Tue Nov 12 17:16 - 09:14  (15:58)
reboot   system boot  5.15.0-125-gener Tue Nov 12 16:55 - 09:14  (16:19)
me       tty7         :0               Tue Nov 12 15:22 - 16:42  (01:19)
reboot   system boot  5.15.0-125-gener Tue Nov 12 15:21 - 16:42  (01:20)
me       tty7         :0               Tue Nov 12 09:46 - 12:09  (02:22)
reboot   system boot  5.15.0-125-gener Tue Nov 12 09:46 - 12:09  (02:23)
me       tty7         :0               Mon Nov 11 15:38 - 09:45  (18:07)
reboot   system boot  5.15.0-124-gener Mon Nov 11 15:38 - 09:45  (18:07)
me       tty7         :0               Mon Nov 11 15:10 - 15:35  (00:25)
reboot   system boot  5.15.0-124-gener Mon Nov 11 15:10 - 15:35  (00:25)
me       tty7         :0               Mon Nov 11 15:05 - 15:07  (00:02)
reboot   system boot  5.15.0-124-gener Mon Nov 11 15:04 - 15:07  (00:03)
me       tty7         :0               Mon Nov 11 10:53 - 14:59  (04:06)
reboot   system boot  5.15.0-124-gener Mon Nov 11 10:41 - 14:59  (04:18)
me       tty7         :0               Mon Nov 11 10:35 - 10:40  (00:05)
reboot   system boot  5.15.0-124-gener Mon Nov 11 10:34 - 10:40  (00:05)
me       tty7         :0               Mon Nov 11 10:26 - 10:30  (00:04)
reboot   system boot  5.15.0-124-gener Mon Nov 11 10:26 - 10:30  (00:04)
me       tty7         :0               Sat Nov  2 08:45 - 10:18 (9+02:33)
reboot   system boot  5.15.0-124-gener Sat Nov  2 08:44 - 10:18 (9+02:33)
me       tty7         :0               Tue Oct 15 08:34 - 08:44 (18+00:10)
reboot   system boot  5.15.0-122-gener Tue Oct 15 08:33 - 08:44 (18+00:10)
me       tty7         :0               Sun Sep  1 11:34 - crash (43+20:59)
reboot   system boot  5.15.0-119-gener Sun Sep  1 11:34 - 08:44 (61+21:10)
me       tty7         :0               Sat Aug 10 17:05 - 11:33 (21+18:28)
reboot   system boot  5.15.0-117-gener Sat Aug 10 17:05 - 11:33 (21+18:28)
reboot   system boot  5.15.0-117-gener Sat Aug 10 16:49 - 17:04  (00:14)
reboot   system boot  5.15.0-117-gener Sat Aug 10 16:46 - 16:49  (00:02)
reboot   system boot  5.15.0-117-gener Sat Aug 10 16:45 - 16:46  (00:00)
me       tty7         :0               Fri Aug  9 07:28 - 16:45 (1+09:16)
me       tty7         :0               Sat Aug  3 17:39 - 07:28 (5+13:48)
reboot   system boot  5.15.0-117-gener Sat Aug  3 17:07 - 16:45 (6+23:37)
me       tty7         :0               Fri Aug  2 12:10 - 17:07 (1+04:56)
reboot   system boot  5.15.0-117-gener Fri Aug  2 12:10 - 17:07 (1+04:56)
me       tty7         :0               Fri Aug  2 11:04 - 12:09  (01:05)
reboot   system boot  5.15.0-116-gener Fri Aug  2 11:04 - 12:09  (01:05)
me       tty7         :0               Fri Aug  2 10:25 - 11:03  (00:38)
reboot   system boot  5.15.0-116-gener Fri Aug  2 10:03 - 11:03  (01:00)
me       tty7         :0               Tue Jul 23 17:34 - 10:02 (9+16:27)
reboot   system boot  5.15.0-116-gener Tue Jul 23 17:21 - 10:02 (9+16:40)
me       tty7         :0               Mon Jul 15 07:51 - 17:21 (8+09:29)
reboot   system boot  5.15.0-113-gener Sun Jul 14 21:15 - 17:21 (8+20:05)
me       tty7         :0               Sun Jun 30 18:16 - crash (14+02:58)
reboot   system boot  5.15.0-113-gener Sun Jun 30 15:45 - 17:21 (23+01:35)
me       tty7         :0               Sat Jun 15 12:14 - 15:44 (15+03:30)
reboot   system boot  5.15.0-112-gener Sat Jun 15 12:06 - 15:44 (15+03:38)
me       tty7         :0               Fri Jun  7 08:12 - crash (8+03:54)
reboot   system boot  5.15.0-112-gener Thu Jun  6 18:25 - 15:44 (23+21:19)
me       tty7         :0               Thu Jun  6 17:56 - 18:25  (00:28)
reboot   system boot  5.15.0-112-gener Thu Jun  6 17:56 - 18:25  (00:28)
me       tty7         :0               Tue Jun  4 15:23 - 14:01 (1+22:37)
reboot   system boot  5.15.0-107-gener Tue Jun  4 15:23 - 14:01 (1+22:37)
me       tty7         :0               Mon May 27 08:44 - 15:22 (8+06:38)
reboot   system boot  5.15.0-105-gener Mon May 27 08:43 - 15:22 (8+06:38)
me       tty7         :0               Sat Apr 20 19:39 - 08:43 (36+13:03)
reboot   system boot  5.15.0-105-gener Sat Apr 20 19:38 - 08:43 (36+13:04)
me       tty7         :0               Sat Apr 20 19:34 - 19:38  (00:03)
reboot   system boot  5.15.0-102-gener Sat Apr 20 19:33 - 19:38  (00:04)
me       tty7         :0               Thu Apr  4 15:35 - 19:32 (16+03:57)
reboot   system boot  5.15.0-101-gener Thu Apr  4 15:34 - 19:32 (16+03:57)
me       tty7         :0               Tue Mar 19 20:11 - 15:33 (15+19:22)
reboot   system boot  5.15.0-101-gener Tue Mar 19 19:44 - 15:33 (15+19:48)
me       tty7         :0               Mon Mar 11 08:19 - 19:44 (8+11:24)
reboot   system boot  5.15.0-100-gener Mon Mar 11 08:19 - 19:44 (8+11:24)
me       tty7         :0               Fri Mar  8 13:50 - 08:19 (2+17:29)
reboot   system boot  5.15.0-100-gener Fri Mar  8 13:34 - 08:19 (2+17:45)
me       tty7         :0               Mon Mar  4 12:41 - 13:33 (4+00:52)
reboot   system boot  5.15.0-97-generi Mon Mar  4 12:39 - 13:33 (4+00:53)
me       tty7         :0               Sat Mar  2 18:57 - 12:00 (1+17:02)
reboot   system boot  5.15.0-97-generi Sat Mar  2 18:57 - 12:00 (1+17:03)
me       tty7         :0               Sat Mar  2 18:42 - 18:44  (00:01)
reboot   system boot  5.15.0-97-generi Sat Mar  2 18:42 - 18:44  (00:01)
me       tty7         :0               Wed Feb 28 12:33 - 18:41 (3+06:08)
reboot   system boot  5.15.0-97-generi Wed Feb 28 12:32 - 18:41 (3+06:08)
me       tty7         :0               Tue Feb 27 15:38 - 15:41  (00:03)
reboot   system boot  5.15.0-97-generi Tue Feb 27 15:38 - 15:42  (00:03)
me       tty7         :0               Sun Feb 25 09:24 - 15:27 (2+06:02)
reboot   system boot  5.15.0-97-generi Sun Feb 25 09:24 - 15:27 (2+06:02)
me       tty7         :0               Sun Feb 25 08:22 - 09:24  (01:01)
reboot   system boot  5.15.0-97-generi Sun Feb 25 08:13 - 09:24  (01:10)
me       tty7         :0               Sun Feb 25 08:05 - 08:12  (00:06)
reboot   system boot  5.15.0-97-generi Sun Feb 25 08:05 - 08:12  (00:07)
me       tty7         :0               Fri Feb 23 17:17 - 08:04 (1+14:47)
reboot   system boot  5.15.0-97-generi Fri Feb 23 17:17 - 08:04 (1+14:47)
me       tty7         :0               Fri Feb 23 16:57 - 17:09  (00:12)
reboot   system boot  5.15.0-97-generi Fri Feb 23 16:56 - 17:09  (00:12)
me       tty7         :0               Tue Feb 20 08:48 - 16:56 (3+08:07)
reboot   system boot  5.15.0-91-generi Tue Feb 20 08:48 - 16:56 (3+08:07)
me       tty7         :0               Fri Feb 16 19:12 - 16:34  (21:22)
reboot   system boot  5.15.0-91-generi Fri Feb 16 19:12 - 16:34  (21:22)
me       tty7         :0               Wed Feb 14 15:20 - 15:24  (00:03)
reboot   system boot  5.15.0-91-generi Wed Feb 14 15:20 - 15:24  (00:04)
me       tty7         :0               Mon Feb 12 15:53 - 16:01  (00:08)
reboot   system boot  5.15.0-91-generi Mon Feb 12 15:53 - 16:01  (00:08)
me       tty7         :0               Wed Jan 24 16:35 - 16:55  (00:19)
reboot   system boot  5.15.0-91-generi Wed Jan 24 16:35 - 16:55  (00:19)
me       tty7         :0               Sun Jan 21 17:16 - 17:26  (00:10)
reboot   system boot  5.15.0-91-generi Sun Jan 21 16:45 - 17:26  (00:41)

wtmp begins Sun Jan 21 16:45:00 2024
linux-mint
  • 2 个回答
  • 54 Views

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    模块 i915 可能缺少固件 /lib/firmware/i915/*

    • 3 个回答
  • Marko Smith

    无法获取 jessie backports 存储库

    • 4 个回答
  • Marko Smith

    如何将 GPG 私钥和公钥导出到文件

    • 4 个回答
  • Marko Smith

    我们如何运行存储在变量中的命令?

    • 5 个回答
  • Marko Smith

    如何配置 systemd-resolved 和 systemd-networkd 以使用本地 DNS 服务器来解析本地域和远程 DNS 服务器来解析远程域?

    • 3 个回答
  • Marko Smith

    dist-upgrade 后 Kali Linux 中的 apt-get update 错误 [重复]

    • 2 个回答
  • Marko Smith

    如何从 systemctl 服务日志中查看最新的 x 行

    • 5 个回答
  • Marko Smith

    Nano - 跳转到文件末尾

    • 8 个回答
  • Marko Smith

    grub 错误:你需要先加载内核

    • 4 个回答
  • Marko Smith

    如何下载软件包而不是使用 apt-get 命令安装它?

    • 7 个回答
  • Martin Hope
    user12345 无法获取 jessie backports 存储库 2019-03-27 04:39:28 +0800 CST
  • Martin Hope
    Carl 为什么大多数 systemd 示例都包含 WantedBy=multi-user.target? 2019-03-15 11:49:25 +0800 CST
  • Martin Hope
    rocky 如何将 GPG 私钥和公钥导出到文件 2018-11-16 05:36:15 +0800 CST
  • Martin Hope
    Evan Carroll systemctl 状态显示:“状态:降级” 2018-06-03 18:48:17 +0800 CST
  • Martin Hope
    Tim 我们如何运行存储在变量中的命令? 2018-05-21 04:46:29 +0800 CST
  • Martin Hope
    Ankur S 为什么 /dev/null 是一个文件?为什么它的功能不作为一个简单的程序来实现? 2018-04-17 07:28:04 +0800 CST
  • Martin Hope
    user3191334 如何从 systemctl 服务日志中查看最新的 x 行 2018-02-07 00:14:16 +0800 CST
  • Martin Hope
    Marko Pacak Nano - 跳转到文件末尾 2018-02-01 01:53:03 +0800 CST
  • Martin Hope
    Kidburla 为什么真假这么大? 2018-01-26 12:14:47 +0800 CST
  • Martin Hope
    Christos Baziotis 在一个巨大的(70GB)、一行、文本文件中替换字符串 2017-12-30 06:58:33 +0800 CST

热门标签

linux bash debian shell-script text-processing ubuntu centos shell awk ssh

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve