Sun Bear's questions

To play music through both the Line Out Built-in Audio and Bluetooth speakers, I implemented the answer by @DidierL that created a new “Simultaneous Output” as output device.

I then noticed a slight delay in the bluetooth speak sound. To remedy this delay, I tried the answer by @PoDuck. That is implementing

#!/bin/bash

BLUEZCARD=$(pactl list cards short | egrep -o bluez.*[[:space:]])
pactl set-card-profile $BLUEZCARD a2dp_sink
pactl set-card-profile $BLUEZCARD headset_head_unit
pactl set-card-profile $BLUEZCARD a2dp_sink

As this solution could not rectify the delay, I tried :

#!/bin/bash

BLUEZCARD=$(pactl list cards short | egrep -o bluez.*[[:space:]])
pactl set-card-profile $BLUEZCARD off
pactl set-card-profile $BLUEZCARD a2dp_sink
pactl set-card-profile $BLUEZCARD off
pactl set-card-profile $BLUEZCARD a2dp_sink

Unfortunately, this setting broke the performance of the “Simultaneous Output” device. It does not play any sound.

Also, only the Line Out Built-in Audio works if select explicitly. When the bluetooth speaker is selected explicity, the sound is very muted.

I don't know how to undo the mess as in Ubuntu 24.04, there is not option to undo the custom Shortcut as was mentioned by @PoDuck's answer.

and then click on the right where it says Disabled to set up a keyboard shortcut to execute the script.

How do I undo the mess?

Update:

I just discovered qpwgraph. Below gives a visual of the. I notice a few repeated modules, I wonder how it got there.

Any advice on what to do would be great.

When configuring unbound with --enable-dnstap, it can't locate protobuf-c.

$ ./configure --enable-dnstap
...
...
...
checking for protoc-c... no
configure: error: The protoc-c program was not found. Please install protobuf-c!

However, protobuf-c appears to be installed.

$ sudo apt search protobuf-c
Sorting... Done
Full Text Search... Done
libprotobuf-c-dev/stable,now 1.4.1-1+b1 armhf [installed]
  Protocol Buffers C static library and headers (protobuf-c)

libprotobuf-c1/stable,now 1.4.1-1+b1 armhf [installed,automatic]
  Protocol Buffers C shared library (protobuf-c)

librust-prometheus+protobuf-codegen-pure-dev/stable 0.13.3-1 armhf
  Prometheus instrumentation library for Rust applications - feature "protobuf-codegen-pure" and 1 more

librust-protobuf-codegen-dev/stable 2.27.1-1+b2 armhf
  Code generator for rust-protobuf - Rust source code

librust-protobuf-codegen-pure-dev/stable 2.27.1-1 armhf
  Pure-rust codegen for protobuf using protobuf-parser crate - Rust source code

protobuf-c-compiler/stable 1.4.1-1+b1 armhf
  Protocol Buffers C compiler (protobuf-c)

protobuf-codegen/stable 2.27.1-1+b2 armhf
  Code generator for rust-protobuf

protobuf-compiler/stable 3.21.12-3 armhf
  compiler for protocol buffer definition files

protobuf-compiler-grpc/stable 1.51.1-3+b1 armhf
  high performance general RPC framework - protobuf plugin

protobuf-compiler-grpc-java-plugin/stable 1.41.3+ds-1 armhf
  high performance general RPC framework - protobuf Java plugin  
$ dpkg -l | grep protobuf
ii  libprotobuf-c-dev:armhf              1.4.1-1+b1                              armhf        Protocol Buffers C static library and headers (protobuf-c)
ii  libprotobuf-c1:armhf                 1.4.1-1+b1                              armhf        Protocol Buffers C shared library (protobuf-c)
$ sudo find / -name libprotobuf-c1
/usr/share/doc/libprotobuf-c1
$ sudo find / -name libprotobuf-c-dev
/usr/share/doc/libprotobuf-c-dev
$ ls /usr/bin/ | grep proto
$ ls /usr/local/bin/ | grep proto
$ ls /bin/ | grep proto
$ ls /usr/lib/ | grep proto
$ ls /usr/local/lib/ | grep proto
$ ls /lib/ | grep proto
$

I can't locate the protobuf-c library or program either although it is installed.

I do I resolve this configuration issue?

Update:

I discovered from this answer that the library name is libprotobuf-c.so.1.

Its location was found using:

$ sudo find / -name libprotobuf-c.so.1
/usr/lib/arm-linux-gnueabihf/libprotobuf-c.so.1
$

I tried linking this file into /usr/local/lib (Unbound default installation library directory) via

$ ln -s /usr/lib/arm-linux-gnueabihf/libprotobuf-c.so.1 

and reran

$ ./configure --enable-dnstap

and still got the same error msg as mentioned above.

I further tried:

./configure --enable-dnstap --with-protobuf-c=/usr/lib/arm-linux-gnueabihf/libprotobuf-c.so.1

and still got the same error msg as mentioned above.

The unbound version that I am trying to configure is 1.22.0.

This question does not duplicate How do I find the package that provides a file?. Reasons:

1. I am already using dpkg.
2. I found that using apt search to be more suitable as it shows all the other packages related to protobuf-c with description.
3. Apart from the libprotobuf-c, unbound also uses the protoc-c program (informed to me by an unbound member), which is available after installing protobuf-c-compiler (see @steeldriver comment). This information isn't disclosed using dpkg.

I have configured Unbound to:

1. listen for domain queries on all interfaces in a LAN,
2. forward these domain queries to an external DNS resolver via TLS,
3. receive the resolved domain IPs from the external DNS resolver and return them to the corresponding clients.

How do I verify that such a configuration is functioning? Especially, how do I verify that:

1. Unbound has forwarded the domain queries to the desired external DNS resolver over TLS?
2. The resolved domain IPS are from the external DNS resolver and are not resolved by Unbound?

Below are two results from digging google.com. How can i use these results to do the above mentioned verifications?

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

Below are logs in unbound.log with verbosity: 3 after restarting the unbound.service and running the above dig command twice. I can see that the external DNS resolver is mentioned but I can't understand which line shows that it has resolved the domain and return the results to 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

This is a follow-up question to my 2nd question. The solution by @mpboden was implemented. In addition, I have added the auto-trust-anchor-file: and enabled remote-control:, as is defined in the Unbound example for Setting up for the rest of the network example.

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

However, I discovered 4 errors and 1 failure message using debug mode. From my troubleshooting efforts, I found that these error and failure messages occurred whenever control-enable: yes was allowed.

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

I have checked that /var/lib/unbound/root.key exists. Unbound still works but unbound-control can't be used. Unbound is looking for /etc/unbound/unbound_server.pem but this file does not exist. How do I resolve this remote-control config issue?

Update:

with @mpboden answer, I discovered that the command unbound-control-setup is meant to create these files in /etc/unbound: unbound_control.pem, unbound_server.pem, unbound_control.key, unbound_server.key, to allow remote control.

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

This is a follow-up question to my earlier question. Below is the /etc/unbound/unbound.conf file:

# 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

With unbound.service started, I tried to dig a domain via the local unbound server:

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

I don't understand why WARNING: recursion requested but not available as unbound is configured to be a recursive resolver by default. Also. SERVER: 192.168.1.50#3000(192.168.1.50) (UDP) shows that unbound was used, however, it failed to get the domain. What is wrong and how do I fix this issue?

Below shows the answer via systemd-resolved.service stub server:

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

Update:

After correcting the subnet as mentioned by @mpboden answer, the dig command only worked once. Why is this the case?

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

unbound.service runs w/o error when these 3 default files (created after installing unbound) are used:

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"

However, when these 3 files are removed and the content of /etc/unbound/unbound.conf made to contain

# 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.service fails to restart using service unbound restart. e.g.

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.

To troubleshoot, I commented out every line, followed by uncommenting each line until unbound.service failed to restart. I discovered that the line interface: 0.0.0.0 is the cause of the error. I can't figure out why 0.0.0.0 is causing the issue. Why is this ip address causing this issue?

System:

• Unbound version: 1.19.2
• OS: Linux DNS 6.1.63 #218 SMP Thu Nov 30 20:48:04 CST 2023 aarch64 aarch64 aarch64 GNU/Linux in Ubuntu Server 24.04.1
• unbound -V output:

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

Update:

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

When I execute dig example.com, one of the returned line states:

;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)

Can you explain the meaning of each of the components in this line?

I noticed that Nautilus in Ubuntu 24.04 does not show the progress disc when copying a large amount of files. Is this situation unique to me or is there a bug or this feature has been removed? Nautilus in Ubuntu 22.04 does show this copying progress disc.

Reply to @cordlord answer:

The image below illustrates what I meant in my comment to your answer. The benefit of this approach over the use of multiple tabs in one window is that the contents in both folders are simultaneously visible.

This next image shows the menu bar when the nautilus window is not in a compact mode. As you have mentioned in your answer, the copying progress info is shown at the bottom of the left menu bar.

While doing do-release-upgrade from 22.04 to 24.04, this system encountered an issue during restart(i.e. after installing 24.04 was completed). How do I recover from this issue? The upgrade procedure is given by nixCraft.

Below is the EFI boot screen:

I am trying to do 2-sided copy using the Document Scanner app via the top feeder of a Canon E4570 scanner-printer.

The picture below shows the app setting before clicking Scan. The app is able to scan the top page of the paper but not the bottom page of the paper. How do I activate duplex scanning?

System and App Info:

• system: Linux 6.8.0-40-generic #40~22.04.3-Ubuntu
• canon firmware: 1.070
• document scanner: 42.0

After downloading and extracting libreoffice and going to ~/Downloads/tmp/LibreOffice_24.2.3.2_Linux_x86-64_deb/DEB, I encoutered this issue. How do I overcome them on Ubuntu 22.04? I can't install any of these files.

$ 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

Note

If you’d like a requirements.txt output of the lockfile, run $ pipenv lock -r. This will include all hashes, however (which is great!). To get a requirements.txt without hashes, use $ pipenv run pip freeze.

According to the above pipenv notice, if you’d like a requirements.txt output of the lockfile, you should run $ pipenv lock -r. However, the -r options does not exist:

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

May I know the command to get the requirements.txt output of the pipenv lockfile?

I want a fresh install of Openshot using its latest Linux(64-bit AppImage) file on a machine that had previously installed Openshot via apt, snap and flatpak. I have purged all its old installations. I have even purged flatpak. However, I still found Openshot files on this machine and its thumbnail appears in the Ubuntu 22.04 applications grid.

$ 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

However, according to Nautilus, many residual files are in the /var/lib/flatpak/app directory.

Also, the Openshot thumbnail continues to exist in the Applications grid

but folders ~/.local/share/applications and /usr/share/applications do not contain any openshot .desktop files.

Questions:

1. Can I simply delete the folder /var/lib/flatpak/app/org.openshot.OpenShot and not cause any problem to the machine?
2. Since I have purged flatpak, can I even delete folder /var/lib/flatpak?
3. Also, how do I remove the Openshot thumbnail in the Applications grid?

Update:

I discovered the existence of a file called org.openshot.OpenShot.desktop. It's paths are:

• /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

This terminal command removed the Openshot thumbnail from the Applications grid:

sudo rm /var/lib/flatpak/exports/share/applications/org.openshot.OpenShot.desktop

After pressing on PrtScrn and going to the video mode to record a video of the desktop, the recorded video shows the following issue:

How do I fix this Screencast video mode recording issue? The Screencast is able to take a photo of the Desktop but not able to record video on the Desktop.

System details:

Ubuntu 22.04

Acer E14 laptop.

Linux 6.2.0-35-generic

FYI:

1. The Cheese app also could not work but the Guvcview app does work.
2. The Zoom app works right out of the box.

$ 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

The above shows a Ubuntu 22.04 system having two types of software update files. Namely, :

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

On the dock, these two app icons are present(see below). Both programs do the same job.

Am I correct to think that only one of them is needed? Which should I uninstall to avoid duplicated programs residing in the system?

While examining the snap packages that are installed in a system, I noticed that some packages have a duplicate, one having an over revision number while the other having a newer revision number. For such duplicated packages, my questions are:

1. Why are they duplicated?
2. Can I remove the older package to ensure better disk space management?
3. How do I remove the older package?

Below are examples of packages that do and do not have duplicates:

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

On the system that I am looking at, the total disk space utilized by /var/lib/snapd/snaps/* is 12,180.248 MB. The disk space of all the duplicated packages(i.e. older revision of the same package) is 4,163.1 MB. In short, the older revision packages currently takes up 34.18% of the 12,180.248 MB. This appears to be a cost to using SNAP apps that I had not realised before.

How does a user list the size of each installed snap package in Ubuntu 20.04? The purpose is to get an overview perspective of the disk space utilised by each installed snap package. The command snap list does not do this. Also, the app Disk Usage Analyzer could not show further than /var/lib/snapd/snaps.

My Ubuntu 18.04 system has been working fine for quite some time (a few years). It suddenly threw up this error. Causes the system to auto-reboot several time. Sometimes it is able to boot into the login but even after login, it is behaving in a cranky manner. What gives?

linux kernel 5.4.0-42-generic

Update:

1. The BIOS was updated and that resolved the crazy auto-reboot issue and made the system usable.

2. I found that this Error appears in the dmesg log of both 18.04 and 16.04. Below is a more detailed list of the ACPI error msg (I found some related ACPI msgs was issued but without the ACPI syntax). It seems the issue pertains to the method _GTF. What is that and what does it do? Also, what is a DSSP?

More details from dmesg on the error:

[    1.201570] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.201575] No Local Variables are initialized for Method [_GTF]
[    1.201576] No Arguments are initialized for method [_GTF]
[    1.201577] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.205307] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205311] No Local Variables are initialized for Method [_GTF]
[    1.205312] No Arguments are initialized for method [_GTF]
[    1.205313] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.249944] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.249949] No Local Variables are initialized for Method [_GTF]
[    1.249950] No Arguments are initialized for method [_GTF]
[    1.249951] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.333524] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.333529] No Local Variables are initialized for Method [_GTF]
[    1.333530] No Arguments are initialized for method [_GTF]
[    1.333531] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)

There used to be many tools in the GIMP Toolbox. However, recently after an Update, many of the tools in the Toolbox seems to have been removed. How do I restore the original layout of the Toolbox?

Current Toolbox with less tools:

$ snap list | grep gimp
gimp                     2.10.18                     252   stable    snapcrafters

I just tried to run gimp from the command line and found the below msg. I also see this msg in other computer.

$ gimp
ln: failed to create symbolic link '~/snap/gimp/252/.config/gtk-2.0/gtkfilechooser.ini': File exists
/snap/gimp/252/usr/bin/gimp: Gimp-Widgets-WARNING: parse_iso_codes: error parsing '/build/gimp/parts/gimp/install/usr/share/xml/iso-codes/iso_639.xml': No such file or directory

How can I share/display what I am seeing on my Ubuntu system to a networked Samsung Smart TV? The Ubuntu system and Samsung Smart TV are LAN connected to the same network. The Ubuntu system is a workstation.

I found this question however the solution there on using hdmi and vga cable isn't what i am looking for. I am looking for a solution akin to what we can get from mirroring or chromecasting.

Update: I found the following useful links on this subject (but there is no mention of Linux/Ubuntu):

1. Best Miracast and Screen-Mirroring Devices 2018
2. How to Mirror PC to TV