Adrian's questions

I try to connect my Ubuntu 23.10 with an LG C2 TV to then output the sound from LG to Ubuntu; the same works fine with my iPhone which then plays some music through my Ubuntu attached speakers. I use bluetoothctl:

devices Paired
Device 20:28:BC:81:F8:D9 [LG] webOS TV OLED55C22LB
connect 20:28:BC:81:F8:D9
Attempting to connect to 20:28:BC:81:F8:D9
[CHG] Device 20:28:BC:81:F8:D9 Connected: yes
Connection successful
[CHG] Device 20:28:BC:81:F8:D9 ServicesResolved: yes

but then I can't see in the LG's "Bluetooth Device" menu my Ubuntu as a speaker.
What should I do to solve this?

Actually, for iPhone to output audio to Bluetooth, I had first to specify that the Bluetooth connection's target (i.e. computer) is a speaker.

PS: I use pipewire, pipewire-pulse and wireplumber which work fine

info 20:28:BC:81:F8:D9
Device 20:28:BC:81:F8:D9 (public)
        Name: LG TV[[LG] webOS TV OLED55C22LB
        Alias: LG TV[[LG] webOS TV OLED55C22LB
        Class: 0x0008243c (533564)
        Icon: audio-card
        Paired: yes
        Bonded: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: LG Electronics            (0000feb9-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v0046p1200d1436
        ManufacturerData Key: 0x00c4 (196)
        ManufacturerData Value:
  02 34 15 13 17 fd 80                             .4.....

I have Ubuntu 21.10 and I get the below results related to pulseaudio.
What should I do to "connect" to pulseaudio such that pacmd list-sinks to correctly report something?

$sudo netstat -tlupn | egrep -i "mopidy|pulse"
tcp        0      0 0.0.0.0:4713            0.0.0.0:*               LISTEN      1730/pulseaudio
tcp6       0      0 :::4713                 :::*                    LISTEN      1730/pulseaudio

$pacmd list-sinks
No PulseAudio daemon running, or not running as session daemon.

$ps -ef | egrep "/[p]ulseaudio"
lightdm     1730    1668  0 Oct30 ?        00:04:35 /usr/bin/pulseaudio --daemonize=no --log-target=journal

I have an Ubuntu 21.10 and I get the below confusing network status related to ppp0; RDS (aka StamAcasa.rdsne) is the name of my network connection providing access to Internet.

Why ppp0 is reported as disconnected by nmcli device but connected by ifconfig? How should I fix this?

$nmcli device
DEVICE           TYPE      STATE                   CONNECTION      
eno1             ethernet  connected               RDS             
enp2s0           ethernet  connected               enp2s0          
br-4d725814c237  bridge    connected               br-4d725814c237 
br-667e68774f98  bridge    connected (externally)  br-667e68774f98 
docker0          bridge    connected (externally)  docker0         
ppp0             ppp       disconnected            --              
lo               loopback  unmanaged               --              

$nmcli device show ppp0
GENERAL.DEVICE:                         ppp0
GENERAL.TYPE:                           ppp
GENERAL.HWADDR:                         (unknown)
GENERAL.MTU:                            1492
GENERAL.STATE:                          30 (disconnected)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --

$ip link show | grep -i ppp
5: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 3
    link/ppp 

$ifconfig | grep -A5 ppp
ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1492
        inet 86.124.169.167  netmask 255.255.255.255  destination 10.0.0.1
        ppp  txqueuelen 3  (Point-to-Point Protocol)
        RX packets 64158  bytes 57421437 (57.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 33280  bytes 13396662 (13.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         StamAcasa.rdsne 0.0.0.0         UG        0 0          0 ppp0
StamAcasa.rdsne 0.0.0.0         255.255.255.255 UH        0 0          0 ppp0
link-local      0.0.0.0         255.255.0.0     U         0 0          0 enp2s0
172.17.0.0      0.0.0.0         255.255.0.0     U         0 0          0 docker0
172.20.0.0      0.0.0.0         255.255.0.0     U         0 0          0 br-4d725814c237
172.29.0.0      0.0.0.0         255.255.0.0     U         0 0          0 br-667e68774f98
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 enp2s0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 enp2s0
192.168.31.0    0.0.0.0         255.255.255.0   U         0 0          0 enp2s0

$ping www.google.com
PING www.google.com (172.217.19.100) 56(84) bytes of data.
64 bytes from bud02s27-in-f4.1e100.net (172.217.19.100): icmp_seq=1 ttl=59 time=33.3 ms
64 bytes from muc03s07-in-f100.1e100.net (172.217.19.100): icmp_seq=2 ttl=59 time=33.5 ms

$lspci | grep -i eth
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

I have a Asus H370-i with an Intel Wireless-AC 9560 and Ubuntu 20.10. What should I configure to have bluetooth only? so without WIFI.

What should I install for the update-usbids command to be found?

I have:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.10
Release:    20.10
Codename:   groovy

I notice that epylog is missing and also is not possible to install using sudo apt-get install epylog. Is it replaced by something else? otherwise how to install it?

After upgrading from Ubuntu 18.10 to Ubuntu 19.04 (Disco Dingo) the command /usr/bin/sensors -A no longer shows the fan information. Before upgrate I get this kind of information:

fan1:                      334 RPM  (min =    0 RPM)
fan2:                      864 RPM  (min =    0 RPM)
fan6:                     1076 RPM  (min =    0 RPM)
SYSTIN:                    +23.0°C  (high = +98.0°C, hyst = +95.0°C)  sensor = thermistor
CPUTIN:                    +27.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                   +23.5°C    sensor = thermistor
AUXTIN2:                   +23.0°C    sensor = thermistor
AUXTIN3:                   +97.0°C    sensor = thermistor
PECI Agent 0:              +30.0°C  (high = +98.0°C, hyst = +95.0°C)
PECI Agent 0 Calibration:  +27.0°C  
Core 0:        +27.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:        +33.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:        +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:        +29.0°C  (high = +80.0°C, crit = +100.0°C)

while after upgrade I get only this:

asus-isa-0000
cpu_fan:        0 RPM

acpitz-acpi-0
temp1:        +27.8°C  (crit = +119.0°C)

coretemp-isa-0000
Package id 0:  +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:        +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:        +33.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:        +32.0°C  (high = +80.0°C, crit = +100.0°C)

I have the modules coretemp and nct6775 already declared into /etc/modules (same as for Ubuntu 18.10) and I also run sudo sensors-detect which also recommends those modules.

I have an Asus H370-I motherboard with an i3-8300 Intel CPU.

What is the problem and how should I solve it?

With XUbuntu 18.10 (pretty fresh install) when locking the system the monitor is immediately suspended; pressing any key or mouse button doesn't wake it. Pressing CTRL + ALT + F7 finally wakes the monitor and the message below is presented:

This session is locked You'll be redirected to the unlock dialog automatically in a few seconds

then the lock screen appears and everything goes as expected.

Another solution is to type the password (while the monitor is still blank) then press ENTER which then wakes the monitor and also unlocks the session (if the password is correctly typed, of course).

I have these settings (Display Power Management on or off and/or Automatically lock the session activated or not make no difference):

The expected behavior with Display Power Management on and Automatically lock the session activated is:

1. when locking the system first the monitor should be still on
2. the lock window should be presented
3. after 10 min the monitor should go black
4. after 15 min the monitor should sleep
5. after 60 min the monitor should switch off
6. when pressing any key or mouse the monitor should switch on and the lock window be presented

What should I do in order to obtain the desired behavior? also I don't want to avoid the problem by using xscreensaver

UPDATE

The same behavior is no matter what I choose for Display Power Management and/or Automatically lock the session.

With Power Manager unchecked in Session and Startup (Screen Locker still checked) the behavior is the same. I guess it's a Screen Locker (light-locker) issue.

This is the /var/log/syslog created when locking:

Apr 12 20:24:26 adrhc systemd[1]: Started /run/user/111 mount wrapper.
Apr 12 20:24:26 adrhc systemd[1]: Created slice User Slice of UID 111.
Apr 12 20:24:26 adrhc systemd[1]: Starting User Manager for UID 111...
Apr 12 20:24:26 adrhc systemd[1]: Started Session c9 of user lightdm.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Paths.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG network certificate management daemon.
Apr 12 20:24:26 adrhc systemd[21272]: Starting D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on Sound System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Timers.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Sockets.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Basic System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Default.
Apr 12 20:24:26 adrhc systemd[21272]: Startup finished in 33ms.
Apr 12 20:24:26 adrhc systemd[1]: Started User Manager for UID 111.
Apr 12 20:24:26 adrhc systemd[21272]: Started D-Bus User Message Bus.
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] AppArmor D-Bus mediation is enabled
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc systemd[21272]: Starting Accessibility services bus...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.a11y.Bus'
Apr 12 20:24:26 adrhc systemd[21272]: Started Accessibility services bus.
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 12 20:24:26 adrhc systemd[21272]: Starting Virtual filesystem service...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 12 20:24:26 adrhc systemd[21272]: Started Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21244 (lightdm) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21327 (gnome-keyring-d) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21336 (lightdm-greeter) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21337 (lightdm-gtk-gre) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: Stopping Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: Stopped Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: [email protected]: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping User Manager for UID 111...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Default.
Apr 12 20:24:57 adrhc gvfsd[21352]: A connection to the bus can't be made
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Accessibility services bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping D-Bus User Message Bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Virtual filesystem service...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped D-Bus User Message Bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Accessibility services bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Basic System.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Paths.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Timers.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Sockets.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:57 adrhc systemd[21272]: Closed Sound System.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG network certificate management daemon.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:57 adrhc systemd[21272]: Closed D-Bus User Message Bus Socket.
Apr 12 20:24:57 adrhc systemd[21272]: Reached target Shutdown.
Apr 12 20:24:57 adrhc systemd[21272]: Starting Exit the Session...
Apr 12 20:24:57 adrhc systemd[1]: [email protected]: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopped User Manager for UID 111.
Apr 12 20:24:57 adrhc systemd[1]: [email protected]: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping /run/user/111 mount wrapper...
Apr 12 20:24:57 adrhc systemd[1]: Removed slice User Slice of UID 111.
Apr 12 20:24:57 adrhc systemd[1]: Stopped /run/user/111 mount wrapper.

By mistake I noticed that in /tmp directory are continuously created some files then immediately deleted. Using a succession of ls -l /tmp I managed to catch the created files:

-rw------- 1 root root       0 Apr  2 19:37  YlOmPA069G
-rw------- 1 root root       0 Apr  2 19:37  l74jZzbcs6

or another example:

-rw------- 1 root root       0 Apr  2 19:44  AwVhWakvQ_
-rw------- 1 root root       0 Apr  2 19:44  RpRGl__cIM
-rw------- 1 root root       0 Apr  2 19:44  S0e72nkpBl
-rw------- 1 root root       0 Apr  2 19:44  emxIQQMSy2

It's about Ubuntu 18.10 with 4.18.0-16-generic. This is an almost fresh install: I added some server software (nginx, mysql, php7.2-fpm) but even with those closed the problem persists.

What are the files created and why? How would I stop this behaviour? a very undesirable one on a SSD

Thank you!

UPDATE

The question is about when not having /tmp in RAM (no tmpfs).
The guilty software is x2goserver.service otherwise a must have one.

What should I do in order to install Windows 10 after I already installed Ubuntu (>= 18.10)? both should work in UEFI mode

GParted shows this after failed Windows installation attempt (/dev/nvme0n1p 4-7 were created at install moment):

At installation moment I get:

Windows detected that the EFI system partition was formatted as NTFS. Format the EFI system partition as FAT32, and restart the installation

I'm trying to install Ubuntu 18.10 on a new not partitioned HDD (using a VMWare machine). I try with manual partitioning to create the EFI System Partition but there is no EFI System Partition option (or other option containing the EFI word). I tried with 100M, 300M, 500M, 512M sizes but no luck. What's the solution for this?

PS: the similar question related to Ubuntu 15.10 doesn't help

I just bought new hardware (Intel i3-8300 + Asus ROG STRIX H370-I GAMING) which I want to replace and Intel N3150 + Asrock N3150DC-ITX. Both systems have 16G RAM. Would this work by just moving the old HDD containing the OS (Ubuntu 16.04.6 LTS) to the new hardware? or the OS will just fail to boot or to allow login?

UPDATE

• using onboard video for both systems
• I have no WIFI but only ethernet (2x)
• I'm afraiding about network interfaces issues, e.g.:
  • the new interfaces have other names & settings and they should somehow come into /etc/NetworkManager/system-connections/ at least
  • the new interfaces have overlapping names but other settings

I start a remote desktop XFCE4 session where then I'm clicking the chrome shortcut. I can see with ps that chrome is started, but I don't see its window.

Why this happens?
How to bring to front the chrome's window?

lsb_release -a:

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:    16.04
Codename:   xenial

uname -a:

Linux utg353l 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:34:45 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux