为什么这么多已安装的程序没有在菜单中显示?
我正在使用 Ubuntu_Mate 24.04。
我尝试使用 Synaptic 包管理器,但许多程序没有列出。
当发生这种情况时,我必须搜索如何启动该程序。
我愿意手动将程序添加到菜单中。
为什么这么多已安装的程序没有在菜单中显示?
我正在使用 Ubuntu_Mate 24.04。
我尝试使用 Synaptic 包管理器,但许多程序没有列出。
当发生这种情况时,我必须搜索如何启动该程序。
我愿意手动将程序添加到菜单中。
Ubuntu 24.10
Wayland
Nvidia MX330
Nvidia 560.35.03
我被告知,运行 Nvidia 卡的先前问题已在 Ubuntu 24.10 中的 Wayland 下得到修复。
因此我从 24.04 升级到 24.10 并在 Xorg 下运行,解决了一些升级问题,并且它似乎运行良好。
然后我启用了 Wayland。虽然出现了一些小问题,但运行良好。我决定将 Nvidia 置于“性能模式”,一切似乎都很好,直到我检查nvidia-smi
并注意到只有 Nvidiagnome-shell
正在加速。
在这里我通过 CLI 显示选择了 Nvidia 性能模式...
这是nvidia-smi
在 Xorg 下运行的...请注意加速的全部进程...而在 Wayland 下它只显示gnome-shell
...
所以我的问题是...这是 Wayland 还是 Nvidia 的问题?我可以采取哪些步骤来进一步排除故障并修复它?
更新:所以我从 24.04 升级到 24.10 并在 Xorg 下运行,解决了一些升级问题,并且它似乎运行良好。
我发现在“性能模式”下,我无法在 Xorg 中打开桌面上的文件夹。“按需”模式则工作正常。
我是 Ubuntu 的新用户,但我已经使用 Mint 大约 10 年了。我刚刚在新买的 Thinkpad T490 上安装了 Ubuntu Studio 24.10,所以我有一个基于 Kubuntu 的配置。我想做的第一件事就是安装 TLP 来控制电池电量水平,就像我在旧 Thinkpad 上做的那样。
当我开始从 Discover 安装时,我看到了有关软件包删除的消息,这让我很不舒服,所以我没有继续。它想要删除与 ubuntustudio-desktop 相关的 2 个软件包。我担心我会失去一些核心功能。请参阅附图了解确切的消息。软件包是 ubuntustudio-desktop 24.10.18 和 ubuntustudio-desktop-core 24.10.18。它还想删除 power-profiles-daemon,这对我来说并不重要。
安装 TLP-软件包删除消息:
从 apt 启动安装会导致相同的消息。
谁能解释一下那里发生了什么事?
我的系统是双启动的,所以我启动了 Windows 10 并安装了 Lenovo Vantage 应用程序,然后我可以在那里设置电池电量水平。我验证了当我不在 Windows 中时它继续使用这些电量。所以迫切的需求得到了解决,但我仍然对软件包删除感到好奇;它是良性的还是某种错误。
我确实再次启动了 24.10 live USB ISO,安装了 TLP,(那些 ubuntustudio 包显然已从 live 会话中删除),我没有发现 Ubuntu Studio 有任何明显问题。但我无法重新启动该系统;这将是一个新的 live 会话,所以我不知道重新启动后会发生什么。
接下来,我启动了 24.04 实时会话并开始安装 TLP。在 24.04 中,它只想删除 power-profiles-daemon;没有提到 2 个 ubuntustudio 包。
# /etc/crypttab: mappings for encrypted partitions.
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/<name> paths for encrypted devices.
#
# See crypttab(5) for the supported syntax.
#
# NOTE: You need not list your root (/) partition here, but it must be set up
# beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
# to encrypted swap, which should be set up with mkinitcpio-openswap
# for resume support.
#
# <name> <device> <password> <options>
cryptHome UUID=e2652883-XXXX-4d1b-XXXX-c842019fb8d9 none luks,timeout=30
# /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>
UUID=1442-DF7D /boot/efi vfat defaults 0 2
UUID=3025d2f2-1e29-464a-a7f8-bd1a5a6c9830 / ext4 defaults 0 1
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
/dev/mapper/cryptHome /home ext4 defaults 0 2
journalctl -xb 没有显示任何与 LUKS 相关的错误,也没有显示 /var/log/syslog。当我手动解密并将分区挂载到 /home 时,一切都运行正常。但是,我不确定如何解决自动解密的问题。请帮忙!
我想设置一个少于 8 个字符的密码,实际上是一个 4 位简单的密码。就像我们在 Fedora 中所做的一样 -
sudo passwd lamy
我正在寻找一种替代方案,以便在 ubuntu 24.10 中执行相同操作。
当我运行“apt upgrade”、“apt update”等时,出现以下错误:
Setting up shim-signed (1.40.10+15.8-0ubuntu1)
Mount /var/lib/grub/esp: special device /dev/sda1 does not exist
Dpkg: error processing package shim-signed
我认为这会失败,因为 /etc/fstab 中的 /boot/efi 分区是一个链接到 /dev/sdc1 的 UUID(这是正确的)。
(/dev/sda 是没有分区的原始数据磁盘)
文件 /var/cache/debconf/config.dat 具有以下设置:
Name: grub-efi/install_devices
Template: grub-efi/install_devices
Value: /dev/sda1
Owners: grub-common, grub-efi-amd64, grub-pc
Flags: seen
Variables:
CHOICES:
RAW_CHOICES
Name: grub-efi/install_devices_disks_changed
Template: grub-efi/install_devices_disks_changed
Value: /dev/sda1, /dev/sdc1
Owners: grub-common, grub-efi-amd64,
Flags: seen
Variables:
CHOICES:
RAW_CHOICES
'parted -l 显示 /dev/sdc1 上的 'esp' 标志设置是正确的。
我的问题是:
我是否可以只更改 config.dat 文件以使用 /dev/sdc1?
是否有命令可以执行此操作,而不仅仅是编辑文件?
当有相同的服务器且运行正常时,是什么原因导致这种情况发生?
我对重新安装 grub 等持谨慎态度,因为我不知道这是否会对 /dev/sda 产生任何影响。
任何帮助都感激不尽。
我刚刚开始使用 Linux,并决定使用 Windows 11 笔记本电脑双启动 Kubuntu 24.04。我完全无法通过 Kubuntu 访问 D 盘上的任何数据,而 Windows 运行正常。Kubuntu 似乎也没有任何其他问题。
在 Dolphin 中,我可以很好地处理 Kubuntu 分区,但看不到 D 盘(存储我所有数据的地方)。Windows 系统文件位于 C 盘,我根本不想碰它。我知道我应该将分区安装到 Kubuntu 中,但我找到的说明只是说它将位于文件管理器(Dolphin)的左侧窗格中,而我的情况并非如此。
在 Dolphin 中,左侧窗格的设备标题下有两个基本数据分区,我猜是 C 盘和 D 盘,但它们无法打开。我收到一个要求输入密码的窗口,但我不知道在哪里可以找到它。我尝试输入我的用户密码,但没有成功。
我尝试过的一些方法:
chkdsk
在 Windows 中我有一台运行 Windows 11 的 1TB SSD
当我运行时,lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
它显示两个驱动器的 FSTYPE 为 BitLocker,但没有挂载点。这是问题吗?我有 Windows Home,但没有 Bitlocker,那么为什么会显示这个?
如果我在 Windows 中检查文件类型,D 盘会显示 NTFS。
因此,我的笔记本电脑删除键卡在内部。我尝试使用 禁用它xmod -e 'keycode 119 = 0x0000'
。但我仍然在 xev 中检测到它。有时当文本编辑器打开时,所有内容都会被删除。我已在启动应用程序中添加了上述命令,但无济于事。
我无法通过 SSH 从一台主机连接到我的 Ubuntu 22.04 服务器。我可以从其他主机毫无问题地连接到该服务器。但是,当我尝试从该主机连接时:ssh -p 5435 -i ~/.ssh/id_ed25519 user@my_server.com -vvv
我得到:
OpenSSH_8.9p1 Ubuntu-3ubuntu0.10, OpenSSL 3.0.2 15 Mar 2022
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/user/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/user/.ssh/known_hosts2'
debug2: resolving "my_server.com" port 5435
debug3: resolve_host: lookup my_server.com: 5435
debug3: ssh_connect_direct: entering
debug1: Connecting to my_server.com [xxx.xxx.xxx.xxx] port 5435.
debug3: set_sock_tos: set socket 3 IP_TOS 0x10
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type -1
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/user/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/user/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519 type 3
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519_sk type -1
debug1: identity file /home/user/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/user/.ssh/id_xmss type -1
debug1: identity file /home/user/.ssh/id_xmss-cert type -1
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 Ubuntu-3ubuntu0.10
debug1: compat_banner: match: OpenSSH_8.9p1 Ubuntu-3ubuntu0.10 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to my_server.com:5435 as 'user'
debug3: put_host_port: [my_server.com]:5435
debug3: record_hostkey: found key type ED25519 in file /home/user/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from [my_server.com]:5435
debug1: load_hostkeys: fopen /home/user/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type [email protected], using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,[email protected],diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected]
debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected],zlib
debug2: compression stoc: none,[email protected],zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,[email protected],diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,[email protected]
debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected]
debug2: compression stoc: none,[email protected]
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug3: kex_choose_conf: will use strict KEX ordering
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:ChCUrM9ZYCR057q60M84kB6pAQa9bQ8ZEHVuw8g7/p0
debug3: put_host_port: [xxx.xxx.xxx.xxx]:5435
debug3: put_host_port: [my_server.com]:5435
debug3: record_hostkey: found key type ED25519 in file /home/user/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from [my_server.com]:5435
debug1: load_hostkeys: fopen /home/user/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '[my-server.com]:5435' is known and matches the ED25519 host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug3: send packet: type 21
debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: ssh_packet_read_poll2: resetting read seqnr 3
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/user/.ssh/id_rsa
debug1: Will attempt key: /home/user/.ssh/id_ecdsa
debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk
debug1: Will attempt key: /home/user/.ssh/id_ed25519 ED25519 SHA256:95gTIyyYHXV+UgGYTJiGgC5ulxp3jQoeHmhohQRbIPI
debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk
debug1: Will attempt key: /home/user/.ssh/id_xmss
debug1: Will attempt key: /home/user/.ssh/id_dsa
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,[email protected],ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected]>
debug1: kex_input_ext_info: [email protected]=<0>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred gssapi-with-mic,keyboard-interactive,password
debug1: No more authentication methods to try.
[email protected]: Permission denied (publickey).
客户端似乎没有向服务器提供任何公钥。Offering public key:...
之后应该有Authentications that can continue: publickey
该~/.ssh
文件夹似乎具有正确的权限:
user@client:~$ ll .ssh
total 24
drwx------ 2 user user 4096 Oct 13 18:54 ./
drwxr-xr-x 8 user user 4096 Oct 12 12:13 ../
-rw------- 1 user user 96 Sep 14 16:50 authorized_keys
-rw------- 1 user user 411 Oct 12 11:42 id_ed25519
-rw-r--r-- 1 user user 96 Oct 12 11:42 id_ed25519.pub
-rw-r--r-- 1 user user 142 Oct 12 11:45 known_hosts
另外,我在密钥中启用了 ed25519:
$ ssh -Q key
ssh-ed25519
[email protected]
...
我的公钥在服务器的authorised_keys
文件中,我仔细检查了本地文件id_ed25519.pub
。它们是相同的。在服务器的日志中,我有:
$ tail -f /var/log/auth.log
Oct 13 19:19:53 my_server sshd[3131]: Connection closed by authenticating user user xxx.xxx.xxx.xxx port 39810 [preauth]
可能是什么问题?我重新安装了 ssh,但没用。我还生成并上传了一个新密钥 - 同样的错误。同样,我可以从至少 2 个其他主机使用同一用户连接到该服务器。