我的 gvfs 守护进程有问题
我有一个安装的 gvfsd-fuse
$ mount | grep gvfs
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
Run Code Online (Sandbox Code Playgroud)
在 pc1 上(不使用 ssh)
$ gvfs-info -w $HOME
<...>
Writable attribute namespaces:
metadata (string, Copy with file, Keep with file when moved)
xattr (string, Copy with file, Keep with file when moved)
xattr-sys (string, Keep with file when moved)
Run Code Online (Sandbox Code Playgroud)
但是当我在这台机器上用 ssh 登录时
$ ssh -X user@pc1
$ gvfs-info -w $HOME
<...>
Writable attribute namespaces:
xattr (string, Copy with file, Keep with file when moved) …
Run Code Online (Sandbox Code Playgroud) 我有 2 台不同的机器,具有相同的操作系统版本和相同的源列表。
$ lsb_release -a
LSB Version: core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
Run Code Online (Sandbox Code Playgroud)
我在pc-1
和上使用以下命令更新我的软件包pc-2
:
$ sudo apt update
<...>
$ sudo apt -y upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Run Code Online (Sandbox Code Playgroud)
但是,我为每台机器获得了不同的内核版本:
pc-1 $ uname -r
5.0.0-25-generic
Run Code Online (Sandbox Code Playgroud)
和
pc-2 $ uname -r
4.15.0-58-generic
Run Code Online (Sandbox Code Playgroud)
为什么会这样,以及如何pc-2
使用官方存储库而不是 ppas安全地更新到最新的通用内核?
有没有办法在 apt 中调试/打印内核选择逻辑?