我需要使用 lyx 的早期版本，该版本在 24.04 中不可用。我该如何添加此存储库？我想我问的是新格式化的 Ubuntu.sources 文件中的 Signed-By 行，该文件替换了 sources.list 文件。
# route -v
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default RT-00904C0FF018 0.0.0.0 UG 1024 0 0 eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.18.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-55985fc83fa9
172.19.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-4a2e674be385
172.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-c4a5411407dd
172.21.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-7eb7fa74a326
172.22.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-3b304b8d2b9f
172.23.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-519d33f42172
172.24.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-10bfee6d9dcb
172.25.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-5f628b8f8682
172.26.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-d7fcffbb970a
172.27.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-4b57aa2459c5
172.28.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-a4759ccfc8c4
172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-fa55d2bd337d
172.30.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-f7574a62a5c4
172.31.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-45084db52c51
192.168.0.0 0.0.0.0 255.255.240.0 U 0 0 0 br-65a630f9019d
192.168.16.0 0.0.0.0 255.255.240.0 U 0 0 0 br-5aa5d76d0c7a
192.168.32.0 0.0.0.0 255.255.240.0 U 0 0 0 br-e0d66f2d6753
192.168.48.0 0.0.0.0 255.255.240.0 U 0 0 0 br-beb580b505a2
192.168.214.0 0.0.0.0 255.255.255.0 U 1024 0 0 eth0
RT-00904C0FF018 0.0.0.0 255.255.255.255 UH 1024 0 0 eth0
- 我有一个 LXC，里面运行着一堆 Docker 容器
- 我看到很多 172.xxx，并假设它们属于某些容器
- 我不太明白为什么
192.x.x.x还有 - 为什么从 172.x 跳到 192.x？
我的问题是，我在 192.168.9.111 上有一个实际的服务器，但由于这些路由，我无法访问它。有什么想法吗？
我正在尝试从 IOS iPad 连接到 Ubuntu 计算机。按照此处的说明（您可以将 iPhone 连接到 Ubuntu 媒体共享吗？）我已经共享了我的用户文档文件夹并连接到它，但当我尝试打开它时，我收到“内容不可用”消息（见屏幕截图）。我在网上读到了一些建议，删除 IOS 上的文件应用程序并再次下载，重新启动 iPad - 但这些都没有改变。有什么想法可能是什么问题吗？
更新 1：
以下是文件内容/etc/samba/smb.conf。我使用的是 Ubuntu 22.04。我也尝试过从 OSX 连接到 Ubuntu 计算机 - 同样的问题，连接但不显示内容。
# 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 <<[email protected]> 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 = classic
# primary domain controller', 'server role = classic 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
更新2：
以下输出net usershare info --long：
$ net usershare info --long
[Documents]
path=/home/garrett/Documents
comment=
usershare_acl=Everyone:F,
guest_ok=n
我已使用和禁用ctrl++键命令。altDELsudo systemctl mask ctrl-alt-del.targetsudo systemctl daemon-reload
但即使如此，如果我连续按下ctrl+ alt+DEL键命令，系统也会重新启动。
这是 Ubuntu 的一个已知问题还是预期的行为？
PS：我仅通过 SSH 使用 cli 界面。因此基于 GUI 的答案没有帮助。
我已经从 ubuntu 22.04 升级到 24.04，但 skype repo 出现了一些问题。我卸载了 skypeforlinux，但 repo...我无法删除它。
每次更新我都会收到此错误：
Err:5 https://repo.skype.com/deb stable InRelease
503 Service Unavailable [IP: 2a02:26f0:3500:c84::1263 443]
Fetched 1.080 kB in 7s (144 kB/s)
Reading package lists... Done
W: Failed to fetch https://repo.skype.com/deb/dists/stable/InRelease 503 Service Unavailable [IP: 2a02:26f0:3500:c84::1263 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
我尝试像这样删除 ppa：
sudo add-apt-repository --remove https://repo.skype.com/deb stable main
但我收到此错误：
Repository: 'deb https://repo.skype.com/deb noble stable main'
Description:
Archive for codename: noble components: stable,main
More info: https://repo.skype.com/deb
Removing repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in <module>
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 355, in main
shortcut.remove()
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 233, in remove
self.remove_source()
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 349, in remove_source
sourceslist.save(remove=True)
File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 391, in save
with open(filename, "w") as f:
PermissionError: [Errno 1] Operation not permitted: '/etc/apt/sources.list.d/skype-stable.list'
我怎样才能删除 skype ppa???
更新
输出ps -ea
PID TTY TIME CMD
1 ? 00:00:01 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 pool_workqueue_release
4 ? 00:00:00 kworker/R-rcu_g
5 ? 00:00:00 kworker/R-rcu_p
6 ? 00:00:00 kworker/R-slub_
7 ? 00:00:00 kworker/R-netns
8 ? 00:00:00 kworker/0:0-events
10 ? 00:00:00 kworker/0:0H-events_highpri
11 ? 00:00:00 kworker/u64:0-netns
12 ? 00:00:00 kworker/R-mm_pe
13 ? 00:00:00 rcu_tasks_kthread
14 ? 00:00:00 rcu_tasks_rude_kthread
15 ? 00:00:00 rcu_tasks_trace_kthread
16 ? 00:00:00 ksoftirqd/0
17 ? 00:00:00 rcu_preempt
18 ? 00:00:00 migration/0
19 ? 00:00:00 idle_inject/0
20 ? 00:00:00 cpuhp/0
21 ? 00:00:00 cpuhp/1
22 ? 00:00:00 idle_inject/1
23 ? 00:00:00 migration/1
24 ? 00:00:00 ksoftirqd/1
25 ? 00:00:00 kworker/1:0-events
26 ? 00:00:00 kworker/1:0H-events_highpri
27 ? 00:00:00 cpuhp/2
28 ? 00:00:00 idle_inject/2
29 ? 00:00:00 migration/2
30 ? 00:00:00 ksoftirqd/2
31 ? 00:00:00 kworker/2:0-events
32 ? 00:00:00 kworker/2:0H-events_highpri
33 ? 00:00:00 cpuhp/3
34 ? 00:00:00 idle_inject/3
35 ? 00:00:00 migration/3
36 ? 00:00:00 ksoftirqd/3
38 ? 00:00:00 kworker/3:0H-events_highpri
39 ? 00:00:00 cpuhp/4
40 ? 00:00:00 idle_inject/4
41 ? 00:00:00 migration/4
42 ? 00:00:00 ksoftirqd/4
44 ? 00:00:00 kworker/4:0H-events_highpri
45 ? 00:00:00 cpuhp/5
46 ? 00:00:00 idle_inject/5
47 ? 00:00:00 migration/5
48 ? 00:00:00 ksoftirqd/5
49 ? 00:00:00 kworker/5:0-events
50 ? 00:00:00 kworker/5:0H-events_highpri
51 ? 00:00:00 cpuhp/6
52 ? 00:00:00 idle_inject/6
53 ? 00:00:00 migration/6
54 ? 00:00:00 ksoftirqd/6
56 ? 00:00:00 kworker/6:0H-events_highpri
57 ? 00:00:00 cpuhp/7
58 ? 00:00:00 idle_inject/7
59 ? 00:00:00 migration/7
60 ? 00:00:00 ksoftirqd/7
62 ? 00:00:00 kworker/7:0H-events_highpri
63 ? 00:00:00 cpuhp/8
64 ? 00:00:00 idle_inject/8
65 ? 00:00:00 migration/8
66 ? 00:00:00 ksoftirqd/8
68 ? 00:00:00 kworker/8:0H-events_highpri
69 ? 00:00:00 cpuhp/9
70 ? 00:00:00 idle_inject/9
71 ? 00:00:00 migration/9
72 ? 00:00:00 ksoftirqd/9
74 ? 00:00:00 kworker/9:0H-events_highpri
75 ? 00:00:00 cpuhp/10
76 ? 00:00:00 idle_inject/10
77 ? 00:00:00 migration/10
78 ? 00:00:00 ksoftirqd/10
80 ? 00:00:00 kworker/10:0H-events_highpri
81 ? 00:00:00 cpuhp/11
82 ? 00:00:00 idle_inject/11
83 ? 00:00:00 migration/11
84 ? 00:00:00 ksoftirqd/11
86 ? 00:00:00 kworker/11:0H-events_highpri
87 ? 00:00:00 cpuhp/12
88 ? 00:00:00 idle_inject/12
89 ? 00:00:00 migration/12
90 ? 00:00:00 ksoftirqd/12
91 ? 00:00:00 kworker/12:0-events
92 ? 00:00:00 kworker/12:0H-events_highpri
93 ? 00:00:00 cpuhp/13
94 ? 00:00:00 idle_inject/13
95 ? 00:00:00 migration/13
96 ? 00:00:00 ksoftirqd/13
98 ? 00:00:00 kworker/13:0H-events_highpri
99 ? 00:00:00 cpuhp/14
100 ? 00:00:00 idle_inject/14
101 ? 00:00:00 migration/14
102 ? 00:00:00 ksoftirqd/14
104 ? 00:00:00 kworker/14:0H-events_highpri
105 ? 00:00:00 cpuhp/15
106 ? 00:00:00 idle_inject/15
107 ? 00:00:00 migration/15
108 ? 00:00:00 ksoftirqd/15
109 ? 00:00:00 kworker/15:0-rcu_par_gp
110 ? 00:00:00 kworker/15:0H-events_highpri
113 ? 00:00:00 kdevtmpfs
114 ? 00:00:00 kworker/R-inet_
116 ? 00:00:00 kauditd
117 ? 00:00:00 kworker/0:2-events
119 ? 00:00:00 kworker/1:2-rcu_par_gp
120 ? 00:00:00 khungtaskd
121 ? 00:00:00 oom_reaper
123 ? 00:00:00 kworker/R-write
124 ? 00:00:00 kcompactd0
125 ? 00:00:00 ksmd
126 ? 00:00:00 khugepaged
127 ? 00:00:00 kworker/R-kinte
128 ? 00:00:00 kworker/R-kbloc
129 ? 00:00:00 kworker/R-blkcg
130 ? 00:00:00 irq/9-acpi
132 ? 00:00:00 kworker/R-tpm_d
133 ? 00:00:00 kworker/R-ata_s
134 ? 00:00:00 kworker/R-md
135 ? 00:00:00 kworker/R-md_bi
136 ? 00:00:00 kworker/R-edac-
137 ? 00:00:00 kworker/u64:1-ext4-rsv-conversion
138 ? 00:00:00 kworker/R-devfr
139 ? 00:00:00 watchdogd
140 ? 00:00:00 kworker/1:1H-kblockd
142 ? 00:00:00 irq/25-AMD-Vi
143 ? 00:00:00 kswapd0
144 ? 00:00:00 ecryptfs-kthread
145 ? 00:00:00 kworker/R-kthro
146 ? 00:00:00 irq/26-aerdrv
147 ? 00:00:00 irq/27-aerdrv
148 ? 00:00:00 irq/28-aerdrv
149 ? 00:00:00 irq/29-aerdrv
150 ? 00:00:00 irq/31-aerdrv
152 ? 00:00:00 kworker/4:1-events
154 ? 00:00:00 kworker/6:1-mm_percpu_wq
155 ? 00:00:00 kworker/7:1-events
158 ? 00:00:00 kworker/11:1-events
159 ? 00:00:00 kworker/12:1-events
160 ? 00:00:00 kworker/13:1-mm_percpu_wq
161 ? 00:00:00 kworker/14:1-rcu_par_gp
163 ? 00:00:00 kworker/R-acpi_
166 ? 00:00:00 kworker/R-mld
167 ? 00:00:00 kworker/R-ipv6_
169 ? 00:00:00 kworker/5:1H-kblockd
175 ? 00:00:00 kworker/R-kstrp
177 ? 00:00:00 kworker/u67:0-hci0
178 ? 00:00:00 kworker/u68:0-ttm
192 ? 00:00:00 kworker/R-charg
218 ? 00:00:00 kworker/6:1H-kblockd
220 ? 00:00:00 kworker/0:1H-kblockd
234 ? 00:00:00 kworker/13:1H-kblockd
240 ? 00:00:00 kworker/9:1H-kblockd
263 ? 00:00:00 kworker/2:1H-kblockd
264 ? 00:00:00 kworker/12:1H-kblockd
265 ? 00:00:00 kworker/7:1H-kblockd
266 ? 00:00:00 kworker/15:1H-kblockd
267 ? 00:00:00 kworker/11:1H-kblockd
268 ? 00:00:00 kworker/3:1H-kblockd
269 ? 00:00:00 kworker/10:1H-kblockd
270 ? 00:00:00 kworker/8:1H-kblockd
273 ? 00:00:00 kworker/14:1H-kblockd
275 ? 00:00:00 kworker/4:1H-kblockd
288 ? 00:00:00 kworker/R-nvme-
289 ? 00:00:00 kworker/14:2-events
296 ? 00:00:00 kworker/R-nvme-
297 ? 00:00:00 kworker/R-nvme-
301 ? 00:00:00 kworker/R-nvme-
324 ? 00:00:00 scsi_eh_0
325 ? 00:00:00 kworker/R-scsi_
326 ? 00:00:00 scsi_eh_1
327 ? 00:00:00 kworker/R-scsi_
328 ? 00:00:00 scsi_eh_2
329 ? 00:00:00 kworker/R-scsi_
330 ? 00:00:00 scsi_eh_3
331 ? 00:00:00 kworker/R-scsi_
332 ? 00:00:00 scsi_eh_4
333 ? 00:00:00 kworker/R-scsi_
334 ? 00:00:00 scsi_eh_5
335 ? 00:00:00 kworker/R-scsi_
336 ? 00:00:00 scsi_eh_6
337 ? 00:00:00 kworker/R-scsi_
338 ? 00:00:00 scsi_eh_7
339 ? 00:00:00 kworker/R-scsi_
342 ? 00:00:15 kworker/u66:4+events_unbound
348 ? 00:00:00 scsi_eh_8
349 ? 00:00:00 kworker/R-scsi_
350 ? 00:00:16 kworker/u66:10-events_unbound
352 ? 00:00:00 kworker/4:2-rcu_par_gp
355 ? 00:00:00 kworker/7:2-cgroup_destroy
358 ? 00:00:00 kworker/8:2-mm_percpu_wq
378 ? 00:00:00 jbd2/nvme0n1p2-8
379 ? 00:00:00 kworker/R-ext4-
420 ? 00:00:00 psimon
425 ? 00:00:00 systemd-journal
449 ? 00:00:00 kworker/2:2-rcu_par_gp
455 ? 00:00:00 kworker/9:2-events
503 ? 00:00:00 kworker/9:3-events
506 ? 00:00:00 systemd-udevd
508 ? 00:00:00 kworker/u65:4-writeback
574 ? 00:00:00 psimon
626 ? 00:00:01 kworker/u65:9-events_power_efficient
635 ? 00:00:19 kworker/u65:17-flush-259:0
636 ? 00:00:06 kworker/u65:18-events_unbound
661 ? 00:00:00 kworker/5:2-events
702 ? 00:00:00 kworker/3:2-events
771 ? 00:00:00 kworker/10:2-events
780 ? 00:00:00 ccp-1-q2
781 ? 00:00:00 ccp-1-q3
782 ? 00:00:00 ccp-1-q4
783 ? 00:00:00 hwrng
893 ? 00:00:00 kworker/R-crypt
929 ? 00:00:00 kworker/u67:1-hci0
1027 ? 00:00:00 kworker/R-nvkm-
1028 ? 00:00:00 kworker/R-ttm
1029 ? 00:00:00 card0-crtc0
1030 ? 00:00:00 card0-crtc1
1031 ? 00:00:00 card0-crtc2
1032 ? 00:00:00 card0-crtc3
1320 ? 00:00:00 systemd-oomd
1377 ? 00:00:00 systemd-resolve
1379 ? 00:00:00 systemd-timesyn
1508 ? 00:00:00 accounts-daemon
1509 ? 00:00:01 acpid
1510 ? 00:00:00 anacron
1512 ? 00:00:00 avahi-daemon
1514 ? 00:00:00 bluetoothd
1515 ? 00:00:00 cron
1516 ? 00:00:00 dbus-daemon
1523 ? 00:00:00 networkd-dispat
1528 ? 00:00:01 polkitd
1532 ? 00:00:00 power-profiles-
1545 ? 00:00:02 snapd
1550 ? 00:00:00 switcheroo-cont
1558 ? 00:00:00 systemd-logind
1563 ? 00:00:00 udisksd
1573 ? 00:00:00 avahi-daemon
1581 ? 00:00:00 NetworkManager
1588 ? 00:00:00 wpa_supplicant
1629 ? 00:00:00 ModemManager
1642 ? 00:00:00 rsyslogd
1773 ? 00:00:00 unattended-upgr
1788 ? 00:00:00 containerd
1793 ? 00:00:00 anydesk
1869 ? 00:00:00 colord
1874 ? 00:00:00 cupsd
1919 ? 00:00:04 mysqld
1966 ? 00:00:00 apache2
1971 ? 00:00:00 apache2
1972 ? 00:00:00 apache2
1973 ? 00:00:00 apache2
1974 ? 00:00:00 apache2
1975 ? 00:00:00 apache2
2148 ? 00:00:00 cups-browsed
2166 ? 00:00:00 dockerd
2176 ? 00:00:00 nmbd
2198 ? 00:00:00 kerneloops
2203 ? 00:00:00 kerneloops
2209 ? 00:00:01 teamviewerd
2247 ? 00:00:00 smbd
2265 ? 00:00:00 smbd-notifyd
2266 ? 00:00:00 cleanupd
2267 ? 00:00:00 samba-bgqd
2533 ? 00:00:00 gdm3
2575 ? 00:00:00 rtkit-daemon
2677 ? 00:00:00 upowerd
2680 ? 00:00:07 packagekitd
2821 ? 00:00:00 kworker/u68:1-ttm
2893 ? 00:00:00 gdm-session-wor
2902 ? 00:00:00 kworker/3:3-inet_frag_wq
2909 ? 00:00:00 systemd
2914 ? 00:00:00 (sd-pam)
2926 ? 00:00:00 pipewire
2927 ? 00:00:00 pipewire-media-
2928 ? 00:00:00 pulseaudio
2937 ? 00:00:00 gnome-keyring-d
2950 ? 00:00:00 dbus-daemon
2952 ? 00:00:00 xdg-document-po
2958 ? 00:00:00 xdg-permission-
2964 ? 00:00:00 fusermount3
3004 tty2 00:00:00 gdm-wayland-ses
3007 tty2 00:00:00 gnome-session-b
3054 ? 00:00:00 gnome-session-c
3068 ? 00:00:00 gvfsd
3076 ? 00:00:00 gvfsd-fuse
3079 ? 00:00:00 gnome-session-b
3107 ? 00:00:00 at-spi-bus-laun
3111 ? 00:00:34 gnome-shell
3119 ? 00:00:00 dbus-daemon
3157 ? 00:00:00 gnome-shell-cal
3163 ? 00:00:00 evolution-sourc
3170 ? 00:00:00 goa-daemon
3171 ? 00:00:00 dconf-service
3176 ? 00:00:00 evolution-calen
3177 ? 00:00:00 gvfs-udisks2-vo
3188 ? 00:00:00 goa-identity-se
3201 ? 00:00:00 gvfs-gphoto2-vo
3205 ? 00:00:00 gvfs-goa-volume
3209 ? 00:00:00 gvfs-afc-volume
3214 ? 00:00:00 gvfs-mtp-volume
3220 ? 00:00:00 gvfsd-trash
3231 ? 00:00:00 gjs
3232 ? 00:00:00 at-spi2-registr
3251 ? 00:00:00 sh
3252 ? 00:00:00 gsd-a11y-settin
3255 ? 00:00:00 gsd-color
3256 ? 00:00:00 gsd-datetime
3258 ? 00:00:00 gsd-housekeepin
3260 ? 00:00:00 ibus-daemon
3262 ? 00:00:00 gsd-keyboard
3263 ? 00:00:00 gsd-media-keys
3266 ? 00:00:00 gsd-power
3268 ? 00:00:00 gsd-print-notif
3269 ? 00:00:00 gsd-rfkill
3270 ? 00:00:00 gsd-screensaver
3272 ? 00:00:00 gsd-sharing
3277 ? 00:00:00 gsd-smartcard
3278 ? 00:00:00 gsd-sound
3282 ? 00:00:00 gsd-wacom
3283 ? 00:00:00 blueman-applet
3304 ? 00:00:00 evolution-alarm
3343 ? 00:00:00 ibus-memconf
3344 ? 00:00:00 ibus-extension-
3351 ? 00:00:00 gsd-disk-utilit
3356 ? 00:00:00 ibus-portal
3397 ? 00:00:05 snap-store
3429 ? 00:00:00 kworker/15:4-events
3430 ? 00:00:00 ibus-engine-sim
3443 ? 00:00:00 gsd-printer
3453 ? 00:00:00 kworker/u68:3-ttm
3462 ? 00:00:00 kworker/u68:12-ttm
3463 ? 00:00:00 kworker/u68:13-ttm
3464 ? 00:00:00 kworker/u68:14-ttm
3465 ? 00:00:00 kworker/u68:15-ttm
3471 ? 00:00:00 tracker-miner-f
3479 ? 00:00:00 xdg-desktop-por
3485 ? 00:00:00 xdg-desktop-por
3494 ? 00:00:00 gjs
3599 ? 00:00:00 snapd-desktop-i
3658 ? 00:00:00 obexd
3660 ? 00:00:00 blueman-tray
3665 ? 00:00:00 xdg-desktop-por
3668 ? 00:00:00 krfcommd
3673 ? 00:00:00 snapd-desktop-i
3711 ? 00:00:00 gjs
3811 ? 00:00:01 fwupd
3812 ? 00:00:00 gvfsd-metadata
4077 ? 00:00:10 insync
4424 ? 00:00:00 QtWebEngineProc
4425 ? 00:00:00 QtWebEngineProc
4438 ? 00:00:00 QtWebEngineProc
4448 ? 00:00:01 QtWebEngineProc
4523 ? 00:00:00 kworker/13:3-rcu_par_gp
5292 ? 00:00:06 Xwayland
5298 ? 00:00:00 gsd-xsettings
5344 ? 00:00:00 ibus-x11
5502 ? 00:00:00 kworker/u69:3-ttm
6035 ? 00:00:00 kworker/6:3-events
6049 ? 00:00:00 kworker/u69:6-ttm
6170 ? 00:00:00 update-notifier
6361 ? 00:00:00 kworker/11:0
6365 ? 00:00:00 kworker/10:0-cgroup_destroy
6497 ? 00:00:00 kworker/8:0
6500 ? 00:00:00 kworker/u69:2-ttm
6504 ? 00:00:00 kworker/u69:7-ttm
6505 ? 00:00:00 kworker/u69:8-ttm
6506 ? 00:00:00 kworker/u69:9-ttm
6507 ? 00:00:00 kworker/u69:10-ttm
6508 ? 00:00:00 kworker/u69:11-ttm
6511 ? 00:00:07 kworker/u66:0-events_unbound
6512 ? 00:00:00 kworker/u68:4-ttm
6514 ? 00:00:00 kworker/u68:6-ttm
6516 ? 00:00:00 kworker/u68:8-ttm
6517 ? 00:00:00 kworker/u68:9-ttm
6518 ? 00:00:00 kworker/u68:10-ttm
6519 ? 00:00:00 kworker/u68:11-ttm
6617 ? 00:00:01 gnome-terminal-
6635 pts/0 00:00:00 bash
6765 ? 00:00:00 kworker/u65:0
6767 ? 00:00:00 kworker/u66:1
6775 ? 00:00:00 kworker/2:1-rcu_par_gp
6776 pts/0 00:00:00 ps
我的笔记本电脑主机是 Windows 11 Home。VirtualBox 客户虚拟机是 Ubuntu 22.04。
- Ubuntu IP：
192.168.56.102 - Windows IP：
192.168.56.11
主机和客户机都位于同一个WORKGROUP中。
我可以直接从主机操作系统和客户操作系统的文件管理器访问共享：
- 从 Windows 11 开始：
\\192.168.56.102\share - 从 Ubuntu：
smb://192.168.56.11/share
一切似乎都按设计运行。这是困扰 Windows 和 Samba 网络的一个迫切问题。
为什么我在文件管理器的网络文件夹中看不到计算机名称？由于 SMB1 已弃用，我应该看到它们吗？
当我运行时，smbclient我得到以下内容。
查询Ubuntu访客地址：
# smbclient -L \\192.168.56.102 -U root
Password for [WORKGROUP\root]:
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
share Disk Samba on Ubuntu 22.04
IPC$ IPC IPC Service
HP Printer HP Deskjet 4100
SMB1 disabled -- no workgroup available
查询Windows主机地址：
# smbclient -L \\192.168.56.11 -U root
Password for [WORKGROUP\root]:
session setup failed: NT_STATUS_LOGON_FAILURE
我不知道这是否是维护人员的决定，但像文本编辑器这样的默认应用程序应该移至新版本的操作系统，有人告诉我为什么在 Noble Numbat 中看不到文本编辑器应用程序？
我需要在 EC2 ubuntu 22.04 上为 Spark 项目使用较旧的 python 2.7 和 numpy。这些就是我所做的...
sudo apt update
sudo apt install python2.7
sudo apt-get install python-numpy
最后一步出现错误“E：无法找到包 python-numpy”。
有什么建议可以解决该问题吗？
我正在努力访问连接到 USB 并以串行端口形式呈现的 MCU：。/dev/ttyACM0在 Ubuntu 22.04 中运行良好的功能在 24.04 中不起作用。每当我连接设备时，让它访问的唯一方法就是访问
chmod 666它，但这只是暂时的。
我正在处理的用户已添加到dialout组中，并ls -l /dev/ttyACM0返回：crw-rw---- 1 root dialout 166, 0 Oct 25 15:33 /dev/ttyACM0，因此我可以理解，拥有 r/w 权限和任何拨出组成员的是 root。我是否遗漏了任何需要配置/添加的内容？
编辑：驱动程序似乎是正确的，因此不存在触发无效 UDEV 规则的情况：
[21856.363341] usb 3-6: new full-speed USB device number 6 using xhci_hcd
[21856.761217] usb 3-6: New USB device found, idVendor=2e8a, idProduct=0005, bcdDevice= 1.00
[21856.761236] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21856.761240] usb 3-6: Product: Board in FS mode
[21856.761244] usb 3-6: Manufacturer: MicroPython
[21856.761247] usb 3-6: SerialNumber: e6614c311b7f8c38
[21857.365083] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
[21857.365219] usbcore: registered new interface driver cdc_acm
[21857.365225] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
问候，
皮奥特
经过一次看似无害的更新后，我的Ubuntu 22.04.5 LTS系统不再在以太网或 wifi 接口上自动配置 ipv4 网络。Ipv6 工作正常，手动配置 ipv4 也正常。
以下是有问题的更新的历史记录：
libpskc0:amd64 (2.6.7-3build1, 2.6.7-3ubuntu0.1),
cups-filters:amd64 (1.28.15-0ubuntu1.3, 1.28.15-0ubuntu1.4),
ovmf:amd64 (2022.02-3ubuntu0.22.04.2, 2022.02-3ubuntu0.22.04.3),
google-chrome-stable:amd64 (129.0.6668.70-1, 129.0.6668.100-1),
ubuntu-advantage-desktop-daemon:amd64 (1.10~22.04.1, 1.10.ubuntu0.22.04.2),
libfontembed1:amd64 (1.28.15-0ubuntu1.3, 1.28.15-0ubuntu1.4),
cups-filters-core-drivers:amd64 (1.28.15-0ubuntu1.3, 1.28.15-0ubuntu1.4),
nodejs:amd64 (20.17.0-1nodesource1, 20.18.0-1nodesource1),
cups-browsed:amd64 (1.28.15-0ubuntu1.3, 1.28.15-0ubuntu1.4),
brave-browser:amd64 (1.70.119, 1.70.126),
code:amd64 (1.93.1-1726079302, 1.94.2-1728494015),
kubectl:amd64 (1:494.0.0-0, 1:496.0.0-0),
libcupsfilters1:amd64 (1.28.15-0ubuntu1.3, 1.28.15-0ubuntu1.4),
ruby-webrick:amd64 (1.7.0-3, 1.7.0-3ubuntu0.1)
我尝试回滚libpskc0，但nodejs无济于事。以前的版本ovmf在存储库中不可用。
这是一个有效的手动配置（/etc/NetworkManager/system-connections/Wired\ connection\ 1.nmconnection）：
[connection]
id=Wired connection 1
uuid=a9d94420-f026-3f3f-bfdd-8142ae130e71
type=ethernet
autoconnect-priority=-100
[ethernet]
[ipv4]
address1=192.168.0.123/24,192.168.0.1
dns=8.8.8.8;
method=manual
[ipv6]
addr-gen-mode=stable-privacy
method=auto
[proxy]
还有一个不会自动运行的：
[connection]
id=Wired connection 1
uuid=a9d94420-f026-3f3f-bfdd-8142ae130e71
type=ethernet
autoconnect-priority=-100
[ethernet]
[ipv4]
method=auto
[ipv6]
addr-gen-mode=stable-privacy
method=auto
[proxy]
ifconfig以下是自动配置不起作用的结果：
enx089204536db9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 2601:207:680:29e2:d864:1ed3:f424:6a31 prefixlen 64 scopeid 0x0<global>
inet6 fe80::b92c:2b5:5510:e58b prefixlen 64 scopeid 0x20<link>
inet6 2601:207:680:29e2:fb45:144e:3353:9272 prefixlen 64 scopeid 0x0<global>
ether 08:92:04:53:6d:b9 txqueuelen 1000 (Ethernet)
RX packets 40433 bytes 39759055 (39.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18507 bytes 7483707 (7.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 16119 bytes 1722379 (1.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 16119 bytes 1722379 (1.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:78:d9:8c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp0s20f3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 4c:03:4f:c3:f5:5f txqueuelen 1000 (Ethernet)
RX packets 23 bytes 6925 (6.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 33 bytes 6203 (6.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
有没有想过是什么原因导致了这种情况？如何解决？我不介意手动配置有线连接，但这是一台笔记本电脑，每次连接新的 wifi 时都这样做会非常麻烦。
感谢您的帮助。