问题[snap](unix)

突然，快照包无法在我的系统中运行，并出现以下错误：

/user.slice/user-1000.slice/session-1.scope 不是 snap cgroup

操作系统：Debian 11

内核：5.10.0-12-amd64

$ SNAPD_DEBUG=1 snap run slack

2022/03/23 18:48:37.614818 tool_linux.go:204: DEBUG: restarting into "/snap/snapd/current/usr/bin/snap"
2022/03/23 18:48:37.625495 cmd_run.go:1026: DEBUG: executing snap-confine from /snap/snapd/15177/usr/lib/snapd/snap-confine
2022/03/23 18:48:37.625874 cmd_run.go:433: DEBUG: SELinux not enabled
2022/03/23 18:48:37.626049 tracking.go:46: DEBUG: creating transient scope snap.slack.slack
2022/03/23 18:48:37.626597 tracking.go:186: DEBUG: using session bus
2022/03/23 18:48:37.627860 tracking.go:294: DEBUG: StartTransientUnit failed with "org.freedesktop.DBus.Error.Spawn.ChildExited": [Process org.freedesktop.systemd1 exited with status 1]
2022/03/23 18:48:37.627986 cmd_run.go:1198: DEBUG: snapd cannot track the started application
2022/03/23 18:48:37.627996 cmd_run.go:1199: DEBUG: snap refreshes will not be postponed by this process
DEBUG: umask reset, old umask was  022
DEBUG: security tag: snap.slack.slack
DEBUG: executable:   /usr/lib/snapd/snap-exec
DEBUG: confinement:  non-classic
DEBUG: base snap:    core18
DEBUG: ruid: 1000, euid: 0, suid: 0
DEBUG: rgid: 1000, egid: 1000, sgid: 1000
DEBUG: apparmor label on snap-confine is: /snap/snapd/15177/usr/lib/snapd/snap-confine
DEBUG: apparmor mode is: enforce
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: opening lock file: /run/snapd/lock/.lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: acquiring exclusive lock (scope (global), uid 0)
DEBUG: sanity timeout reset and disabled
DEBUG: ensuring that snap mount directory is shared
DEBUG: unsharing snap namespace directory
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: releasing lock 5
DEBUG: opened snap-update-ns executable as file descriptor 5
DEBUG: opened snap-discard-ns executable as file descriptor 6
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: opening lock file: /run/snapd/lock/slack.lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: acquiring exclusive lock (scope slack, uid 0)
DEBUG: sanity timeout reset and disabled
DEBUG: initializing mount namespace: slack
DEBUG: setting up device cgroup
DEBUG: libudev has current tags support
DEBUG: device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 has matching current tag
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: get bpf object at path /sys/fs/bpf/snap/snap_slack_slack
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: found existing device map
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: get next key for map 8
DEBUG: found 20 existing entries in devices map
DEBUG: delete key for c 143:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 1:8
DEBUG: delete elem in map 8
DEBUG: delete key for c 10:239
DEBUG: delete elem in map 8
DEBUG: delete key for c 1:7
DEBUG: delete elem in map 8
DEBUG: delete key for c 138:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 142:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 137:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 141:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 5:0
DEBUG: delete elem in map 8
DEBUG: delete key for c 226:0
DEBUG: delete elem in map 8
DEBUG: delete key for c 140:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 1:9
DEBUG: delete elem in map 8
DEBUG: delete key for c 139:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 5:2
DEBUG: delete elem in map 8
DEBUG: delete key for c 1:5
DEBUG: delete elem in map 8
DEBUG: delete key for c 1:3
DEBUG: delete elem in map 8
DEBUG: delete key for c 226:128
DEBUG: delete elem in map 8
DEBUG: delete key for c 136:-1
DEBUG: delete elem in map 8
DEBUG: delete key for c 5:1
DEBUG: delete elem in map 8
DEBUG: delete key for c 10:200
DEBUG: delete elem in map 8
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: load program of type 0xf, 33 instructions
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: v2 allow c 1:3
DEBUG: v2 allow c 1:5
DEBUG: v2 allow c 1:7
DEBUG: v2 allow c 1:8
DEBUG: v2 allow c 1:9
DEBUG: v2 allow c 5:0
DEBUG: v2 allow c 5:1
DEBUG: v2 allow c 5:2
DEBUG: v2 allow c 136:4294967295
DEBUG: v2 allow c 137:4294967295
DEBUG: v2 allow c 138:4294967295
DEBUG: v2 allow c 139:4294967295
DEBUG: v2 allow c 140:4294967295
DEBUG: v2 allow c 141:4294967295
DEBUG: v2 allow c 142:4294967295
DEBUG: v2 allow c 143:4294967295
DEBUG: v2 allow c 10:239
DEBUG: v2 allow c 10:200
DEBUG: inspecting type of device: /dev/dri/card0
DEBUG: v2 allow c 226:0
DEBUG: device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1 has matching current tag
DEBUG: cannot get major/minor numbers for syspath /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1
DEBUG: device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1 has matching current tag
DEBUG: cannot get major/minor numbers for syspath /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1
DEBUG: device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-2 has matching current tag
DEBUG: cannot get major/minor numbers for syspath /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-2
DEBUG: device /sys/devices/pci0000:00/0000:00:02.0/drm/renderD128 has matching current tag
DEBUG: inspecting type of device: /dev/dri/renderD128
DEBUG: v2 allow c 226:128
DEBUG: process in cgroup /user.slice/user-1000.slice/session-1.scope
/user.slice/user-1000.slice/session-1.scope is not a snap cgroup

从 snapd 日志中，我认为根本问题是：

2022/03/23 18:48:37.627860 tracking.go:294：调试：StartTransientUnit 因“org.freedesktop.DBus.Error.Spawn.ChildExited”失败：[进程 org.freedesktop.systemd1 以状态 1 退出]

我可以采取哪些步骤来解决此问题？一些附加信息：

$ snap --version

snap    2.54.4
snapd   2.54.4
series  16
debian  11
kernel  5.10.0-12-amd64

$ systemctl --version

systemd 247 (247.3-6)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified

$ sudo systemct status dbus.service

 dbus.service - D-Bus System Message Bus
     Loaded: loaded (/lib/systemd/system/dbus.service; static)
     Active: active (running) since Wed 2022-03-23 18:17:36 MDT; 34min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 551 (dbus-daemon)
      Tasks: 1 (limit: 18764)
     Memory: 2.3M
        CPU: 1.785s
     CGroup: /system.slice/dbus.service
             └─551 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Mar 23 18:17:36 sboban-desktop systemd[1]: Started D-Bus System Message Bus.
Mar 23 18:17:37 sboban-desktop dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.11' >
Mar 23 18:17:37 sboban-desktop dbus-daemon[551]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 18:17:44 sboban-desktop dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.16' (uid=1000 pid=8>
Mar 23 18:17:44 sboban-desktop dbus-daemon[551]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Mar 23 18:18:10 sboban-desktop dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.11' >
Mar 23 18:18:10 sboban-desktop dbus-daemon[551]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 18:18:18 sboban-desktop dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.36' (uid=1000 pid=1192 comm="/u>
Mar 23 18:18:18 sboban-desktop dbus-daemon[551]: [system] Successfully activated service 'org.freedesktop.UPower'

$ systemctl --user dbus.service

dbus.service - D-Bus User Message Bus
     Loaded: loaded (/usr/lib/systemd/user/dbus.service; static)
     Active: active (running) since Wed 2022-03-23 18:17:44 MDT; 36min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 877 (dbus-daemon)
      Tasks: 1 (limit: 18764)
     Memory: 1.1M
        CPU: 5ms
     CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/dbus.service
             └─877 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Mar 23 18:17:44 sboban-desktop systemd[846]: Started D-Bus User Message Bus.

$ sudo systemctl status user@$(id -u)

 [email protected] - User Manager for UID 1000
     Loaded: loaded (/lib/systemd/system/[email protected]; static)
     Active: active (running) since Wed 2022-03-23 18:17:44 MDT; 37min ago
       Docs: man:[email protected](5)
   Main PID: 846 (systemd)
     Status: "Startup finished in 774ms."
      Tasks: 9
     Memory: 41.1M
        CPU: 484ms
     CGroup: /user.slice/user-1000.slice/[email protected]
             ├─app.slice
             │ ├─dbus.service
             │ │ └─877 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
             │ ├─pipewire.service
             │ │ ├─866 /usr/bin/pipewire
             │ │ └─878 /usr/bin/pipewire-media-session
             │ └─pulseaudio.service
             │   └─867 /usr/bin/pulseaudio --daemonize=no --log-target=journal
             └─init.scope
               ├─846 /lib/systemd/systemd --user
               └─847 (sd-pam)

Mar 23 18:17:44 sboban-desktop systemd[846]: Reached target Sockets.
Mar 23 18:17:44 sboban-desktop systemd[846]: Reached target Basic System.
Mar 23 18:17:44 sboban-desktop systemd[1]: Started User Manager for UID 1000.
Mar 23 18:17:44 sboban-desktop systemd[846]: Started Multimedia Service.
Mar 23 18:17:44 sboban-desktop systemd[846]: Starting Sound Service...
Mar 23 18:17:44 sboban-desktop systemd[846]: Started D-Bus User Message Bus.
Mar 23 18:17:44 sboban-desktop pipewire[866]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Mar 23 18:17:45 sboban-desktop systemd[846]: Started Sound Service.
Mar 23 18:17:45 sboban-desktop systemd[846]: Reached target Main User Target.
Mar 23 18:17:45 sboban-desktop systemd[846]: Startup finished in 774ms.

如果您需要更多信息，请告诉我。任何形式的帮助将不胜感激。谢谢你。

我已经将 Kubuntu 与 Snap 一起使用了很长一段时间，到目前为止还没有更大的问题。今天我所有的快照应用程序都停止启动，报告以下错误：

/user.slice/user-1000.slice/session-3.scope is not a snap cgroup

我怎样才能解决这个问题？

我最近切换到使用 OpenRC 作为初始化系统的 Artix Linux。我之前使用过 Manjaro，它使用 Systemd。无论如何，我试图安装一些我在 Manjaro 上使用的软件包，这些软件包是从 snap-store 获得的。但由于某些 systemd 依赖性，我无法安装它。我想是在尝试onlyOffice和其他东西。

我正在尝试在带有 Pop_OS 的 System 76 计算机上安装 GitKraken！安装。这是linux数据：

NAME="Pop!_OS"
VERSION="19.10"
ID=ubuntu
ID_LIKE=debian

姓名： Linux 5.3.0-7625-generic x86_64

我使用 snap 使用以下命令安装它： sudo snap install gitkraken

现在，当我在控制台中运行 gitkraken 时，我收到了这个错误：

Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
state:  update-not-available
cat: /etc/os-release: Permission denied

启动页面加载，但它永远不会超过。当我尝试安装 canberra-gtk-module 时，我看到了这个：

libcanberra-gtk3-module is already the newest version (0.30-7ubuntu1).
libcanberra-gtk3-module set to manually installed.
libcanberra-gtk-module is already the newest version (0.30-7ubuntu1).
libcanberra-gtk-module set to manually installed.

而且，当我检查是否有奇怪的权限时，/etc/os-release我看到了这个：

ls -lh /etc/os-release
lrwxrwxrwx 1 root root 17 Jul  9 16:14 /etc/os-release -> pop-os/os-release

所以它是一个符号链接而不是一个文件，但 GitKraken 无法正常运行似乎很奇怪。有没有人找到解决方案？我担心如果我将 os-release 从 pop-os 中移出，未来的升级将会中断。

请注意，我有 GitKraken 的个人许可证，如果您要求此级别的支持，他们会通过电子邮件告诉您支付更多支持费用。

我正在寻找在 Xfce 中安装 Okular 的最佳方法，避免过多的依赖项。虽然apt在 19 MB 的下载中提到了 100 个依赖项，在磁盘上占用了 101 MB，但我尝试了 flatpak 和 snap：第一个是通过打开文件添加到软件管理器中的org.kde.okular.flatpakref，但我宣布798,8 MB will be downloaded in total. 2,7 GB more disk space will be used

安装为 snap ( sudo snap install okular) 我在终端中看到下载不大于 1-2 MB。/var/lib/snapd/snaps/okular_73.snap有 21 MB 和/snap/bin/okular14.5 MB。这个快照是否存储了其他（更大的）文件？

那个flatpak公告是假的吗？

为什么会有巨大的差异？

snap Okular 是不完整的吗？（顺便说一句，它停止工作了。）

在学习 Linux bash 脚本的视频教程时，老师使用 atom 作为编辑器。

当我这样做时，我尝试安装 atom ：

sudo snap install atom

我收到消息：

错误：快照“原子”的此修订版是使用经典限制发布的，因此可能会在快照通常受限的安全沙箱之外执行任意系统更改，这可能会使您的系统处于危险之中。

如果您理解并想要继续重复该命令，包括 --classic.*

你会做什么/建议？

我在非 Ubuntu 系统上运行 snap 应用程序：

$ snap version                                                                                                                                   
snap    2.30-5+b1
snapd   2.30-5+b1
series  16
pureos  
kernel  4.18.0-1-amd64

当我snap run的一些应用程序工作，但其他人返回此错误：

cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied

按照snapcraft.io 的建议，我尝试过：

• 切换到 beta 核心。同样的错误。

• 修改 AppArmor 配置文件如下：

  1. 运行snap list以确定我正在使用的核心版本（核心 16-2.35.2 r 5548）

  2. 修改适当的文件 ( /etc/apparmor.d/snap.core.5548.usr.lib.snapd.snap-confine)，如所述添加ptrace read peer=unconfined,到末尾。

  3. 使用更新 AppArmorsudo apparmor_parser -r /etc/apparmor.d/snap.core.5548.usr.lib.snapd.snap-confine

但这没有什么区别。失败的应用程序继续失败。我还可以做些什么？

笔记

确认第 2 步：

$ tail /etc/apparmor.d/snap.core.5548.usr.lib.snapd.snap-confine                                                                                 
    # from the core snap but we are already inside the constructed mount
    # namespace. Here the apparmor kernel module re-constructs the path to
    # snap-update-ns using the "hostfs" mount entry rather than the more
    # "natural" /snap mount entry but we have no control over that.  This is
    # reported as (LP: #1716339). The variants here represent different
    # locations of snap mount directory across distributions.
    /var/lib/snapd/hostfs/{,var/lib/snapd/}snap/core/*/usr/lib/snapd/snap-update-ns r,

    ptrace read peer=unconfined,
}

我可以在 linux mint 18.3 中构建快照吗？在 snapcraft 教程中，我读到他们强烈推荐 ubuntu 16.04.3(LTS) 和 mint 18.3 基于 16.04。只需要Ubuntu吗？