Início / user-548230

xenoid's questions

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

Eu quero dizer isso:

insira a descrição da imagem aqui

Esta não é a barra de rolagem (que está do outro lado da janela). Parece mostrar a saída do último comando executado, mas se eu rolar para trás, parece mostrar linhas "aleatórias". A melhor explicação para seu comportamento é que ele agrupa as saídas que foram produzidas com um curto intervalo de tempo, mas isso se aplica apenas ao último comando.

Isso apareceu quando atualizei para o Kubuntu 22.04 (executando o Konsole 21.12.3 agora).

Alguma dica?

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

Estou usando markdown dos repositórios no Ubuntu 19.10. Esta parece ser uma versão bastante antiga:

>markdown -v

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

Ele não suporta recursos úteis, como blocos de código "fechados" (as linhas são concatenadas como se apenas mantivesse o último dos acentos graves de abertura e o primeiro dos acentos graves de fechamento).

Quando procuro uma página de manual de remarcação na web , obviamente há uma versão mais recente (2008) e mais completa (muito mais opções do que na minha página de manual local). Onde posso encontrá-lo? Sua fonte está disponível em algum lugar? Pesquisar por markdown na web é quase impossível, pois você obtém milhares de acessos para cheatsheets de sintaxe de markdown.

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

Kubuntu 19.10 recém-instalado

Eu instalo o Kalarm, que arrasta 39 outros pacotes, a maioria com "akonadi" ou "pim" no nome.

Em seguida, tento iniciar o Kalarm e recebo um painel dizendo que "O serviço de gerenciamento de informações pessoais do Akonadi não está em execução. Este aplicativo não pode ser usado sem ele.". Logo abaixo há um grande botão "Iniciar", mas clicar nele não faz nada.

Se eu iniciar kalarmem um terminal, vejo:

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

Clicar no botão Iniciar adiciona outro:

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

Criar o /home/me/.config/autostart/kalarm.autostart.desktopremove a 2ª linha, mas não resolve o problema.

Alguma ideia?

Versões:

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

Edit: Então instalei o servidor mariadb e akonadi (5.11.3). Reiniciado. Agora começando kalarmdiz:

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

akonadiselftestrelata dois erros:

  • Configuração padrão do MySQL Server não encontrada
  • Nenhum agente de recursos encontrado

Status atual da instalação:

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

Nova instalação do Kubuntu 19.10 em um novo Lenovo P53.

No início, a rede Wifi funciona e consigo me conectar ao meu Wifi doméstico usando a senha usual.

O gerenciador de drivers recomenda instalar o backport-iwlwifi-dkms, o que eu faço, mas agora as senhas são rejeitadas. Também tentei o hotspot do meu telefone (que tem uma senha bastante simples) e também é rejeitado. Posso me conectar ao ponto de acesso do telefone se o reconfigurar para que seja sem senha.

A senha pode ser exibida e está OK, eu até copiei/colei.

O log de uma sequência de conexão de /var/log/syslog (parece que tentou se conectar primeiro usando uma senha armazenada que provavelmente também é a correta):

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')

A parte lshwdisso parece relevante:

        *-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

Alguma ideia?

Caso contrário, como faço para reinstalar o anterior?

$$>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

Como posso adicionar dicionários de idiomas aos aplicativos do KDE? Até agora, eles suportam apenas algumas variantes do inglês. Há indícios de que o Hunspell poderia ser usado, mas segundo dpkg -l 'hunspell*', hunspellele próprio não está instalado, enquanto, curiosamente, hunspell-en-usestá). Além disso, a lista de pacotes de idiomas disponíveis é pequena e não contém os principais idiomas, como espanhol ou francês.

O manual do KDE é um beco sem saída (link quebrado...)

Usando o Kubuntu 16.04

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

Na esperança de corrigir alguns problemas com os aplicativos do KDE no Kubuntu 16.04, adicionei um PPA de backports ( kubuntu-ppa-ubuntu-backports-xenial) e atualizei manualmente alguns aplicativos (apt-get install --only-upgrade`).

  • fez mudanças muito extensas no sistema (muitos pacotes adicionados/removidos)
  • criou mais problemas do que resolveu (culpa minha?)

Além disso, já é hora de aplicar várias atualizações regulares e não estou confiante o suficiente para permitir uma atualização geral do PPA.

Então

  1. como posso remover o PPA com danos mínimos? (O que acontece com o software já instalado?)
  2. Existe alguma chance de que os problemas venham de não atualizar meu sistema antes de adicionar o PPA (sem atualizações nos últimos dois meses) ou porque usei a opção errada para atualizar?
kde kubuntu apt
Martin Hope
xenoid
Asked: 2017-07-11 16:23:46 +0800 CST
  • 3

No KDE4 (Kubuntu 14.04) havia um diretório de lixo por sistema de arquivos (em /home estava em algum lugar em ~, em outros sistemas de arquivos era (da memória) um /.trash/{id}/. O benefício era que a lixeira de arquivos era rápido, pois eles acabaram de ser movidos para esse diretório.

No KDE5 (Kubuntu 16.04), tenho apenas um diretório de lixo em /home, e deletar coisas no segundo disco é lento (e causa desgaste no SSD). Existe uma maneira de configurar o lixo para funcionar como no KDE4?

kde