All perguntas(ubuntu)

Esta é uma pergunta de acompanhamento para minha pergunta anterior . Abaixo está o /etc/unbound/unbound.confarquivo:

# unbound.conf(5) config file for unbound(8).
server:
    directory: "/etc/unbound"
    username: "unbound"
    chroot: ""
    logfile: "/etc/unbound/unbound.log"
    pidfile: "/etc/unbound/unbound.pid"
    verbosity: 1
    # listen on all interfaces and answer queries from the local port 3000.
    interface: 0.0.0.0 
    interface: ::0
    port: 3000
    access-control: 10.0.0.0/8 allow
    #access-control: 2001:DB8::/64 allow

Com unbound.serviceiniciado, tentei digum domínio através do servidor local não vinculado:

root@DNS:/etc/unbound# dig example.com A @192.168.1.50 -p 3000

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> example.com A @192.168.1.50 -p 3000
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 8367
;; flags: qr rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; Query time: 0 msec
;; SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)
;; WHEN: Tue Oct 29 16:18:19 UTC 2024
;; MSG SIZE  rcvd: 12

Não entendo por que WARNING: recursion requested but not availableunbound é configurado para ser um resolvedor recursivo por padrão. Também. SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)mostra que unbound foi usado, no entanto, ele falhou em obter o domínio. O que está errado e como eu conserto esse problema?

Abaixo mostramos a resposta via systemd-resolved.serviceservidor stub:

root@DNS:/etc/unbound# dig example.com

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36356
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;example.com.           IN  A

;; ANSWER SECTION:
example.com.        3304    IN  A   93.184.215.14

;; Query time: 12 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Tue Oct 29 16:43:59 UTC 2024
;; MSG SIZE  rcvd: 56

Atualizar:

Após corrigir a sub-rede, como mencionado pela resposta de @mpboden, o digcomando só funcionou uma vez. Por que esse é o caso?

root@DNS:/etc/unbound/unbound.conf.d# systemctl start unbound.service
root@DNS:/etc/unbound/unbound.conf.d# [1730230920] unbound[5780:0] notice: init module 0: subnetcache
[1730230920] unbound[5780:0] notice: init module 1: validator
[1730230920] unbound[5780:0] notice: init module 2: iterator
[1730230921] unbound[5780:0] info: start of service (unbound 1.19.2).

root@DNS:/etc/unbound/unbound.conf.d# dig example.com A @192.168.1.50 -p 3000

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> example.com A @192.168.1.50 -p 3000
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40273
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;example.com.           IN  A

;; ANSWER SECTION:
example.com.        3600    IN  A   93.184.215.14

;; Query time: 712 msec
;; SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)
;; WHEN: Tue Oct 29 19:42:34 UTC 2024
;; MSG SIZE  rcvd: 56

root@DNS:/etc/unbound/unbound.conf.d# dig google.com A @192.168.1.50 -p 3000

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> google.com A @192.168.1.50 -p 3000
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 49774
;; flags: qr rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; Query time: 0 msec
;; SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)
;; WHEN: Tue Oct 29 19:42:56 UTC 2024
;; MSG SIZE  rcvd: 12


root@DNS:/etc/unbound/unbound.conf.d# dig example.com A @192.168.1.50 -p 3000

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> example.com A @192.168.1.50 -p 3000
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 46236
;; flags: qr rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; Query time: 0 msec
;; SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)
;; WHEN: Tue Oct 29 19:43:36 UTC 2024
;; MSG SIZE  rcvd: 12

Este test.shscript:

cd test-1
source .venv/bin/activate
python test.py
deactivate

funciona bem no terminal no Ubuntu 20.04.6 com este comando:

nick@jetson:~$ ./test.sh

Quando eu o adiciono às Preferências de Aplicativos de Inicialização com:

não funciona. O que está errado?

Esta pergunta é diferente de Como inicio aplicativos automaticamente no login?. Não estou perguntando como inicio aplicativos automaticamente no login. Estou perguntando por que um comando diferente tem que ser usado na Commandlinha de comando Add Startup programdo que o comando que eu digito no terminal em ~pasta.

unbound.serviceé executado sem erro quando estes 3 arquivos padrão (criados após a instalação do unbound) são usados:

root@DNS:/etc/unbound# cat unbound.conf
# Unbound configuration file for Debian.
#
# See the unbound.conf(5) man page.
#
# See /usr/share/doc/unbound/examples/unbound.conf for a commented
# reference config file.
#
# The following line includes additional configuration files from the
# /etc/unbound/unbound.conf.d directory.
include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"
root@DNS:/etc/unbound# cat unbound.conf.d/remote-control.conf 
remote-control:
  control-enable: yes
  # by default the control interface is is 127.0.0.1 and ::1 and port 8953
  # it is possible to use a unix socket too
  control-interface: /run/unbound.ctl
root@DNS:/etc/unbound# cat unbound.conf.d/root-auto-trust-anchor-file.conf 
server:
    # The following line will configure unbound to perform cryptographic
    # DNSSEC validation using the root trust anchor.
    auto-trust-anchor-file: "/var/lib/unbound/root.key"

No entanto, quando esses 3 arquivos são removidos e o conteúdo é /etc/unbound/unbound.conffeito para conter

# unbound.conf(5) config file for unbound(8).
server:
    directory: "/etc/unbound"
    username: "unbound"
    # make sure unbound can access entropy from inside the chroot.
    # e.g. on linux the use these commands (on BSD, devfs(8) is used):
    #      mount --bind -n /dev/urandom /etc/unbound/dev/urandom
    # and  mount --bind -n /dev/log /etc/unbound/dev/log
    #chroot: "/etc/unbound"
    # logfile: "/etc/unbound/unbound.log"  #uncomment to use logfile.
    pidfile: "/etc/unbound/unbound.pid"
    # verbosity: 1      # uncomment and increase to get more logging.
    # listen on all interfaces, answer queries from the local subnet.
    interface: 0.0.0.0
    interface: ::0
    access-control: 10.0.0.0/8 allow
    #access-control: 2001:DB8::/64 allow

unbound.servicefalha ao reiniciar usando service unbound restart. por exemplo

root@DNS:/etc/unbound# service unbound restart
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xeu unbound.service" for details.
root@DNS:/etc/unbound# systemctl status unbound.service
× unbound.service - Unbound DNS server
     Loaded: loaded (/usr/lib/systemd/system/unbound.service; disabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2024-10-28 16:01:59 UTC; 18s ago
   Duration: 50min 13.453s
       Docs: man:unbound(8)
    Process: 3385 ExecStartPre=/usr/libexec/unbound-helper chroot_setup (code=exited, status=0/SUCCESS)
    Process: 3388 ExecStartPre=/usr/libexec/unbound-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
    Process: 3391 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE)
    Process: 3393 ExecStopPost=/usr/libexec/unbound-helper chroot_teardown (code=exited, status=0/SUCCESS)
   Main PID: 3391 (code=exited, status=1/FAILURE)
        CPU: 168ms

Oct 28 16:01:59 DNS systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Oct 28 16:01:59 DNS systemd[1]: unbound.service: Start request repeated too quickly.
Oct 28 16:01:59 DNS systemd[1]: unbound.service: Failed with result 'exit-code'.
Oct 28 16:01:59 DNS systemd[1]: Failed to start unbound.service - Unbound DNS server.

Para solucionar o problema, comentei cada linha, seguido de descomentei cada linha até que unbound.servicefalhou ao reiniciar. Descobri que a linha interface: 0.0.0.0é a causa do erro. Não consigo descobrir o que 0.0.0.0está causando o problema. Por que esse endereço IP está causando esse problema?

Sistema:

• Versão não consolidada: 1.19.2
• SO: Linux DNS 6.1.63 #218 SMP Qui Nov 30 20:48:04 CST 2023 aarch64 aarch64 aarch64 GNU/Linux no Ubuntu Server 24.04.1
• unbound -Vsaída:

root@DNS::/etc/unbound# unbound -V
Version 1.19.2

Configure line: --build=aarch64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/aarch64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --with-pythonmodule --with-pyunbound --enable-subnet --enable-dnstap --enable-systemd --enable-cachedb --with-libhiredis --with-libnghttp2 --with-chroot-dir= --with-dnstap-socket-path=/run/dnstap.sock --disable-rpath --with-pidfile=/run/unbound.pid --with-libevent --enable-tfo-client --with-rootkey-file=/usr/share/dns/root.key --disable-flto --enable-tfo-server
Linked libs: libevent 2.1.12-stable (it uses epoll), OpenSSL 3.0.13 30 Jan 2024
Linked modules: dns64 python cachedb subnetcache respip validator iterator
TCP Fastopen feature available


BSD licensed, see LICENSE in source package for details.
Report bugs to [email protected] or https://github.com/NLnetLabs/unbound/issues

Atualizar:

root@DNS:/etc/unbound# unbound -d -vv -c /etc/unbound/unbound.conf
[1730176049] unbound[4263:0] notice: Start of unbound 1.19.2.
[1730176049] unbound[4263:0] error: can't bind socket: Address already in use for 0.0.0.0 port 53
[1730176049] unbound[4263:0] fatal error: could not open ports

Tenho algumas fotos com a .jxlextensão de nome de arquivo. Elas estão no novo formato de imagem conhecido como JPEG-XL.

Eu instalei o novo programa visualizador de imagens do GNOME chamado Loupe ou Image Viewer no Ubuntu 24.10, assim:

sudo apt install loupe

(Loupe é uma alternativa ao antigo programa GNOME conhecido como Eye of GNOME)

Quando abro um arquivo JPEG-XL, recebo este erro:

Não foi possível carregar a imagem

O formato de imagem "JPEG XL image (image/jxl)" é conhecido, mas não está instalado.

Como instalo suporte para JPEG XL no Loupe?

Acabei de atualizar para o Ubuntu 24.4 LTS do que acredito ser o Ubuntu 22 LTS, mas agora meu display de hora do gnome está quebrado. Em vez de exibir a hora, ele exibe um "k". Alguém sabe o que quebrou ou o que eu fiz incorretamente? Obrigado!

captura de tela

Estou executando o Ubuntu 24.10 em um laptop Dell Inspiron 5502. Não tenho certeza se isso é um problema do Ubuntu ou da Dell. Percebi hoje que as alterações de gerenciamento térmico que faço no BIOS não estão sendo salvas. Seleciono o modo silencioso nas opções de gerenciamento de energia, mas quando volto para o BIOS após a inicialização, vejo que elas voltaram para "otimizadas".

Se eu fizer as alterações no BIOS, desligar o computador e ligá-lo novamente e voltar direto para o BIOS, as alterações permanecerão definidas. Elas só mudam após uma inicialização. No entanto, outras alterações (como desligar os c-states permanecem definidas como eu as defini). Não tenho certeza se isso tem algo a ver com o Ubuntu ou se é um problema separado da Dell. Eu não costumava ter esse problema. Parece ter acontecido após a atualização do BIOS, mas pode ter começado após a atualização para 24.10. Eu realmente não me importo. Eu só quero que o ventilador seja o mais silencioso possível porque eu uso o laptop para gravar vocais.

Em algum momento meu servidor MySQL parou de funcionar (eu instalei meu Kubuntu 22.04 doméstico há vários meses)

Eu verifico os comandos:

# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
root@master-at-home:/path# mysql -h 127.0.0.1 -P 3306 -u root
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1:3306' (111)
root@master-at-home:/path# sudo service mysql start
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xeu mysql.service" for details.
root@master-at-home:/path# systemctl status mysql.service
× mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-10-27 09:33:42 EET; 10s ago
Process: 32412 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)
CPU: 2ms

master-at-home systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
master-at-home systemd[1]: Stopped MySQL Community Server.
master-at-home systemd[1]: mysql.service: Start request repeated too quickly.
master-at-home systemd[1]: mysql.service: Failed with result 'exit-code'.
master-at-home systemd[1]: Failed to start MySQL Community Server.
root@master-at-home:/path# journalctl -xeu mysql.service
░░ The job identifier is 3931 and the job result is done.
master-at-home systemd[1]: Starting MySQL Community Server...
░░ Subject: A start job for unit mysql.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mysql.service has begun execution.
░░
░░ The job identifier is 3931.
master-at-home mysql-systemd-start[32412]: MySQL configuration not found at /etc/mysql/my.cnf. Please create one.
master-at-home systemd[1]: mysql.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStartPre= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
master-at-home systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
master-at-home systemd[1]: Failed to start MySQL Community Server.
░░ Subject: A start job for unit mysql.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mysql.service has finished with a failure.
░░
░░ The job identifier is 3931 and the job result is failed.
master-at-home systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit mysql.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
master-at-home systemd[1]: Stopped MySQL Community Server.
░░ Subject: A stop job for unit mysql.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit mysql.service has finished.
░░
░░ The job identifier is 4065 and the job result is done.
master-at-home systemd[1]: mysql.service: Start request repeated too quickly.
master-at-home systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
master-at-home systemd[1]: Failed to start MySQL Community Server.
░░ Subject: A start job for unit mysql.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mysql.service has finished with a failure.
░░
░░ The job identifier is 4065 and the job result is failed.

Eu encontrei a linha:

 master-at-home mysql-systemd-start[32412]: MySQL configuration not found at /etc/mysql/my.cnf. Please create one.

Não tenho nenhum subdiretório /etc/mysql/. Não sei por que e como restaurar /etc/mysql/my.cnf no meu SO?

uname -a
Linux master-at-home 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Decidi atualizar meu sistema operacional, mas recebi os seguintes erros nas mensagens:

path# sudo apt-get update
Hit:1 https://artifacts.elastic.co/packages/8.x/apt stable InRelease
Hit:2 http://ua.archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 https://ppa.launchpadcontent.net/giuspen/ppa/ubuntu jammy InRelease
Hit:6 https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy InRelease
Hit:7 https://ppa.launchpadcontent.net/openswoole/ppa/ubuntu jammy InRelease
Reading package lists... Done
path# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  php-common php-mcrypt php-mongodb php8.2-mongodb php8.3-mcrypt php8.3-mongodb
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up mysql-server-8.0 (8.0.28-0ubuntu4) ...
update-alternatives: error: alternative path /etc/mysql/mysql.cnf doesn't exist
dpkg: error processing package mysql-server-8.0 (--configure):
 installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2
Setting up elasticsearch (8.15.3) ...
/usr/share/elasticsearch/bin/elasticsearch-env: line 78: source: /etc/default/elasticsearch: is a directory
dpkg: error processing package elasticsearch (--configure):
 installed elasticsearch package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-8.0; however:
  Package mysql-server-8.0 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
 mysql-server-8.0
 elasticsearch
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Essas questões estão relacionadas? Como isso pode ser corrigido?

Tenho minha instalação SQL padrão, sem nenhuma opção específica...

ATUALIZADO:

path# sudo apt install --reinstall mysql-server-8.0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 6 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for mysql-server-8.0:amd64
path# sudo apt install --reinstall mysql-server
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 6 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for mysql-server:amd64

ATUALIZADO # 2:

# sudo apt purge mysql-server-8.0 && sudo apt install --reinstall mysql-server-8.0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libcgi-fast-perl libcgi-pm-perl libfcgi-bin libfcgi-perl libfcgi0ldbl libhtml-template-perl mecab-ipadic mecab-ipadic-utf8 mecab-utils
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
mysql-server* mysql-server-8.0*
0 upgraded, 0 newly installed, 2 to remove and 6 not upgraded.
3 not fully installed or removed.
After this operation, 1 713 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 288059 files and directories currently installed.)
Removing mysql-server (8.0.28-0ubuntu4) ...
Removing mysql-server-8.0 (8.0.28-0ubuntu4) ...
Setting up elasticsearch (8.15.3) ...
/usr/share/elasticsearch/bin/elasticsearch-env: line 78: source: /etc/default/elasticsearch: is a directory
dpkg: error processing package elasticsearch (--configure):
installed elasticsearch package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
elasticsearch
E: Sub-process /usr/bin/dpkg returned an error code (1)

Ainda não tenho nenhum subdiretório /etc/mysql/.

ATUALIZADO #3:

Eu saio toot:

whoami
master

Executar comandos:

master@master-at-home:path$ sudo apt purge elasticsearch && sudo apt install mysql-server-8.0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libcgi-fast-perl libcgi-pm-perl libfcgi-bin libfcgi-perl libfcgi0ldbl libhtml-template-perl mecab-ipadic mecab-ipadic-utf8 mecab-utils
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
elasticsearch*
0 upgraded, 0 newly installed, 1 to remove and 6 not upgraded.
1 not fully installed or removed.
After this operation, 1 179 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 288042 files and directories currently installed.)
Removing elasticsearch (8.15.3) ...
Stopping elasticsearch service... OK
(Reading database ... 286653 files and directories currently installed.)
Purging configuration files for elasticsearch (8.15.3) ...
dpkg: warning: elasticsearch: conffile '/etc/default/elasticsearch' is not a plain file or symlink (= '/etc/default/elasticsearch')
Deleting security auto-configuration directory...OK
dpkg: warning: while removing elasticsearch, directory '/var/lib/elasticsearch' not empty so not removed
dpkg: warning: while removing elasticsearch, directory '/usr/lib/systemd/system' not empty so not removed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
tinyca
The following NEW packages will be installed:
mysql-server-8.0
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 0 B/1 386 kB of archives.
After this operation, 1 603 kB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 286641 files and directories currently installed.)
Preparing to unpack .../mysql-server-8.0_8.0.28-0ubuntu4_amd64.deb ...
grep: /etc/mysql/: No such file or directory
Unpacking mysql-server-8.0 (8.0.28-0ubuntu4) ...
Setting up mysql-server-8.0 (8.0.28-0ubuntu4) ...
update-alternatives: error: alternative path /etc/mysql/mysql.cnf doesn't exist
dpkg: error processing package mysql-server-8.0 (--configure):
installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2
Errors were encountered while processing:
mysql-server-8.0
E: Sub-process /usr/bin/dpkg returned an error code (1)

Não encontrei erros durante o processo. Perto do fim, meu fundo ficou preto, mas eu descartei isso... Olhei as outras respostas com a tela Oh No, mas meu caso parece diferente, pois não consigo acessar uma tela de login via ctl alt f3 ou outras variações de teclas.

Mudei do gdm3 para o lightdm e agora consigo ir para a tela inicial de login. Quando entro, infelizmente, ele volta para a tela Oh No. Meu touchpad consegue mover o mouse, mas não clica.

Conectei um mouse externo e agora posso tentar diferentes opções de desktop. Selecionar Wayland me deu uma tela preta, no entanto, o OpenBox realmente funcionou. Então não acho mais que seja um problema de driver da nvidia. Talvez tenha a ver com meu trackpad??

Alguma dica sobre esse ponto?

Eu segui https://ubuntu.com/tutorials/configure-ssh-2fa para configurar a proteção 2FA no SSH no meu sistema Ubuntu 22.04.5. Eu tenho apenas autenticação baseada em chave habilitada, então isso pode ser excessivo, mas parece mais seguro que mesmo se de alguma forma minha chave privada se soltasse, não seria o suficiente por si só.

Não quero ter que inserir um código TOTP ao conectar de um sistema na minha LAN, então o meu /etc/pam.d/sshdtem isto:

auth [success=done default=ignore] pam_access.so accessfile=/etc/security/access-local.conf
auth required pam_google_authenticator.so

/etc/security/access-local.conftem:

+ : ALL : 192.168.1.0/24
+ : ALL : LOCAL
- : ALL : ALL

Tudo isso funciona bem. Sou solicitado a fornecer um código TOTP quando estou fora da minha LAN e não quando estou nela.

Meu problema agora é que o tab-completion scpnão funciona mais. Por exemplo, em outro sistema eu tento:

$ scp server:someth<TAB>

e somethingdeve completar automaticamente, assumindo que o arquivo existe. Isso funciona bem quando não tenho o módulo PAM habilitado, mas não funciona quando está. Mesmo no caso em que estou na minha LAN e não sou solicitado a fornecer o código TOTP, ele falha. Quando pressiono TAB, recebo mensagens como esta no servidor /var/log/auth.log:

Oct 26 17:08:13 server sshd[1136620]: Connection closed by authenticating user user 192.168.1.182 port 53145 [preauth]
Oct 26 17:08:13 server sshd[1136732]: Connection closed by authenticating user user 192.168.1.182 port 53146 [preauth]

As mensagens sempre aparecem em pares como esta para cada pressionamento de TAB.

Alguém tem alguma ideia do que posso fazer para que isso funcione?

Quero instalar o Zen Browser a partir de builds no meu sistema Linux ( Kubuntu 24.04.1 LTS ), mas não tenho certeza sobre a melhor maneira de fazer isso. Eu adoraria alguma ajuda com os passos, especialmente para baixar, extrair e configurar para que eu possa acessá-lo facilmente do meu menu de aplicativos ou desktop com todas as contas de usuário.