其他人screen-sharing在设置->共享中有一个选项。但我没有。从这个答案中，我意识到最小安装是根本原因。尽管我已经尝试过该解决方案，但它不会显示给我。
我需要在 Wayland 上使用 obs 屏幕录像机的选项。这个项目需要启用屏幕共享选项，这样我才能记录完整的屏幕。
预期的：
我所看到的
如何在 Ubuntu 20.04 上禁用super+快捷方式。s我已经尝试了 compiz 管理器，然后去博览会，然后禁用博览会密钥。但它不会起作用。我想将此快捷方式绑定到其他应用程序。
如果有什么不同，我使用 Wayland 而不是 X11。
我尝试了以下解决方案
如何使用 <super>+w/a/s/d 作为快捷方式？
在 ubuntu 13.04 中禁用 super + s
我观察到的是手册页中的文本间距不均匀。有些单词之间有一个空格，而有些单词有双倍空格。
我观察到的是，这种双倍行距仅在第一行之间DESCRIPTION和任何段落的第一个句号之后。
这有什么原因吗？如上所述，这绝对不是随机的（或错误），存在模式。这确实激起了我的好奇心。
这是我跑步后看到的man more。但是我几乎在我看到的每个手册页上都观察到了这一点。我也在我的虚拟机上试过这个，所以不是系统错误（或故障）。
在 VLC 网站上，它说它仅支持 16.04 和 18.04 版本。
但是当我sudo apt install vlc直接在终端运行时，它确实安装了 vlc。那么，它在 20.04 上是如何工作的呢？
我也尝试添加他们的 PPA ( sudo add-apt-repository ppa:videolan/stable-daily)，但它显示发布文件错误，这也证实了他们没有在 20.04 发布它。
那么，它如何与sudo apt install vlc.
我最初在我的 PC 上的 SSD 上安装了 Windows 10。然后我决定在 HDD 上双启动 Ubuntu。grub 安装在 HDD 上，因此要查看 GRUB 菜单，我必须在启动优先级中选择 HDD（在 BIOS 中命名为 Ubuntu，SSD 命名为 Windows Boot Manager）。
现在我在 SSD 上安装了 Ubuntu，并在安装时格式化了 SSD。我期待摆脱Windows。但是在 BIOS 中，SSD 仍然被命名为 Windows Boot Manager 而不是 Ubuntu，并且当在启动优先级中选择 SSD 优先时，它会打开恢复模式。仅当我将 HDD 置于启动优先级中时，我才会看到 GRUB。
那么，如何从 SSD 中删除 Windows 启动管理器，并使其成为 Ubuntu。这样当我在 Boot priority 中选择 SSD first 时，它会直接启动进入 Ubuntu，而无需打开 grub。
启动优先级：
Windows 错误恢复模式：
Grub 启动菜单：
的输出sudo os-prober：
/dev/sdb2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sdb3:Ubuntu 20.04 LTS (20.04):Ubuntu:linux
/dev/sdb4:Pop!_OS 20.04 LTS (20.04):Pop:linux
这里sdb3磁盘上的 Ubuntu 是之前安装的 Ubuntu，SSD 上较新的 Ubuntu 没有显示。
我删除了/boot/efi/EFI/Microsoft/，现在Windows Boot Manager已经删除了，但 SSD 无法直接启动。
新的启动优先级选项：
我想摆脱 Windows 启动管理器，我通过删除/boot/efi/EFI/Microsoft/文件夹来做到这一点。
当我使用 Windows 时，我可以选择 SSD 或 HDD 作为启动优先级的第一个选项。当我选择安装了 Windows 10 的 SSD 时，我会直接启动到 Windows，没有任何 GRUB 提示。但是当我选择 HDD 时，我会得到带有 windows、Ubuntu 和 Pop!_OS 选项的 GRUB 提示符。
现在我想实现类似的结果，只是我想在 SSD 上使用 Ubuntu 而不是 Windows。这样，当在启动优先级中首先选择 SSD 时，它会在没有任何 GRUB 提示的情况下在 SSD 上启动到 Ubuntu，但是当我在启动优先级中首先选择 HDD 时，我会得到 GRUB 提示，以选择 Ubuntu（从SSD）、Ubuntu（来自 HDD）或 Pop!_OS。
现在的问题是我在 BIOS 启动优先级中看不到 SSD，如第四张屏幕照片所示。早些时候，我可以像第一张屏幕照片一样选择 SSD 或 HDD。Windows 引导管理器是 SSD，另一个操作系统是 HDD。
当我gnome-shell使用alt + F2 + r以下主要问题重新启动时：
- 无响应的窗口
- 无响应的桌面
- 高内存使用率
得到完美修复。那么，它究竟为什么会起作用以及重新启动时会发生什么gnome-shell？
当我跑步时，ls -al ~/.local/share/gnome-shell/extensions我看到
total 16
drwxrwxr-x 4 abhay abhay 4096 May 16 15:08 .
drwx------ 3 abhay abhay 4096 Jun 1 03:12 ..
drwxrwxr-x 4 abhay abhay 4096 May 16 15:02 clipboard-indicator@tudmotu.com
drwxrwxr-x 4 abhay abhay 4096 May 3 15:28 user-theme@gnome-shell-extensions.gcampax.github.com
当我跑步时，ls -al /usr/share/gnome-shell/extensions我看到
total 20
drwxr-xr-x 5 root root 4096 Apr 23 13:05 .
drwxr-xr-x 7 root root 4096 May 23 01:14 ..
drwxr-xr-x 2 root root 4096 Apr 23 13:05 desktop-icons@csoriano
drwxr-xr-x 3 root root 4096 Apr 23 13:05 ubuntu-appindicators@ubuntu.com
drwxr-xr-x 3 root root 4096 May 27 15:38 ubuntu-dock@ubuntu.com
当我跑步时，free -h我看到
total used free shared buff/cache available
Mem: 7.6Gi 1.5Gi 4.9Gi 289Mi 1.1Gi 5.5Gi
Swap: 4.0Gi 0B 4.0Gi
当我跑步时，top我看到
top - 23:26:52 up 6 min, 1 user, load average: 1.01, 1.02, 0.57
Tasks: 300 total, 1 running, 299 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.4 us, 0.2 sy, 0.0 ni, 99.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 7801.6 total, 5044.1 free, 1599.8 used, 1157.7 buff/cache
MiB Swap: 4096.0 total, 4096.0 free, 0.0 used. 5666.4 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1757 abhay 20 0 912636 118792 79564 S 3.3 1.5 0:35.37 Xorg
2382 abhay 20 0 965964 49564 37136 S 3.3 0.6 0:05.89 gnome-terminal-
2002 abhay 20 0 4924592 277768 116092 S 2.3 3.5 0:36.19 gnome-shell
2608 abhay 20 0 2895956 378652 191188 S 0.7 4.7 0:35.07 Web Content
1 root 20 0 167704 11632 8480 S 0.3 0.1 0:03.13 systemd
1956 abhay 20 0 162812 7596 6816 S 0.3 0.1 0:00.20 at-spi2-registr
2496 abhay 20 0 3564084 393188 186492 S 0.3 4.9 1:03.71 firefox
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
5 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0-cgroup_destroy
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-kblockd
7 root 20 0 0 0 0 I 0.0 0.0 0:00.06 kworker/0:1-events
8 root 20 0 0 0 0 I 0.0 0.0 0:00.98 kworker/u24:0-events_unbound
9 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
11 root 20 0 0 0 0 I 0.0 0.0 0:00.41 rcu_sched
12 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
13 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/0
14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
15 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
16 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/1
17 root rt 0 0 0 0 S 0.0 0.0 0:00.06 migration/1
18 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
20 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-kblockd
21 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2
22 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/2
23 root rt 0 0 0 0 S 0.0 0.0 0:00.06 migration/2
24 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/2
26 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/2:0H-kblockd
27 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3
28 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/3
29 root rt 0 0 0 0 S 0.0 0.0 0:00.07 migration/3
30 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/3
当我跑步时，systemd-analyze blame我看到
1min 30.122s nmbd.service
12.973s networkd-dispatcher.service
11.924s udisks2.service
11.297s snapd.service
8.876s samba-ad-dc.service
7.313s dev-sdb3.device
5.269s NetworkManager.service
5.225s accounts-daemon.service
4.762s polkit.service
3.740s ModemManager.service
3.666s avahi-daemon.service
3.665s bluetooth.service
3.300s switcheroo-control.service
3.295s thermald.service
3.292s wpa_supplicant.service
3.291s systemd-logind.service
2.996s dev-loop4.device
2.970s gpu-manager.service
2.881s dev-loop5.device
2.798s systemd-resolved.service
2.622s dev-loop3.device
2.496s apport.service
2.443s grub-common.service
2.006s gdm.service
1.915s dev-loop0.device
1.761s rsyslog.service
1.756s secureboot-db.service
1.640s grub-initrd-fallback.service
1.373s dev-loop2.device
1.370s dev-loop1.device
995ms systemd-tmpfiles-setup.service
823ms upower.service
816ms pppd-dns.service
776ms e2scrub_reap.service
738ms systemd-fsck@dev-disk-by\x2duuid-E866\x2d1E0F.service
723ms systemd-modules-load.service
717ms apparmor.service
713ms tlp.service
542ms systemd-sysusers.service
541ms systemd-random-seed.service
515ms systemd-timesyncd.service
508ms snapd.seeded.service
507ms smbd.service
480ms systemd-journald.service
457ms swapfile.swap
434ms systemd-udevd.service
430ms systemd-udev-trigger.service
347ms snapd.apparmor.service
342ms keyboard-setup.service
333ms snap-bitwarden-25.mount
319ms colord.service
318ms snap-bitwarden-24.mount
299ms snap-core18-1754.mount
266ms snap-snapd-7264.mount
256ms modprobe@drm.service
255ms snap-gtk\x2dcommon\x2dthemes-1506.mount
240ms systemd-backlight@backlight:intel_backlight.service
235ms snap-gnome\x2d3\x2d28\x2d1804-116.mount
227ms systemd-tmpfiles-setup-dev.service
224ms kerneloops.service
213ms binfmt-support.service
196ms systemd-sysctl.service
182ms setvtrgb.service
175ms ufw.service
141ms openvpn.service
140ms geoclue.service
135ms user@1000.service
127ms systemd-remount-fs.service
106ms console-setup.service
104ms plymouth-read-write.service
98ms dev-hugepages.mount
97ms dev-mqueue.mount
96ms sys-kernel-debug.mount
96ms sys-kernel-tracing.mount
92ms kmod-static-nodes.service
89ms systemd-user-sessions.service
85ms boot-efi.mount
67ms systemd-tmpfiles-clean.service
28ms systemd-update-utmp.service
25ms rtkit-daemon.service
25ms proc-sys-fs-binfmt_misc.mount
23ms systemd-journal-flush.service
14ms systemd-update-utmp-runlevel.service
13ms user-runtime-dir@1000.service
9ms alsa-restore.service
4ms sys-fs-fuse-connections.mount
3ms plymouth-quit-wait.service
3ms sys-kernel-config.mount
825us snapd.socket
当我跑步时，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>
# / was on /dev/sdb3 during installation
UUID=729e17ba-8e24-41fb-ab2d-779ba62bfb60 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb2 during installation
UUID=E866-1E0F /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
当我跑步时，cat /etc/samba/smb.conf我看到
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap config * : backend = tdb
; idmap config * : range = 3000-7999
; idmap config YOURDOMAINHERE : backend = tdb
; idmap config YOURDOMAINHERE : range = 100000-999999
; template shell = /bin/bash
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 means that usershare is disabled.
# usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
当我跑步时，testparm我看到
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
log file = /var/log/samba/log.%m
logging = file
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
passwd program = /usr/bin/passwd %u
server role = standalone server
server string = %h server (Samba, Ubuntu)
unix password sync = Yes
usershare allow guests = Yes
idmap config * : backend = tdb
[printers]
browseable = No
comment = All Printers
create mask = 0700
path = /var/spool/samba
printable = Yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
Swappiness设置为60。
我在 Ubuntu 20.04 LTS 上安装了 GNOME-sushi。最初，当我选择一个视频并按下spacebar时，出现以下错误。
安装gstreamer1.0-plugins-bad和gstreamer1.0-plugins-ugly包后，只播放音频，不播放视频。
以下已安装（使用dpkg -l | grep gstreamer）
ii gir1.2-gstreamer-1.0:amd64 1.16.2-2 amd64 GObject introspection data for the GStreamer library
ii gstreamer1.0-alsa:amd64 1.16.2-4 amd64 GStreamer plugin for ALSA
ii gstreamer1.0-clutter-3.0:amd64 3.0.27-1 amd64 Clutter PLugin for GStreamer 1.0
ii gstreamer1.0-gl:amd64 1.16.2-4 amd64 GStreamer plugins for GL
ii gstreamer1.0-gtk3:amd64 1.16.2-1ubuntu2 amd64 GStreamer plugin for GTK+3
ii gstreamer1.0-packagekit 1.1.13-2ubuntu1 amd64 GStreamer plugin to install codecs using PackageKit
ii gstreamer1.0-plugins-bad:amd64 1.16.2-2.1ubuntu1 amd64 GStreamer plugins from the "bad" set
ii gstreamer1.0-plugins-base:amd64 1.16.2-4 amd64 GStreamer plugins from the "base" set
ii gstreamer1.0-plugins-base-apps 1.16.2-4 amd64 GStreamer helper programs from the "base" set
ii gstreamer1.0-plugins-good:amd64 1.16.2-1ubuntu2 amd64 GStreamer plugins from the "good" set
ii gstreamer1.0-plugins-ugly:amd64 1.16.2-2build1 amd64 GStreamer plugins from the "ugly" set
ii gstreamer1.0-pulseaudio:amd64 1.16.2-1ubuntu2 amd64 GStreamer plugin for PulseAudio
ii gstreamer1.0-tools 1.16.2-2 amd64 Tools for use with GStreamer
ii gstreamer1.0-x:amd64 1.16.2-4 amd64 GStreamer plugins for X11 and Pango
ii libgstreamer-gl1.0-0:amd64 1.16.2-4 amd64 GStreamer GL libraries
ii libgstreamer-plugins-bad1.0-0:amd64 1.16.2-2.1ubuntu1 amd64 GStreamer libraries from the "bad" set
ii libgstreamer-plugins-base1.0-0:amd64 1.16.2-4 amd64 GStreamer libraries from the "base" set
ii libgstreamer-plugins-good1.0-0:amd64 1.16.2-1ubuntu2 amd64 GStreamer development files for libraries from the "good" set
ii libgstreamer1.0-0:amd64 1.16.2-2 amd64 Core GStreamer libraries and elements
如何安装缺少的插件？
我的主计算机上安装了 Ubuntu 20.04 LTS，辅助计算机上安装了 Windows 10 1909。我通常建立网站。如果我想查看一个简单的 HTML 文件，我只需在浏览器上打开它。但是，如果我想在我的辅助 PC 上查看这些内容怎么办。
我应该怎么做才能在我的辅助计算机上的浏览器上打开这些 HTML 文件？
我最近安装了 chrome dev 版本，即使我已经安装了 chrome（稳定版）。
在检查更新后，sudo apt update我收到以下错误（可能是警告）。
我该如何处理它们？原因是什么。
额外信息：我通过下载包安装了 dev .deb，然后执行sudo apt install /home/abhay/Downloads/google-chrome-unstable_current_amd64.deb.
我还可以在Software & Updates.
这和这件事有什么关系吗？这是一个问题，有两个相同的 PPA。
我正在尝试安装一个名为 Stacer 的工具，以从我的 PC（Ubuntu 20.04 LTS）中清除垃圾文件。
该应用程序已安装但每次使用sudo apt-get update && sudo apt-get upgrade时，我都会收到以下错误
Ign:11 http://ppa.launchpad.net/oguzhaninan/stacer/ubuntu焦点 InRelease
Err:12 http://ppa.launchpad.net/oguzhaninan/stacer/ubuntu焦点版本 404 未找到 [IP: 2001:67c: 1560:8008::15 80] 正在读取包列表...完成 E：存储库“ http://ppa.launchpad.net/oguzhaninan/stacer/ubuntu焦点发布”没有发布文件。N：从这样的存储库更新不能安全地完成，因此默认情况下是禁用的。N：有关存储库创建和用户配置的详细信息，请参见 apt-secure(8) 手册页。
我应该怎么办？
编辑 1如果存储库/PPA 没有发布文件，我该怎么办 ？.
他们建议删除 PPA。但是错误消息说默认情况下它是禁用的。所以可能有一种方法可以启用它。
firefox-locale-en尽管我在第一天就卸载了 Firefox，但在我的系统（Ubuntu 20.04 lts）上调用了一个包。用 清除它是否安全sudo apt purge firefox-locale-en？
编辑 1
如果是，它有什么作用？
编辑 2
尽管这听起来像是一个愚蠢的疑问，但我总是希望有一个有见识的人的意见，因为我记得上次python3.6没有被我专门使用，我决定清除它。才发现我的电脑根本不能用了。因此我从 18.04 到 20.04。同样，我认为 Firefox 可能与 Ubuntu 上的某些互联网相关服务相关联。
旧版本的 Ubuntu 附带 python 2.7 和 python 3.6。但是在 Ubuntu 20.04 LTS 中，只安装了 python 3.8。所以当python在终端输入时，python3.8 打开了。python，python3并python3.8做了同样的打开python3.8的工作。
但后来当我安装 python2.7 时，它弄乱了python命令。当我使用python命令时，python2.7 开始打开。现在要使用 python3.8 我需要python3或python3.8.
有人能解释一下为什么pythoncommand 改变了它的目标应用程序吗？
Ubuntu（早于 20.04 LTS）附带 Python 3 和 python 2。当python在终端中输入时，python2.7 会打开，而要打开 python 3.6，python3则需要命令。然而python3.6也有效。
所以我的疑问是为什么python3两者python3.6都有效？从技术上讲，因为我安装了 python3.6，所以python3.6应该可以工作。但是为什么python3也有效呢？
编辑 1
当我键入python并按两次制表符（显示可能的命令）时，我同时看到了 python3 和 python3.8。
python3我的疑问是命令和python3.6命令在执行中的区别是什么。
我最近在 Ubuntu 20.04 LTS 上安装了来自gnome-look.org的 GRUB 主题（我的 PC 是带有 Ubuntu 的 Windows 10 双启动）。要成功安装主题，/etc/default/grub需要编辑文件。
所以我使用sudo gedit /etc/default/grub命令来这样做。保存后编辑后，在终端中看到以下警告：
(gedit:7169): Tepl-WARNING **: 21:13:18.135: GVfs metadata is not supported. Fallback to TeplMetadataManager. Either GVfs is not correctly installed or GVfs metadata are not supported on this platform. In the latter case, you should configure Tepl with --disable-gvfs-metadata.
后来我还/boot/grub/grub.cfg通过使用sudo gedit /boot/grub/grub.cfg.
保存文件后，我收到了类似的警告
(gedit:8887): Tepl-WARNING **: 21:18:46.163: GVfs metadata is not supported. Fallback to TeplMetadataManager. Either GVfs is not correctly installed or GVfs metadata are not supported on this platform. In the latter case, you should configure Tepl with --disable-gvfs-metadata.
有人可以告诉我原因吗？以及如何处理？
我最近从 Elementary OS 转移到了 UBUNTU 20.04 LTS。Elementary OS 上一个非常有用的功能是终端铃声。终端中的命令执行完毕后，会有铃声响起，通知区有提示。
这可以通过使用notify-send "Task Complete" && printf '\a'与原始命令一起使用来实现&&。
但这里有一个问题：
1. 这个命令很长，每次都需要输入。alias可以使用，但您仍然必须每次都键入它。
2. 即使在终端对焦时也会响起。
所以我的问题是，我希望每次notify-send "Task Complete" && printf '\a'只在终端失焦时执行一个特定的命令。这也无需每次都输入。
编辑 1
有人建议如何在流程完成后发出声音？
但我的问题是在不输入任何额外命令的情况下按铃。有没有办法可以在终端本身中集成一些脚本或其他东西，以便它自己调用哔声而无需任何额外的命令。