bluetooth keeps turning off in 19.04 after physically and manually turning off bluetooth device, any fix to this?

I keep having my bluetooth turned off in ubuntu 19.04. it happens if I physically turn off or disconnect my Bluetooth speaker. Bluetooth in ubuntu 19.04 won’t turn on even if the slider is on “on” mode. I have to restart ubuntu several times to make it work. I already reinstalled Bluetooth but still, it happens.

anybody here who has the same problem or have a fix for it?

thanks πŸ™‚

If device is infected, can new devices get malware from associated social media accounts?

I have a couple social media accounts i want to use on a new phone ive got. The old phone i believe is infected with deep-malware. If I switch 2fa to my new phone which uses the same number but connected on a seperate network and change their passwords, could malware be transfered onto the new device? (Facebook, email, Discord, etc.)

No DispalyPort option in audio output device menu, Nvidia Drivers

I can’t get my DisplayPort-connected monitor (AW2518HF, external speakers connected) to show up on this drop-down menu: Settings > Sound > Output > Output Device.

I’ve opened Nvidia X Server Settings and can assure that DP Audio is enabled. Additionally, I booted Windows 7 and was able to select it and play sound just fine.

I’m using a GTX 750 (EVGA; they added a DP port in their version) with the 418 driver installed from Software & Updates on Ubuntu 19.04.

Here’s aplay -l

**** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]   Subdevices: 1/1   Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]   Subdevices: 1/1   Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]   Subdevices: 1/1   Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]   Subdevices: 1/1   Subdevice #0: subdevice #0 

Ubuntu 18.04: Roland USB “Quad Capture” Two Channel Sound Device Enumerated as Analog Surround 4.0

Ran Ubuntu 18.04.2 LTS as a “Live DVD” and the Roland Quad Capture USB sound device worked perfectly. When Ubuntu 18.04 was installed to the hard drive, the “Quad Capture” (two channel, quad in name only) is enumerated as Analog Surround 4.0 with no option in the configuration to change it to 2 channel stereo. I cannot find a .conf file for the Roland in order to change the channel mappings. This is clearly a bug: The Quad Capture worked fine with an 18.04 live demo (with I suppose a default USB sound device configuration) but when enumerated on the final install the device does not work because its misidentified as being a four channel output device. Any ideas?

device control in enterprises

I was reading about products that vendors like to call device control and it got me thinking, how do companies deal with removable devices/media? Is it a common step to lock down everything or perhaps permit only particular vendor-specific devices? How can one decide what to allow and what not in case of missing inventory (CMDB) of removable devices/media used within an org?

Ubuntu 18.04 Network Manager Not Creating New Connection for USB Ethernet device

The issue is that when I add a usb ethernet device, network manager doesn’t create a new connection for the added device. It correctly manages it but it is stuck in the disconnected state until you manually add a connection with network manager. This is not how a regular install behaves which has network manager creating connections in memory and attaching it to the device you just plugged in.

I installed ubuntu using the alternative installer and use a preseed file to set up the machine. In the preseed file we install all the packages for the ubuntu desktop and a few others. This may be related to the issues. Possibly relevant sections of the preseed file, everything else is related to partitioning and encryption.

d-i netcfg/choose_interface select auto tasksel tasksel/first multiselect ubuntu-desktop d-i pkgsel/include string ssh build-essential python-minimal ubuntu-desktop vim  

The reason for installation this way is beyond this question. It can be changed but this bug effects devices that have already been setup this way and fixing them can’t be “reinstall”.

An example of nmcli output when there is a ethernet connection on the motherboard and two usb ethernet connections.

eno1: connected to netplan-eno1  enx8cae4cfea138: connected to Wired connection 1  enx00e08f005933: disconnected         "Realtek USB 10/100/1000 LAN"         1 connection available         ethernet (r8152), 00:E0:8F:00:59:33, hw, mtu 1500  

It seems somewhere during the install, network manager creates ‘Wired Connection 1’ in /etc/NetworkManager/system-connections/ which it then applies it to any connected usb device. eno1 seems to be using something that netplan generates. I’m not sure where I should be looking for all of this, the mix of netplan, networkmanager and systemd-networkd that this Frankenstein machine results in is a bit confusing but here are some relevant config files. These are untouched from a fresh install.


[main] plugins=ifupdown,keyfile  [ifupdown] managed=false  [device] wifi.scan-rand-mac-address=no 

/etc/NetworkManager/system-connections/Wired connection 1

[connection] id=Wired connection 1 uuid=5da83520-ee6d-4e0a-a21d-27d0c9eb5b77 type=802-3-ethernet  [802-3-ethernet]  [ipv4] method=auto  [ipv6] method=auto ip6-privacy=2 


# This file describes the network interfaces available on your system # For more information, see netplan(5) network:   version: 2   renderer: networkd   ethernets:     eno1:       dhcp4: yes 


# Let NetworkManager manage all devices on this system network:   version: 2   renderer: NetworkManager 


[connection] id=netplan-eno1 type=ethernet interface-name=eno1  [ethernet] wake-on-lan=0  [ipv4] method=auto  [ipv6] method=ignore 


source-directory /etc/network/interfaces.d 

and interfaced.d is an empty directory.

NetworkManager is an enabled service and systemd-networkd is not enable.

Journalctl from network manager when I plug the usb ethernet into the device when it fails to assign it a connection.

Aug 09 15:06:25 <computer> NetworkManager[1011]: <info>  [1565388385.0741] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8) Aug 09 15:06:25 <computer> NetworkManager[1011]: <info>  [1565388385.1246] devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-8/2-8.1/2-8.1:1.0/net/enx8cae4ce9dc04, iface: enx8cae4ce9dc04) Aug 09 15:06:25 <computer> NetworkManager[1011]: <info>  [1565388385.1246] device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-8/2-8.1/2-8.1:1.0/net/enx8cae4ce9dc04, iface: enx8cae4ce9dc04): no ifupdown configuration found. Aug 09 15:06:25 <computer> NetworkManager[1011]: <info>  [1565388385.1247] device (enx8cae4ce9dc04): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Aug 09 15:06:28 <computer> NetworkManager[1011]: <info>  [1565388388.4869] device (enx8cae4ce9dc04): carrier: link connected Aug 09 15:06:28 <computer> NetworkManager[1011]: <info>  [1565388388.4897] device (enx8cae4ce9dc04): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')  

Journalctl from network manager when I plug the usb device into my own destkop.

Aug 09 15:04:25 <computer> NetworkManager[2382]: <info>  [1565388265.0379] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/11) Aug 09 15:04:25 <computer> NetworkManager[2382]: <info>  [1565388265.0961] devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/net/enx8cae4ce9dc04, iface: enx8cae4ce9dc04) Aug 09 15:04:25 <computer> NetworkManager[2382]: <info>  [1565388265.0961] device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/net/enx8cae4ce9dc04, iface: enx8cae4ce9dc04): no ifupdown configuration found. Aug 09 15:04:25 <computer> NetworkManager[2382]: <info>  [1565388265.0964] device (enx8cae4ce9dc04): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Aug 09 15:04:25 <computer> NetworkManager[2382]: <info>  [1565388265.4268] keyfile: add connection in-memory (15600b6f-63ad-37ae-9f6c-2f2e28f05489,"Wired connection 4") Aug 09 15:04:25 <computer> NetworkManager[2382]: <info>  [1565388265.4272] settings: (enx8cae4ce9dc04): created default wired connection 'Wired connection 4' Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5839] device (enx8cae4ce9dc04): carrier: link connected Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5877] device (enx8cae4ce9dc04): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5899] policy: auto-activating connection 'Wired connection 4' Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5926] device (enx8cae4ce9dc04): Activation: starting connection 'Wired connection 4' (15600b6f-63ad-37ae-9f6c-2f2e28f05489) Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5935] device (enx8cae4ce9dc04): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5949] device (enx8cae4ce9dc04): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5961] device (enx8cae4ce9dc04): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.5972] dhcp4 (enx8cae4ce9dc04): activation: beginning transaction (timeout in 45 seconds) Aug 09 15:04:28 <computer> NetworkManager[2382]: <info>  [1565388268.6012] dhcp4 (enx8cae4ce9dc04): dhclient started with pid 25848 Aug 09 15:04:28 <computer> dhclient[25848]: DHCPREQUEST of on enx8cae4ce9dc04 to port 67 (xid=0x46cb0eef)  

It’s the “Creating connection in memory” line that is missing from the device logs. Is there some setting I’m missing to set for network manager that enables it to do that?

Reinstalling correct grub package to Acer device 18.04

After installing ubuntu to my machine (Acer Aspire F5-572G), UEFI is unable to detect grub as the boot manager. The closest answer to fixing this is Unable to install Ubuntu on Acer Aspire ES1-533.

The issue is that this solution above proposess sudo apt-get install --reinstall grub-efi-amd64. However my machine is of Intel 64 bit architecture.. and not AMD.. When preforming apt-cache search grub-efi it provides the possible packages:

grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-dbg grub-efi-amd64-signed grub-efi-ia32 grub-efi-ia32-bin grub-efi-ia32-dbg 

Since my computer is Intel 64-bit arch, I’m not completely sure of the consequences either installing a ia32 or amd64…

Hence I am wanting to know:

  • Would amd64 bit work?
  • Is there any risk to choosing ia32 with 64 bit archeture?
  • Any other possible method of getting grub noticed by UEFI?

Note: I have wiped hard disk recently and able to reinstall ubuntu to hard drive if anything breaks πŸ™‚


What is this user-friendly device registration process called?

Logging in with a username/password can be annoying on non-keyboard devices (game consoles, Rokus, etc). Many media apps on these devices improve on this process by letting me activate my device on my account via these steps:

  1. I download and open the app on my device. It displays a 6-character code.
  2. I log into the web version on my laptop and go to a special device-activation page (e.g. ).
  3. The activation page has an input for the code displayed on my device. I enter the code in, and after that my device is associated with my account.

Is there a name for this protocol? I would like to implement it or find a library that implements it, but I don’t know what it’s called, if anything.

Ubuntu 18.04 says `Gave up waiting for suspend/resume device` when it’s booting after upgrading from 16.04

I just upgraded Ubuntu 16.04 to 18.04 and after reboot it shows

Gave up waiting for suspend/resume device /: clean, 293537/3932160 files, 4067550/15719936 blocks cryptsetup (md5_crypt): set up successfully 

then it doesn’t go to log in page.

Even though it hangs here, I can ssh in the computer and I can access folders and files. (one problem is terminal doesn’t have the ability of interpolation and showing history command though)

My quick search on this error is telling this problem is related to swap memory. Let me share some of the command outputs here and some approaches I already tried and not worked.

$   sudo blkid | grep swap /dev/mapper/sdb8_crypt: UUID="19a5cc43-2391-461e-9d36-ecb21d23cbe1" TYPE="swap" /dev/mapper/sda8_crypt: UUID="a68d5301-6f0c-4069-be2b-b43d42e4697c" TYPE="swap" 
$   sudo cat  /etc/initramfs-tools/conf.d/resume #RESUME=UUID=6f0ca38b-604e-4641-8d12-c81fd8228098 #RESUME=none RESUME=UUID=19a5cc43-2391-461e-9d36-ecb21d23cbe1 #RESUME=UUID=a68d5301-6f0c-4069-be2b-b43d42e4697c 

First row was a row I had first and I commented out it then added second, third and fourth, and tried them respectively but non of them worked well with $ sudo update-initramfs -u

$   cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: #   info -f grub -n 'Simple configuration'  GRUB_DEFAULT=0 #GRUB_HIDDEN_TIMEOUT=0 #GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_TIMEOUT_STYLE=hidden GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" GRUB_ENABLE_CRYPTODISK=y  # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"  # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console  # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480  # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true  # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true"  # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" 
$   sudo lsinitramfs /initrd.img |grep resume bin/resume conf/conf.d/resume scripts/local-premount/resume 
$   swapon NAME      TYPE      SIZE USED PRIO /dev/dm-2 partition  16G   0B   -2 /dev/dm-3 partition  16G   0B   -3 
$   sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-55-generic cryptsetup: WARNING: resume device UUID=7bad70b9-6b90-424b-88e1-3b36e63ea23f uses a key file W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast 

I saw tried the following solutions but none of them worked. Swap: From partition to file, now get "no matching swap device is available" threads I could find is similar to this) (I don’t have /swapfile
$ ls /swapfile
ls: cannot access ‘/swapfile’: No such file or directory)

Issue in Boot , platform device creation failed: -16

acpi MSFT0101:00: platform device creation failed: -16 Unable to mount root fs on unknown-block(0,0) Hardware name : HP HP pavilion notebook/820C , BIOS F.07 05/27/2016

I have dual boot Windows 10 + Elementary Os(Ubuntu 16.04+)

Everything is working fine for last two years, today when I opened elementary os and run sudo apt upgrade.

In meanwhile I’m working with Firefox and vs code , suddenly my pc was slow down. Yeah that’s genuine because upgrades are progressing… Firefox frized due to progress in upgrades. So i decided to shut down my laptop. When i startup my laptop the above msgs are flash in screen.

How can i boot my elementary without settings and data loss.