主页 / user-548230

xenoid's questions

Martin Hope
xenoid
Asked: 2023-05-14 17:29:24 +0800 CST
  • 5

我的意思是：

在此处输入图像描述

这不是滚动条（在窗口的另一边）。它似乎显示了最后一个命令运行的输出，但如果我向后滚动，它似乎显示“随机”行。对其行为的最好解释是它将短时间内产生的输出分组在一起，但这只适用于最后一个命令。

这在我升级到 Kubuntu 22.04 时出现（所以现在运行 Konsole 21.12.3）。

有什么提示吗？

kde5
Martin Hope
xenoid
Asked: 2020-05-04 09:31:00 +0800 CST
  • 2

我在 Ubuntu 19.10 上使用 repos 中的降价。这似乎是一个相当旧的版本：

>markdown -v

This is Markdown, version 1.0.1.
Copyright 2004 John Gruber
http://daringfireball.net/projects/markdown/

它不支持有用的功能，例如“隔离”代码块（行被连接起来，就好像只保留了最后一个开始反引号和第一个结束反引号）。

当我在网上寻找markdown 手册页时，显然有一个更新的（2008 年）和更完整的版本（比我的本地手册页中的选项多得多）。我在哪里可以找到它？它的来源在某处可用吗？在 Web 上搜索 markdown 几乎是不可能的，因为您获得了成千上万的 markdown 语法备忘单。

markdown
Martin Hope
xenoid
Asked: 2020-03-02 16:26:49 +0800 CST
  • 0

新安装的 Kubuntu 19.10

我安装了 Kalarm，它拖入了 39 个其他包，其中大多数包的名称中带有“akonadi”或“pim”。

然后我尝试启动 Kalarm，并得到一个面板说“Akonadi 个人信息管理服务未运行。没有它，此应用程序无法使用。”。正下方是一个大的“开始”按钮，但单击它什么也不做。

如果我从kalarm终端开始，我会看到：

org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
org.kde.pim.kalarm: Preferences::setNoAutoStart: Error writing autostart file: "/home/me/.config/autostart/kalarm.autostart.desktop"
org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch

单击开始按钮会添加另一个：

org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch

创建/home/me/.config/autostart/kalarm.autostart.desktop删除第二行但不能解决问题。

有任何想法吗？

版本：

plasmashell 5.16.5
Qt: 5.12.4
KDE Frameworks: 5.62.0
kf5-config: 1.0

编辑：所以安装了 mariadb 和 akonadi 服务器（5.11.3）。重新启动。现在开始kalarm说：

 org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
Failed to register /MainApplication on DBus
""

akonadiselftest报告两个错误：

  • 未找到 MySQL 服务器默认配置
  • 未找到资源代理

当前安装状态：

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                              Version            Architecture Description
+++-=================================-==================-============-==========================================
ii  akonadi-backend-mysql             4:19.04.3-0ubuntu3 all          MySQL storage backend for Akonadi
un  akonadi-backend-postgresql        <none>             <none>       (no description available)
un  akonadi-backend-sqlite            <none>             <none>       (no description available)
ii  akonadi-server                    4:19.04.3-0ubuntu3 amd64        Akonadi PIM storage service
un  akonadiconsole                    <none>             <none>       (no description available)
un  libakonadi-kf5                    <none>             <none>       (no description available)
ii  libkf5akonadicontact-data         4:19.04.3-0ubuntu1 all          akonadi-contacts - data files
un  libkf5akonadicontact5             <none>             <none>       (no description available)
ii  libkf5akonadicontact5abi1:amd64   4:19.04.3-0ubuntu1 amd64        Akonadi contacts access library
ii  libkf5akonadicore-bin             4:19.04.3-0ubuntu3 amd64        Tools for Akonadi core library
un  libkf5akonadicore5                <none>             <none>       (no description available)
ii  libkf5akonadicore5abi1:amd64      4:19.04.3-0ubuntu3 amd64        Akonadi core library
ii  libkf5akonadimime-data            4:19.04.3-0ubuntu1 all          akonadi-mime - data files
ii  libkf5akonadimime5:amd64          4:19.04.3-0ubuntu1 amd64        Akonadi MIME handling library
ii  libkf5akonadiprivate5abi2:amd64   4:19.04.3-0ubuntu3 amd64        libraries for the Akonadi PIM storage serv
ii  libkf5akonadisearchpim5:amd64     4:19.04.3-0ubuntu1 amd64        Akonadi search library
un  libkf5akonadisocialutils5         <none>             <none>       (no description available)
ii  libkf5akonadiwidgets5abi1:amd64   4:19.04.3-0ubuntu3 amd64        Akonadi widgets library
un  libkf5akonadixml5                 <none>             <none>       (no description available)
ii  libkf5libkdepimakonadi5:amd64     4:19.04.3-0ubuntu1 amd64        KDE PIM Akonadi library
ii  libkf5mailtransportakonadi5:amd64 19.04.3-0ubuntu1   amd64        mail transport service library for akonadi
kde akonadi
Martin Hope
xenoid
Asked: 2020-01-18 13:28:14 +0800 CST
  • 2

在新的联想 P53 上全新安装 Kubuntu 19.10。

起初 Wifi 网络正常工作，我可以使用常用密码连接到我家的 Wifi。

驱动程序管理器建议安装backport-iwlwifi-dkms，我这样做了，但现在密码被拒绝了。我也试过我的手机热点（有一个相当简单的密码），它也被拒绝了。如果我将其重新配置为无密码，我可以连接到手机热点。

可以显示密码并且没问题，我什至复制/粘贴了它。

来自 /var/log/syslog 的连接序列日志（似乎它首先尝试使用存储的密码进行连接，这很可能也是正确的密码）：

Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9624] device (wlp82s0): Activation: starting connection 'HomeNetwork' (9ca67590-8a02-495c-a7cb-da56076aad08)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9627] audit: op="connection-activate" uuid="9ca67590-8a02-495c-a7cb-da56076aad08" name="HomeNetwork" pid=1633 uid=1000 result="success"
Jan 17 21:45:41 P53 kernel: [ 2997.428660] wlp82s0: authenticate with 14:0c:76:bc:ab:68
Jan 17 21:45:41 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9630] device (wlp82s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9643] manager: NetworkManager state is now CONNECTING
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9656] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9664] device (wlp82s0): Activation: (wifi) access point 'HomeNetwork' has security, but secrets are required.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9665] device (wlp82s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9684] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9687] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist.  No new secrets needed.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'scan_ssid' value '1'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9689] Config: added 'psk' value '<hidden>'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9793] device (wlp82s0): supplicant interface state: inactive -> authenticating
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9793] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> authenticating
Jan 17 21:45:41 P53 kernel: [ 2997.433797] wlp82s0: send auth to 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0044] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0044] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:42 P53 kernel: [ 2997.458775] wlp82s0: authenticated
Jan 17 21:45:42 P53 kernel: [ 2997.461167] wlp82s0: associate with 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 kernel: [ 2997.463098] wlp82s0: RX AssocResp from 14:0c:76:bc:ab:68 (capab=0x111 status=0 aid=4)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:42 P53 kernel: [ 2997.468796] wlp82s0: associated
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0195] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0195] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 kernel: [ 2997.523928] wlp82s0: Limiting TX power to 17 (20 - 3) dBm as advertised by 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 kernel: [ 2998.015706] iwlwifi 0000:52:00.0: Unhandled alg: 0x707
Jan 17 21:45:43 P53 kernel: [ 2998.480972] wlp82s0: deauthenticating from 14:0c:76:bc:ab:68 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:bc:ab:68)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:bc:ab:68 reason=1 locally_generated=1
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:43 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:43 P53 NetworkManager[1121]: <warn>  [1579293943.0361] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0412] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0420] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0420] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0424] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.1413] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.1413] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0258] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0262] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist.  No new secrets needed.
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'scan_ssid' value '1'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0266] Config: added 'psk' value '<hidden>'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0372] device (wlp82s0): supplicant interface state: inactive -> scanning
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0372] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> scanning
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.490277] wlp82s0: authenticate with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0417] device (wlp82s0): supplicant interface state: scanning -> authenticating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0417] device (p2p-dev-wlp82s0): supplicant management interface state: scanning -> authenticating
Jan 17 21:45:55 P53 kernel: [ 3010.496321] wlp82s0: send auth to 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.520689] wlp82s0: authenticated
Jan 17 21:45:55 P53 kernel: [ 3010.521092] wlp82s0: associate with 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0662] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0662] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:55 P53 kernel: [ 3010.525437] wlp82s0: RX AssocResp from 14:0c:76:55:47:d1 (capab=0x411 status=0 aid=3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:55 P53 kernel: [ 3010.531546] wlp82s0: associated
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0822] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0822] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:55:47:d1)
Jan 17 21:45:55 P53 kernel: [ 3010.543158] wlp82s0: deauthenticating from 14:0c:76:55:47:d1 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:55:47:d1 reason=1 locally_generated=1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:55 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:55 P53 NetworkManager[1121]: <warn>  [1579293955.1000] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1051] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1056] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1057] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1060] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.2052] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.2052] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn>  [1579293957.0813] device (wlp82s0): no secrets: User canceled the secrets request.
Jan 17 21:45:57 P53 NetworkManager[1121]: <info>  [1579293957.0814] device (wlp82s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Jan 17 21:45:57 P53 NetworkManager[1121]: <info>  [1579293957.0817] manager: NetworkManager state is now DISCONNECTED
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn>  [1579293957.0824] device (wlp82s0): Activation: failed for connection 'HomeNetwork'
Jan 17 21:45:57 P53 NetworkManager[1121]: <info>  [1579293957.0826] device (wlp82s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

这部分lshw似乎是相关的：

        *-pci:3
             description: PCI bridge
             product: Cannon Lake PCH PCI Express Root Port #6
             vendor: Intel Corporation
             physical id: 1c.5
             bus info: pci@0000:00:1c.5
             version: f0
             width: 32 bits
             clock: 33MHz
             capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:125 memory:ce200000-ce2fffff
           *-network
                description: Ethernet interface
                product: Intel Corporation
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:52:00.0
                logical name: wlp82s0
                version: 1a
                serial: 94:e6:f7:f4:70:cc
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
                configuration: broadcast=yes driver=iwlwifi driverversion=5.3.0-26-generic firmware=48.4fa0041f.0 latency=0 link=no multicast=yes
                resources: irq:17 memory:ce200000-ce203fff

有任何想法吗？

否则我如何重新安装以前的？

$$>dkms status
backport-iwlwifi, 7906, 5.3.0-26-generic, x86_64: installed
nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
networking lenovo iwlwifi 19.10
Martin Hope
xenoid
Asked: 2018-05-16 07:55:10 +0800 CST
  • 3

如何将语言词典添加到 KDE 应用程序？到目前为止，他们只支持英语的一些变体。有迹象表明可以使用 Hunspell，但根据dpkg -l 'hunspell*'，hunspell它本身没有安装，而奇怪的是，hunspell-en-us是）。此外，可用语言包的列表很小，并且不包含主要语言，例如西班牙语或法语。

KDE 手册是一个死胡同（断开的链接......）

使用 Kubuntu 16.04

kde kubuntu spell-checking hunspell
Martin Hope
xenoid
Asked: 2018-03-18 15:43:53 +0800 CST
  • 2

为了解决 Kubuntu 16.04 上 KDE 应用程序的一些问题，我添加了一个反向移植 PPA ( kubuntu-ppa-ubuntu-backports-xenial)，并手动更新了几个应用程序 (apt-get install --only-upgrade`)。

  • 对系统进行了非常广泛的更改（添加/删除了许多软件包）
  • 造成的问题多于解决的问题（我的错？）

此外，现在是我应用大量常规升级的时候了，我没有足够的信心允许从 PPA 进行常规升级。

所以

  1. 如何以最小的损坏移除 PPA？（已经安装的软件会怎样？）
  2. 问题是否有可能来自在添加 PPA 之前没有升级我的系统（过去两个月没有升级）或者因为我使用了错误的升级选项？
kde kubuntu apt
Martin Hope
xenoid
Asked: 2017-07-11 16:23:46 +0800 CST
  • 3

在 KDE4（Kubuntu 14.04）中，每个文件系统都有一个垃圾目录（在 /home 上它位于 ~ 下的某个位置，在其他文件系统上它（从内存中）是 /.trash/{id}/。好处是垃圾文件是很快，因为他们刚刚被移动到那个目录。

在 KDE5 (Kubuntu 16.04) 中，我在 /home 中只有一个垃圾目录，并且删除第二个磁盘上的内容很慢（并且会导致 SSD 磨损）。有没有办法将垃圾配置为在 KDE4 中工作？

kde
Martin Hope
xenoid
Asked: 2016-12-18 14:02:07 +0800 CST
  • 2

我正在使用 UFW 附带的基于 Ubuntu 16.04 的 VPS。UFW 的一个默认规则限制了 SSH 连接的数量（考虑到我在 auth.log 文件中看到的尝试次数，这是一件好事，我不想删除）。

然而，这使得编写使用远程命令来管理服务器的脚本变得困难，因为这些通常会创建许多连接（每个命令一个）。

那么有没有办法解除对少数受信任 IP 的限制？

firewall
Martin Hope
xenoid
Asked: 2016-06-07 07:46:34 +0800 CST
  • 2

我使用 KDE (Kubuntu 14.04)、Oxygen 主题和 Firefox，而 FF46 与 GTK3 有几个错误，最烦人的是将工具提示显示为暗色文本并在稍暗的背景上显示。

因此，我正在寻找对它们的设置进行临时更改，以使文本为白色（但我认为问题在于 FF46 未使用主题颜色）或具有较浅的背景。

据我所知，工具提示背景甚至不是纯色，而是垂直渐变，从顶部的大约 60、53、48 到底部的 42、37、33，我无法将这些与/usr/share/themes/oxygen-gtk/gtk-3.0/ 中的主题（kdeglobals、oxygenrc 或两个 CSS 文件）。

那么，这些颜色是在哪里定义的呢？

kubuntu