Tag: 1804

I used my Samsung Galaxy S10e to provide internet tethering for my Ubuntu 18.04 LTS tower, and it worked fine until I updated my S10e when it stopped working. I tried to enable and disable USB debugging on my phone, but it does not work. How can I solve this?

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 testPXE-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.

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

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?

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.

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.

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.