SebMa's questions

The ptex-jtex DEB package containing the multicol.sty LaTeX package has been removed from the multiverse : ptex-jtex.

EDIT0: I had already installed the texlive-latex-extra or texlive-latex-base packages.

Here is what I have and did :

$ dpkg -l | grep texlive-
ii  texlive-base                          2023.20240207-1                         all          TeX Live: Essential programs and files
ii  texlive-binaries                      2023.20230311.66589-9build3             amd64        Binaries for TeX Live
ii  texlive-fonts-recommended             2023.20240207-1                         all          TeX Live: Recommended fonts
ii  texlive-latex-base                    2023.20240207-1                         all          TeX Live: LaTeX fundamental packages
ii  texlive-latex-extra                   2023.20240207-1                         all          TeX Live: LaTeX additional packages
ii  texlive-latex-recommended             2023.20240207-1                         all          TeX Live: LaTeX recommended packages
ii  texlive-pictures                      2023.20240207-1                         all          TeX Live: Graphics, pictures, diagrams
ii  texlive-plain-generic                 2023.20240207-1                         all          TeX Live: Plain (La)TeX packages
$
$ tlmgr init-usertree
$ tlmgr update --list
(running on Debian, switching to user mode!)
(see /usr/share/doc/texlive-base/README.tlmgr-on-Debian.md)

tlmgr: Local TeX Live (2023) is older than remote repository (2024).
Cross release updates are only supported with
  update-tlmgr-latest(.sh/.exe) --update
See https://tug.org/texlive/upgrade.html for details.
$ tlmgr info multicol
(running on Debian, switching to user mode!)
(see /usr/share/doc/texlive-base/README.tlmgr-on-Debian.md)

tlmgr: Local TeX Live (2023) is older than remote repository (2024).
Cross release updates are only supported with
  update-tlmgr-latest(.sh/.exe) --update
See https://tug.org/texlive/upgrade.html for details.
$

How can I install a specific version of multicol.sty LaTeX package without updating/breaking the others LaTeX packages already installed from texlive-latex-* DEB packages ?

I've installed a 22.04 LTS Ubuntu Server as a minimal install and installed the following packages :

vim man-db manpages dialog bash-completion screen

Now when I run man ls, ubuntu is asking me to run the unminimize command although the man packages are already installed :

$ dpkg -l | egrep "man-db|manpages"
ii  isc-dhcp-common                       4.4.1-2.3ubuntu2.1                      amd64        common manpages relevant to all of the isc-dhcp packages
ii  man-db                                2.10.2-1                                amd64        tools for reading manual pages
ii  manpages                              5.10-1ubuntu1                           all          Manual pages about using a GNU/Linux system

And the directory /usr/share/man/man1 is empty :

$ ls /usr/share/man/man1
$ man -w ls
This system has been minimized by removing packages and content that are
not required on a system that users do not log into.

To restore this content, including manpages, you can run the 'unminimize'
command. You will still need to ensure the 'man-db' package is installed.

and mandb outputs :

$ sudo mandb
Purging old database entries in /usr/share/man...
Processing manual pages under /usr/share/man...
Purging old database entries in /usr/share/man/id...
Processing manual pages under /usr/share/man/id...
...
Processing manual pages under /usr/local/man...
mandb: can't update index cache /var/cache/man/oldlocal/8087: No such file or directory
0 man subdirectories contained newer manual pages.
0 manual pages were added.
0 stray cats were added.
0 old database entries were purged.
$

The strangest thing is this :

$ ls $(dpkg -L coreutils | grep man1/ls.1)
ls: cannot access '/usr/share/man/man1/ls.1.gz': No such file or directory

Found this :

$ dpkg -S bin/man
man-db: /usr/bin/manpath
local diversion from: /usr/bin/man
local diversion to: /usr/bin/man.REAL
man-db: /usr/bin/man
local diversion from: /usr/bin/man
local diversion to: /usr/bin/man.REAL
man-db: /usr/bin/mandb
man-db: /usr/bin/man-recode
$ head $(which man)
#!/bin/sh
echo "This system has been minimized by removing packages and content that are"
echo "not required on a system that users do not log into."
echo ""
echo "To restore this content, including manpages, you can run the 'unminimize'"
echo "command. You will still need to ensure the 'man-db' package is installed."
$ man.REAL -w ls
No manual entry for ls

How can this be solved without having to unminimize Ubuntu ?

I'm using Ubuntu 20.04 LTS.

I'm trying to get the mpv package from the https://non-gnu.uvt.nl/ repository to be chosen over that of the Launchpad ppa:mc3man/mpv-tests PPA repository, so far I did this :

$ cat /etc/apt/sources.list.d/mc3man-ubuntu-mpv-tests-focal.list
deb http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu focal main
$ cat /etc/apt/sources.list.d/mpv-non-gnu.uvt.nl.list
deb https://non-gnu.uvt.nl/debian focal uvt
$ egrep -v '^(#|$)' /etc/apt/preferences.d/mpv 
Package: mpv
Pin: origin non-gnu.uvt.nl
Pin-Priority: 991
$ apt policy mpv
mpv:
  Installed: 2:0.33.0~focal1
  Candidate: 2:0.33.0~focal1
  Version table:
 *** 2:0.33.0~focal1 500
        500 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
     0.34.1+fruit.2 991
        100 https://non-gnu.uvt.nl/debian focal/uvt amd64 Packages
     0.34.1+fruit.1 991
        100 https://non-gnu.uvt.nl/debian focal/uvt amd64 Packages
     0.34.0+fruit.1 991
        100 https://non-gnu.uvt.nl/debian focal/uvt amd64 Packages
     0.33.1+wsl.1 991
        100 https://non-gnu.uvt.nl/debian focal/uvt amd64 Packages
     0.33.0+wsl.1 991
        100 https://non-gnu.uvt.nl/debian focal/uvt amd64 Packages
     0.32.0-1ubuntu1 500
        500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

The priority was successfully changed from 100 to 991 but as you can notice on the apt policy mpv output, the chosen Candidate didn't change to 0.34.1+fruit.2.

How can I do that ?

After installing Ubuntu 20.04 LTS on my Asus EP1501P, I found out my SDCard reader was associated with /dev/sda instead of /dev/mmcblk0 and my main SSD with /dev/sdb :

$ sudo fdisk -l /dev/sd[ab]
Disk /dev/sda: 59,9 GiB, 64289243136 bytes, 125564928 sectors
Disk model: STORAGE DEVICE  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start       End   Sectors  Size Id Type
/dev/sda1       32768 125564927 125532160 59,9G  7 HPFS/NTFS/exFAT


Disk /dev/sdb: 465,78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3175f771

Device     Boot  Start       End   Sectors   Size Id Type
/dev/sdb1         2048    534527    532480   260M  b W95 FAT32
/dev/sdb2  *    534528 976773119 976238592 465,5G 8e Linux LVM
$ lsblk -pf /dev/sd[ab] | grep -v VG_Samsung | column -t
NAME         FSTYPE       LABEL                                   UUID       FSAVAIL  FSUSE%  MOUNTPOINT
/dev/sda
└─/dev/sda1  exfat        XXXX-YYYY
/dev/sdb
├─/dev/sdb1  vfat         FUTURE_EFI                              E81C-0DBA
└─/dev/sdb2  LVM2_member  xxxxxx-yyyy-zzzzz-xxxx-yyyy-zzzz-xxxxxx
$ sudo hdparm -I /dev/sda

/dev/sda:
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ATA device, with non-removable media
Standards:
    Likely used: 1
Configuration:
    Logical     max current
    cylinders   0   0
    heads       0   0
    sectors/track   0   0
    --
    Logical/Physical Sector size:           512 bytes
    device size with M = 1024*1024:           0 MBytes
    device size with M = 1000*1000:           0 MBytes 
    cache/buffer size  = unknown
Capabilities:
    IORDY not likely
    Cannot perform double-word IO
    R/W multiple sector transfer: not supported
    DMA: not supported
    PIO: pio0 
$ sudo hdparm -I /dev/sdb | sed "s/Serial Number:\s.*/Serial Number:      XXXXXXXXXXXXXXX/" | head 

/dev/sdb:

ATA device, with non-removable media
    Model Number:       Samsung SSD 870 EVO 500GB               
    Serial Number:      XXXXXXXXXXXXXXX
    Firmware Revision:  SVT01B6Q
    Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
    Used: unknown (minor revision code 0x005e) 

And when there is no SD Card inside the SD Card reader, I get these errors when updating grub configuration :

$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found linux image: /boot/vmlinuz-5.13.0-40-generic
Found initrd image: /boot/initrd.img-5.13.0-40-generic
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found linux image: /boot/vmlinuz-5.13.0-39-generic
Found initrd image: /boot/initrd.img-5.13.0-39-generic
Found linux image: /boot/vmlinuz-5.13.0-35-generic
Found initrd image: /boot/initrd.img-5.13.0-35-generic
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
done

EDIT0 : The SD Card reader is connected to the USB Bus instead of the PCI Bus :

$ lsusb | egrep -i "(sd|card).reader"
Bus 001 Device 005: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
$ lsusb -d 05e3:0727 -v | egrep -i "(sd|card).reader|idVendor|idProduct"
Couldn't open device, some information will be missing
Bus 001 Device 005: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
  idVendor           0x05e3 Genesys Logic, Inc.
  idProduct          0x0727 microSD Reader/Writer

How come the device connected to the USB controller appears before the device connected to the PCI controller (supposed to be faster than USB) ?

Is it possible to write an udev rule to assign /dev/sdb to this USB card reader and /dev/sda to my SSD so as to prevent os-prober errors (when calling update-grub) ?

EDIT1 : In the past, grub got installed onto the SDCard and my Ubuntu SSD disk could not boot without it.

So, to avoid confusion and future problems, I would love for my SDCard to be associated with a different device than /dev/sda

How do I switch the SSD back to /dev/sda and the SD Card reader to /dev/mmcblk0 ?

I'd like to know which groups are simple (non-admin) users member of by default.

Then I will script user group member ship like this :

for group in $simpleUserGroups
do
    groups $userName | grep -q $group || $sudo adduser $userName $group
done

So I went to the GUI of KUbuntu 20.04.3 LTS where the users are managed (kcmshell5 user_manager) after filling the fields (name, password, etc...), when I click on the Apply nothing happen (the system should open a popup prompting for the admin password) : see launchpad bug #1883357.

When I check if the user as been created I get :

$ id testUser
id: ‘testUser’: no such user

EDIT0 : You can reproduce this bug every time by doing the following :

$ ssh -X remote-PC
Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-89-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

68 updates can be applied immediately.
To see these additional updates run: apt list --upgradable

Web console: https://seb-x-y-z:9090/ or https://192.168.x.Y:9090/

Last login: Sun Nov  7 16:10:48 2021 from 127.0.0.1


.cache -> /tmp/sebastien/.cache/

dim. 07 nov. 2021 16:12:19 CET

$ kcmshell5 user_manager
Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use:
   QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen factors.
   QT_SCREEN_SCALE_FACTORS to set per-screen factors.
   QT_SCALE_FACTOR to set the application global scale factor.
Couldn't load plugin: "The shared library was not found."
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1938, resource id: 32072962, major code: 40 (TranslateCoords), minor code: 0

And then click "Apply", you will notice the sudo password window does not popup.

What groups do non-admin users belong to by default on KUbuntu ?

I'm using Ubuntu 20.04 LTS.

My snapd service is unavailable :

$ systemctl status snapd.service
● snapd.service - Snap Daemon
     Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
     Active: deactivating (stop-sigterm) (Result: timeout)
TriggeredBy: ● snapd.socket
   Main PID: 29952 (snapd)
      Tasks: 10 (limit: 8186)
     Memory: 12.8M
     CGroup: /system.slice/snapd.service
             └─29952 /usr/lib/snapd/snapd

Oct 27 00:47:07 seb-C70D-B-311 systemd[1]: Starting Snap Daemon...
Oct 27 00:47:07 seb-C70D-B-311 snapd[29952]: AppArmor status: apparmor is enabled and all features are available
Oct 27 00:47:07 seb-C70D-B-311 snapd[29952]: AppArmor status: apparmor is enabled and all features are available
Oct 27 00:48:37 seb-C70D-B-311 systemd[1]: snapd.service: start operation timed out. Terminating.
$ time snap version
snap    2.52.1
snapd   unavailable
series  -

real    0m25.075s
user    0m0.036s
sys 0m0.060s

My /var/lib/snapd filesystem is full :

$ df -PTh /var/lib/snapd
Filesystem                                                            Type  Size  Used Avail Use% Mounted on
/dev/mapper/VG_Samsung_SSD_860_EVO_1TB__S3Z9NB0K4019-LV_var_lib_snapd ext4  4.9G  4.9G     0 100% /var/lib/snapd
$ ls -lh /var/lib/snapd/snaps
total 4.0G
-rw------- 1 root root  68K Sep 10 23:08 acrordrdc_53.snap
-rw------- 1 root root  68K Sep 20 13:03 acrordrdc_62.snap
-rw------- 2 root root 4.0K Sep 26 12:44 bare_5.snap
-rw------- 1 root root 146M Oct 10 21:58 chromium_1781.snap
-rw------- 2 root root 145M Oct 23 12:29 chromium_1801.snap
-rw------- 1 root root  56M Jun 23 18:57 core18_2074.snap
-rw------- 1 root root  56M Aug 15 17:45 core18_2128.snap
-rw------- 1 root root  62M Jul 24 10:15 core20_1081.snap
-rw------- 1 root root  62M Oct  8 22:05 core20_1169.snap
-rw------- 1 root root 100M Oct 15 11:18 core_11798.snap
-rw------- 1 root root 100M Oct 21 12:26 core_11993.snap
-rw------- 2 root root 163M Dec 19  2020 gnome-3-28-1804_145.snap
-rw------- 1 root root 165M Jul  8 16:18 gnome-3-28-1804_161.snap
-rw------- 1 root root 219M Jan  9  2021 gnome-3-34-1804_66.snap
-rw------- 1 root root 219M Jun 14 14:23 gnome-3-34-1804_72.snap
-rw------- 1 root root  66M Apr 22  2021 gtk-common-themes_1515.snap
-rw------- 1 root root  66M Sep 26 12:44 gtk-common-themes_1519.snap
-rw------- 2 root root 140K Aug 23  2020 gtk2-common-themes_13.snap
drwxr-xr-x 2 root root 4.0K Jul 10  2020 partial/
-rw------- 1 root root  33M Oct 13 20:06 snapd_13270.snap
-rw------- 1 root root  33M Oct 20 21:14 snapd_13640.snap
-rw------- 1 root root 136M Aug 23 00:17 whatsapp-for-linux_26.snap
-rw------- 1 root root 112M Oct 18 15:58 whatsapp-for-linux_27.snap
-rw------- 2 root root 304M Feb  6  2021 wine-platform-5-stable_16.snap
-rw------- 1 root root 304M Sep 26 12:44 wine-platform-5-stable_18.snap
-rw------- 2 root root 323M Sep 20 13:03 wine-platform-6-stable_8.snap
-rw------- 1 root root 347M Oct  8 22:05 wine-platform-runtime_250.snap
-rw------- 1 root root 347M Oct 15 11:19 wine-platform-runtime_251.snap
-rw------- 1 root root 347M Oct 23 12:29 wine-platform-runtime_252.snap
-rw------- 1 root root 164M Oct 26 22:50 wine-platform-runtime_252.snap.partial

Howto can I free up space properly on my /var/lib/snapd filesystem when snapd is unavailable ?

EDIT0 : Cannot start the snapd service successfully, maybe because my /var/lib/snapd filesystem is full.

After a sudo apt upgrade, grub-install failed so I had to reboot on a Live Ubuntu 18.04 USB.

After mounting /proc, /dev, /dev/pts, /run, /sys, /sys/firmware/efi/efivars into /mnt/destinationVGDir/ I chroot to my ubuntu on /dev/sda and re-run grub-install :

ubuntu@ubuntu:~$ sudo chroot /mnt/destinationVGDir/
root@ubuntu:/# mount -a # Mounts all other filesystems including /boot/efi
root@ubuntu:/# grub-install 
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 18151: grub-install
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 18151: grub-install
Could not prepare Boot variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.

If do a grub-install -v, one can see that efibootmgr is the one failing here :

root@ubuntu:/# grub-install -v 2>&1 | uniq | tail
grub-install: info: copying `/usr/lib/shim/BOOTX64.CSV' -> `/boot/efi/EFI/ubuntu/BOOTX64.CSV'.
grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' -> `/boot/efi/EFI/ubuntu/grub.cfg'.
grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' -> `/boot/efi/EFI/Boot/bootx64.efi'.
grub-install: info: copying `/usr/lib/shim/fbx64.efi' -> `/boot/efi/EFI/Boot/fbx64.efi'.
grub-install: info: Registering with EFI: distributor = `ubuntu', path = `\EFI\ubuntu\shimx64.efi', ESP at hostdisk//dev/sda,gpt1.
grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
grub-install: info: executing modprobe -q efivars.
grub-install: info: executing efibootmgr -c -d /dev/sda -p 1 -w -L ubuntu -l \EFI\ubuntu\shimx64.efi.
Could not prepare Boot variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
root@ubuntu:/# efibootmgr -c -d /dev/sda -p 1 -w -L ubuntu -l \EFI\ubuntu\shimx64.efi
Could not prepare Boot variable: Invalid argument
root@ubuntu:/# efibootmgr -v -v -c -d /dev/sda -p 1 -w -L ubuntu -l \EFI\ubuntu\shimx64.efi
Could not prepare Boot variable: Invalid argument
error trace:
 efivarfs.c:351 efivarfs_set_variable(): write failed: Invalid argument
 lib.c:81 _efi_set_variable_mode(): ops->set_variable() failed: Invalid argument
 efibootmgr.c:323 make_var(): efi_set_variable failed: Invalid argument
 efibootmgr.c:333 make_var(): Could not set variable Boot0000: Invalid argument
root@ubuntu:/# 

My SSD is fine :

ubuntu@ubuntu:~$ sudo smartctl -A /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.4.0-42-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1947
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       673
177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       1
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   069   049   000    Old_age   Always       -       31
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       30
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       1179332232

EDIT0 : Here are the special filesystems I mounted prior to the chroot :

root@ubuntu:/# mount | grep -v ext4
proc on /proc type proc (rw,relatime)
tmpfs on /run type tmpfs (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=2947064k,nr_inodes=736766,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda1 on /boot/efi type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
root@ubuntu:/# 

EDIT1 : Thanks to @SamyAbdellatif, this error does not appear by adding --no-nvram option to the grub-install command :

root@ubuntu:~# grub-install --no-nvram 
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 6065: grub-install
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 6065: grub-install
Installation finished. No error reported.
root@ubuntu:~# 

Now If I re-install the grub-efi-amd64-signed to simulate an update, the --no-nvram option of grub-install is not used and the pb. re-appears :

root@ubuntu:~# apt install --reinstall grub-efi-amd64-signed
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  grub-efi-amd64-signed
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/300 kB of archives.
After this operation, 3459 kB of additional disk space will be used.
Selecting previously unselected package grub-efi-amd64-signed.
(Reading database ... 475217 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64-signed_1.93.22+2.02-2ubuntu8.20_amd64.deb ...
Unpacking grub-efi-amd64-signed (1.93.22+2.02-2ubuntu8.20) ...
Setting up grub-efi-amd64-signed (1.93.22+2.02-2ubuntu8.20) ...
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 6191: grub-install
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 6191: grub-install
Could not prepare Boot variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

EDIT2: When I rebooted, there was just a black screen. After re-checking with the Live USB, I can see no EFI boot entry for Ubuntu :

root@ubuntu:~# efibootmgr | grep -i ubuntu
root@ubuntu:~# 

EDIT3 : I removed the grub-efi-amd64-signed package because mokutil --sb-state says This system doesn't support Secure Boot and reinstalled grub-efi-amd64 :

root@ubuntu:~# apt install --reinstall -V grub-efi-amd64
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/47.9 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 475223 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64_2.02-2ubuntu8.20_amd64.deb ...
Unpacking grub-efi-amd64 (2.02-2ubuntu8.20) over (2.02-2ubuntu8.20) ...
Setting up grub-efi-amd64 (2.02-2ubuntu8.20) ...
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[189443]) leaked on vgs invocation. Parent PID 16137: grub-
install
File descriptor 5 (/dev/sda1) leaked on vgs invocation. Parent PID 16137: grub-inst
all
File descriptor 3 (pipe:[189443]) leaked on vgs invocation. Parent PID 16137: grub-
install
File descriptor 5 (/dev/sda1) leaked on vgs invocation. Parent PID 16137: grub-inst
all
Could not prepare Boot variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Input/output err
or.
Failed: grub-install --target=x86_64-efi --no-extra-removable 
WARNING: Bootloader is not properly installed, system may not be bootable
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-42-generic
Found initrd image: /boot/initrd.img-5.4.0-42-generic
Found linux image: /boot/vmlinuz-4.15.0-128-generic
Found initrd image: /boot/initrd.img-4.15.0-128-generic
Found linux image: /boot/vmlinuz-4.15.0-122-generic
Found initrd image: /boot/initrd.img-4.15.0-122-generic
done

There is still a WARNING: Bootloader is not properly installed, system may not be bootable error so I run grub-install manually with the --no-nvram option :

root@ubuntu:~# grub-install --no-nvram
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 20234: grub-install
File descriptor 4 (/dev/sda1) leaked on vgs invocation. Parent PID 20234: grub-install
Installation finished. No error reported

grub-install --no-nvram reports no error but does NOT create any ubuntu EFI boot entry :

root@ubuntu:~# efibootmgr | grep -i ubuntu
root@ubuntu:~# 

EDIT3.1 : grub-install --removable reports no error but does NOT create any ubuntu EFI boot entry either.

EDIT4 : My /etc/fstab :

root@ubuntu:~# grep -v ^# /etc/fstab
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/rootFS /               ext4    errors=remount-ro 0       1
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/boot /boot           ext4    defaults,noatime        0       2
UUID=9ADF-05E5  /boot/efi       vfat    defaults,noatime        0       1
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/home /home           ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/opt /opt            ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/tmp /tmp            ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/usr /usr            ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/usr_local /usr/local      ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/var /var            ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/var_cache /var/cache      ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/var_lib_snapd /var/lib/snapd           ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/var_mail /var/mail      ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/var_tmp /var/tmp        ext4    defaults,noatime        0       2
/dev/VG_ALL_Samsung_SSD_850_EVO_500GB/photos /photos        ext4    defaults,noatime        0       2
root@ubuntu:~# 

And the output of lsblk :

root@ubuntu:~# lsblk 
NAME                                               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0                                                7:0    0     2G  1 loop 
loop1                                                7:1    0  29.9M  1 loop 
loop2                                                7:2    0    55M  1 loop 
loop3                                                7:3    0 255.6M  1 loop 
loop4                                                7:4    0  62.1M  1 loop 
loop5                                                7:5    0  49.8M  1 loop 
sda                                                  8:0    0 465.8G  0 disk 
├─sda1                                               8:1    0   256M  0 part /boot/efi
└─sda2                                               8:2    0 465.5G  0 part 
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-boot          253:0    0     1G  0 lvm  /boot
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-opt           253:1    0     7G  0 lvm  /opt
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-rootFS        253:2    0     2G  0 lvm  /
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-var_lib_snapd 253:3    0    10G  0 lvm  /var/lib/snapd
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-tmp           253:4    0    10G  0 lvm  /tmp
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-usr_local     253:5    0     7G  0 lvm  /usr/local
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-usr           253:6    0    20G  0 lvm  /usr
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-var_cache     253:7    0     5G  0 lvm  /var/cache
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-var_mail      253:8    0    20G  0 lvm  /var/mail
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-var_tmp       253:9    0     2G  0 lvm  /var/tmp
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-var           253:10   0     6G  0 lvm  /var
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-VMs           253:11   0  75.5G  0 lvm  
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-.q            253:12   0    90G  0 lvm  
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-home          253:13   0   100G  0 lvm  /home
  ├─VG_ALL_Samsung_SSD_850_EVO_500GB-datas         253:14   0    60G  0 lvm  
  └─VG_ALL_Samsung_SSD_850_EVO_500GB-photos        253:15   0    50G  0 lvm  
sdc                                                  8:32   1  28.9G  0 disk 
├─sdc1                                               8:33   1  28.9G  0 part 
│ └─ventoy                                         253:16   0   2.6G  1 dm   
└─sdc2                                               8:34   1    32M  0 part 
sr0                                                 11:0    1  1024M  0 rom  
root@ubuntu:~# 

To re-install grub on my system, do I need to use a newer grub2-common package or a newer efibootmgr package ?

I have a list of packages and I want to know which packages are not available in the ubuntu repositories.

I type this command but it returns nothing :

$ apt-cache show vim TotO perl 2>&1 | grep "Unable to locate package"
$

It occurs in both Ubuntu 16.04 LTS and 18.04 LTS.

Can you help ?

I have some filesystem loops on my HDD :

$ time for dir in $(df -T | awk "/ext[234]|btrfs/"'{print$NF}' | egrep -vw "/home|/tmp")
do
    sudo /usr/bin/find $dir -xdev -follow -printf ""
done

/usr/bin/find: File system loop detected; ‘/lib/recovery-mode/recovery-mode’ is part of the same file system loop as ‘/lib/recovery-mode’.
/usr/bin/find: File system loop detected; ‘/usr/bin/X11’ is part of the same file system loop as ‘/usr/bin’.
/usr/bin/find: File system loop detected; ‘/usr/share/arduino/hardware/tools/avr/bin/X11’ is part of the same file system loop as ‘/usr/share/arduino/hardware/tools/avr/bin’.

real    0m4.162s
user    0m0.808s
sys     0m3.260s

Is it safe to remove those filesystem loops ?

I'm trying to list all packages (and their respective repositories) from other sources than the main/restricted/universe/multiverse.

First I've typed that command to list those packages :

$ aptitude search -F '%p' '!?origin(Ubuntu) ( ?architecture(amd64) | ?architecture(all) ) ?installed' | head
albert                                                                          
brave-browser                                                                   
brave-keyring                                                                   
browsh                                                                          
cdda2wav                                                                        
cdrecord                                                                        
dockmanager                                                                     
e2fsprogs-l10n                                                                  
ffmbc                                                                           
firefox-esr                                                                     

But if I add '%e' or '%E' or '%O' to the -F argument, the aptitude immediately returns ... nothing :

$ aptitude search -F '%p %O' '!?origin(Ubuntu) ( ?architecture(amd64) | ?architecture(all) ) ?installed' | head
$

Is this an aptitude bug ?

Each time I go to about:support and click on "Open Directory", Firefox opens it with SMPlayer and then mpv/mplayer complains about :

  Playing: /home/sebastien/.mozilla/firefox-esr/empty6/persdict.dat
Failed to recognize file format.
Exiting... (Errors when loading file)

So I've searched "smplayer" in about:preferences#applications but couldn't find it.

I've also searched for "smplayer" in about:config but couldn't find it either.

And finally I've searched in the XDG mimes types definitions :

$ xdg-mime query filetype ~/.mozilla/firefox-esr/empty6/persdict.dat
text/plain
$ xdg-mime query default text/plain
kate.desktop
$ xdg-mime query filetype ~/
inode/directory
$ xdg-mime query default inode/directory
dolphin.desktop

EDIT 0 : Adding a few xdg-open commands :

$ xdg-open ~/.mozilla/firefox-esr/empty6/persdict.dat
Fontconfig warning: ignoring C.UTF-8: not a valid language tag
$ pgrep -af /persdict.dat
32659 /usr/bin/kate -b /home/sebastien/.mozilla/firefox-esr/empty6/persdict.dat
$ xdg-open Documents
Fontconfig warning: ignoring C.UTF-8: not a valid language tag
$ pgrep -af /Documents
8437 /usr/bin/dolphin --icon system-file-manager -caption Dolphin /home/sebastien/Documents

EDIT 1 : inode/directory= entry in ~/.local/share/applications/mimeapps.list :

$ grep inode/directory= ~/.local/share/applications/mimeapps.list
inode/directory=dolphin.desktop;smplayer.desktop;kde4-dolphin.desktop;vlc.desktop;caja-2.desktop;kde4-kfmclient_dir.desktop;kde4-gwenview.desktop;easytag.desktop;nemo.desktop;audacious-qt.desktop;Thunar-folder-handler.desktop;qmmp_cue.desktop;audacious.desktop;kde4-k4dirstat.desktop;pcmanfm.desktop;qmmp_dir.desktop;qmmp_enqueue.desktop;
inode/directory=dolphin.desktop

EDIT 2 : The Dolphin application launcher is not found by Firefox because it's in the kde4 subfolder of /usr/share/applications/ :

$ locate /dolphin.desktop
/usr/share/applications/kde4/dolphin.desktop

Explanation : Firefox couldn't find dolphin.desktop in /usr/share/applications/, therefore it was using the next entry for inode/directory mimetype in ~/.local/share/applications/mimeapps.list file which was smplayer.desktop :

$ grep inode/directory= ~/.local/share/applications/mimeapps.list
inode/directory=dolphin.desktop;smplayer.desktop;kde4-dolphin.desktop;vlc.desktop;caja-2.desktop;kde4-kfmclient_dir.desktop;kde4-gwenview.desktop;easytag.desktop;nemo.desktop;audacious-qt.desktop;Thunar-folder-handler.desktop;qmmp_cue.desktop;audacious.desktop;kde4-k4dirstat.desktop;pcmanfm.desktop;qmmp_dir.desktop;qmmp_enqueue.desktop;
inode/directory=dolphin.desktop

Solution : Thanks to ashvatthama's anwser : To solve this pb., you can type this command :

xdg-mime default kde4-dolphin.desktop inode/directory

and now it works fine :

$ pgrep -af /empty6
29083 dolphin --icon system-file-manager -caption Dolphin /home/sebastien/.mozilla/firefox-esr/empty6

I've seen this bug for years, I'd love to solve it.

Can you help me ?

The python3-pychromecast source package does not exist from Ubuntu Xenial official Ubuntu repositories.

I want to download the Ubuntu Bionic python3-pychromecast source package and rebuild it on Ubuntu Xenial :

$ sudo apt-get build-dep python3-pychromecast/bionic-universe
Reading package lists... Done
E: Unable to find a source package for python3-pychromecast/bionic-universe
$ apt-get source --compile python3-pychromecast/bionic-universe
Reading package lists... Done
E: Unable to find a source package for python3-pychromecast

EDIT0 : Downloaded and extracted the source package :

$ wget http://archive.ubuntu.com/ubuntu/pool/universe/p/pychromecast/pychromecast_0.8.1-1.dsc http://archive.ubuntu.com/ubuntu/pool/universe/p/pychromecast/pychromecast_0.8.1.orig.tar.gz http://archive.ubuntu.com/ubuntu/pool/universe/p/pychromecast/pychromecast_0.8.1-1.debian.tar.xz 
--2020-05-27 11:50:58--  http://archive.ubuntu.com/ubuntu/pool/universe/p/pychromecast/pychromecast_0.8.1-1.dsc
Resolving archive.ubuntu.com (archive.ubuntu.com)... 2001:67c:1360:8001::23, 2001:67c:1360:8001::24, 2001:67c:1562::15, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|2001:67c:1360:8001::23|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2205 (2,2K)
Saving to: ‘pychromecast_0.8.1-1.dsc’

pychromecast_0.8.1-1.dsc      100%[=================================================>]   2,15K  --.-KB/s    in 0,001s  

2020-05-27 11:50:58 (3,24 MB/s) - ‘pychromecast_0.8.1-1.dsc’ saved [2205/2205]

--2020-05-27 11:50:58--  http://archive.ubuntu.com/ubuntu/pool/universe/p/pychromecast/pychromecast_0.8.1.orig.tar.gz
Reusing existing connection to [archive.ubuntu.com]:80.
HTTP request sent, awaiting response... 200 OK
Length: 37130 (36K) [application/x-gzip]
Saving to: ‘pychromecast_0.8.1.orig.tar.gz’

pychromecast_0.8.1.orig.tar.g 100%[=================================================>]  36,26K  --.-KB/s    in 0,03s   

2020-05-27 11:50:58 (1,37 MB/s) - ‘pychromecast_0.8.1.orig.tar.gz’ saved [37130/37130]

--2020-05-27 11:50:58--  http://archive.ubuntu.com/ubuntu/pool/universe/p/pychromecast/pychromecast_0.8.1-1.debian.tar.xz
Reusing existing connection to [archive.ubuntu.com]:80.
HTTP request sent, awaiting response... 200 OK
Length: 3208 (3,1K) [application/x-xz]
Saving to: ‘pychromecast_0.8.1-1.debian.tar.xz’

pychromecast_0.8.1-1.debian.t 100%[=================================================>]   3,13K  --.-KB/s    in 0s      

2020-05-27 11:50:58 (50,8 MB/s) - ‘pychromecast_0.8.1-1.debian.tar.xz’ saved [3208/3208]

FINISHED --2020-05-27 11:50:58--
Total wall clock time: 0,2s
Downloaded: 3 files, 42K in 0,03s (1,53 MB/s)
$ dpkg-source -x pychromecast_0.8.1-1.dsc 
dpkg-source: info: extracting pychromecast in pychromecast-0.8.1
dpkg-source: info: unpacking pychromecast_0.8.1.orig.tar.gz
dpkg-source: info: unpacking pychromecast_0.8.1-1.debian.tar.xz

EDIT1 : Trying to build :

$ debuild -i -us -uc -b
 dpkg-buildpackage -rfakeroot -D -us -uc -i -b
dpkg-buildpackage: source package pychromecast
dpkg-buildpackage: source version 0.8.1-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Ruben Undheim <[email protected]>
 dpkg-source -i --before-build pychromecast-0.8.1
dpkg-buildpackage: host architecture i386
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-protobuf
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc -i -b failed
$ dpkg-checkbuilddeps
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-protobuf
$ grep python3-protobuf debian/control 
               python3-protobuf,
Depends: ${python3:Depends}, ${misc:Depends}, python3-zeroconf, python3-protobuf (>= 3)

Can you help me ?

The bluetooth service cannot not restart properly :

$ sudo service bluetooth restart;service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since jeu. 2020-02-27 11:18:05 CET; 398ms ago
     Docs: man:bluetoothd(8)
 Main PID: 18310 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─18310 /usr/lib/bluetooth/bluetoothd

févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: gatt-time-server: Input/output error (5)
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Not enough free handles to register service
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Not enough free handles to register service
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Sap driver initialization failed.
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: sap-server: Operation not permitted (1)
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSource
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSink
févr. 27 11:18:05 sebastien-B206 bluetoothd[18310]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)

It needs to be done in two steps (see the last line of the status) :

$ sudo service bluetooth stop;sudo service bluetooth start;service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since jeu. 2020-02-27 11:20:12 CET; 2s ago
     Docs: man:bluetoothd(8)
 Main PID: 18390 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─18390 /usr/lib/bluetooth/bluetoothd

févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Not enough free handles to register service
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Not enough free handles to register service
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Sap driver initialization failed.
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: sap-server: Operation not permitted (1)
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSource
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSink
févr. 27 11:20:12 sebastien-B206 bluetoothd[18390]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
févr. 27 11:20:15 sebastien-B206 systemd[1]: Started Bluetooth service.

I tried adding the RestartSec=5 parameter in the [Service] section of /lib/systemd/system/bluetooth.service (man systemd.service) but it didn't work :

$ sudo systemctl edit --full bluetooth
$ systemctl cat bluetooth | grep RestartSec
RestartSec=5
$ sudo systemctl daemon-reload
$ sudo service bluetooth restart;service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since jeu. 2020-02-27 11:30:28 CET; 524ms ago
     Docs: man:bluetoothd(8)
 Main PID: 18830 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─18830 /usr/lib/bluetooth/bluetoothd

févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: gatt-time-server: Input/output error (5)
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Not enough free handles to register service
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Not enough free handles to register service
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Sap driver initialization failed.
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: sap-server: Operation not permitted (1)
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSource
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSink
févr. 27 11:30:28 sebastien-B206 bluetoothd[18830]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)

Here is my bluetooth.service configuration :

$ systemctl cat bluetooth
# /lib/systemd/system/bluetooth.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
RestartSec=5

[Install]
WantedBy=bluetooth.target,suspend.target
Alias=dbus-org.bluez.service

EDIT0 : Just rebooted then :

$ sudo systemctl restart bluetooth
$ systemctl status -n 20 bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/etc/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since jeu. 2020-02-27 17:23:24 CET; 2min 42s ago
     Docs: man:bluetoothd(8)
 Main PID: 5050 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─5050 /usr/lib/bluetooth/bluetoothd

févr. 27 17:23:24 sebastien-B206 systemd[1]: Started Bluetooth service.
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Starting SDP server
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Bluetooth management interface 1.10 initialized
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Failed to obtain handles for "Service Changed" characteristic
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Not enough free handles to register service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Error adding Link Loss service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Not enough free handles to register service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Not enough free handles to register service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Not enough free handles to register service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Current Time Service could not be registered
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: gatt-time-server: Input/output error (5)
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Not enough free handles to register service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Not enough free handles to register service
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Sap driver initialization failed.
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: sap-server: Operation not permitted (1)
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Endpoint registered: sender=:1.65 path=/MediaEndpoint/A2DPSource
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Endpoint registered: sender=:1.65 path=/MediaEndpoint/A2DPSink
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink
févr. 27 17:23:25 sebastien-B206 bluetoothd[5050]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)

EDIT1 : rfkill list output :

$ rfkill list
0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

EDIT2 : Tried this but it didn't solve the RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) pb.

CONCLUSION : I added the --noplugin=sap option to the ExecStart= command line from a solution proposed by @6666 and it solved my restart pb. Still have the other errors but bluetooth is working fine after each bluetooth service restart so who cares about them :-)

Lightdm automatically logs in my user on Ubuntu Xenial when I log out from XFCE on Ubuntu Xenial.

I have no /etc/lightdm/lightdm.conf file and don't belong to the nopasswdlogin group either :

$ ls /etc/lightdm/lightdm.conf
ls: cannot access '/etc/lightdm/lightdm.conf': No such file or directory
$ groups | grep nopasswdlogin
$

EDIT0: My default DM :

$ cat /etc/X11/default-display-manager
/usr/sbin/lightdm

EDIT1 : I have /etc/lightdm/lightdm.conf.d/10-xubuntu.conf :

$ cat /etc/lightdm/lightdm.conf.d/10-xubuntu.conf
[SeatDefaults]
user-session=xubuntu

EDIT2: Here's what I have in the lightdm.service journal :

$ journalctl -au lightdm -S "2020-01-29 1:59"
-- Logs begin at lun. 2020-01-27 11:14:43 CET, end at mer. 2020-01-29 02:01:47 CET. --
janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Failed to write utmpx: Permission denied
janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Error writing to daemon: Bad file descriptor
janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Error writing to daemon: Bad file descriptor
janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Error writing to daemon: Bad file descriptor
janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Failed to write utmpx: Permission denied

EDIT3: So I've just restarted the lightdm.service :

$ sudo service lightdm restart
$ service lightdm status
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-01-29 02:09:37 CET; 13s ago
     Docs: man:lightdm(1)
  Process: 15476 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS)
 Main PID: 15480 (lightdm)
   CGroup: /system.slice/lightdm.service
           ├─15480 /usr/sbin/lightdm
           ├─15490 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
           └─15618 lightdm --session-child 12 19

Jan 29 02:09:37 sebastien-B206 systemd[1]: Starting Light Display Manager...
Jan 29 02:09:37 sebastien-B206 systemd[1]: Started Light Display Manager.
Jan 29 02:09:38 sebastien-B206 lightdm[15522]: pam_kwallet(lightdm-greeter:setcred): (null): pam_sm_setcred
Jan 29 02:09:38 sebastien-B206 lightdm[15522]: pam_kwallet5(lightdm-greeter:setcred): (null): pam_sm_setcred
Jan 29 02:09:38 sebastien-B206 lightdm[15522]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jan 29 02:09:42 sebastien-B206 lightdm[15618]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "sebastien"

Can you help me disable autologin ?

The command iw dev does not show the wifi dongle, neither does rfkill list but iwconfig does :

$ iw dev
$ echo $?
0
$ rfkill list all
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
$ iwconfig 2>/dev/null
wlx0      unassociated  Nickname:"rtl_wifi"
          Mode:Managed  Access Point: Not-Associated   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If iwconfig can "see" the Wi-Fi dongle, I assume there no need to rebuild the r8712u driver.

Here is some more information about this dongle :

$ lsusb -s 1:19 
Bus 001 Device 019: ID 06f8:e031 Guillemot Corp. Hercules HWNUm-300 Wireless N mini [Realtek RTL8191SU]
$ lsusb -t | grep Dev.19
    |__ Port 1: Dev 19, If 0, Class=Vendor Specific Class, Driver=r8712u, 480M
$ inxi -Nxx
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK P8P67 and other motherboards 
           driver: r8169 v: 2.3LK-NAPI port: e800 bus ID: 03:00.0 chip ID: 10ec:8168 
           Device-2: Guillemot Hercules HWNUm-300 Wireless N mini [Realtek RTL8191SU] type: USB driver: r8712u bus ID: 1-1:19 
           chip ID: 06f8:e031 

The wireless-tools and iw packages are already installed :

$ dpkg -l wireless-tools iw
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                     Version           Architecture      Description
+++-========================-=================-=================-======================================================
ii  iw                       3.17-1            amd64             tool for configuring Linux wireless devices
ii  wireless-tools           30~pre9-8ubuntu1  amd64             Tools for manipulating Linux Wireless Extensions

I'm using Ubuntu 16.04.6 LTS by the way :-)

I cannot rebuilt the /etc/apt/trusted.gpg keyring properly :

$ sudo rm /etc/apt/trusted.gpg
rm: remove regular file ‘/etc/apt/trusted.gpg’? y
$ sudo apt-key update 2>&1 | egrep "gpg:.*(invalid|failed)"
gpg: [don't know]: invalid packet (ctb=01)
gpg: keydb_get_keyblock failed: eof
gpg: [don't know]: invalid packet (ctb=01)
gpg: keydb_get_keyblock failed: eof
gpg: [don't know]: invalid packet (ctb=01)
gpg: keydb_get_keyblock failed: eof
gpg: [don't know]: invalid packet (ctb=01)
gpg: keydb_get_keyblock failed: eof
$ apt-key list >/dev/null
gpg: [don't know]: invalid packet (ctb=01)
gpg: keydb_search_next failed: invalid packet

EDIT 1 : I found this pb. was related to the keyrings in /etc/apt/trusted.gpg.d/, so I recreated them with add-apt-repository :

$ sudo mv /etc/apt/trusted.gpg.d /etc/apt/trusted.gpg.d.BACKUP
$ sudo mkdir /etc/apt/trusted.gpg.d
$ time awk -F / '/^deb .*ppa.launchpad.net/{print "sudo add-apt-repository -y ppa:"$4"/"$5}' /etc/apt/sources.list.d/*.list | sh -x
+ sudo add-apt-repository -y ppa:aims/sagemath
gpg: keyring `/tmp/tmpv9cab2oz/secring.gpg' created
gpg: keyring `/tmp/tmpv9cab2oz/pubring.gpg' created
gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpv9cab2oz/trustdb.gpg: trustdb created
gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
+ sudo add-apt-repository -y ppa:apandada1/brightness-controller
gpg: keyring `/tmp/tmp74ndc3fv/secring.gpg' created
gpg: keyring `/tmp/tmp74ndc3fv/pubring.gpg' created
gpg: requesting key A7803E3B from hkp server keyserver.ubuntu.com
gpg: /tmp/tmp74ndc3fv/trustdb.gpg: trustdb created
gpg: key A7803E3B: public key "Launchpad PPA for Archisman Panigrahi" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
...
gpg: /tmp/tmp49wcgvjj/trustdb.gpg: trustdb created
gpg: key EEAD66BD: public key "Launchpad PPA for Xu Zhen" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK

real    6m20.794s
user    5m49.528s
sys 0m17.888s
$ apt-key list >/dev/null
gpg: keyblock resource `/etc/apt/trusted.gpg.d/notepadqq-team-notepadqq.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/nowrep-qupzilla.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/octave-stable.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/openlp-core-release.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/otto-kesselgulasch-gimp.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/pinta-maintainers-pinta-stable.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/pmjdebruijn-gnoduino-release.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/privoox-privoox.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/pypy-ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/rvm-smplayer.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/sbates-ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/skunk-pepper-flash.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/smathot-cogscinl.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/stebbins-handbrake-releases.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/stefanobalocco-multimedia.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/team-xbmc-ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/timchen119-bluez5-trusty.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/ubuntu-mate-dev-ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/ubuntu-mate-dev-trusty-mate.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/ubuntu-toolchain-r-test.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/ufleisch-kid3.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/unit193-inxi.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/wseverin-ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/xuzhen666-gnome-mpv.gpg': resource limit

After some digging, I found that GnuPG v1 (which a dependency of the Ubuntu Trust APT packet) cannot handle more than 40 keyrings, that it so say, it cannot handle more than 39 keyrings in /etc/apt/trusted.gpg.d/ (according to this : https://askubuntu.com/a/508337/426176 and that : https://www.mail-archive.com/[email protected]/msg23302.html)

EDIT 2 : I have removed 10 duplicate keys in /etc/apt/trusted.gpg.d/ :

$ sudo fdupes -rnASd /etc/apt/trusted.gpg.d
[1] /etc/apt/trusted.gpg.d/guardianproject-fdroidserver.gpg  
[2] /etc/apt/trusted.gpg.d/guardianproject-ppa.gpg

Set 1 of 6, preserve files [1 - 2, all] (916 bytes each): 2

   [-] /etc/apt/trusted.gpg.d/guardianproject-fdroidserver.gpg
   [+] /etc/apt/trusted.gpg.d/guardianproject-ppa.gpg

[1] /etc/apt/trusted.gpg.d/jonathonf-ffmpeg-3.gpg
[2] /etc/apt/trusted.gpg.d/jonathonf-ffmpeg-4.gpg
[3] /etc/apt/trusted.gpg.d/jonathonf-texlive.gpg
[4] /etc/apt/trusted.gpg.d/jonathonf-vim.gpg
[5] /etc/apt/trusted.gpg.d/jonathonf-vlc.gpg

Set 2 of 6, preserve files [1 - 5, all] (1135 bytes each): 2

   [-] /etc/apt/trusted.gpg.d/jonathonf-ffmpeg-3.gpg
   [+] /etc/apt/trusted.gpg.d/jonathonf-ffmpeg-4.gpg
   [-] /etc/apt/trusted.gpg.d/jonathonf-texlive.gpg
   [-] /etc/apt/trusted.gpg.d/jonathonf-vim.gpg
   [-] /etc/apt/trusted.gpg.d/jonathonf-vlc.gpg

[1] /etc/apt/trusted.gpg.d/noobslab-apps.gpg
[2] /etc/apt/trusted.gpg.d/noobslab-mint.gpg
[3] /etc/apt/trusted.gpg.d/noobslab-themes.gpg

Set 3 of 6, preserve files [1 - 3, all] (943 bytes each): 2

   [-] /etc/apt/trusted.gpg.d/noobslab-apps.gpg
   [+] /etc/apt/trusted.gpg.d/noobslab-mint.gpg
   [-] /etc/apt/trusted.gpg.d/noobslab-themes.gpg

[1] /etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg
[2] /etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg

Set 4 of 6, preserve files [1 - 2, all] (6570 bytes each): 1

   [+] /etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg
   [-] /etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg

[1] /etc/apt/trusted.gpg.d/ubuntu-mate-dev-ppa.gpg
[2] /etc/apt/trusted.gpg.d/ubuntu-mate-dev-trusty-mate.gpg

Set 5 of 6, preserve files [1 - 2, all] (1313 bytes each): 2

   [-] /etc/apt/trusted.gpg.d/ubuntu-mate-dev-ppa.gpg
   [+] /etc/apt/trusted.gpg.d/ubuntu-mate-dev-trusty-mate.gpg

[1] /etc/apt/trusted.gpg.d/mc3man-mpv-tests.gpg
[2] /etc/apt/trusted.gpg.d/mc3man-trusty-media.gpg

Set 6 of 6, preserve files [1 - 2, all] (527 bytes each): 2

   [-] /etc/apt/trusted.gpg.d/mc3man-mpv-tests.gpg
   [+] /etc/apt/trusted.gpg.d/mc3man-trusty-media.gpg

Is adding all my gpg launchpad ppa keys in the same /etc/apt/trusted.gpg keyring the only solution, it seems a little less ordered ?

EDIT 3 : Now I have 16 extra (rejected) keys in /etc/apt/trusted.gpg.d/, so I'm gonna move them to the /etc/apt/trusted.gpg keyring :

$ apt-key list 2>&1 >/dev/null | awk -F"[\`']" '/resource limit/{print "sudo apt-key add "$2" 2>/dev/null ; sudo \\rm -vf "$2}' | sh -x
+ sudo apt-key add /etc/apt/trusted.gpg.d/pypy-ppa.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/pypy-ppa.gpg
removed ‘/etc/apt/trusted.gpg.d/pypy-ppa.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/rvm-smplayer.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/rvm-smplayer.gpg
removed ‘/etc/apt/trusted.gpg.d/rvm-smplayer.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/sbates-ppa.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/sbates-ppa.gpg
removed ‘/etc/apt/trusted.gpg.d/sbates-ppa.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/skunk-pepper-flash.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/skunk-pepper-flash.gpg
removed ‘/etc/apt/trusted.gpg.d/skunk-pepper-flash.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/smathot-cogscinl.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/smathot-cogscinl.gpg
removed ‘/etc/apt/trusted.gpg.d/smathot-cogscinl.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/stebbins-handbrake-releases.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/stebbins-handbrake-releases.gpg
removed ‘/etc/apt/trusted.gpg.d/stebbins-handbrake-releases.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/stefanobalocco-multimedia.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/stefanobalocco-multimedia.gpg
removed ‘/etc/apt/trusted.gpg.d/stefanobalocco-multimedia.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/team-xbmc-ppa.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/team-xbmc-ppa.gpg
removed ‘/etc/apt/trusted.gpg.d/team-xbmc-ppa.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/timchen119-bluez5-trusty.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/timchen119-bluez5-trusty.gpg
removed ‘/etc/apt/trusted.gpg.d/timchen119-bluez5-trusty.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/ubuntu-mate-dev-trusty-mate.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/ubuntu-mate-dev-trusty-mate.gpg
removed ‘/etc/apt/trusted.gpg.d/ubuntu-mate-dev-trusty-mate.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/ubuntu-toolchain-r-test.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/ubuntu-toolchain-r-test.gpg
removed ‘/etc/apt/trusted.gpg.d/ubuntu-toolchain-r-test.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/ufleisch-kid3.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/ufleisch-kid3.gpg
removed ‘/etc/apt/trusted.gpg.d/ufleisch-kid3.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/unit193-inxi.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/unit193-inxi.gpg
removed ‘/etc/apt/trusted.gpg.d/unit193-inxi.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg
removed ‘/etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/wseverin-ppa.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/wseverin-ppa.gpg
removed ‘/etc/apt/trusted.gpg.d/wseverin-ppa.gpg’
+ sudo apt-key add /etc/apt/trusted.gpg.d/xuzhen666-gnome-mpv.gpg
+ sudo rm -vf /etc/apt/trusted.gpg.d/xuzhen666-gnome-mpv.gpg
removed ‘/etc/apt/trusted.gpg.d/xuzhen666-gnome-mpv.gpg’
$ apt-key list >/dev/null
$

Problem fixed.

Trying to fix a problem with my keys on Ubuntu Trusty :

$ apt-key list >/dev/null
gpg: [don't know]: invalid packet (ctb=2d)
gpg: keydb_search_next failed: invalid packet

So I have backed up my keys from PPA repos into /etc/apt/trusted.gpg.d.BACKUP/ :

$ sudo mv /etc/apt/trusted.gpg.d /etc/apt/trusted.gpg.d.BACKUP
$ apt-key list | grep gpg$
/etc/apt/trusted.gpg

And then I imported the keys back to GPG :

$ sudo mkdir /etc/apt/trusted.gpg.d/
$ for file in $(\ls /etc/apt/trusted.gpg.d.BACKUP/ | grep gpg$) 
> do
>   sudo gpg --no-default-keyring --keyring /etc/apt/trusted.gpg.d/$file --import /etc/apt/trusted.gpg.d.BACKUP/$file
> done
gpg: keyring `/etc/apt/trusted.gpg.d/andykimpe-gparted.gpg' created
gpg: key 274A7DA0: public key "Launchpad PPA for andykimpe" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
...
gpg: keyring `/etc/apt/trusted.gpg.d/openlp-core-release.gpg' created
gpg: key DF629112: public key "Launchpad Development Packages" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
$

And when I check, I still have the same :

$ apt-key list | grep gpg$
/etc/apt/trusted.gpg

It is as if nothing had been imported.

Can you help ?

The file /etc/locale.gen does not exist on my Ubuntu 14.04 LTS, how can I add a new locale the right way ?

I'm using bluez v5.46 on Ubuntu 17.10 and I cannot connect to a paired bluetooth device.

Here is the output of the bluetoothctl command :

$ bluetoothctl 
[NEW] Controller 6C:0B:84:27:43:66 tensorFlowPHY [default]
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 6C:0B:84:27:43:66 Discovering: yes
[NEW] Device FC:58:FA:A1:C2:70 OE-P51
[bluetooth]# pair FC:58:FA:A1:C2:70 
Attempting to pair with FC:58:FA:A1:C2:70
[CHG] Device FC:58:FA:A1:C2:70 Connected: yes
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 ServicesResolved: yes
[CHG] Device FC:58:FA:A1:C2:70 Paired: yes
Pairing successful
[CHG] Device FC:58:FA:A1:C2:70 ServicesResolved: no
[CHG] Device FC:58:FA:A1:C2:70 Connected: no
[CHG] Controller 6C:0B:84:27:43:66 Discoverable: no
[bluetooth]# connect FC:58:FA:A1:C2:70 
Attempting to connect to FC:58:FA:A1:C2:70
Failed to connect: org.bluez.Error.Failed

Here is a little bit more info :

$ journalctl -u bluetooth | tail
Mar 29 12:06:01 tensorFlowPHY systemd[1]: Started Bluetooth service.
Mar 29 12:06:01 tensorFlowPHY bluetoothd[1136]: Starting SDP server
Mar 29 12:06:01 tensorFlowPHY bluetoothd[1136]: Bluetooth management interface 1.14 initialized
Mar 29 14:36:12 tensorFlowPHY bluetoothd[1136]: a2dp-sink profile connect failed for FC:58:FA:A1:C2:70: Protocol not available
Mar 29 14:36:59 tensorFlowPHY bluetoothd[1136]: a2dp-sink profile connect failed for FC:58:FA:A1:C2:70: Protocol not available

And systemctl says :

$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-03-30 16:30:15 CEST; 21s ago
     Docs: man:bluetoothd(8)
 Main PID: 1492 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 1.5M
      CPU: 42ms
   CGroup: /system.slice/bluetooth.service
           └─1492 /usr/lib/bluetooth/bluetoothd

Mar 30 16:30:15 tensorFlowPHY systemd[1]: Starting Bluetooth service...
Mar 30 16:30:15 tensorFlowPHY bluetoothd[1492]: Bluetooth daemon 5.46
Mar 30 16:30:15 tensorFlowPHY systemd[1]: Started Bluetooth service.
Mar 30 16:30:15 tensorFlowPHY bluetoothd[1492]: Starting SDP server
Mar 30 16:30:15 tensorFlowPHY bluetoothd[1492]: Bluetooth management interface 1.14 initialized
Mar 30 16:30:20 tensorFlowPHY bluetoothd[1492]: a2dp-sink profile connect failed for FC:58:FA:A1:C2:70: Protocol not available
Mar 30 16:30:31 tensorFlowPHY bluetoothd[1492]: a2dp-sink profile connect failed for FC:58:FA:A1:C2:70: Protocol not available

EDIT 1: I installed one Ubuntu package that was missing : pulseaudio-module-bluetooth and restarted pulseaudio with the command : pulseaudio -k

Now the output of the bluetooth log after connection trial is :

Mar 30 16:36:59 tensorFlowPHY bluetoothd[1492]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Mar 30 16:37:00 tensorFlowPHY bluetoothd[1492]: connect error: Connection refused (111)
Mar 30 16:37:02 tensorFlowPHY bluetoothd[1492]: connect error: Connection refused (111)

Any idea why ?

EDIT 2 : I just restarted Ubuntu as someone asked to do. Still have the same pb.

EDIT 3 : I already have both modules loaded in /etc/pulse/default.pa :

$ egrep "(policy|discover)" /etc/pulse/default.pa
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover

But I cannot find those on the hdd, do I need to install something else ?

EDIT 4: My mistake, I used the locate command. After a sudo updatedb, the locate command is now able to find those 2 files.

EDIT 5 : Here is the pactl output :

$ pactl list modules | grep "Name:"
    Name: module-device-restore
    Name: module-stream-restore
    Name: module-card-restore
    Name: module-augment-properties
    Name: module-switch-on-port-available
    Name: module-udev-detect
    Name: module-alsa-card
    Name: module-alsa-card
    Name: module-bluetooth-policy
    Name: module-bluetooth-discover
    Name: module-bluez5-discover
    Name: module-native-protocol-unix
    Name: module-default-device-restore
    Name: module-rescue-streams
    Name: module-always-sink
    Name: module-intended-roles
    Name: module-suspend-on-idle
    Name: module-console-kit
    Name: module-systemd-login
    Name: module-position-event-sounds
    Name: module-role-cork
    Name: module-filter-heuristics
    Name: module-filter-apply
    Name: module-switch-on-connect
    Name: module-x11-publish
    Name: module-x11-cork-request
    Name: module-x11-xsmp

and the dpkg -l output :

$ dpkg -l | grep blue
ii  bluefish                                  2.2.9-1                                                    amd64        advanced Gtk+ text editor for web and software development
ii  bluefish-data                             2.2.9-1                                                    all          advanced Gtk+ text editor (data)
ii  bluefish-plugins                          2.2.9-1                                                    amd64        advanced Gtk+ text editor (plugins)
ii  blueman                                   2.0.4-1ubuntu3                                             amd64        Graphical bluetooth manager
ii  bluez                                     5.46-0ubuntu3                                              amd64        Bluetooth tools and daemons
ii  bluez-cups                                5.46-0ubuntu3                                              amd64        Bluetooth printer driver for CUPS
ii  bluez-obexd                               5.46-0ubuntu3                                              amd64        bluez obex daemon
ii  bluez-tools                               0.2.0~20140808-5build1                                     amd64        Set of tools to manage Bluetooth devices for linux
ii  gnome-bluetooth                           3.26.1-1                                                   amd64        GNOME Bluetooth tools
ii  indicator-bluetooth                       0.0.6+17.10.20170605-0ubuntu3                              amd64        System bluetooth indicator.
ii  libbluetooth3:amd64                       5.46-0ubuntu3                                              amd64        Library to use the BlueZ Linux Bluetooth stack
ii  libgnome-bluetooth13:amd64                3.26.1-1                                                   amd64        GNOME Bluetooth tools - support library
ii  pulseaudio-module-bluetooth               1:10.0-2ubuntu3.1                                          amd64        Bluetooth module for PulseAudio sound server

And here are the bluetooth pulseaudio modules loaded :

$ pactl list modules short | grep module-bluetooth
9   module-bluetooth-policy     
10  module-bluetooth-discover

EDIT 6: Your solution worked ! So to sum up :

$ bluetoothctl
[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 6C:0B:84:27:43:66 Powered: yes
[bluetooth]# remove FC:58:FA:A1:C2:70
[DEL] Device FC:58:FA:A1:C2:70 OE-P51
Device has been removed
[bluetooth]# exit
Agent unregistered
[DEL] Controller 6C:0B:84:27:43:66 tensorFlowPHY [default]
$ sudo service bluetooth restart

and finally :

$ bluetoothctl
[NEW] Controller 6C:0B:84:27:43:66 tensorFlowPHY [default]
Agent registered
[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 6C:0B:84:27:43:66 Powered: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 6C:0B:84:27:43:66 Discovering: yes
[NEW] Device FC:58:FA:A1:C2:70 OE-P51
[bluetooth]# pair FC:58:FA:A1:C2:70 
Attempting to pair with FC:58:FA:A1:C2:70
[CHG] Device FC:58:FA:A1:C2:70 Connected: yes
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 ServicesResolved: yes
[CHG] Device FC:58:FA:A1:C2:70 Paired: yes
Pairing successful
[CHG] Device FC:58:FA:A1:C2:70 ServicesResolved: no
[CHG] Device FC:58:FA:A1:C2:70 Connected: no
[bluetooth]# connect FC:58:FA:A1:C2:70 
Attempting to connect to FC:58:FA:A1:C2:70
[CHG] Device FC:58:FA:A1:C2:70 Connected: yes
Connection successful
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:A1:C2:70 ServicesResolved: yes
[OE-P51]#

I'm using Ubuntu 17.10.

I formatted an USB pen-drive to NTFS to prepare a Windows7 USB Installer.

I set the bootable flag on this pen-drive and copied the files into it.

EDIT 1: The USB pen-drive is automatically mounted by udev.

umount /dev/sdb1 takes from 10 upto 12 minutes to complete.

Here are the mount options :

$ mount | grep sdb
/dev/sdb1 on /media/mansfeld/Win7_USB_Installer type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)

EDIT 2: The cp operation is not INSTANTANEOUS at all, it took 3 minutes to copy the files to the USB pen-drive.

EDIT 3: The sync operation (done right after the cp) took 12 minutes to complete ! But then the umount will be instantaneous.

For FAT32, (with sync also disabled during mount), I notice the same behaviour.

Any ideas why it takes so long to unmount NTFS USB pendrive ?