tribbloid's questions

When I run btrfs check --repair to try to fix the following error, I got the following output:

$ sudo btrfs check --repair /dev/sda1
enabling repair mode
WARNING:

    Do not use --repair unless you are advised to do so by a developer
    or an experienced user, and then only after having accepted that no
    fsck can successfully repair all types of filesystem corruption. Eg.
    some software or hardware bugs can fatally damage a volume.
    The operation will start in 10 seconds.
    Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check...
parent transid verify failed on 111692120064 wanted 360498 found 364003
parent transid verify failed on 111692120064 wanted 360498 found 364003
Ignoring transid failure
parent transid verify failed on 29671424 wanted 360534 found 364003
parent transid verify failed on 29671424 wanted 360534 found 364003
Ignoring transid failure
parent transid verify failed on 34750464 wanted 363754 found 364003
parent transid verify failed on 34750464 wanted 363754 found 364003
Ignoring transid failure
Checking filesystem on /dev/sda1
UUID: e75d569a-400c-4076-8b9f-903a7a1f4f03
[1/7] checking root items
parent transid verify failed on 111692120064 wanted 360498 found 364003
Ignoring transid failure
parent transid verify failed on 29671424 wanted 360534 found 364003
Ignoring transid failure
parent transid verify failed on 34750464 wanted 363754 found 364003
Ignoring transid failure
Fixed 0 roots.
[2/7] checking extents
parent transid verify failed on 29671424 wanted 360534 found 364003
Ignoring transid failure
parent transid verify failed on 34750464 wanted 363754 found 364003
Ignoring transid failure
parent transid verify failed on 111692120064 wanted 360498 found 364003
Ignoring transid failure
extent back ref already exists for 21790720 parent 0 root 10
extent back ref already exists for 21839872 parent 0 root 10
extent back ref already exists for 21856256 parent 0 root 10
extent back ref already exists for 22003712 parent 0 root 10
extent back ref already exists for 22036480 parent 0 root 10
extent back ref already exists for 23396352 parent 0 root 10
extent back ref already exists for 23412736 parent 0 root 10
parent transid verify failed on 37912576 wanted 351287 found 364003
parent transid verify failed on 37912576 wanted 351287 found 364003
Ignoring transid failure
parent transid verify failed on 38420480 wanted 351287 found 364003
parent transid verify failed on 38420480 wanted 351287 found 364003
Ignoring transid failure
parent transid verify failed on 38486016 wanted 351287 found 364003
parent transid verify failed on 38486016 wanted 351287 found 364003
Ignoring transid failure
parent transid verify failed on 46858240 wanted 351287 found 364003
parent transid verify failed on 46858240 wanted 351287 found 364003
Ignoring transid failure
parent transid verify failed on 62865408 wanted 363983 found 364003
parent transid verify failed on 62865408 wanted 363983 found 364003
Ignoring transid failure
parent transid verify failed on 67059712 wanted 363983 found 364003
parent transid verify failed on 67059712 wanted 363983 found 364003
Ignoring transid failure
parent transid verify failed on 71417856 wanted 360532 found 364003
parent transid verify failed on 71417856 wanted 360532 found 364003
Ignoring transid failure
Chunk[256, 228, 182558130176]: length(1073741824), offset(182558130176), type(1) is not found in block group
Chunk[256, 228, 192221806592]: length(1073741824), offset(192221806592), type(1) is not found in block group
Chunk[256, 228, 279194894336]: length(1073741824), offset(279194894336), type(1) is not found in block group
Chunk[256, 228, 299595988992]: length(1073741824), offset(299595988992), type(1) is not found in block group
well this shouldn't happen, extent record overlaps but is metadata? [21790720, 16384]

Aborted

the Aborted is triggered after 1 minute after the prompt, so I assume that btrfs check was asking me to make a hard decision. The problem is: what kind of decision do I have and how do I inform the program to conduct the fix?

I'm using ubuntu 22.04, the btrfs is on the second HDD slot without being mounted.

Thanks a lot for your help!

When no external mouse is connected, here is the xinput & libinput output respectively:

$ xinput
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Asus Keyboard                             id=14   [slave  pointer  (2)]
⎜   ↳ ELAN1203:00 04F3:307A Mouse               id=15   [slave  pointer  (2)]
⎜   ↳ ELAN1203:00 04F3:307A Touchpad            id=16   [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Video Bus                                 id=9    [slave  keyboard (3)]
    ↳ Power Button                              id=10   [slave  keyboard (3)]
    ↳ Sleep Button                              id=11   [slave  keyboard (3)]
    ↳ Asus Keyboard                             id=12   [slave  keyboard (3)]
    ↳ Asus Keyboard                             id=13   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=17   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=18   [slave  keyboard (3)]
    ↳ Asus Keyboard                             id=19   [slave  keyboard (3)]

$ sudo libinput list-devices
Device:           ELAN1203:00 04F3:307A Mouse
Kernel:           /dev/input/event6
Group:            8
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           ELAN1203:00 04F3:307A Touchpad
Kernel:           /dev/input/event13
Group:            8
Seat:             seat0, default
Size:             101x52mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    none
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation:         n/a
...

As a result, sometimes the touchpad will suddenly lose ability to do gestures and 2-finger scrolling, because the mouse takes higher input priority. How to avoid this situation?

When I upgrade Ubuntu from 21.10 to 22.04, I encounter the following error:

# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 gdm3 : Depends: gir1.2-gdm-1.0 (= 41~rc-0ubuntu2pop0~1634915133~21.10~cf40258) but 42.0-1ubuntu6pop1~1650301427~22.04~2055533 is installed
        Depends: libgdm1 (= 41~rc-0ubuntu2pop0~1634915133~21.10~cf40258) but 42.0-1ubuntu6pop1~1650301427~22.04~2055533 is installed
 gnome-control-center : Depends: gnome-control-center-data (< 1:41) but 1:41.4-1ubuntu12pop1~1651079086~22.04~c5012df is installed
 gnome-settings-daemon : Depends: gnome-settings-daemon-common (= 40.0.1-1ubuntu3pop0~1639691325~21.10~3bcd31b) but 42.1-1ubuntu1pop0~1649081298~22.04~192b1be is installed
 libwacom2 : Depends: libwacom-common (= 1.8-2ubuntu2) but 2.2.0-1 is installed
 systemd : Depends: libsystemd0 (= 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e) but 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
 gdm3 : Depends: gir1.2-gdm-1.0 (= 41~rc-0ubuntu2pop0~1634915133~21.10~cf40258) but 42.0-1ubuntu6pop1~1650301427~22.04~2055533 is installed
        Depends: libgdm1 (= 41~rc-0ubuntu2pop0~1634915133~21.10~cf40258) but 42.0-1ubuntu6pop1~1650301427~22.04~2055533 is installed
 gnome-control-center : Depends: gnome-control-center-data (< 1:41) but 1:41.4-1ubuntu12pop1~1651079086~22.04~c5012df is installed
 gnome-settings-daemon : Depends: gnome-settings-daemon-common (= 40.0.1-1ubuntu3pop0~1639691325~21.10~3bcd31b) but 42.1-1ubuntu1pop0~1649081298~22.04~192b1be is installed
 libwacom2 : Depends: libwacom-common (= 1.8-2ubuntu2) but 2.2.0-1 is installed
 systemd : Depends: libsystemd0 (= 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e) but 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af is installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies

All options fail. How to fix it?

When I open the system log in Ubuntu 20.04 I consistently run in this error:

BTRFS error (device sda1): incorrect extent count for 153567100928; counted 221, expected 222

I can't get extra information, run further diagnose or fix it through any btrfs tools (btrfs check, ftrim, defrag et al.) How do I fix it?

I got the following error message:

$ sudo apt -f remove libgranite-common 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libgranite5 : Depends: libgranite-common (>= 5.3.0-1) but it is not going to be installed
 libgranite6 : Depends: libgranite-common (>= 6.0.0+r2017+pkg118~daily~ubuntu6.1) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libgranite-common
The following packages will be upgraded:
  libgranite-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
27 not fully installed or removed.
Need to get 0 B/53.0 kB of archives.
After this operation, 9,216 B disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 364127 files and directories currently installed.)
Preparing to unpack .../libgranite-common_6.0.0+r2017+pkg118~daily~ubuntu6.1_all.deb ...
Unpacking libgranite-common (6.0.0+r2017+pkg118~daily~ubuntu6.1) over (5.3.0-1) ...
dpkg: error processing archive /var/cache/apt/archives/libgranite-common_6.0.0+r2017+pkg118~daily~ubuntu6.1_all.deb (--unpack):
 trying to overwrite '/usr/share/metainfo/granite.appdata.xml', which is also in package libgranite5:amd64 5.3.0-1
Errors were encountered while processing:
 /var/cache/apt/archives/libgranite-common_6.0.0+r2017+pkg118~daily~ubuntu6.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Recently ubuntu apt always try to upgrade libnvidia-common package with no effect, so I query this package and found 2 sources that are totally identical, one is from canonical & the other is from nvidia cuda ppa:

$ apt show libnvidia-common-450 -a
Package: libnvidia-common-450
Version: 450.36.06-0ubuntu1
Priority: optional
Section: non-free/libs
Source: nvidia-graphics-drivers-450
Maintainer: Ubuntu Core Developers <[email protected]>
Installed-Size: 35.8 kB
Provides: libnvidia-common
Replaces: libnvidia-common, libnvidia-gl-450 (<< 390.25-0ubuntu2~)
Download-Size: 10.2 kB
APT-Sources: http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  Packages
Description: Shared files used by the NVIDIA libraries
 This package provides a set of files that are required by the NVIDIA
 libraries.

Package: libnvidia-common-450
Version: 450.36.06-0ubuntu1
Status: install ok installed
Priority: optional
Section: non-free/libs
Source: nvidia-graphics-drivers-450
Maintainer: Ubuntu Core Developers <[email protected]>
Installed-Size: 35.8 kB
Provides: libnvidia-common
Breaks: libnvidia-gl-450 (<< 390.25-0ubuntu2~)
Replaces: libnvidia-common, libnvidia-gl-450 (<< 390.25-0ubuntu2~)
Homepage: http://www.nvidia.com
Download-Size: unknown
APT-Manual-Installed: no
APT-Sources: /var/lib/dpkg/status
Description: Shared files used by the NVIDIA libraries
 This package provides a set of files that are required by the NVIDIA
 libraries.


$ aptitude show libnvidia-common-450
Package: libnvidia-common-450     
Version: 450.36.06-0ubuntu1
State: installed (450.36.06-0ubuntu1), upgrade available (450.36.06-0ubuntu1)
Automatically installed: yes
Priority: optional
Section: non-free/libs
Maintainer: Ubuntu Core Developers <[email protected]>
Architecture: all
Uncompressed Size: 35.8 k
Replaces: libnvidia-common, libnvidia-gl-450 (< 390.25-0ubuntu2~)
Provides: libnvidia-common
Description: Shared files used by the NVIDIA libraries
 This package provides a set of files that are required by the NVIDIA libraries.

So how do I avoid this situation?

I'm using ubuntu 18.04 which has systemd-resolved enabled by default, and by convention the local 'virtual' DNS ip address set to 127.0.0.53:53. other dns services like dnsmasq are not installed, all their configurations and launching scripts are purged from the system so they have no impact.

The local DNS seems to be functioning properly. When I test it using dig it yields the proper lookup:

$ dig @127.0.0.53 www.google.com

; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> @127.0.0.53 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21226
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
www.google.com.     18  IN  A   172.217.1.164

;; Query time: 24 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Sep 24 01:24:52 EDT 2019
;; MSG SIZE  rcvd: 59

In comparison, the LAN DNS suggested by DHCP gives similar lookup:

$ dig @192.168.0.1 www.google.com

; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> @192.168.0.1 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11809
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
www.google.com.     53  IN  A   172.217.0.228

;; Query time: 65 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Tue Sep 24 01:25:12 EDT 2019
;; MSG SIZE  rcvd: 59

Unfortunately it appears that they differs in terms of capability. When they are used as DNS server by local containers (e.g. Anbox for android simulation):

$ sudo snap get anbox -d
{
    "bridge": {
        "nat": {
            "enable": true
        }
    },
    "container": {
        "network": {
            "dns": "127.0.0.53"
        }
    },
    "rootfs-overlay": {
        "enable": true
    }
}

It turns out that only the LAN DNS 192.168.0.1 can work properly, the local 'virtual' DNS 127.0.0.53 can only be pinged, but no lookup can be performed.

My questions are:

1. Is the systemd-resolved functioning properly as a DNS forwarder now?

2. How to further identify the problem using whatever tools available in ubuntu, adb, and android application?

It should be noted that I have all firewall disabled to simplify test. And the default DNS 8.8.8.8 also doesn't work for unknown reason. The adb shell doesn't have enough utilities to further identify DNS problem

snap has 2 modules: snap-store and gnome-3-28-1804, the first one depends on the second.

Yet when I use $ snap remove gnome-3-28-1804, I got no error information: no warning of consequence, no prompt to remove snap-store, no nothing.

So obviously the next time I use snap-store I got the following error:

$ snap-store 
/home/peng/snap/snap-store/common/.cache/gio-modules/libgiognomeproxy.so: cannot open shared object file: No such file or directory
Failed to load module: /home/peng/snap/snap-store/common/.cache/gio-modules/libgiognomeproxy.so
/home/peng/snap/snap-store/common/.cache/gio-modules/libdconfsettings.so: cannot open shared object file: No such file or directory
Failed to load module: /home/peng/snap/snap-store/common/.cache/gio-modules/libdconfsettings.so
/home/peng/snap/snap-store/common/.cache/gio-modules/libgiolibproxy.so: cannot open shared object file: No such file or directory
Failed to load module: /home/peng/snap/snap-store/common/.cache/gio-modules/libgiolibproxy.so
/home/peng/snap/snap-store/common/.cache/gio-modules/libgiognutls.so: cannot open shared object file: No such file or directory
Failed to load module: /home/peng/snap/snap-store/common/.cache/gio-modules/libgiognutls.so
20:09:52:0025 Gtk Locale not supported by C library.
        Using the fallback 'C' locale.
20:09:52:0155 Gtk Failed to load module "canberra-gtk-module"
20:09:52:0163 Gtk Failed to load module "canberra-gtk-module"
20:09:52:0167 GLib-GIO Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.
20:09:52:0221 Gs  enabled plugins: odrs, rewrite-resource, snap, icons, key-colors, key-colors-metadata
20:09:52:0221 Gs  disabled plugins: appstream, desktop-categories, desktop-menu-path, dpkg, dummy, epiphany, fedora-pkgdb-collections, generic-updates, hardcoded-blacklist, hardcoded-featured, hardcoded-popular, modalias, os-release, provenance, provenance-license, repos, shell-extensions
Fontconfig error: Cannot load default config file
20:09:52:0342 Gtk Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /snap/snap-store/188/data-dir/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Aborted                             

My question is: why snap chose to make such a low level mistake?

After the OS is running for a while, it may trigger for a bug that caused pkexec (including any application that use it, including synaptic) to hang. This can only be recovered from relaunching OS or gnome-shell.

This is a screenshot that describe this situation:

xhost +si:localuser:root
pkexec synaptic

I remember the same error in Manjaro with gnome 3.28, it disappeared in gnome 3.30. How do I backport the fix (if there is any) to Ubuntu 18.04?

UPDATE 1

these are my desktop environment:

$ export | grep XDG_SESS
declare -x XDG_SESSION_DESKTOP="ubuntu"
declare -x XDG_SESSION_ID="1"
declare -x XDG_SESSION_TYPE="x11"

... and synaptics version

$ apt-cache policy synaptic
synaptic:
  Installed: 0.84.3ubuntu1
  Candidate: 0.84.3ubuntu1
  Version table:
 *** 0.84.3ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status
peng@peng-ThinkPad-P51s:~$ 

UPDATE 2: it appears that it is caused by an unknown bug in gnome authentication agent, as I switched to XFCE and this problem never happens again, so now the problem becomes: how to get rid of the gnome authentication agent?

I'm trying to install cuda 10 on my ubuntu, I already have nvidia-cuda-toolkit 9.2 so this should be an upgrade

I download the installation self-extractor and execute it:

sudo ./cuda_10.0.130_410.48_linux.run 

However, when I finished all options, the following error was thrown.

ERROR: An NVIDIA kernel module 'nvidia-uvm' appears to already be loaded in your kernel.  This may be because it is in use (for example, by an X server, a CUDA program, or the NVIDIA Persistence Daemon), but this may also happen if your kernel was configured without support for module unloading.  Please be sure to exit any programs that may be using the GPU(s) before attempting to upgrade your driver.  If no GPU-based programs are running, you know that your kernel supports module unloading, and you still receive this message, then an error may have occured that has corrupted an NVIDIA kernel module's usage count, for which the simplest remedy is to reboot your computer.
ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.

This error has never been encountered when I installed nvidia-cuda-toolkit 9.2 (despite that nvidia driver is always used). Why the latest version is unable to handle such situation? Is the support of cuda 10 for ubuntu bad?

environment:

• ubuntu 18.04
• nvidia-driver-410
• nvidia-cuda-toolkit 9.2
• no bbswitch is used

Example:

$> tar -vxf something.tar
(normal output)
...

$> tar -xfv something.tar

tar: v: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

This is absurd, is it a bug or oversight in tar?

My touchpad can be detected as a USB device,

$ lsusb | grep touchpad
Bus 003 Device 003: ID 06cb:2970 Synaptics, Inc. touchpad

But when it is queried by xinput or libinput-list-devices, it has a strange device name:

$ xinput
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳     Touchpad                              id=11   [slave  pointer  (2)]
...

The tab prefix of Touchpad is preventing many touchpad configuration tools from finding it (e.g. KDE system settings). How do I manually correct it?