boot error after uninstalling Windows 10 with OS Uninstaller from Ubuntu 18.04

After uninstalling Windows 10 following the instructions in this post: https://askubuntu.com/questions/167778/dualboot-ubuntu-w-windows-deleting-windows/167785#167785 When you restart my computer, you receive the following error message:

PXE-EG1: Check cables for faulty media test
PXE-MOF: Stop the PXE-ROM

Bootable keys do not work

The same applies to the BIOS / EFI key. I tried all the options: F1, F2, F12, Del. I can not access it.

Other data:

Lenovo B570 laptop
Installed operating system: Ubuntu 18.04, Windows 10

The following message was displayed at the end of the uninstall process with the operating system uninstaller:

An error occurred while uninstalling.
We hope you enjoyed it and send us your comments now you can restart the computer. Do not forget to boot your BIOS into the sda2 file.
If your computer starts directly in Windows, try changing the boot order of the BIOS.
If you can not change the boot order in your BIOS, change the default entry in Windo

FileZilla can not open certain folders in Ubuntu 18.04

I have installed LLVM and its components on Ubuntu 18.04. After the installation, I wanted to view the installation files to check them.

The files are in separate folders in / usr / bin and identical folders in / usr / lib / llvm-8 / bin. However, if I click on one of the folders, Filezilla answers:

Error:  Directory /usr/lib/llvm-8/bin/clang: no such file or directory
Error:  Failed to retrieve directory listing

Regardless of whether I navigate to subfolders in / usr / bin or / usr / lib / llvm-8 / bin, I get the same error message.

I kept the Putty installation dialog for each of the components when I installed them, and there were no error messages.

What does that mean?

Thank you very much.

ubuntu 18.04 – Fix and fix gpg2 or explain

I am having a problem importing or generating secret GPG keys on Ubuntu 18.04 with my root (sudo) user without root authority. With root user I have no problems with gpg, but not root and it is basically denied permission.
When I run tty, you can see that g & o has no read permissions. Is there an address somewhere that I can address to safely open it at boot time?

ls -la $(tty);
crw--w---- 1 root tty 136, 1 Sep 13 02:22 /dev/pts/1

gparted on 18:04 shows no gui

I installed gparted from the Ubuntu repository. When I tried to use it, I was asked to authenticate myself, but then nothing was displayed. I am using the NIDIA version 418 driver as recommended by the manufacturer software and updates Program. Gparted keeps running without anything being displayed.

18.04 – How does Ubuntu determine the date / time when there is no NTP server and a broken RTC clock?

I'm trying to determine how Ubuntu 18.04 determines how to set the system clock for a computer that has a broken RTC clock and no access to an NTP server and systemd-timesyncd is disabled. When booting, the time is always 2018-01-28 10:58:48 EST. This seems to be very similar

Prevents the clock from advancing to a system time after the Ubuntu Server build time

Specification of time as 2018-01-28 15:58. The only advice he got was to turn off timesyncd, which I already disabled and did not solve his problem.

Normally an application starts, receives a GPS signal, sets the clock and starts to run. But it does not take GPS to run. What it takes is that the clock does not go back in time. I thought I might be able to fix that if I knew how Ubuntu sets the time to 2018-01-28 10:58:48 EST.

I tried activating systemd-timesyncd. While the computer is usually not connected to the Internet, I can connect it as a maintenance procedure. Then I get the correct time and touch a file under / var / lib / private / systemd / timesync / clock. If I break the connection to the Internet and touch the file manually, the next start will use that time. But even this approach, though better, can put the clock backwards, effectively remembering the last time the computer was connected to the Internet.

Apart from that, it seems puzzling that Ubuntu uses the same time at boot time when it can not time and that time is not January 1 of a year. If I knew what Linux does, I might be able to find a solution. So far, apart from the above URL, I find a lot of "how to use NTP" and "using NTP is a good idea" etc. I would, if I could, but no internet except in maintenance mode.

Sound – Ubuntu 18.04 crashed. I can not understand what went wrong

So my Ubuntu 18.04 crashed. I am aware, that journalctl -b -1 -e spends what went wrong in previous boats. The output for my laptop is

abyssalcramps@AbyssalCramps:/var/crash$ journalctl -b -1 -e
Sep 12 01:41:35 AbyssalCramps systemd(992): Reached target Shutdown.
Sep 12 01:41:35 AbyssalCramps systemd(992): Starting Exit the Session...
Sep 12 01:41:35 AbyssalCramps fusuma.desktop(1701): I, (2019-09-12T01:41:31.220406 #1701)  INFO -- : Execute: xdotool key super
Sep 12 01:41:35 AbyssalCramps bluetoothd(790): Endpoint unregistered: sender=:1.108 path=/MediaEndpoint/A2DPSource
Sep 12 01:41:35 AbyssalCramps bluetoothd(790): Endpoint unregistered: sender=:1.108 path=/MediaEndpoint/A2DPSink
Sep 12 01:41:35 AbyssalCramps systemd(1336): Stopped Sound Service.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Stopped target Basic System.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Stopped target Sockets.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed GnuPG cryptographic agent and passphrase cache.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed D-Bus User Message Bus Socket.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed GnuPG network certificate management daemon.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Stopped target Paths.
Sep 12 01:41:35 AbyssalCramps systemd(992): Received SIGRTMIN+24 from PID 14588 (kill).
Sep 12 01:41:35 AbyssalCramps systemd(1336): Stopped Pending report trigger for Ubuntu Report.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Stopped target Timers.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Closed Sound System.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Reached target Shutdown.
Sep 12 01:41:35 AbyssalCramps systemd(1336): Starting Exit the Session...
Sep 12 01:41:35 AbyssalCramps systemd(1336): Received SIGRTMIN+24 from PID 14589 (kill).
Sep 12 01:41:35 AbyssalCramps systemd(1337): pam_unix(systemd-user:session): session closed for user abyssalcramps
Sep 12 01:41:35 AbyssalCramps systemd(993): pam_unix(systemd-user:session): session closed for user gdm
Sep 12 01:42:00 AbyssalCramps systemd-logind(691): Failed to abandon session scope, ignoring: Connection timed out
Sep 12 01:42:00 AbyssalCramps systemd-logind(691): Power key pressed.
Sep 12 01:42:00 AbyssalCramps gdm3(970): GdmLocalDisplayFactory: Failed to issue method call: Timeout was reached
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:72
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:71
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:70
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:82
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:74
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:73
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:66
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:65
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:75
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) UnloadModule: "libinput"
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) systemd-logind: releasing fd for 13:67
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
Sep 12 01:42:00 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
Sep 12 01:42:00 AbyssalCramps gdm3(970): Freeing conversation 'gdm-password' with active job
Sep 12 01:42:00 AbyssalCramps gdm3(970): GLib: g_variant_new_string: assertion 'string != NULL' failed
Sep 12 01:42:01 AbyssalCramps /usr/lib/gdm3/gdm-x-session(1354): (II) Server terminated successfully (0). Closing log file.

It seems my sound service crashed the entire system. Is it because I set the priority of Pulse Audio on very high? I changed daemon.conf and asound.conf from pulse audio to get better output.
The name of the crash file is _usr_bin_pulseeffects.1000.crash this is available in / var / crash. Should I simply uninstall Pulse Effects?
If you need specific information directly from the .crash file itself, please let me know. I will try to give it to you. I'm new to this area and can not understand the .crash file.

Speed ​​up the boot time Ubuntu 18.04

I've searched and read so many questions and blogs, including ArchWiki, but have not found how to properly speed up the launch process.

Here's a summary of some things I've done:

  1. Checked fstab File confirming that the UUID matches the for /dev/sda3 Where is my file system?

  2. Disables most startup items (including apt updates)

  3. Check if the problems were with mine grub config, changed nomodeset and quiet splash This has worsened my boot time.

  4. Read about the blacklisting of the tmp_module, but had no idea what it was, and did not try.

I've just listed a few things that I can remember by heart.

This is the edition I get systemd:

systemd-analyze  blame | head
         23.550s dev-sda3.device
         21.272s systemd-journal-flush.service
         16.297s apport-autoreport.service
         15.562s dev-loop21.device
         15.413s dev-loop20.device
         15.115s dev-loop13.device
         15.040s dev-loop12.device
         15.039s dev-loop11.device
         15.021s dev-loop19.device
         14.225s dev-loop14.device

As you can probably see, this is unusually slow and I'm currently not sure how to cut those times off best. If it helps, I'll double-boot from an external 1TB hard drive.

Issue of the critical chain:

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

graphical.target @1min 4.977s
└─multi-user.target @1min 4.975s
  └─postfix.service @1min 4.902s +70ms
    └─postfix@-.service @55.756s +9.141s
      └─network-online.target @55.753s
        └─NetworkManager-wait-online.service @49.616s +6.136s
          └─NetworkManager.service @41.505s +8.108s
            └─dbus.service @38.428s
              └─basic.target @38.298s
                └─sockets.target @38.295s
                  └─snapd.socket @38.251s +38ms
                    └─sysinit.target @37.976s
                      └─apparmor.service @33.286s +4.689s
                        └─local-fs.target @33.280s
                          └─run-user-121.mount @1min 5.982s
                            └─local-fs-pre.target @12.209s
                              └─systemd-tmpfiles-setup-dev.service @8.726s +3.47
                                └─kmod-static-nodes.service @8.359s +362ms
                                  └─systemd-journald.socket @8.355s
                                    └─system.slice @8.304s

How can I solve this best?

Thanks a lot!

18.04 – How to prevent the system from being "minimized"

Today I noticed a new message when I log in to my Ubuntu 18.04 Docker container.

This system has been minimized by removing packages and content
are not required on a system where users do not log on.

To restore this content, you can use the command & # 39; Unminimize & # 39; To run.

However, this is a container that I log into from time to time.

IMHO does not think it's a very sensible strategy to change systems this way without the user's permission, but other than that, how can I prevent Ubuntu from minimizing my systems?

The minimization breaks the functionality of my container and the unminimize Command ends with a kernel error.