Início / user-541417

Sun Bear's questions

Martin Hope
Sun Bear
Asked: 2024-10-30 21:29:40 +0800 CST
  • 8

Configurei o Unbound para:

  1. ouvir consultas de domínio em todas as interfaces em uma LAN,
  2. encaminhar essas consultas de domínio para um resolvedor DNS externo via TLS,
  3. receber os IPs de domínio resolvidos do resolvedor DNS externo e devolvê-los aos clientes correspondentes.

Como verifico se tal configuração está funcionando? Especialmente, como verifico que:

  1. O Unbound encaminhou as consultas de domínio para o resolvedor DNS externo desejado via TLS?
  2. Os IPS de domínio resolvidos são do resolvedor DNS externo e não são resolvidos pelo Unbound?

Abaixo estão dois resultados de digging google.com. Como posso usar esses resultados para fazer as verificações mencionadas acima?

root@DNS:/etc/unbound# 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: NOERROR, id: 22452
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
google.com.     300 IN  A   142.251.175.138
google.com.     300 IN  A   142.251.175.100
google.com.     300 IN  A   142.251.175.113
google.com.     300 IN  A   142.251.175.101
google.com.     300 IN  A   142.251.175.139
google.com.     300 IN  A   142.251.175.102

;; Query time: 12 msec
;; SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)
;; WHEN: Wed Oct 30 14:04:16 UTC 2024
;; MSG SIZE  rcvd: 135

root@DNS:/etc/unbound# 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: NOERROR, id: 39764
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
google.com.     300 IN  A   142.251.175.139
google.com.     300 IN  A   142.251.175.113
google.com.     300 IN  A   142.251.175.100
google.com.     300 IN  A   142.251.175.101
google.com.     300 IN  A   142.251.175.138
google.com.     300 IN  A   142.251.175.102

;; Query time: 184 msec
;; SERVER: 192.168.1.50#3000(192.168.1.50) (UDP)
;; WHEN: Wed Oct 30 14:05:30 UTC 2024
;; MSG SIZE  rcvd: 135

Abaixo estão os logs unbound.logcom verbosity: 3depois de reiniciar o unbound.servicee executar o comando dig acima duas vezes. Posso ver que o resolvedor DNS externo é mencionado, mas não consigo entender qual linha mostra que ele resolveu o domínio e retorna os resultados para unbound.

[1730296502] unbound[6506:0] info: service stopped (unbound 1.19.2).
[1730296502] unbound[6506:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
[1730296502] unbound[6506:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
[1730296502] unbound[6506:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
[1730296502] unbound[6506:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
[1730296502] unbound[6506:0] info: server stats for thread 2: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
[1730296502] unbound[6506:0] info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0
[1730296502] unbound[6506:0] info: server stats for thread 3: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
[1730296502] unbound[6506:0] info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0
[1730296503] unbound[6658:0] debug: module config: "subnetcache validator iterator"
[1730296503] unbound[6658:0] notice: init module 0: subnetcache
[1730296503] unbound[6658:0] warning: subnetcache: serve-expired is set but not working for data originating from the subnet module cache.
[1730296503] unbound[6658:0] warning: subnetcache: prefetch is set but not working for data originating from the subnet module cache.
[1730296503] unbound[6658:0] debug: subnetcache: option registered (8)
[1730296503] unbound[6658:0] notice: init module 1: validator
[1730296503] unbound[6658:0] notice: init module 2: iterator
[1730296503] unbound[6658:0] debug: target fetch policy for level 0 is 3
[1730296503] unbound[6658:0] debug: target fetch policy for level 1 is 2
[1730296503] unbound[6658:0] debug: target fetch policy for level 2 is 1
[1730296503] unbound[6658:0] debug: target fetch policy for level 3 is 0
[1730296503] unbound[6658:0] debug: target fetch policy for level 4 is 0
[1730296503] unbound[6658:0] debug: Forward zone server list:
[1730296503] unbound[6658:0] info: DelegationPoint<dns.quad9.net.>: 0 names (0 missing), 4 addrs (0 result, 4 avail) parentNS
[1730296503] unbound[6658:2] debug: Forward zone server list:
[1730296503] unbound[6658:2] info: DelegationPoint<dns.quad9.net.>: 0 names (0 missing), 4 addrs (0 result, 4 avail) parentNS
[1730296503] unbound[6658:0] debug: cache memory msg=66104 rrset=66104 infra=7952 val=66400 subnet=74536
[1730296503] unbound[6658:1] debug: Forward zone server list:
[1730296503] unbound[6658:1] info: DelegationPoint<dns.quad9.net.>: 0 names (0 missing), 4 addrs (0 result, 4 avail) parentNS
[1730296503] unbound[6658:0] info: start of service (unbound 1.19.2).
[1730296503] unbound[6658:2] debug: cache memory msg=66104 rrset=66104 infra=7952 val=66400 subnet=74536
[1730296503] unbound[6658:3] debug: Forward zone server list:
[1730296503] unbound[6658:3] info: DelegationPoint<dns.quad9.net.>: 0 names (0 missing), 4 addrs (0 result, 4 avail) parentNS
[1730296503] unbound[6658:1] debug: cache memory msg=66104 rrset=66104 infra=7952 val=66400 subnet=74536
[1730296503] unbound[6658:3] debug: cache memory msg=66104 rrset=66104 infra=7952 val=66400 subnet=74536
[1730297056] unbound[5388:0] debug: subnetcache[module 0] operate: extstate:module_state_initial event:module_event_new
[1730297056] unbound[5388:0] info: subnetcache operate: query google.com. A IN
[1730297056] unbound[5388:0] debug: validator[module 1] operate: extstate:module_state_initial event:module_event_pass
[1730297056] unbound[5388:0] info: validator operate: query google.com. A IN
[1730297056] unbound[5388:0] debug: iterator[module 2] operate: extstate:module_state_initial event:module_event_pass
[1730297056] unbound[5388:0] info: resolving google.com. A IN
[1730297056] unbound[5388:0] info: resolving (init part 2):  google.com. A IN
[1730297056] unbound[5388:0] info: resolving (init part 3):  google.com. A IN
[1730297056] unbound[5388:0] info: processQueryTargets: google.com. A IN
[1730297056] unbound[5388:0] info: sending query: google.com. A IN
[1730297056] unbound[5388:0] debug: sending to target: <google.com.> 216.239.38.10#53
[1730297056] unbound[5388:0] debug: cache memory msg=70045 rrset=100203 infra=29147 val=67208 subnet=74536
[1730297056] unbound[5388:0] debug: iterator[module 2] operate: extstate:module_wait_reply event:module_event_reply
[1730297056] unbound[5388:0] info: iterator operate: query google.com. A IN
[1730297056] unbound[5388:0] info: response for google.com. A IN
[1730297056] unbound[5388:0] info: reply from <google.com.> 216.239.38.10#53
[1730297056] unbound[5388:0] info: query response was ANSWER
[1730297056] unbound[5388:0] info: finishing processing for google.com. A IN
[1730297056] unbound[5388:0] debug: validator[module 1] operate: extstate:module_wait_module event:module_event_moddone
[1730297056] unbound[5388:0] info: validator operate: query google.com. A IN
[1730297056] unbound[5388:0] debug: subnetcache[module 0] operate: extstate:module_wait_module event:module_event_moddone
[1730297056] unbound[5388:0] info: subnetcache operate: query google.com. A IN
[1730297056] unbound[5388:0] debug: cache memory msg=70045 rrset=100203 infra=29147 val=67208 subnet=74536
[1730297130] unbound[5379:0] debug: subnetcache[module 0] operate: extstate:module_state_initial event:module_event_new
[1730297130] unbound[5379:0] info: subnetcache operate: query google.com. A IN
[1730297130] unbound[5379:0] debug: validator[module 1] operate: extstate:module_state_initial event:module_event_pass
[1730297130] unbound[5379:0] info: validator operate: query google.com. A IN
[1730297130] unbound[5379:0] debug: iterator[module 2] operate: extstate:module_state_initial event:module_event_pass
[1730297130] unbound[5379:0] info: resolving google.com. A IN
[1730297130] unbound[5379:0] info: resolving (init part 2):  google.com. A IN
[1730297130] unbound[5379:0] info: resolving (init part 3):  google.com. A IN
[1730297130] unbound[5379:0] info: processQueryTargets: google.com. A IN
[1730297130] unbound[5379:0] info: sending query: google.com. A IN
[1730297130] unbound[5379:0] debug: sending to target: <com.> 2001:503:83eb::30#53
[1730297130] unbound[5379:0] debug: cache memory msg=78073 rrset=130165 infra=41184 val=69264 subnet=74536
[1730297130] unbound[5379:0] debug: iterator[module 2] operate: extstate:module_wait_reply event:module_event_noreply
[1730297130] unbound[5379:0] info: iterator operate: query google.com. A IN
[1730297130] unbound[5379:0] info: processQueryTargets: google.com. A IN
[1730297130] unbound[5379:0] info: sending query: google.com. A IN
[1730297130] unbound[5379:0] debug: sending to target: <com.> 192.41.162.30#53
[1730297130] unbound[5379:0] debug: cache memory msg=78073 rrset=130165 infra=41184 val=69264 subnet=74536
[1730297130] unbound[5379:0] debug: iterator[module 2] operate: extstate:module_wait_reply event:module_event_reply
[1730297130] unbound[5379:0] info: iterator operate: query google.com. A IN
[1730297130] unbound[5379:0] info: response for google.com. A IN
[1730297130] unbound[5379:0] info: reply from <com.> 192.41.162.30#53
[1730297130] unbound[5379:0] info: query response was REFERRAL
[1730297130] unbound[5379:0] info: processQueryTargets: google.com. A IN
[1730297130] unbound[5379:0] info: sending query: google.com. A IN
[1730297130] unbound[5379:0] debug: sending to target: <google.com.> 216.239.32.10#53
[1730297130] unbound[5379:0] debug: cache memory msg=78073 rrset=132972 infra=41184 val=69414 subnet=74536
[1730297130] unbound[5379:0] debug: iterator[module 2] operate: extstate:module_wait_reply event:module_event_reply
[1730297130] unbound[5379:0] info: iterator operate: query google.com. A IN
[1730297130] unbound[5379:0] info: response for google.com. A IN
[1730297130] unbound[5379:0] info: reply from <google.com.> 216.239.32.10#53
[1730297130] unbound[5379:0] info: query response was ANSWER
[1730297130] unbound[5379:0] info: finishing processing for google.com. A IN
[1730297130] unbound[5379:0] debug: validator[module 1] operate: extstate:module_wait_module event:module_event_moddone
[1730297130] unbound[5379:0] info: validator operate: query google.com. A IN
[1730297130] unbound[5379:0] debug: subnetcache[module 0] operate: extstate:module_wait_module event:module_event_moddone
[1730297130] unbound[5379:0] info: subnetcache operate: query google.com. A IN
[1730297130] unbound[5379:0] debug: cache memory msg=78333 rrset=133364 infra=41492 val=69414 subnet=74536
networking
Martin Hope
Sun Bear
Asked: 2024-10-30 12:13:59 +0800 CST
  • 5

Esta é uma pergunta de acompanhamento para minha 2ª pergunta . A solução de @mpboden foi implementada. Além disso, adicionei auto-trust-anchor-file:e enabled remote-control:, conforme definido no exemplo Unbound para Setting up para o restante do exemplo de rede .

server:
    directory: "/etc/unbound"
    username: "unbound"
    chroot: ""
    verbosity: 1
    logfile: "/etc/unbound/unbound.log"
    pidfile: "/etc/unbound/unbound.pid"
    # location of the trust anchor file that enables DNSSEC
    auto-trust-anchor-file: "/var/lib/unbound/root.key"
    # send minimal amount of information to upstream servers to enhance privacy
    qname-minimisation: yes
    # The port number on which the server responds to queries. 
    port: 3000
    # the interface that is used to connect to the network (this will listen to all interfaces)
    interface: 0.0.0.0
    interface: ::0
    # addresses from the IP range that are allowed to connect to the resolver
    access-control: 192.168.1.0/24 allow
    access-control: 2001:DB8::/64 allow

remote-control:
    # allows controling unbound using "unbound-control"
    control-enable: yes

No entanto, descobri 4 erros e 1 mensagem de falha usando o modo de depuração. Com meus esforços de solução de problemas, descobri que essas mensagens de erro e falha ocorriam sempre que control-enable: yesera permitido.

root@DNS:/etc/unbound# unbound -d -vv -c unbound.conf
[1730259092] unbound[6165:0] notice: Start of unbound 1.19.2.
[1730259092] unbound[6165:0] error: Error for server-cert-file: /etc/unbound/unbound_server.pem
[1730259092] unbound[6165:0] error: Error in SSL_CTX use_certificate_chain_file crypto error:80000002:system library::No such file or directory
[1730259092] unbound[6165:0] error: and additionally crypto error:10080002:BIO routines::system lib
[1730259092] unbound[6165:0] error: and additionally crypto error:0A080002:SSL routines::system lib
[1730259092] unbound[6165:0] fatal error: could not set up remote-control

Verifiquei que /var/lib/unbound/root.keyexiste. O Unbound ainda funciona, mas unbound-controlnão pode ser usado. O Unbound está procurando, /etc/unbound/unbound_server.pemmas este arquivo não existe. Como resolvo este problema de configuração de controle remoto?

Atualizar:

com a resposta do @mpboden , descobri que o comando unbound-control-setupserve para criar esses arquivos em /etc/unbound: unbound_control.pem, unbound_server.pem, unbound_control.key, unbound_server.key, para permitir o controle remoto.

root@DNS:/etc/unbound# unbound-control-setup -h
usage: /usr/sbin/unbound-control-setup OPTIONS
OPTIONS
-d <dir>  used directory to store keys and certificates (default: /etc/unbound)
-h        show help notice
-r        recreate certificates
root@DNS:/etc/unbound# unbound-control-setup
setup in directory /etc/unbound
Certificate request self-signature ok
subject=CN = unbound-control
removing artifacts
Setup success. Certificates created. Enable in unbound.conf file to use
root@DNS:/etc/unbound# ls
unbound.conf    unbound.conf.d       unbound.pid          unbound_control.pem  unbound_server.pem
unbound.log     unbound_control.key  unbound_server.key
networking
Martin Hope
Sun Bear
Asked: 2024-10-30 00:39:49 +0800 CST
  • 8

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
networking
Martin Hope
Sun Bear
Asked: 2024-10-29 10:49:26 +0800 CST
  • 7

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
networking
Martin Hope
Sun Bear
Asked: 2024-09-28 15:04:10 +0800 CST
  • 5

Notei que o Nautilus no Ubuntu 24.04 não mostra o disco de progresso ao copiar uma grande quantidade de arquivos. Essa situação é exclusiva minha ou há um bug ou esse recurso foi removido? O Nautilus no Ubuntu 22.04 mostra esse disco de progresso de cópia.

Responder à resposta do @cordlord :

A imagem abaixo ilustra o que eu quis dizer no meu comentário à sua resposta. O benefício dessa abordagem sobre o uso de várias abas em uma janela é que o conteúdo em ambas as pastas fica visível simultaneamente.

emitir

A próxima imagem mostra a barra de menu quando a janela do nautilus não está em modo compacto. Como você mencionou em sua resposta, as informações de progresso da cópia são mostradas na parte inferior da barra de menu esquerda.

uma janela

nautilus
Martin Hope
Sun Bear
Asked: 2024-09-03 09:58:49 +0800 CST
  • 6

Ao fazer do-release-upgradede 22.04 para 24.04, este sistema encontrou um problema durante a reinicialização (ou seja, após a instalação de 24.04 ter sido concluída). Como me recupero desse problema? O procedimento de atualização é fornecido pelo nixCraft .

emitir

Abaixo está a tela de inicialização do EFI:

efi

upgrade
Martin Hope
Sun Bear
Asked: 2024-08-26 22:15:09 +0800 CST
  • 9

Estou tentando fazer cópias frente e verso usando o Document Scanneraplicativo por meio do alimentador superior de um scanner-impressora Canon E4570.

A imagem abaixo mostra a configuração do aplicativo antes de clicar em Scan. O aplicativo consegue escanear a página superior do papel, mas não a página inferior do papel. Como faço para ativar a digitalização duplex?

Informações do sistema e do aplicativo:

  • sistema: Linux 6.8.0-40-generic #40~22.04.3-Ubuntu
  • firmware canônico: 1.070
  • scanner de documentos: 42.0

Scanner de documentos

Janela de Preferências

pdf
Martin Hope
Sun Bear
Asked: 2024-05-17 21:03:40 +0800 CST
  • 4

Depois de baixar e extrair o libreoffice e acessar ~/Downloads/tmp/LibreOffice_24.2.3.2_Linux_x86-64_deb/DEB, encontrei esse problema. Como faço para superá-los no Ubuntu 22.04? Não consigo instalar nenhum desses arquivos.

$ ls
libobasis24.2-base_24.2.3.2-2_amd64.deb                                  libobasis24.2-images_24.2.3.2-2_amd64.deb                  libobasis24.2-xsltfilter_24.2.3.2-2_amd64.deb
libobasis24.2-calc_24.2.3.2-2_amd64.deb                                  libobasis24.2-impress_24.2.3.2-2_amd64.deb                 libreoffice24.2_24.2.3.2-2_amd64.deb
libobasis24.2-core_24.2.3.2-2_amd64.deb                                  libobasis24.2-kde-integration_24.2.3.2-2_amd64.deb         libreoffice24.2-base_24.2.3.2-2_amd64.deb
libobasis24.2-draw_24.2.3.2-2_amd64.deb                                  libobasis24.2-librelogo_24.2.3.2-2_amd64.deb               libreoffice24.2-calc_24.2.3.2-2_amd64.deb
libobasis24.2-en-us_24.2.3.2-2_amd64.deb                                 libobasis24.2-libreofficekit-data_24.2.3.2-2_amd64.deb     libreoffice24.2-debian-menus_24.2.3-2_all.deb
libobasis24.2-extension-beanshell-script-provider_24.2.3.2-2_amd64.deb   libobasis24.2-math_24.2.3.2-2_amd64.deb                    libreoffice24.2-dict-en_24.2.3.2-2_amd64.deb
libobasis24.2-extension-javascript-script-provider_24.2.3.2-2_amd64.deb  libobasis24.2-ogltrans_24.2.3.2-2_amd64.deb                libreoffice24.2-dict-es_24.2.3.2-2_amd64.deb
libobasis24.2-extension-mediawiki-publisher_24.2.3.2-2_amd64.deb         libobasis24.2-onlineupdate_24.2.3.2-2_amd64.deb            libreoffice24.2-dict-fr_24.2.3.2-2_amd64.deb
libobasis24.2-extension-nlpsolver_24.2.3.2-2_amd64.deb                   libobasis24.2-ooofonts_24.2.3.2-2_amd64.deb                libreoffice24.2-draw_24.2.3.2-2_amd64.deb
libobasis24.2-extension-pdf-import_24.2.3.2-2_amd64.deb                  libobasis24.2-ooolinguistic_24.2.3.2-2_amd64.deb           libreoffice24.2-en-us_24.2.3.2-2_amd64.deb
libobasis24.2-extension-report-builder_24.2.3.2-2_amd64.deb              libobasis24.2-postgresql-sdbc_24.2.3.2-2_amd64.deb         libreoffice24.2-impress_24.2.3.2-2_amd64.deb
libobasis24.2-firebird_24.2.3.2-2_amd64.deb                              libobasis24.2-python-script-provider_24.2.3.2-2_amd64.deb  libreoffice24.2-math_24.2.3.2-2_amd64.deb
libobasis24.2-gnome-integration_24.2.3.2-2_amd64.deb                     libobasis24.2-pyuno_24.2.3.2-2_amd64.deb                   libreoffice24.2-ure_24.2.3.2-2_amd64.deb
libobasis24.2-graphicfilter_24.2.3.2-2_amd64.deb                         libobasis24.2-writer_24.2.3.2-2_amd64.deb                  libreoffice24.2-writer_24.2.3.2-2_amd64.deb

$ sudo dpkg -i libreoffice24.2-base_24.2.3.2-2_amd64.deb 
Selecting previously unselected package libreoffice24.2-base.
(Reading database ... 520086 files and directories currently installed.)
Preparing to unpack libreoffice24.2-base_24.2.3.2-2_amd64.deb ...
Unpacking libreoffice24.2-base (24.2.3.2-2) ...
dpkg: dependency problems prevent configuration of libreoffice24.2-base:
 libreoffice24.2-base depends on libreoffice24.2 (>= 24.2.3.2); however:
  Package libreoffice24.2 is not installed.
 libreoffice24.2-base depends on libreoffice24.2 (<= 24.2.3.2-2); however:
  Package libreoffice24.2 is not installed.
 libreoffice24.2-base depends on libobasis24.2-base (>= 24.2.3.2); however:
  Package libobasis24.2-base is not installed.
 libreoffice24.2-base depends on libobasis24.2-base (<= 24.2.3.2-2); however:
  Package libobasis24.2-base is not installed.

dpkg: error processing package libreoffice24.2-base (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libreoffice24.2-base
22.04
Martin Hope
Sun Bear
Asked: 2024-03-27 12:20:30 +0800 CST
  • 5

Observação

Se você quiser uma requirements.txtsaída do arquivo de bloqueio, execute $ pipenv lock -r. No entanto, isso incluirá todos os hashes (o que é ótimo!). Para obter um requirements.txtsem hashes, use $ pipenv run pip freeze.

De acordo com o aviso pipenv acima , se desejar uma requirements.txtsaída do arquivo de bloqueio, você deve executar $ pipenv lock -r. No entanto, as -ropções não existem:

$ pipenv lock -r
Usage: pipenv lock [OPTIONS]
Try 'pipenv lock -h' for help.
$ pipenv lock -h
Usage: pipenv lock [OPTIONS]

  Generates Pipfile.lock.

Options:
  --categories TEXT
  --dev-only             Emit development dependencies *only* (overrides
                         --dev)
  -d, --dev              Generate both develop and default requirements  [env
                         var: PIPENV_DEV]
  --extra-pip-args TEXT
  --pre                  Allow pre-releases.
  --python TEXT          Specify which version of Python virtualenv should
                         use.
  --clear                Clears caches (pipenv, pip).  [env var: PIPENV_CLEAR]
  -q, --quiet            Quiet mode.
  -v, --verbose          Verbose mode.
  --pypi-mirror TEXT     Specify a PyPI mirror.
  -h, --help             Show this message and exit.

Posso saber o comando para obter a requirements.txtsaída do arquivo de bloqueio pipenv?

pipenv
Martin Hope
Sun Bear
Asked: 2024-01-30 00:53:56 +0800 CST
  • 5

Quero uma nova instalação do Openshot usando seu arquivo Linux mais recente (AppImage de 64 bits) em uma máquina que já havia instalado o Openshot via apt, snap e flatpak. Eu limpei todas as suas instalações antigas. Eu até limpei o flatpak. No entanto, ainda encontrei arquivos Openshot nesta máquina e sua miniatura aparece na grade de aplicativos do Ubuntu 22.04.

$ sudo apt list | grep openshot

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libopenshot-audio-dev/jammy 0.2.0+dfsg1-4 amd64
libopenshot-audio-doc/jammy,jammy 0.2.0+dfsg1-4 all
libopenshot-audio-test-sound/jammy 0.2.0+dfsg1-4 amd64
libopenshot-audio7/jammy 0.2.0+dfsg1-4 amd64
libopenshot-dev/jammy 0.2.5+dfsg1-6build2 amd64
libopenshot-doc/jammy,jammy 0.2.5+dfsg1-6build2 all
libopenshot19/jammy 0.2.5+dfsg1-6build2 amd64
openshot-qt-doc/jammy,jammy 2.5.1+dfsg1-2 all
openshot-qt/jammy,jammy 2.5.1+dfsg1-2 all
python3-openshot/jammy 0.2.5+dfsg1-6build2 amd64

$ sudo apt purge openshot
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'openshot' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  libappstream-glib8 libmalcontent-0-0 libostree-1-1
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

$ sudo apt purge openshot-qt
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'openshot-qt' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  libappstream-glib8 libmalcontent-0-0 libostree-1-1
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

$ dpkg -l | grep openshot

$ flatpak
bash: /usr/bin/flatpak: No such file or directory

Porém, de acordo com o Nautilus, muitos arquivos residuais estão no /var/lib/flatpak/appdiretório.

arquivos openshot residuais

Além disso, a miniatura do Openshot continua existindo na grade de Aplicativos

miniatura openshot na grade de aplicativos

mas pastas ~/.local/share/applicationse /usr/share/applicationsnão contêm nenhum .desktoparquivo openshot.

Questões :

  1. Posso simplesmente deletar a pasta /var/lib/flatpak/app/org.openshot.OpenShote não causar nenhum problema à máquina?
  2. Como eliminei o flatpak, posso excluir a pasta /var/lib/flatpak?
  3. Além disso, como faço para remover a miniatura do Openshot na grade de Aplicativos?

Atualizar:

Descobri a existência de um arquivo chamado org.openshot.OpenShot.desktop. Seus caminhos são:

  • /var/lib/flatpak/app/org.openshot.OpenShot/x86_64/stable/a3e062afc67b6bcba4c61fffa4a9c7d4baab1fb0843f99b8f79e2497e15bc42e/export/share/applications/org.openshot.OpenShot.desktop
  • /var/lib/flatpak/exports/share/applications/org.openshot.OpenShot.desktop

Este comando do terminal removeu a miniatura do Openshot da grade de Aplicativos:

sudo rm /var/lib/flatpak/exports/share/applications/org.openshot.OpenShot.desktop
apt
Martin Hope
Sun Bear
Asked: 2023-10-30 18:54:59 +0800 CST
  • 5

Após pressionar PrtScrne ir para o modo de vídeo para gravar um vídeo da área de trabalho, o vídeo gravado mostra o seguinte problema:problema de vídeo screencast

Como faço para corrigir esse problema de gravação no modo de vídeo Screencast ? O Screencast é capaz de tirar uma foto da área de trabalho, mas não de gravar vídeo na área de trabalho.

Detalhes do sistema:

Ubuntu 22.04

Notebook Acer E14.

Linux 6.2.0-35-genérico

PARA SUA INFORMAÇÃO:

  1. O aplicativo Cheese também não funcionou, mas o aplicativo Guvcview funciona.
  2. O aplicativo Zoom funciona imediatamente.
sound
Martin Hope
Sun Bear
Asked: 2023-09-02 19:07:58 +0800 CST
  • 5
$ dpkg -l | grep softwar
ii  brltty                                        6.4-4ubuntu3                                amd64        Access software for a blind person using a braille display
ii  docbook-xml                                   4.5-11                                      all          standard XML documentation system for software and systems
ii  espeak-ng-data:amd64                          1.50+dfsg-10                                amd64        Multi-lingual software speech synthesizer: speech data files
ii  gnome-software                                41.5-2ubuntu2                               amd64        Software Center for GNOME
ii  gnome-software-common                         41.5-2ubuntu2                               all          Software Center for GNOME (common files)
ii  gnome-software-plugin-flatpak                 41.5-2ubuntu2                               amd64        Flatpak support for GNOME Software
ii  gnome-software-plugin-snap                    41.5-2ubuntu2                               amd64        Snap support for GNOME Software
ii  libdv4:amd64                                  1.0.0-14build1                              amd64        software library for DV format digital video (runtime lib)
ii  libespeak-ng1:amd64                           1.50+dfsg-10                                amd64        Multi-lingual software speech synthesizer: shared library
ii  libfluidsynth-dev:amd64                       2.2.5-1                                     amd64        Real-time MIDI software synthesizer (development files)
ii  libfluidsynth3:amd64                          2.2.5-1                                     amd64        Real-time MIDI software synthesizer (runtime library)
ii  libqpdf28:amd64                               10.6.3-1                                    amd64        runtime library for PDF transformation/inspection software
ii  libwildmidi2:amd64                            0.4.3-1                                     amd64        software MIDI player library
ii  python3-software-properties                   0.99.22.7                                   all          manage the repositories that you install software from
ii  software-properties-common                    0.99.22.7                                   all          manage the repositories that you install software from (common)
ii  software-properties-gtk                       0.99.22.7                                   all          manage the repositories that you install software from (gtk)
ii  steam:i386                                    1:1.0.0.74-1ubuntu2                         i386         Valve's Steam digital software delivery system
ii  xbrlapi                                       6.4-4ubuntu3                                amd64        Access software for a blind person using a braille display - xbrlapi

A imagem acima mostra um sistema Ubuntu 22.04 com dois tipos de arquivos de atualização de software. Ou seja,:

  1. gnome-software, gnome-software-common, gnome-software-plugin-flatpak,gnome-software-plugin-snap
  2. python3-software-propertiese software-properties-common_software-properties-gtk

No dock, esses dois ícones de aplicativos estão presentes (veja abaixo). Ambos os programas fazem o mesmo trabalho.

ícones

Estou correto em pensar que apenas um deles é necessário? O que devo desinstalar para evitar programas duplicados residentes no sistema?

apt
Martin Hope
Sun Bear
Asked: 2022-02-12 08:34:41 +0800 CST
  • 2

Como resolvo esse sudo apt updateerro?

Err:9 http://download.opensuse.org/repositories/home:/pzz/xUbuntu_20.04  InRelease
  The following signatures were invalid: EXPKEYSIG 23E07629B9E3C9E4 home:pzz OBS Project <home:[email protected]>
Fetched 2,441 B in 3s (819 B/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
19 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org/repositories/home:/pzz/xUbuntu_20.04  InRelease: The following signatures were invalid: EXPKEYSIG 23E07629B9E3C9E4 home:pzz OBS Project <home:[email protected]>
W: Failed to fetch http://download.opensuse.org/repositories/home:/pzz/xUbuntu_20.04/InRelease  The following signatures were invalid: EXPKEYSIG 23E07629B9E3C9E4 home:pzz OBS Project <home:[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.

Eu tentei soluções do post Como faço para corrigir o erro GPG "NO_PUBKEY"? mas não funcionaram:

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 23E07629B9E3C9E4
[sudo] password for master: 
Executing: /tmp/apt-key-gpghome.QYq1pmnpyE/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 23E07629B9E3C9E4
gpg: keyserver receive failed: Server indicated a failure
$ gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv ^C
$ 23E07629B9E3C9E4^C
$ gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 23E07629B9E3C9E4
gpg: keyserver receive failed: No data
apt
Martin Hope
Sun Bear
Asked: 2022-01-11 20:26:38 +0800 CST
  • 9

Ao examinar os pacotes snap que estão instalados em um sistema, notei que alguns pacotes têm uma duplicata, um com um número de revisão superior e o outro com um número de revisão mais recente. Para esses pacotes duplicados, minhas perguntas são:

  1. Por que eles são duplicados?
  2. Posso remover o pacote mais antigo para garantir um melhor gerenciamento de espaço em disco?
  3. Como removo o pacote mais antigo?

Abaixo estão exemplos de pacotes que possuem e não possuem duplicatas:

$ du -hcs /var/lib/snapd/snaps/*
31M /var/lib/snapd/snaps/2048x_3.snap
286M    /var/lib/snapd/snaps/atom_282.snap
4.0K    /var/lib/snapd/snaps/bare_5.snap
72M /var/lib/snapd/snaps/bitwarden_58.snap
72M /var/lib/snapd/snaps/bitwarden_59.snap
196M    /var/lib/snapd/snaps/blender_1113.snap
214M    /var/lib/snapd/snaps/blender_1237.snap
9.1M    /var/lib/snapd/snaps/canonical-livepatch_119.snap
9.1M    /var/lib/snapd/snaps/canonical-livepatch_126.snap
148M    /var/lib/snapd/snaps/chromium_1854.snap
148M    /var/lib/snapd/snaps/chromium_1864.snap
17M /var/lib/snapd/snaps/chromium-ffmpeg_23.snap
18M /var/lib/snapd/snaps/chromium-ffmpeg_24.snap
....

~$ ls -lh /var/lib/snapd/snaps/
total 12G
-rw------- 2 root root  31M Aug  5 06:23 2048x_3.snap
-rw------- 2 root root 286M Aug  5 08:35 atom_282.snap
-rw------- 2 root root 4.0K Sep 22 18:17 bare_5.snap
-rw------- 1 root root  72M Oct 30 00:20 bitwarden_58.snap
-rw------- 1 root root  72M Dec  9 04:28 bitwarden_59.snap
-rw------- 1 root root 196M Nov 18 04:06 blender_1113.snap
-rw------- 1 root root 214M Dec  4 09:39 blender_1237.snap
-rw------- 2 root root 9.1M Nov 17 21:06 canonical-livepatch_119.snap
-rw------- 2 root root 9.1M Nov 22 22:39 canonical-livepatch_126.snap
-rw------- 1 root root 148M Dec 16 04:28 chromium_1854.snap
-rw------- 1 root root 148M Jan  8 08:33 chromium_1864.snap
-rw------- 1 root root  17M Sep  3 06:29 chromium-ffmpeg_23.snap
-rw------- 2 root root  18M Nov 29 14:23 chromium-ffmpeg_24.snap
....

No sistema que estou analisando, o espaço total em disco utilizado /var/lib/snapd/snaps/*é de 12.180,248 MB. O espaço em disco de todos os pacotes duplicados (ou seja, revisões mais antigas do mesmo pacote) é de 4.163,1 MB. Resumindo, os pacotes de revisão mais antigos atualmente ocupam 34,18% dos 12.180,248 MB. Isso parece ser um custo para usar aplicativos SNAP que eu não havia percebido antes.

20.04
Martin Hope
Sun Bear
Asked: 2022-01-08 18:06:34 +0800 CST
  • 0

Não consigo fazer com que o CUDA 11.5 funcione no Ubuntu 20.04 + driver Nvidia 470 + Geforce GTX Titan. Depois de instalar esta versão CUDA e reinicializar, um sistema de monitor duplo fica reduzido a um sistema de monitor único com uma baixa resolução de apenas 1920x1080. Além disso, um driver não-Nvidia parece estar instalado.

Verifiquei que tal sistema pode ser instalado com o CUDA 11.4, tudo funciona bem com esta versão do CUDA.

O CUDA 11.5 é compatível com o Ubuntu 20.04 + driver Nvidia 470 + Geforce GTX Titan?

drivers
Martin Hope
Sun Bear
Asked: 2021-09-02 00:36:09 +0800 CST
  • 1

A impressora e scanner Canon MG5370 está conectado à mesma rede que o Ubuntu 20.04. Usando Settings--> Printers--> Add, o Ubuntu 20.04 é capaz de detectar esta impressora. No entanto, quando tento "Testar impressão", nada acontece.

Acredito que isso aconteça porque está usando um driver de impressora genérico. Veja a imagem abaixo.

problema de impressora

Em um sistema Ubuntu 18.04 na mesma rede, essa mesma impressora funciona e posso ver que está usando o driver chamado Canon MG5300 series - CUPS+Gutenprint v5.2.13.

Para instalar este driver, cliquei no Gearbotão e selecionei Printer Details. Aí eu cliquei Search for Drivers. No entanto, ele não consegue encontrar um driver adequado. Em seguida, cliquei em Select from Database--> Canonmas não consegui encontrar nenhum MGou MG5300drivers.

Eu também tentei esta solução . A instalação foi bem sucedida, mas não conseguiu encontrar o scanner nem mesmo quando a impressora-scanner está conectada ao sistema via usb. Veja abaixo.

mensagem de erro scangear

Anteriormente, eu havia perguntado sobre como configurar o scanner dessa mesma impressora para o Ubuntu 16.04 . Tentei a solução lá. A instalação da Canon scangermptambém falhou devido a .

$ sudo ./install.sh
==================================================

ScanGear MP
Version 1.80
Copyright CANON INC. 2007-2011
All Rights Reserved.

==================================================
Command executed = sudo dpkg -iG ./packages/scangearmp-common_1.80-1_amd64.deb
Selecting previously unselected package scangearmp-common.
(Reading database ... 256647 files and directories currently installed.)
Preparing to unpack .../scangearmp-common_1.80-1_amd64.deb ...
Unpacking scangearmp-common (1.80-1) ...
dpkg: dependency problems prevent configuration of scangearmp-common:
 scangearmp-common depends on libpng12-0 (>= 1.2.8rel); however:
  Package libpng12-0 is not installed.
 scangearmp-common depends on libusb-0.1-4 (>= 2:0.1.10a); however:
  Package libusb-0.1-4 is not installed.

dpkg: error processing package scangearmp-common (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 scangearmp-common
Command executed = sudo dpkg -P scangearmp-common
(Reading database ... 256695 files and directories currently installed.)
Removing scangearmp-common (1.80-1) ...
Purging configuration files for scangearmp-common (1.80-1) ...

O que devo fazer para configurar este scanner de impressora Canon MG5370 no Ubuntu 20.04? Quero imprimir e digitalizar.

Atualizar:

$ driverless
$ driverless list
DEBUG: Started ippfind (PID 25370)
DEBUG: Started post-processing (PID 25371)
DEBUG: PID 25370 (ippfind) stopped with status 1!
DEBUG: PID 25371 (Post-processing) exited with no errors.

$ lpinfo -v
file cups-brf:/
network beh
network http
network ipp
network lpd
serial serial:/dev/ttyS0?baud=115200
network https
network ipps
direct hp
network socket
direct usb://Canon/MG5300%20series?serial=20EE62&interface=1
direct hpfax
network dnssd://Canon%20MG5300%20series._printer._tcp.local/?uuid=urn:uuid:00000000-0000-1000-8000-8887178XXXXX

Resultado de seguir a resposta @brian_p:

$ scanimage -L
device `pixma:04A91754_20EE62' is a CANON Canon PIXMA MG5300 multi-function peripheral
device `airscan:w1:Canon MG5300 series' is a WSD Canon MG5300 series ip=192.168.1.XXX
$ airscan-disciver
airscan-disciver: command not found
$ airscan-discover
[devices]
$

Resultados Para impressão:

sudo apt install printer-driver-gutenprintfoi concluído com sucesso.

$ lpinfo -m | grep MG5370
gutenprint.5.3://bjc-PIXMA-MG5370/expert Canon PIXMA MG5370 - CUPS+Gutenprint v5.3.3
$ lpadmin -p MG5370 -v dnssd://Canon%20MG5300%20series._printer._tcp.local/?uuid=urn:uuid:00000000-0000-1000-8000-8887178XXXXX -E -m gutenprint.5.3://bjc-PIXMA-MG5370/expert
lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS.
$ lp -d MG5370 /etc/nsswitch.conf
request id is MG5370-2 (1 file(s))

A impressão sem fio foi bem-sucedida.

networking
Martin Hope
Sun Bear
Asked: 2021-08-28 01:13:47 +0800 CST
  • 1

Não consigo alternar o espaço de trabalho rolando a roda do mouse quando o ponteiro do mouse está sobre o encaixe para o Ubuntu 20.04.

Para alternar a área de trabalho com a rolagem do mouse sobre o dock: org.gnome.shell.extensions.dash-to-dock.scroll-switch-workspaceestá usando o valor padrão, ou seja, true. Mas esta configuração não parece funcionar.

Para alternar a área de trabalho ao rolar no ícone do aplicativo, org.gnome.shell.extensions.dash-to-dock.scroll-actionestá usando o valor padrão, ou seja, 'switch-workspace'esta configuração funciona.

Como posso corrigir esse problema?

20.04
Martin Hope
Sun Bear
Asked: 2021-08-21 01:45:46 +0800 CST
  • 2

Eu fiz sudo apt upgradee reiniciei o sistema Ubuntu 20.04. No entanto, após o login, o Dock está ausente do ambiente de desktop. O Dock aparece na borda esquerda do monitor quando pressiono o Superbotão para entrar na Activitiestela.

Eu tentei soluções 1 e também fazendo

$ sudo apt install gnome-shell-extension-ubuntu-dock
$ sudo dpkg-reconfigure gnome-shell-extension-ubuntu-dock

Cada vez reinicie para verificar a aparência do dock. Ainda faltando.

notei algo estranho em Settings--> Appearance--> Dock. Icon sizeé 0 e não pode ser alterado e Show onestá em branco. Position on screenestava inicialmente em branco. Eu poderia selecionar qualquer uma das opções, mas o Dock ainda não aparece. Ver imagem

Problema de Configurações-Aparência-Dock

Algum tempo atrás, eu tinha instalado Dash-to-Docke desinstalado. Dock ainda aparece e funcionou bem por semanas até esta atualização. De acordo com o apt log, os pacotes afetados foram:

Upgrade: brave-browser:amd64 (1.27.111, 1.28.106), libegl1-mesa-dev:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libegl-mesa0:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), update-notifier-common:amd64 (3.192.30.8, 3.192.30.9), libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.9, 2:4.11.6+dfsg-0ubuntu1.10), grub-common:amd64 (2.04-1ubuntu26.12, 2.04-1ubuntu26.13), libglapi-mesa:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libglapi-mesa:i386 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libxatracker2:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), grub2-common:amd64 (2.04-1ubuntu26.12, 2.04-1ubuntu26.13), grub-pc:amd64 (2.04-1ubuntu26.12, 2.04-1ubuntu26.13), libgbm1:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.9, 2:4.11.6+dfsg-0ubuntu1.10), grub-pc-bin:amd64 (2.04-1ubuntu26.12, 2.04-1ubuntu26.13), firefox-locale-en:amd64 (91.0+build2-0ubuntu0.20.04.1, 91.0.1+build1-0ubuntu0.20.04.1), libgles2-mesa-dev:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), distro-info-data:amd64 (0.43ubuntu1.5, 0.43ubuntu1.6), libgl1-mesa-dev:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libgl1-mesa-dri:i386 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libgl1-mesa-dri:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libsmbclient:amd64 (2:4.11.6+dfsg-0ubuntu1.9, 2:4.11.6+dfsg-0ubuntu1.10), shim-signed:amd64 (1.40.6+15.4-0ubuntu7, 1.40.7+15.4-0ubuntu9), libgl1-mesa-glx:i386 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), firefox:amd64 (91.0+build2-0ubuntu0.20.04.1, 91.0.1+build1-0ubuntu0.20.04.1), mesa-vdpau-drivers:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), mesa-vulkan-drivers:i386 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), update-notifier:amd64 (3.192.30.8, 3.192.30.9), mesa-va-drivers:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libglx-mesa0:amd64 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1), libglx-mesa0:i386 (21.0.3-0ubuntu0.2~20.04.1, 21.0.3-0ubuntu0.3~20.04.1)
End-Date: 2021-08-20  06:44:43

Como faço para que o Dock reapareça?

Atualizar

@vanadium Não consigo habilitar o Ubuntu Docks de Extensionou Tweaks. Veja abaixo. Não é possível fazer o seu passo 4.

erro ubuntudock

apt