I am trying to learn vLLM with local inference, on my Laptop running Ubuntu 24.04. My RAM is only 32 Gig, but for the model I am trying (med-gemma from google via vLLM), it appears the disk space is the bottleneck, not memory. This is how the disks are allocated (out of 512 GB).

So should I rebalance a bit from my home to root as the root partition always runs out of space when I try to load mid sized language models or fire up vLLM containers?

I believe the latest Ubuntu Docker images published on Docker Hub do not contain the latest security fixes otherwise available with apt-get upgrade.

Here is why I believe so: after starting a fresh container from the latest immutable Docker image, apt list --upgradeable finds 4 packages to update.

$ docker run -it --rm ubuntu:noble-20260210.1
$ apt-get -qq update
$ apt list --upgradeable
Listing... Done
gcc-14-base/noble-updates,noble-security 14.2.0-4ubuntu2~24.04.1 arm64 [upgradable from: 14.2.0-4ubuntu2~24.04]
libgcc-s1/noble-updates,noble-security 14.2.0-4ubuntu2~24.04.1 arm64 [upgradable from: 14.2.0-4ubuntu2~24.04]
libgnutls30t64/noble-updates,noble-security 3.8.3-1.1ubuntu3.5 arm64 [upgradable from: 3.8.3-1.1ubuntu3.4]
libstdc++6/noble-updates,noble-security 14.2.0-4ubuntu2~24.04.1 arm64 [upgradable from: 14.2.0-4ubuntu2~24.04]

According to the changelogs of the associated source packages, they contain fixes for security vulnerabilities.

• https://launchpad.net/ubuntu/+source/gcc-14/14.2.0-4ubuntu2~24.04.1, the source package of
  • https://launchpad.net/ubuntu/noble/+package/gcc-14-base
  • https://launchpad.net/ubuntu/noble/+package/libgcc-s1
  • https://launchpad.net/ubuntu/noble/+package/libstdc++6
• https://launchpad.net/ubuntu/+source/gnutls28/3.8.3-1.1ubuntu3.5, the source package of
  • https://launchpad.net/ubuntu/noble/amd64/libgnutls30t64/3.8.3-1.1ubuntu3.5

Is this analysis correct, or am I mistaken somewhere? If the analysis is correct, would you know the reason why this is the case?

Context: I want to build a container image as reproducibly as possible, and as securely as possible. I was thinking that pulling the latest immutable tag would give me both. But it looks like I have to choose between running apt-get update for security, or not running it for reproducibility.

After many years of having windows turn my brain to mush I am exploring the interesting world of Ubuntu and I am loving it. I installed it successfully on a laptop quite some time ago but, now I have installed it on a PC which had some memory issues under the influence of Windows and it is happier with much Ubuntu! My issue is that it won't find he T6E adaptor so, I have no internet. I have spent a long time looking for a solution with the most promising advice here: https://ubuntu.pkgs.org. The only problem is I can't figure out which package to download or even how I get it. I am desperate so,any help would be hugely appreciated.

Good evening,

I am new to Ubuntu and still trying to figure my way around this new experience, but it has not been easy.

I have recently started experiencing latency and stutters with my audio whether it is from YouTube via Google Chrome, Spotify, Discord, my audio interface: Scarlett 2i2, or my video capture card: NZXT Signal 4K30. I am running all this through Pulsemeeter with pipewire-pulseaudio setup.

I have been searching and searching, and nothing seem to have worked to stabilize the latency and stop the stutter and pops. Everything I have come across seems to be outdated and worked on older versions of Ubuntu.

I cannot lie. This is becoming more frustrating day by day and it is starting to tire me out especially when I do one thing to fix an issue, and all of a sudden I lose everything I have configured so I have remember how I had the configuration from the beginning.

If anyone has any possible solution to fixing the audio latency, stuttering, and pops to the setup I have mentioned above, please help me out.

I was wondering if I were to reinstall Ubuntu on my PC which has the OS on a separate SSD, would it reset the GRUB bootloader to like it's initial installed configuration?

Like, I'm planning to do an "erase disk and install Ubuntu" on the SSD that Ubuntu is already installed on and just starting fresh but I just want to be aware if I need to redo what changes I made to GRUB or not.

Just some background info: I am dual booting Ubuntu 24.04.4 LTS on a separate SSD with Windows 11 on another SSD, and using the GRUB bootloader to boot between the two OS.

I can't login to ubuntu because my system language last set is GREEK. So I can neither login nor enter any commands via root. It's all Greek (to me and anybody else).

For context, I have had Ubuntu 22.04 dual booted with Windows for a while (partitioned on the same drive), and then Windows gave me the screen where I needed to enter a Bitlocker recovery key, so I've been working in Ubuntu instead. The other day I decided to try changing some BIOS settings to see if I could undo what led to Bitlocker activating, but instead I ended up accidentally removing Ubuntu from Windows Boot Manager. I want to regain my ability to access Ubuntu without losing any of my files if possible.

Here's my pastebin from the Boot-Repair tool: https://paste.ubuntu.com/p/4J8ZxStGy8/. Additionally, if it is helpful, here is the information I get when I enter sudo fdisk -l into the Terminal. (I am running a Try Ubuntu session from a bootable Ubuntu live USB):

Disk /dev/loop0: 2.74 GiB, 2945802240 bytes, 5753520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 74.27 MiB, 77881344 bytes, 152112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 505.09 MiB, 529625088 bytes, 1034424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop4: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop5: 271.24 MiB, 284413952 bytes, 555496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop6: 500 KiB, 512000 bytes, 1000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop7: 12.93 MiB, 13553664 bytes, 26472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SAMSUNG MZVLB1T0HBLR-000L7              
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: gpt
Disk identifier: F57CD323-F496-474E-9C38-B41293227AA8
 
Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     206847     204800   100M EFI System
/dev/nvme0n1p2     206848     239615      32768    16M Microsoft reserved
/dev/nvme0n1p3     239616 1024360094 1024120479 488.3G Microsoft basic data
/dev/nvme0n1p4 1024360448 1026623487    2263040   1.1G Windows recovery environm
/dev/nvme0n1p5 1026627584 1999372287  972744704 463.8G Linux filesystem
 
Disk /dev/sda: 14.57 GiB, 15640625152 bytes, 30548096 sectors
Disk model: USB Flash Disk  
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: 0x9aa1e92d
 
Device     Boot    Start      End  Sectors  Size Id Type
/dev/sda1  *        2048 30482559 30480512 14.5G  7 HPFS/NTFS/exFAT
/dev/sda2       30482560 30548095    65536   32M ef EFI (FAT-12/16/32)
 
Disk /dev/mapper/ventoy: 4.44 GiB, 4762707968 bytes, 9302164 sectors
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: gpt
Disk identifier: 389FBC94-38B6-4D1A-8964-87488DB3D5A5
 
Device                     Start     End Sectors  Size Type
/dev/mapper/ventoy-part1      64 9291427 9291364  4.4G Microsoft basic data
/dev/mapper/ventoy-part2 9291428 9301499   10072  4.9M EFI System
/dev/mapper/ventoy-part3 9301500 9302099     600  300K Microsoft basic data
 
Disk /dev/mapper/sda1: 14.53 GiB, 15606022144 bytes, 30480512 sectors
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
 
Disk /dev/loop8: 38.83 MiB, 40714240 bytes, 79520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Please help me figure out how to proceed.

Edit: Additionally, here is my pastebin for after I ran the recommended repair: https://paste.ubuntu.com/p/5ZGVFgC9Wy/. I also got a message from Boot Repair that says "Locked-NVram detected. Please do not forget to make your UEFI firmware boot on the Ubuntu 22.04.5 LTS entry (nvme0n1p1/efi/ubuntu/grubx64.efi file) !"

I installed KDE's spectacle tool for capturing screenshots in Ubuntu Cinnamon (24.04) as the default screenshot tool does not have all the features I need.

sudo apt install kde-spectacle

However, when I try try to capture a screenshot, the app crashes.

Here is the error message in terminal:

$ spectacle 
kf.kirigami: Failed to find a Kirigami platform plugin 
qrc:/src/Gui/ScreenshotView.qml:167:9: Type AnnotationEditor unavailable 
qrc:/src/Gui/Annotations/AnnotationEditor.qml:31:9: Type HoverOutline unavailable 
qrc:/src/Gui/Annotations/HoverOutline.qml:25:22: Type SelectionBackground unavailable 
qrc:/src/Gui/Annotations/SelectionBackground.qml:6:1: module "QtQuick.Shapes" is not installed 
qrc:/src/Gui/ImageCaptureOverlay.qml:36:5: Type AnnotationEditor unavailable AnnotationEditor { ^ 

qrc:/src/Gui/Annotations/AnnotationEditor.qml:31:9: Type HoverOutline unavailable HoverOutline { ^ 

qrc:/src/Gui/Annotations/HoverOutline.qml:25:22: Type SelectionBackground unavailable sourceComponent: SelectionBackground { ^ 

qrc:/src/Gui/Annotations/SelectionBackground.qml:6:1: module "QtQuick.Shapes" is not installed import QtQuick.Shapes 1.15 ^

How to fix it?

I have a Ubuntu 24.10 (I think I upgraded to Ubuntu 24.10) that was on during a power outage. I can enter the password to unlock the hard drive, but during boot I get a black screen with this text display where you can see various services that started, but it hangs after Started colord.service and I never hear from it again. There's a kind of console more or less, but typing into it doesn't seem to do anything.

[  OK  ] Started cups.path - CUPS Scheduler.
[  OK  ] Closed cups.socket - CUPS Scheduler.
         Stopping cups.socket - CUPS Scheduler...
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Started udisks2.service - Disk Manager.
iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[  OK  ] Started NetworkManager.service - Network Manager.
[  OK  ] Reached target network.target - Network.
         Starting NetworkManager-wait-online.service - Network Manager Wait Online...
         Starting apache2.service - The Apache HTTP Server...
         Starting cups.service - CUPS Scheduler...
         Starting openvpn.service - OpenVPN service...
[  OK  ] Started snap.cups.cups-browsed.service - Service for snap application cups.cups-browsed.
[  OK  ] Started snap.cups.cupsd.service - Service for snap application cups.cupsd.
         Starting systemd-user-sessions.service - Permit User Sessions...
[  OK  ] Started unattended-upgrades.service - Unattended Upgrades Shutdown.
[  OK  ] Finished openvpn.service - OpenVPN service.
[  OK  ] Finished systemd-user-sessions.service - Permit User Sessions.
         Starting gdm.service - GNOME Display Manager...
         Starting plymouth-quit-wait.service - Hold until boot process finishes up...
         Starting colord.service - Manage, Install and Generate Color Profiles...
[  OK  ] Started apache2.service - The Apache HTTP Server.
[  OK  ] Started gdm.service - GNOME Display Manager.
[  OK  ] Started colord.service - Manage, Install and Generate Color Profiles.
_

I'd rather not wipe the computer. Can I do something to diagnose and repair it? It's a pure Ubuntu install with no dual boot or anything.

How do I start a gui-app as a different user from a background script?

To be more specific: I am using a notebook in different environments, some of it require a proxy for network connection. To setup all clients (apt, snap, gsettings, nextcloud-desktop) automatically I am using a trigger script in /etc/NetworkManager/dispatcher.d/. For starting apps in user-context I've found a script on stackexchange:

DISPLAY_ID=":$(find /tmp/.X11-unix/* \! -user gdm | sed 's#/tmp/.X11-unix/X##' | head -n 1)"
USER=$(who | grep tty | awk '{print $1}')
USER_ID=$(id -u "$USER")
function user-session() {
    _environment=("DISPLAY=$DISPLAY_ID" "DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$USER_ID/bus")
    sudo -Hu "$USER" env "${_environment[@]}" "$@"
}
# use it for instance like this:
user-session gsettings set org.gnome.system.proxy mode none

This does no longer work for gui apps like the nextcloud client (because of wayland?). This nextcloud client uses a static config file for the network config, so I have to kill the client, rewrite the config and finally restart the client. The latter has to be done in the context of the currently logged in user, but the trigger script runs as root.

So how do I start the nextcloud client for the current gui user from a script running as root triggered by a background job on a current (24.04) ubuntu?

I am using this procedure since several years. Maybe there exists some simpler solution?

Mathias

I run lxd 6.1 on an Intel i9-1390. On the host I can run perf and get all the hardware events. In the VM I can run perf but do not the hardware events.

The command line has the -cpu host,hv_passthrough set.

 701512 ?        Sl    13:41 /snap/lxd/30130/bin/qemu-system-x86_64 -S -name c0-rl -uuid 49ba3cce-de29-43ca-8400-4f1ded88a55d -daemonize -cpu host,hv_passthrough -nographic -serial chardev:console -nodefaults -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=allow,resourcecontrol=deny -readconfig /var/snap/lxd/common/lxd/logs/xxx/qemu.conf -spice unix=on,disable-ticketing=on,addr=/var/snap/lxd/common/lxd/logs/xxx/qemu.spice -pidfile /var/snap/lxd/common/lxd/logs/xxx/qemu.pid -D /var/snap/lxd/common/lxd/logs/xxx/qemu.log -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -runas lxd -bios /var/lib/snapd/hostfs/usr/share/seabios/bios-256k.bin

dmesg on the VM shows:

[    0.223566] Performance Events: unsupported p6 CPU model 183 no PMU driver, software events only.

perf on the VM shows:

root@rlsdwan-vnf:~# perf stat sleep 1

Performance counter stats for 'sleep 1':

          0.84 msec task-clock                #    0.001 CPUs utilized          
             1      context-switches          #    1.188 K/sec                  
             1      cpu-migrations            #    1.188 K/sec                  
            80      page-faults               #   95.079 K/sec                  
  <not supported>      cycles                                                      
  <not supported>      instructions                                                
  <not supported>      branches                                                    
  <not supported>      branch-misses                                               

   1.001526172 seconds time elapsed

   0.001466000 seconds user
   0.000000000 seconds sys

On the host I get the not supported values.

Can anybody help?

Andreas

I'm new both here and to Linux, but liking it aside from the learning curve but glad to be Windows free. I had an issue with Ubuntu 22.04 when I got home where my PC now boots in emergency mode. I'm not sure how to fix this, I'm and hoping for some help.

Initially this was due to a full disk I think. I managed to delete a few files from terminal to free space, but it's still booting in emergency mode.

I'm wondering if this is a fstab file issue where efi and grub aren't mounting.

Emergency mode message:

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):
root@A-1:~# mount -a
mount: /boot/efi: mount point does not exist.
mount: /boot/grub: mount point does not exist.
root@A-1:~# vi /etc/fstab_

Results of /etc/fstab:

GNU nano 6.2                                     /etc/fstab *
# /etc/fstab: static file system information.
# 
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# 
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=88A1-B666 /boot/efi        vfat    umask=0022,fmask=0022,dmask=0022      0       1
#/boot/efi/grub /boot/grub      none    defaults,bind   0       0
/dev/mapper/cryptoswap none     swap    sw              0       0
/dev/disk/by-uuid/fceceda31-252a-462e-8cee-804315612700 /media/fceceda31-252a-462e-8cee-804315612700 auto nosuid,nodev,nofail,x-gvfs-show 0 0

You are correct. The drive is encrypted. I enter code, then get this.

I feel like I'm missing an entry in fstab, but I haven't backed it up. I only have my boot NVMe and a media device.

I've been trying to edit metadata of some mp4 files, and been unable to do it on Ubuntu. I'm specifically looking to edit the 'rating' of the video. On windows, I can right click > properties > details and edit the rating just by clicking it (see image).

if possible, I'm happy to automate it using python too, so whatever works.

This is, for example, how I edit rating of a video file on windows:

Any help is appreciated!

I wanted to reinstall Ubuntu (dual boot with Windows 10) on an Asus ZenBook Flip 15 to have it on a larger partition (I ran out of space beforehand). To do this I have changed the boot order to have it boot directly to Windows 10, and then I deleted and merged the partition with the Windows 10 partition. I have also deleted the Ubuntu boot folder via Diskpart (as explained here).

Then I created a new (larger, 100GB) partition and created a live USB with the latest 20.04 release from the Ubuntu website, but when I boot from this USB I do not get the Install Ubuntu option. The only options are (similar to this):

• Ubuntu
• Ubuntu (safe graphics)
• OEM install (for manufacturers)
• Boot from next volume
• UEFI firmware settings

The things I have tried didn't work, and I was curious if anyone here has another suggestion as to what may help me install my dual boot.

I tried:

• Disabled Secure Boot.
• Disabled Fast Startup.
• I tried creating live USB with Rufus and Universal USB Installer.
• I tried all options. The first three give me a black screen and the fourth boots to Windows 10, the fifth goes to UEFI.
• I tried to manually boot into the three available EFI files on the live USB (BOOTx64.efi, grubx64.efi, mmx64.efi).
• I looked for booting in legacy mode (as suggested here), but my UEFI doesn't show this option.

Additionally in the UEFI the only option it gives next to the Windows bootloader is booting from the USB itself, which usually should get me to the 'Install Ubuntu' option.

I have no idea what to try next, but my friend suggested that somehow the USB may think that a version of Ubuntu is still installed (maybe some remnants from the deleted install?), and will therefore try to boot it, but can't find it, hence the black screen.

I recently upgraded to Ubuntu 20.04 on my machine and everything was fine.But after opening windows(not the first time) and switching back to Ubuntu it starts a fsck which at 32% goes into emergency mode and it comes back to emergence mode even after hitting Ctrl+D See below:

/dev/sda4: recovering journal
/dev/sda4: clean, 521649/2886128 files, 5537425/11553792 blocks
You are in emergency mode.  After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):
Reloading system manager configuration
Starting default target
You are in emergency mode.  After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit to boot into default mode.
Press Enter for maintenance

Reloading system manager configuration
Starting default target
You are in emergency mode.  After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit to boot into default mode.
Press Enter for maintenance

I was trying to set some mount for SFTP, in the process.

I think I messed up the fstab accidentally.

Now on reboot, it boots into recovery, and using

mount -o remount,rw /

can let me boot into the desktop.

I undo the edits for my mounts but unfortunately, I don't have backup of fstab. I tried a different fstab, e.g.: change to UUID, different directories etc., but I still haven't got a clue.

What could be the problem?

My fstab:

LABEL=system-boot /boot vfat defaults 0 1
LABEL=ssd /media/ubuntu/ssd auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0

Results of running fsck on reboot:

Ubuntu 19.10 ubuntu tty1

ubuntu login: ubuntu
Password:
Unable to setup logging. [Errno 30] Read-only file system: '/var/log/landscape/sysinfo.log'
run-parts: /etc/update-motd.d/50-landscape-sysinfo exited with return code 1
mktemp: failed to create file via template '/var/lib/update-notifier/tmp.XXXXXXXXXX': Read-only file system
run-parts: /etc/update-motd.d/95-hwe-eol exited with return code 1
/usr/lib/update-notifier/update-motd-fsck-at-reboot: 38: cannot create /var/lib/update-notifier/fsck-at-reboot: Read-only file system
ubuntu@ubuntu:~$ sudo mount -o remount,rw / [  250.787472] cloud-init[1839]: Traceback (most recent call last):
[  250.788150] cloud-init[1839]:   File "/usr/bin/cloud-init", line 11, in <module>
[  250.788785] cloud-init[1839]:     load_entry_point('cloud-init==19.4', 'console_scripts', 'cloud-init')()
[  250.789356] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 893, in main
[  250.789908] cloud-init[1839]:     get_uptime=True, func=functor, args=(name, args))
[  250.790478] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2558, in log_time
[  250.791031] cloud-init[1839]:     ret = func(*args, **kwargs)
[  250.791478] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 600, in status_wrapper
[  250.791938] cloud-init[1839]:     util.ensure_dirs((data_d, link_d,))
[  250.792446] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1585, in ensure_dirs
[  250.792933] cloud-init[1839]:     ensure_dir(d, mode)
[  250.793429] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1642, in ensure_dir
[  250.793924] cloud-init[1839]:     chmod(path, mode)
[  250.794328] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1874, in chmod
[  250.794827] cloud-init[1839]:     os.chmod(path, real_mode)
[  250.795289] cloud-init[1839]: OSError: [Errno 30] Read-only file system: '/var/lib/cloud/data'
[  250.795746] cloud-init[1839]: Error in sys.excepthook:
[  250.796235] cloud-init[1839]: Traceback (most recent call last):
[  250.796686] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in apport_excepthook
[  250.797162] cloud-init[1839]:     os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
[  250.797690] cloud-init[1839]: OSError: [Errno 30] Read-only file system: '/var/crash/_usr_bin_cloud-init.0.crash'
[  250.798209] cloud-init[1839]: Original exception was:
[  250.798699] cloud-init[1839]: Traceback (most recent call last):
[  250.799217] cloud-init[1839]:   File "/usr/bin/cloud-init", line 11, in <module>
[  250.799709] cloud-init[1839]:     load_entry_point('cloud-init==19.4', 'console_scripts', 'cloud-init')()
[  250.800233] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 893, in main
[  250.800763] cloud-init[1839]:     get_uptime=True, func=functor, args=(name, args))
[  250.801295] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2558, in log_time
[  250.801770] cloud-init[1839]:     ret = func(*args, **kwargs)
[  250.802183] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 600, in status_wrapper
[  250.802633] cloud-init[1839]:     util.ensure_dirs((data_d, link_d,))
[  250.803077] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1585, in ensure_dirs
[  250.803574] cloud-init[1839]:     ensure_dir(d, mode)
[  250.804086] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1642, in ensure_dir
[  250.804539] cloud-init[1839]:     chmod(path, mode)
[  250.805044] cloud-init[1839]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1874, in chmod
[  250.805527] cloud-init[1839]:     os.chmod(path, real_mode)
[  250.805978] cloud-init[1839]: OSError: [Errno 30] Read-only file system: '/var/lib/cloud/data'
_

Before installing Ubuntu 19.10 on my 64GB USB 2.0 flash drive I did some research on partition schemes. Most of the websites recommended 2GB-8GB for the root (/) partition.

But to play on the safe side I set it to 10GB, and guess what happened 1 week later.
I get notified that only 1GB of root space is left!
I freaked out and changed the size of the partition a few hours back and it ruined the performance!

I had this configuration when I installed Ubuntu.

root = 10GB
swap = 2GB
home ~ 50GB

and now, what I did is:

root = 32GB
swap = 2GB
home ~ 28GB

I was expecting better performance But what followed totally pissed me off.
*Now the OS boots in about 1.5 minutes!
Please let me know how i can make the boot process faster !

I just remembered that before I changed the partitions I was having a problem with the CD drive popping out. SoI opened it up, removed the ribbon cable (or whatever that's called), taped it and left it inside. So my CD drive does not pop out every 20 seconds. Do you think it has any impact on the performance? Please let me know what to do in this case.

Were those websites I followed wrong, or did I make some mistake in the first place?

Results of df -h:

rohit@Rohit:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.8G     0  1.8G   0% /dev
tmpfs           374M  1.7M  373M   1% /run
/dev/sdb2        30G  8.2G   20G  30% /
tmpfs           1.9G   51M  1.8G   3% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/loop0      218M  218M     0 100% /snap/atom/248
/dev/loop2      4.4M  4.4M     0 100% /snap/gnome-calculator/704
/dev/loop3       15M   15M     0 100% /snap/gnome-characters/317
/dev/loop1       49M   49M     0 100% /snap/gtk-common-themes/1474
/dev/loop4       68M   68M     0 100% /snap/sublime-text/85
/dev/loop5       92M   92M     0 100% /snap/core/8689
/dev/loop6      227M  227M     0 100% /snap/wine-platform-runtime/104
/dev/loop7      4.0M  4.0M     0 100% /snap/notepad-plus-plus/227
/dev/loop9       55M   55M     0 100% /snap/core18/1705
/dev/loop8      227M  227M     0 100% /snap/wine-platform-runtime/111
/dev/loop11     1.0M  1.0M     0 100% /snap/gnome-logs/93
/dev/loop13      55M   55M     0 100% /snap/core18/1668
/dev/loop10     1.0M  1.0M     0 100% /snap/gnome-logs/81
/dev/loop12      74M   74M     0 100% /snap/wine-platform-3-stable/6
/dev/loop14     161M  161M     0 100% /snap/gnome-3-28-1804/116
/dev/loop15      94M   94M     0 100% /snap/core/8935
/dev/loop17      24M   24M     0 100% /snap/fwupd/1704
/dev/loop16     4.3M  4.3M     0 100% /snap/gnome-calculator/501
/dev/loop18      45M   45M     0 100% /snap/gtk-common-themes/1440
/dev/loop19     150M  150M     0 100% /snap/gnome-3-28-1804/71
/dev/loop20      15M   15M     0 100% /snap/gnome-characters/495
/dev/sdb5        26G  3.3G   21G  14% /home
tmpfs           374M   52K  374M   1% /run/user/1000
rohit@Rohit:~$ █

Results of df -systemd-analyze blame:

rohit@Rohit:~$ systemd-analyze blame
        23.564s plymouth-quit-wait.service
        10.602s dev-sdb2.device
         7.368s snapd.service
         6.765s systemd-journal-flush.service
         5.700s dev-loop20.device
         5.650s dev-loop11.device
         5.635s dev-loop18.device
         5.150s dev-loop9.device
         5.110s dev-loop13.device
         5.105s dev-loop16.device
         5.038s dev-loop17.device
         4.902s dev-loop8.device
         4.756s dev-loop0.device
         4.659s dev-loop15.device
         4.658s dev-loop10.device
         4.580s udisks2.service
         4.553s dev-loop14.device
         4.485s networkd-dispatcher.service
         4.462s dev-loop1.device
         4.115s dev-loop6.device
         3.833s dev-loop5.device
         3.702s ModemManager.service
         3.543s dev-loop19.device
         3.179s accounts-daemon.service
         3.076s dev-loop12.device
         3.045s dev-loop4.device
         2.966s e2scrub_reap.service
         2.600s NetworkManager.service
         2.547s systemd-resolved.service
         2.527s dev-loop7.device
         2.382s dev-loop3.device
         2.358s dev-loop2.device
         2.352s grub-common.service
         2.164s apport.service
         2.143s avahi-daemon.service
         2.103s grub-initrd-fallback.service
         2.037s bluetooth.service

Here is a screenshot of my home directory. All the files with mono on it and the UUID file seems suspicious.

Results of systemd-analyze critical-chain:

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @39.271s
└─multi-user.target @39.271s
  └─snapd.seeded.service @20.610s +111ms
    └─snapd.service @13.238s +7.368s
      └─basic.target @13.003s
        └─sockets.target @13.003s
          └─snapd.socket @12.987s +16ms
            └─sysinit.target @12.981s
              └─systemd-timesyncd.service @12.565s +415ms
                └─systemd-tmpfiles-setup.service @12.405s +152ms
                  └─local-fs.target @12.397s
                    └─run-user-1000-doc.mount @23.947s
                      └─run-user-1000.mount @18.415s
                        └─swap.target @12.270s
                          └─dev-disk-by\x2duuid-08d582e2\x2d38dc\x2d4dc9\x2d98d7\x2df4bd4b7ee9fa.swap @12.164s +105ms
                            └─dev-disk-by\x2duuid-08d582e2\x2d38dc\x2d4dc9\x2d98d7\x2df4bd4b7ee9fa.device @12.146s

When I use a live USB for Ubuntu 18.04 LTS (or other Debian distros actually), depending on what options I choose in grub, I get stuck on either a screen tearing, looking like this:

or stuck at a message saying:

BIOS contains WGDS but no WRDS

Just the default "live mode" results in a screen tearing like in the screenshot.

I have a GTX 1660
System Model ROG Strix GL10CS_GL10CS
I disabled Secure Boot in the BIOS also.

I tried various USB drives and ISOs, but it's still the same.

What else could I try to fix this?

I am using Ubuntu 18.10 which is running the latest, MySQL community edition. After an OS update and restart, it refuses to boot to the GUI. I can access the root account via recovery, and I have tried a lot of solutions also from similar questions where I have thus far changed folder and files ownership to mysql and given user and group read+write permission. I also added a local AppArmor rule for mysqld.

This is now the current state.

Defined-By: systemd
Support: [http://www.ubuntu.com/support](http://www.ubuntu.com/support)

mysql.service has begun starting up.
20 09:38:56 coldcode01-Lenovo-ideapad-100-15IBY audit[1622]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/mysqld" pid=1622 comm="mysqld" capability=12
capname="net_admin"
20 09:38:56 coldcode01-Lenovo-ideapad-100-15IBY kernel: audit: type=1400 audit(1553071136.879:81): apparmor="DENIED" operation="capable" profile="/usr/sbin/mysqld" pi
d=1622 comm="mysqld" capability=12 capname="net_admin"
20 09:38:56 coldcode01-Lenovo-ideapad-100-15IBY audit[820]: USER_AVC pid=820 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation=
"dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.
systemd1" pid=1622 label="/usr/sbin/mysqld" peer_pid=1 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?'
20 09:38:56 coldcode01-Lenovo-ideapad-100-15IBY kernel: audit: type=1107 audit(1553071136.883:82): pid=820 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg
='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask
="send" name="org.freedesktop.systemd1" pid=1622 label="/usr/sbin/mysqld" peer_pid=1 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?'

20 09:38:57 coldcode01-Lenovo-ideapad-100-15IBY mysqld[1629]: Initialization of mysqld failed: 0
20 09:38:57 coldcode01-Lenovo-ideapad-100-15IBY systemd[1]: mysql.service: Control process exited, code=exited status=1
20 09:38:57 coldcode01-Lenovo-ideapad-100-15IBY systemd[1]:  
mysql.service: Failed with result 'exit-code'.
System20 09:38:57 coldcode01-Lenovo-ideapad-100-15IBY systemd[1]: Failed to start MySQL Community Server.
Subject: Unit mysql.service has failed
Defined-By: systemd
Support: [http://www.ubuntu.com/support](http://www.ubuntu.com/support)

Unit mysql.service has failed.

The result is RESULT.
20 09:38:58 coldcode01-Lenovo-ideapad-100-15IBY systemd[1]: mysql.service: Service RestartSec=100ms expired, scheduling restart.
20 09:38:58 coldcode01-Lenovo-ideapad-100-15IBY systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Subject: Automatic restarting of a unit has been scheduled
Defined-By: systemd
Support: [http://www.ubuntu.com/support](http://www.ubuntu.com/support)

Automatic restarting of the unit mysql.service has been scheduled, as the result for

I have turned off quiet and splash to see why my boot takes so long on my new SSD.

I see the following at 3.xx seconds:

sd 4:0:0:0: Attached scsi generic sg2 type 0
sd 4:0:0:0: [sdb] Attached SCSI removable disk

then it sits there for 30 seconds and at 33.xx seconds:

Begin: Waiting for suspend/resume device ... Begin: Running /scripts/...
random: fast init done

I have only one disk (and this is only removable with a screw driver), I imagine it could be waiting for a card in the SD card reader?

Here is the extract from dmesg:

[    3.172236] sd 4:0:0:0: Attached scsi generic sg2 type 0
[    3.177895] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[   33.999093] random: fast init done

I noticed more in my boot messages from the boot screen:

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [
m: uninitialized urandom read (4 bytes read)
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
[    2.368965] random: lvm: uninitialized urandom read (2 bytes read)
done.
Begin: Running /scripts/local-premount ... [        3.170888] scsi 4:0:0:0: Direct-
D/MMC/MS PRO       1.00 PQ: 0 ANSI: 4
[    3.172236] sd 4:0:0:0: Attached scsi generic sg2 type 0
[    3.177895] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Begin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block
[   33.999093] random: fast init done

I'm using the adapta nokto theme on Xubuntu and the icons on my panel are white, but the problem arose when I switched to the binary clock. The clock dots are in blue! And that makes it very difficult to see when I have a bright wallpaper. I tried to change the color of the binary dots, but all attempts did fail.

I'm a noob to linux, so please give me the simplest method as possible.

I've been trying to get my PDP xbox one controller to work (Kernel 4.16.13) but it isn't even turning on (The power light is off) . It is being recognized with lsusb, it even has the right manufacturer and product, but doesn't respond to anything else. I know that there have been problems with pdp controllers and linux in the past but I read that these problems were fixed in 4.15 (https://www.phoronix.com/scan.php?page=news_item&px=PDP-Xbox-One-Linux-4.15). I've played around a bunch with xboxdrv and xpad but I have no idea what to do anymore. any ideas?

Here's the lsusb descriptors for it but im brand new to linux and can't make heads or tails of it so I don't know if it's relevant.

Bus 001 Device 002: ID 0e6f:02a9 Logic3 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass        71 
  bDeviceProtocol       208 
  bMaxPacketSize0        64
  idVendor           0x0e6f Logic3
  idProduct          0x02a9 
  bcdDevice            1.0e
  iManufacturer           1 Performance Designed Products
  iProduct                2 PDP Wired Controller for Xbox One - Midnight Blue
  iSerial                 3 0000AFA7AFE41F1D
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           64
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     71 
      bInterfaceProtocol    208 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               4
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               4
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     71 
      bInterfaceProtocol    208 
      iInterface              0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     71 
      bInterfaceProtocol    208 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x00e0  1x 224 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0080  1x 128 bytes
        bInterval               1
Device Status:     0x0000
  (Bus Powered)

I execute the command sudo cassandra -R to start cassandra and I get the following error.

getopt: invalid option -- 'R'
/usr/sbin/cassandra: 158: exec: java: not found

It points to the following line in the cassandra script.

else
        exec $NUMACTL "$JAVA" $JVM_OPTS $cassandra_parms -cp "$CLASSPATH"

Is it because the environment variable JAVA is not set? If yes, how to set the variable?

The output of echo $JAVA_HOME is blank. This is the output of java -version:

java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)

Very much a noob but I am trying to get this wireless wi-fi adapter to work on an old computer my sister uses. Old wireless wifi adapter was an ASUS but it died. Any step by step help would be appreciated. I have computer on a wired connection currently. Thanks.

I have just installed the 16.04 in dual boot with Windows. The installation was OK, and for a couple of times Ubuntu booted smoothly. Now, after having chosen Ubuntu at the booting, a black screen appears with the following:

/dev/sda8: clean 271789/1222992 files, 1952109/4882432 blocks

[ 10.015870] tom_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]

[ 10.507758] iwlwifi 0000:01:00.0: Unsupported splx structure

Welcome to emergency mode!

I tried to search a bit on the today, but there is nothing specific, even less clear solutions. Do you have any suggestions?

Here is the Pastebin for the dmesg log.

Output of sudo blkid:

/dev/sda1: LABEL="ESP" UUID="2605-3DC2" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="8a5f68a4-5a57-4238-93dd-f4b072f0f75e"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="c8d98f36-1de8-4327-bc66-f14653f56ce4"
/dev/sda3: LABEL="OS" UUID="5CCE72F7CE72C8B2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4d6d4d89-ca38-41b7-ad64-5d7be881f962"
/dev/sda4: LABEL="WINRETOOLS" UUID="EC7AA90F7AA8D81A" TYPE="ntfs" PARTUUID="1ecce821-a7c3-4cfb-9d01-a2ce25f1e1aa"
/dev/sda5: LABEL="Image" UUID="5254A9E354A9C9D5" TYPE="ntfs" PARTUUID="7514622b-bfa8-4f31-93cf-7730e289739d"
/dev/sda6: LABEL="DELLSUPPORT" UUID="9C98DECB98DEA2D6" TYPE="ntfs" PARTUUID="396ddeed-43e8-4d20-b4b4-b1b910688ac3"
/dev/sda7: UUID="c35ada9f-7d1a-4220-8c12-5f69cad3236e" TYPE="swap" PARTUUID="9885e759-1e62-4336-91b4-0997baf71a20"
/dev/sda8: UUID="dd4038ad-17fb-43c6-9528-2a6db31c7371" TYPE="ext4" PARTUUID="c90e1cce-c184-466e-8433-a9816b609c76"
/dev/sda9: UUID="d0114045-d0fa-4128-86eb-1872cf863d4c" TYPE="ext4" PARTUUID="f0ab486d-6a10-4345-8798-95334cc379d6"

Output of the command sudo lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931,5G  0 disk
├─sda1   8:1    0   500M  0 part /boot/efi
├─sda2   8:2    0   128M  0 part
├─sda3   8:3    0 465,7G  0 part /windows
├─sda4   8:4    0   467M  0 part
├─sda5   8:5    0  14,5G  0 part
├─sda6   8:6    0   1,1G  0 part
├─sda7   8:7    0   3,7G  0 part [SWAP]
├─sda8   8:8    0  18,6G  0 part /
└─sda9   8:9    0 426,9G  0 part /home
sr0     11:0    1  1024M  0 rom

Output of the command sudo cat /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda8 during installation
UUID=dd4038ad-17fb-43c6-9528-2a6db31c7371 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
#UUID=2605-3DC2  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda9 during installation
UUID=d0114045-d0fa-4128-86eb-1872cf863d4c /home           ext4    defaults        0       2
# /windows was on /dev/sda3 during installation
UUID=5CCE72F7CE72C8B2 /windows        ntfs    defaults,umask=007,gid=46 0       0
# swap was on /dev/sda7 during installation
UUID=c35ada9f-7d1a-4220-8c12-5f69cad3236e none            swap    sw              0       0
UUID=5CCE72F7CE72C8B2 /media/Data  ntfs-3g  defaults,windows_names,locale=it_IT.UTF-8  0 0
UUID=2605-3DC2  /boot/efi   vfat    defaults    0   1

Here is the output for the commands:

dmseg | grep -i error
dmseg | grep -i warn

/dev/sda8: clean, 271927/1222992 files, 1952671/4882432 blocks
[    9.450771] tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]
[   10.406021] iwlwifi 0000:01:00.0: Unsupported splx structure
[   11.837247] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver
[   11.837281] pcieport 0000:00:1c.0:   device [8086:9d14] error status/mask=00000001/00000000
[   11.837306] pcieport 0000:00:1c.0:    [ 0] Receiver Error           (First)
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):

[    0.042413] mce: [Hardware Error]: Machine check events logged
[    1.007339] i915_bpo 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1.bin failed with error -2
[    8.791557] EXT4-fs (sda8): re-mounted. Opts: errors=remount-ro
[    9.450800] tpm_crb: probe of MSFT0101:00 failed with error -16
[   10.488382] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2
[   10.510832] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2
[   10.510856] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[   11.837236] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[   11.837247] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver
[   11.837281] pcieport 0000:00:1c.0:   device [8086:9d14] error status/mask=00000001/00000000
[   11.837306] pcieport 0000:00:1c.0:    [ 0] Receiver Error           (First)
root@C:~# dmesg | grep -i warn
[    0.884605] i8042: Warning: Keylock active
[    9.391478] ACPI Warning: /_SB_.IETM._TRT: Return Package has no elements (empty) (20150930/nsprepkg-126)
root@C:~#

Results of dmseg | grep iwl:

[   14.752001] audit: type=1400 audit(1479394081.331:2): apparmor="STATUS" operation="profile_load" profile=
[   14.752080] audit: type=1400 audit(1479394081.331:3): apparmor="STATUS" operation="profile_load" profile=
[   14.752093] audit: type=1400 audit(1479394081.331:4): apparmor="STATUS" operation="profile_load" profile=
[   14.752097] audit: type=1400 audit(1479394081.331:5): apparmor="STATUS" operation="profile_load" profile=
[   14.967277] audit: type=1400 audit(1479394081.543:6): apparmor="STATUS" operation="profile_load" profile=
[   14.967284] audit: type=1400 audit(1479394081.543:7): apparmor="STATUS" operation="profile_load" profile=
[   14.985377] audit: type=1400 audit(1479394081.563:8): apparmor="STATUS" operation="profile_load" profile=
[   14.985383] audit: type=1400 audit(1479394081.563:9): apparmor="STATUS" operation="profile_load" profile=
[   14.991402] audit: type=1400 audit(1479394081.567:10): apparmor="STATUS" operation="profile_load" profile=
[   14.991407] audit: type=1400 audit(1479394081.567:11): apparmor="STATUS" operation="profile_load" profile=
[   22.733222] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
root@C:~#
root@C:~#
root@C:~#
root@C:~# dmesg | grep iwl
[   10.905689] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[   10.906738] iwlwifi 0000:01:00.0: Unsupported splx structure
[   11.008594] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2
[   11.053904] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2
[   11.053923] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[   11.096393] iwlwifi 0000:01:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[   11.397903] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210
[   11.398237] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.398676] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.522593] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   11.542634] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
root@C:~# _

I have upgraded to Ubuntu 16.04 and I have installed dnscrypt-proxy from repository. Then I have just edited the /etc/default/dnscrypt-proxy file changing the DNSCRYPT_PROXY_RESOLVER_NAME="" line with DNSCRYPT_PROXY_RESOLVER_NAME=cisco. After that I have just ran the following commands:

sudo service dnscrypt-proxy stop
sudo service dnscrypt-proxy start 

and everything was working fine.

The problem is that after reboot my internet connection does not work and I have to run this again:

sudo service dnscrypt-proxy stop
sudo service dnscrypt-proxy start 

to make it work. What I need is a way to make dnscrypt-proxy starts automatically at startup like it used to work before upgrading to 16.04.

I tried to put those commands in /etc/rc.local file but sometimes it did not work. Also I created a bash script with those commands and I made it run at startup, but still no luck.

Could you help me?

Thanks

So I finally dual booted Windows 10 with Ubuntu 16.04. I have been running Xubuntu on my secondary laptop around 5-6 months and now decided to install it on my main laptop so far Ubuntu runs great but there's only one issue: I can't see my dedicated GPU [AMD Radeon 8670M] it only shows my Intel Integrated GPU [Intel HD Graphics 4400]. On Additional drivers section there are only Intel Proprietary Drivers.

Here are the Commands I ran :

$ sudo lshw -c video

 *-display               
       description: VGA compatible controller
       product: Haswell-ULT Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:44 memory:c2000000-c23fffff memory:b0000000-bfffffff ioport:6000(size=64)**

and

$ lspci -nn | grep VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09)

and

$ dmesg | egrep "radeon|drm"

[    1.345817] [drm] Initialized drm 1.1.0 20060810
[    1.386931] [drm] Memory usable by graphics device = 2048M
[    1.386937] fb: switching to inteldrmfb from VESA VGA
[    1.387046] [drm] Replacing VGA console driver
[    1.391211] [drm] radeon kernel modesetting enabled.
[    1.395226] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.395229] [drm] Driver supports precise vblank timestamp query.
[    1.398577] radeon 0000:0a:00.0: enabling device (0006 -> 0007)
[    1.424927] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
[    1.425088] [drm] initializing kernel modesetting (HAINAN 0x1002:0x6660 0x103C:0x2164).
[    1.425101] [drm] register mmio base: 0xC2400000
[    1.425102] [drm] register mmio size: 262144
[    1.429954] radeon 0000:0a:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    1.429956] radeon 0000:0a:00.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
[    1.429957] [drm] Detected VRAM RAM=1024M, BAR=256M
[    1.429958] [drm] RAM width 64bits DDR
[    1.430106] [drm] radeon: 1024M of VRAM memory ready
[    1.430107] [drm] radeon: 2048M of GTT memory ready.
[    1.430116] [drm] Loading hainan Microcode
[    1.430197] [drm] Internal thermal controller without fan control
[    1.430254] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[    1.438512] [drm] radeon: dpm initialized
[    1.438518] [drm] GART: num cpu pages 524288, num gpu pages 524288
[    1.439806] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[    1.439810] [drm] PCIE gen 2 link speeds already enabled
[    1.442772] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[    1.442964] radeon 0000:0a:00.0: WB enabled
[    1.442967] radeon 0000:0a:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800355bec00
[    1.442968] radeon 0000:0a:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8800355bec04
[    1.442970] radeon 0000:0a:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8800355bec08
[    1.442971] radeon 0000:0a:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800355bec0c
[    1.442973] radeon 0000:0a:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8800355bec10
[    1.442974] radeon 0000:0a:00.0: VCE init error (-22).
[    1.442976] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.442977] [drm] Driver supports precise vblank timestamp query.
[    1.442979] radeon 0000:0a:00.0: radeon: MSI limited to 32-bit
[    1.443009] radeon 0000:0a:00.0: radeon: using MSI.
[    1.443040] [drm] radeon: irq initialized.
[    1.551879] fbcon: inteldrmfb (fb0) is primary device
[    1.551995] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    1.680395] [drm] ring test on 0 succeeded in 1 usecs
[    1.680403] [drm] ring test on 1 succeeded in 1 usecs
[    1.680419] [drm] ring test on 2 succeeded in 0 usecs
[    1.680428] [drm] ring test on 3 succeeded in 4 usecs
[    1.680436] [drm] ring test on 4 succeeded in 4 usecs
[    1.680715] [drm] ib test on ring 0 succeeded in 0 usecs
[    1.680744] [drm] ib test on ring 1 succeeded in 0 usecs
[    1.680771] [drm] ib test on ring 2 succeeded in 0 usecs
[    1.680792] [drm] ib test on ring 3 succeeded in 0 usecs
[    1.680813] [drm] ib test on ring 4 succeeded in 0 usecs
[    1.681381] [drm] Radeon Display Connectors
[    1.682905] [drm] Initialized radeon 2.43.0 20080528 for 0000:0a:00.0 on minor 1
[   21.205885] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[   21.205890] [drm] PCIE gen 2 link speeds already enabled
[   21.212077] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[   21.212176] radeon 0000:0a:00.0: WB enabled
[   21.212178] radeon 0000:0a:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800355bec00
[   21.212180] radeon 0000:0a:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8800355bec04
[   21.212181] radeon 0000:0a:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8800355bec08
[   21.212183] radeon 0000:0a:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800355bec0c
[   21.212184] radeon 0000:0a:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8800355bec10
[   21.212186] radeon 0000:0a:00.0: VCE init error (-22).
[   21.448861] [drm] ring test on 0 succeeded in 1 usecs
[   21.448866] [drm] ring test on 1 succeeded in 1 usecs
[   21.448872] [drm] ring test on 2 succeeded in 1 usecs
[   21.448880] [drm] ring test on 3 succeeded in 4 usecs
[   21.448887] [drm] ring test on 4 succeeded in 4 usecs
[   21.448951] [drm] ib test on ring 0 succeeded in 0 usecs
[   21.449007] [drm] ib test on ring 1 succeeded in 0 usecs
[   21.449062] [drm] ib test on ring 2 succeeded in 0 usecs
[   21.449076] [drm] ib test on ring 3 succeeded in 0 usecs
[   21.449090] [drm] ib test on ring 4 succeeded in 0 usecs

EDIT: Formatting

I'm using Kubuntu 15.04 and Plasma 5.4. The icons on the task-manager is too small. is there a way to make them bigger?

At the moment, sddm will logout the session on expiry. It is different to the way kde worked. 2 things: I am unable to locate where to specfiy the session timeout value and secondly, how to change the action from logout to say lock screen. Issue is I often have long running processes then get bumped off with the forced logout.

After successfully installing Kubuntu 13.10 (64-bit) on my Asus PC, I tried to upgrade to 14.04. After the upgrade completed and I tried to restart, the boot process crashes with a kernel panic.

[    19.805225] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        C  3.13.0-32-generic #58-Ubuntu
[    19.805250] Hardware name: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD/K30AD_M31AD_M51AD, BIOS 0402 11/29/2013
[    19.805273] task: ffffffff81c15480 ti: ffffffff81c00000 task.ti: ffffffff81c00000
[    19.805301] RIP: 0010:[<ffffffffa0548fe5>]  [<ffffffffa0548fe5>] rtl8821ae_rx_query_desc+0x1d5/0xa50 [rtl8821ae]
[    19.805345] RSP: 0018:ffff88011fa03c38  EFLAGS: 00010016
[    19.805365] RAX: 0000000000000020 RBX: ffff88011fa03dc8 RCX: 0000000000000020
[    19.805391] RDX: ffff8800c8c68060 RSI: 0000000000000020 RDI: 92d99716646e0bd6
[    19.805417] RBP: ffff88011fa03ca0 R08: ffff8800cba28900 R09: ffff88011fa03c80
[    19.805443] R10: 0000000000000013 R11: ffff8800cab98600 R12: ffff8800c8c5c000
[    19.805468] R13: 0000000000000001 R14: ffff8800cba28900 R15: ffff88011fa03d68
[    19.805494] FS:  0000000000000000(0000) GS:ffff88011fa00000(0000) knlGS:0000000000000000
[    19.805523] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    19.805543] CR2: 0000000000404180 CR3: 0000000002c0e000 CR4: 00000000000007f0
[    19.805569] Stack:
[    19.805576]  0000000000000000 0000000000000003 ffff88011fa03c58 ffffffff8109a812
[    19.805607]  ffff88011fa03c70 ffffffff810aaf12 0000000180150012 ffff88011fa03c80
[    19.805636]  ffff8800cab98600 ffff8800c8c5c000 ffff88011fa03d68 ffff8800cba28900
[    19.805665] Call Trace:
[    19.805674]  <IRQ> 
[    19.805682]  [<ffffffff8109a812>] ? default_wake_function+0x12/0x20
[    19.805713]  [<ffffffff810aaf12>] ? autoremove_wake_function+0x12/0x40
[    19.805744]  [<ffffffffa053c291>] _rtl_pci_rx_interrupt+0x141/0x680 [rtl8821ae]
[    19.805772]  [<ffffffff81338a9a>] ? blk_peek_request+0x5a/0x250
[    19.805796]  [<ffffffff8148ec57>] ? put_device+0x17/0x20
[    19.805817]  [<ffffffff814e011e>] ? scsi_request_fn+0x3ae/0x5e0
[    19.805840]  [<ffffffff810a2d40>] ? update_curr+0x80/0x180
[    19.805861]  [<ffffffff8109ec18>] ? __enqueue_entity+0x78/0x80
[    19.805884]  [<ffffffff810a5cd2>] ? enqueue_task_fair+0x422/0x6c0
[    19.805914]  [<ffffffffa053d3dd>] rtl_pci_interrupt+0x36d/0xb3e0 [rtl8821ae]
[    19.805941]  [<ffffffff810bf78e>] handle_irq_event_percpu+0x3e/0x1d0
[    19.805964]  [<ffffffff810bf95d>] handle_irq_event+0x3d/0x60
[    19.805986]  [<ffffffff810c2ada>] handle_fasteoi_irq+0x5a/0x100
[    19.806010]  [<ffffffff81015cde>] handle_irq+0x1e/0x30
[    19.806031]  [<ffffffff8172ea0d>] do_IRQ+0x4d/0xc0
[    19.806052]  [<ffffffff817241ad>] common_interrupt+0x6d/0x6d
[    19.806072]  <EOI> 
[    19.806080]  [<ffffffff815ceb52>] ? cpuidle_enter_state+0x52/0xc0
[    19.806107]  [<ffffffff815cec79>] cpuidle_idle_call+0xb9/0x1f0
[    19.806130]  [<ffffffff8101cebe>] arch_cpu_idle+0xe/0x30
[    19.806150]  [<ffffffff810cbcb5>] cpu_startup_entry+0xc5/0x290
[    19.806173]  [<ffffffff8170a1d7>] rest_init+0x77/0x80
[    19.806194]  [<ffffffff81d35f70>] start_kernel+0x438/0x443
[    19.806214]  [<ffffffff81d35941>] ? repair_env_string+0x5c/0x5c
[    19.806237]  [<ffffffff81d35120>] ? early_idt_handlers+0x120/0x120
[    19.806260]  [<ffffffff81d355ee>] x86_64_start_reservations+0x2a/0x2c
[    19.806284]  [<ffffffff81d35733>] x86_64_start_kernel+0x143/0x152
[    19.806306] Code: f6 43 3a 20 0f 84 8c 00 00 00 40 0f b6 cf 48 01 f1 48 01 ca of 84 3d 06 00 00 83 7a 68 18 0f 86 5a 02 00 00 48 8b ba d8 00 00 00 <0f> b7 37 89 f1 66 81 e1 fc 00 66 81 f9 a0 00 74
42 66 81 f9 c0
[    19.806413] RIP  [<ffffffffa0548fe5>] rtl8821ae_rx_query_desc+0x1d5/0xa50 [rtl8821ae]
[    19.806449]  RSP <ffff88011fa03c38>
[    19.813556] Kernel panic - not syncing: Fatal exception in interrupt
[    19.814734] drm_kms_helper: panic occurred, switching back to text console

The same problem occurs when I try and boot directly from a USB stick from the .iso image.

Version 13.10 however works just fine (I have to reinstall this old version now)