Quantcast
Channel: Ubuntu Forums - Installation & Upgrades
Viewing all 26379 articles
Browse latest View live
↧

E: Sub-process /usr/bin/dpkg returned an error code (1)

May 22, 2020, 7:34 pm
$
0
0
I try to upgrade but i see error dpkg, whats wrong?
Code:
richoandika@ur:~$ sudo apt update
Get:1 http://dl.google.com/linux/chrome/deb stable InRelease [1.811 B]
Hit:2 http://packages.microsoft.com/repos/vscode stable InRelease             
Hit:3 http://ppa.launchpad.net/bovender/bovender/ubuntu focal InRelease       
Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease                       
Hit:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease         
Hit:6 https://assets.checkra.in/debian  InRelease
Hit:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:8 http://archive.ubuntu.com/ubuntu focal-security InRelease
Fetched 1.811 B in 2s (927 B/s)
Reading package lists... Done
Building dependency tree     
Reading state information... Done
All packages are up to date.
richoandika@ur:~$ sudo apt upgrade -y
Reading package lists... Done
Building dependency tree     
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 indicator-ip : Depends: python-appindicator but it is not installable
                Depends: python-gtk2 but it is not installable
                Depends: python:any (>= 2.7.5-5~)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
richoandika@ur:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree     
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libappindicator1 libfluidsynth1 libluajit-5.1-2 libluajit-5.1-common
  libmsgpackc2 libnfs12 libpython-all-dev libpython2-dev libpython2.7-dev
  libtermkey1 libunibilium4 libvterm0 lua-luv neovim neovim-runtime python-all
  python-all-dev python-cairo python-cffi-backend python-concurrent.futures
  python-configparser python-crypto python-cryptography python-dbus
  python-entrypoints python-enum34 python-gi python-gobject python-gobject-2
  python-greenlet python-ipaddress python-keyring python-pycodestyle
  python-pysqlite2 python-six python-sqlalchemy python-sqlalchemy-ext
  python-xdg python2-dev python2.7-dev python3-greenlet python3-msgpack
  python3-neovim python3-pynvim xclip
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  indicator-ip
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 134 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 311983 files and directories currently installed.)
Removing indicator-ip (2.2.0) ...
/var/lib/dpkg/info/indicator-ip.prerm: 22: indicator-ip: not found
dpkg: error processing package indicator-ip (--remove):
 installed indicator-ip package pre-removal script subprocess returned error exi
t status 127
dpkg: too many errors, stopping
Errors were encountered while processing:
 indicator-ip
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
richoandika@ur:~$
↧
Search

Do security issues exist on 2nd-hand computer after Erase Disc install?

May 22, 2020, 8:42 pm
$
0
0
I received a Dell Inspiron laptop from a stranger who gave it to me instead of throwing it away. I successfully installed Lubuntu 20.04 using the Erase Disc method with the installer.

I'm wondering if there are any possible security issues related to using this laptop now. (For example, could someone set up a HDD so that it had an un-erasable partition that included a program with keylogger or something. I have no idea if that's possible. Just imagining....) If so, is there anything I can do to mitigate/remove those possible security issues?

Thank you.
↧
↧

[ubuntu] Unable to install Ubuntu 20.04

May 22, 2020, 11:42 pm
↧

[ubuntu] Upgrade to specific version

May 23, 2020, 2:20 am
$
0
0
Hi,

I currently have Ubuntu 18.04 on my PC and I want to upgrade to Ubuntu 18.04.4 but if I use "do-release-upgrade" it will install Ubuntu 20.04.
Is there a way to choose the version I upgrade to?
↧

Problems with Ubuntu 20.04 dual boot

May 23, 2020, 12:18 pm
$
0
0
Hello!

I have dual boot for Ubuntu and Windows. I tried to Upgrade Ubuntu from 19.10 to 20.04 but the system crashed during upgrade.

I tried to re-install Ubuntu using a bootable USB Drive maintaining all files and software, yet this message appeared:

"No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail."

I run GParted from the USB Drive and this is my actual configuration:

Captura de pantalla de 2020-05-23 19-03-48.jpg

According to GParted, the /dev/sda1 partition is a FAT32 partition with boot flag.
I also run tboot-repair and got the following results shown below. These results are available at: https://paste.ubuntu.com/p/KNfh6jks6n/ . Thank you for your help.
Juan

boot-repair-4ppa123 [20200523_1822]

============================== Boot Info Summary ===============================

=> No boot loader is installed in the MBR of /dev/sda.
=> Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________ ________________________

File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Boot/fbx64.efi
/efi/Boot/mmx64.efi /efi/ubuntu/grubx64.efi
/efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi
/efi/ubuntu/grub.cfg /efi/HP/BIOSUpdate/CryptRSA.efi
/efi/HP/BIOSUpdate/HpBiosMgmt.efi
/efi/HP/BIOSUpdate/HpBiosUpdate.efi
/efi/HP/SystemDiags/CryptRSA.efi
/efi/HP/SystemDiags/HpSysDiags.efi
/efi/HP/SystemDiags/SystemDiags.efi
/efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi

sda2: __________________________________________________ ________________________

File system:
Boot sector type: -
Boot sector info:

sda3: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 10
Boot files: /Windows/System32/winload.exe

sda4: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sda5: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD

sda6: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /etc/fstab

sdb1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 6.04
Boot sector info: Syslinux looks at sector 32784 of /dev/sdb1 for its
second stage. The integrity check of Syslinux failed.
No errors found in the Boot Parameter Block.
Operating System:
Boot files: /boot/grub/grub.cfg /syslinux.cfg
/efi/BOOT/grubx64.efi /efi/BOOT/mmx64.efi /ldlinux.sys


================================ 5 OS detected =================================

OS#1: Ubuntu 20.04 LTS on sda1
OS#2: Ubuntu 20.04 LTS on sda3
OS#3: Ubuntu 20.04 LTS on sda4
OS#4: Ubuntu 20.04 LTS on sda5
OS#5: Ubuntu 20.04 LTS on sda6

============================ Architecture/Host Info ============================

CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Ubuntu 20.04 LTS, focal, x86_64)


===================================== UEFI =====================================

BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot enabled.

efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 2001,0000,3000,0001,2002,2004
Boot0000* ubuntu HD(1,GPT,fb7dc12e-799b-442e-8006-ed674c7e24ad,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Windows Boot Manager HD(1,GPT,fb7dc12e-799b-442e-8006-ed674c7e24ad,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS..... ....x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...H................
Boot0002* USB Hard Drive (UEFI) - SanDisk PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,MBR,0x2d1542,0x800,0x1ca3800)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot3000* Internal Hard Disk or Solid State Disk RC



============================= Drive/Partition Info =============================

Disks info: __________________________________________________ __________________

sda : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes

Partitions info (1/3): __________________________________________________ _______

sda1 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, not-far
sda3 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, farbios
sda4 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, farbios
sda5 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, farbios
sda6 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, farbios

Partitions info (2/3): __________________________________________________ _______

sda1 : is---ESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda3 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda4 : isnotESP, fstab-without-efi, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sda5 : isnotESP, fstab-without-efi, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sda6 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot

Partitions info (3/3): __________________________________________________ _______

sda1 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda3 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda4 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda5 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda6 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda

fdisk -l (filtered): __________________________________________________ _________

Disk sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: EB87A399-A93F-48A1-B705-52E1E8EAB40D
Start End Sectors Size Type
sda1 2048 534527 532480 260M EFI System
sda2 534528 567295 32768 16M Microsoft reserved
sda3 567296 632883683 632316388 301.5G Microsoft basic data
sda4 935659520 937666559 2007040 980M Windows recovery environment
sda5 937666560 976762879 39096320 18.7G Microsoft basic data
sda6 632885248 935659519 302774272 144.4G Linux filesystem
Partition table entries are not in disk order.
Disk sdb: 14.33 GiB, 15376318464 bytes, 30031872 sectors
Disk identifier: 0x002d1542
Boot Start End Sectors Size Id Type
sdb1 * 2048 30031871 30029824 14.3G c W95 FAT32 (LBA)

parted -lm (filtered): __________________________________________________ _______

sda:500GB:scsi:512:4096:gpt:ATA ST500LT012-1DG14:;
1:1049kB:274MB:273MB:fat32:EFI system partition:boot, esp;
2:274MB:290MB:16.8MB::Microsoft reserved partition:msftres;
3:290MB:324GB:324GB:ntfs:Basic data partition:msftdata;
6:324GB:479GB:155GB:ext4::;
4:479GB:480GB:1028MB:ntfs:Basic data partition:hidden, diag;
5:480GB:500GB:20.0GB:ntfs:Basic data partition:hidden, msftdata;
sdb:15.4GB:scsi:512:512:msdos:SanDisk Cruzer Blade:;
1:1049kB:15.4GB:15.4GB:fat32::boot, lba;

blkid (filtered): __________________________________________________ ____________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 5E5A-B8FB fb7dc12e-799b-442e-8006-ed674c7e24ad EFI system partition
├─sda2 31dc4588-fe7e-48c1-8145-dee431ba1ef1 Microsoft reserved partition
├─sda3 ntfs E8B45E93B45E63DA 727b367e-059a-46b7-a1b9-8a6200e714c8 Windows Basic data partition
├─sda4 ntfs 5A1E46B81E468D47 2f6648a5-9486-4ed7-a0cb-fb06e467cf17 Windows RE tools Basic data partition
├─sda5 ntfs F81EB5EA1EB5A1D4 f82be1a4-df13-450a-b6e6-6e53adddd16f RECOVERY Basic data partition
└─sda6 ext4 3033201f-8e42-4738-9b52-a9add911f2a0 70a7fb96-9146-4835-b561-d1af53026211
sdb
└─sdb1 vfat 126C-81E3 002d1542-01 UBUNTU 20_0

df (filtered): __________________________________________________ _______________

Avail Use% Mounted on
sdb1 11.8G 18% /cdrom

Mount options: __________________________________________________ ________________

sdb1 ro,noatime,fmask=0022,dmask=0022,codepage=437,ioch arset=iso8859-1,shortname=mixed,errors=remount-ro

===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================

search.fs_uuid 581c463b-27d9-4451-b9b9-580783e441a0 root hd0,gpt6
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

========================== sda6/etc/fstab (filtered) ===========================

# <file system> <mount point> <type> <options> <dump> <pass>
/swapfile none swap sw 0 0

====================== sdb1/boot/grub/grub.cfg (filtered) ======================

Ubuntu
Ubuntu (safe graphics)
OEM install (for manufacturers)
Boot from next volume
UEFI Firmware Settings

========================= sdb1/syslinux.cfg (filtered) =========================

DEFAULT loadconfig

LABEL loadconfig
CONFIG /isolinux/isolinux.cfg
APPEND /isolinux/

==================== sdb1: Location of files loaded by Grub ====================

GiB - GB File Fragment(s)
?? = ?? boot/grub/grub.cfg 1

================== sdb1: Location of files loaded by Syslinux ==================

GiB - GB File Fragment(s)
?? = ?? syslinux.cfg 1
?? = ?? ldlinux.sys 1


Suggested repair: __________________________________________________ ____________

The default repair of the Boot-Repair utility will purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of
sda1,
using the following options: sda1/boot/efi,
Additional repair will be performed: unhide-bootmenu-10s use-standard-efi-file



Final advice in case of suggested repair: ______________________________________


Please do not forget to make your UEFI firmware boot on the Ubuntu 20.04 LTS entry (sda1/efi/****/shim****.efi (**** will be updated in the final message) file) !
↧
↧

[lubuntu] Brother scanner not working in lubuntu version 20.04

May 23, 2020, 4:06 pm
$
0
0
Hi every one ,

I tried install lubuntu 20.04 very good performance but I found one issue with my Brother Scanner installation which it did not work in version 20.04 but it works in version 19.10 (without any change or install any script) .

Can some one help me to solve the issue ???
↧

[ubuntu] 20.04 Boots up with wrong user, NOT admin

May 23, 2020, 6:27 pm
$
0
0
I've never seen this before, after doing a "sudo shutdown -r now" or a reboot as root, the result is my wife's account comes up. Check the user accts and I'm still the admin. I was playing with Virtual box, wanting to speed in up. When starting MS 10, I received an error about AMD-V disabled in BIOS, hence a restart. Everything I change in VB was put back. I should have not touch anything to day. LOL

I just installed 20.04 yesterday.
↧

Upgrade without installing boot loader

May 24, 2020, 5:11 am
$
0
0
While running Ubuntu 19.10 64 bit. i was offered an upgrade to Ubuntu 20.04. Offer accepted. Shortly after the upgrade started it stopped with the message

Quote:
EFI System Partition (ESP) not usable

Your EFI System Partition (ESP) is not mounted at /boot/efi. Please ensure that it is properly configured and try again.
Here's the deal. I don't care if the EFI or ESP is not usable. I don't want a bootloader installed. This is a multi boot system with 5 or 6 other Linux installations and I am using rEFind to boot the computer.

Don't want. Don't need. We do this the way I want it done or we format the partition and install something else.

How can I upgrade without installing a bootloader?

10 minutes later:

I manually mounted /boot/efi (was disabled in /etc/fstab by me) and am attempting upgrade through the command line. Installation of the bootloader, if we get that far, will fail, but that is OK. We shall see.

And about 30 minutes later still:

Well I answered my own question. The upgrade completed just fine. I'm editing this post from Ubuntu 20.04. The upgrade tried to install grub 3 times and failed. I chose to continue anyway even though "your system may be rendered unbootable" and all is well.
↧
Search

Crashed my laptop when trying to install ubunru20.04

May 24, 2020, 12:20 pm
$
0
0
I have an Acer Aspire V5-571G of about 2012(?) and I wanted to install Ubuntu 20.04 alongside a Windows 10 installation. During installation I selected the empty partition to install ubuntu upon. There was no EFI partition and the laptop is not "UEFI aware". When Installation was for 3/4 completed, the installer remarked that there was an error and hung. When I boot I get at the grub> command prompt. I can ls the partitions but when I try to boot from windows I get the error that I have to load the kernel first. What is the adviced way to proceed in this situation?
↧
↧

NVIDIA xorg.conf alternative

May 24, 2020, 1:28 pm
$
0
0
I stumbled upon this NVIDIA config enhancement yesterday and I believe it should be added to the Ubuntu 20.04 repo packages for installing the NVIDIA binary driver. In addition to creating both the directory and file, it should be documented in the release notes that user additions to the NVIDIA configuration should be made to this file, instead of replacing it with a custom '/etc/X11/xorg.conf' file as we have traditionally done.

The driver options below can be included for increased performance:

/etc/X11/xorg.conf.d/20-nvidia.conf

Code:
    Section "Device"
            Identifier "My GPU"
            Driver "nvidia"
            Option "NoLogo" "1"
            Option "RenderAccel" "1"
            Option "TripleBuffer" "true"
            Option "MigrationHeuristic" "greedy"
    EndSection
↧

Cryptsetup: lvm not available after BIOS update

May 24, 2020, 7:04 pm
$
0
0
Hi everyone,

I'm a bit of a newbie and haven't figured out how to fix this problem: I recently installed a BIOS update but afterwards, when I try booting into ubuntu, I get this error: "cryptsetup (nvme0n1p7_crypt): lvm is not available".

For background:
-Lenovo machine
-dual boot with Windows
-I'm able to get past the screen that asks me to choose between booting into Windows or Ubuntu
-had installed ubuntu onto an encrypted partition, following the steps in this I believe https://www.hecticgeek.com/2012/10/h...-installation/
-I installed the BIOS update from Windows, and actually also had problems with booting into Windows after the update (was stuck at "Preparing Automatic Repair") but eventually got that fixed and I'm now able to boot into Windows fine

Searching for fixes, one included reinstalling lvm which I tried from the live ubuntu installation on the USB drive I had used, but I was able to install it. Wondering if anyone might have any tips before I have to reinstall ubuntu altogether? Thanks in advance!
↧

[ubuntu] GRUB Boot repair failed

May 25, 2020, 12:17 am
$
0
0
Hey guys
1. I have installed GRUB with 2 OS Ubuntu Bionic and Windows 10. Everything was working fine for a while with booting to different OS
2. I have moved Windows up to be the first. Still was working
3. I have reinstalled Windows 10 and GRUB disappeared. I heard about that and was ready to (I supposed)
4. I tried to repair GRUB using https://help.ubuntu.com/community/Boot-Repair and attempt has failed.
5. Here is the report http://paste.ubuntu.com/p/SF2szj9NWB/.

Can anybody, please, help with that?
↧

Grub not loading most times (win10 + ubuntu 18.04)

May 25, 2020, 2:03 am
$
0
0
Bit of a newbie in Boot Partition things, but got a weird issue happening:

Machine is a refurbished Dell Latitute E5430 with a 180Gb SSD, came with pre-installed Win10 - all is fine her, works great.
I then installed ubuntu 18.04 and could safely get to the GRUB dual-boot menu and can now access both systems fine.

However, most times (not always), a turn on of this machine now leads to a loop on the dell logo screen (no GRUB menu).
I can only boot from a usb stick then. I now have one ready with boot-repair that just sort of fixes the MBR/GRUB thing. All data and both OS are then accessible as normal -even hybernated ones.

Ideally I would like to fix this permanently, but the solution presented by boot-repair ("The boot files of [Ubuntu 18.04.4 LTS] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk)") is something I'm somewhat afraid to do as I can see conflicting results in a google search

boot-repair results are in:
http://paste.ubuntu.com/p/6xfcXmQRS7/

Can someone please just point me in the right direction to fix this? Is the solution from boor-repair "safe"? Shall I just do it?

Thanks,
↧
↧

Disk encryption key never asked by Ubuntu

May 25, 2020, 4:16 am
$
0
0
Hi all

I've just installed Ubuntu 20.04, with full disk encryption.

Everything's ok, except that I don't have (when I start the system) to enter the encryption key I've given when installing the OS.

Is it a known issue ? I don't find on internet.

KR
↧

[ubuntu] Problems installing Ubuntu on Acer Aspire 5 A514-52

May 25, 2020, 12:43 pm
$
0
0
I'm having difficulty installing Ubunto on the a new Acer Aspire 5 A514-52

During installation it tells me the laptop has RAID and points me in the direction of instructions here:
https://discourse.ubuntu.com/t/ubunt...-enabled/15347

I follow the intructions and as it suggests might happen, it still has problems rebooting. To resolve this it gives instructions on doing something to the boot partition but here it is difficult to follow or I just don't understand. I tried to edit the boot partition but it still doesn't boot.

I here attach some images

IMG-0221.jpgIMG-0226.jpgIMG-0229.jpgIMG-0228.jpgIMG-0225.jpg

Any guidance on what I need to do to get through this problem appreciated.

Tom
Attached Images
↧
Search

20.04 login with strange screens

May 26, 2020, 9:39 am
$
0
0
I have been running a Vostro 460 with a 60GB SSD and 16GB of memory with Linux Mint 18 for the last 1.5 years. I wanted to try Ubuntu 20.04 and possibly change to it for good. I downloaded the iso, checked the SHA, and burnt a DVD.

The installation did no go well. Upon booting the trial, I could only see a weirdly distorted screen with dark patches and text showing with large fonts on a diagonal. I was not able to click on anything. I ended up turning the computer off. I tried installing and got the same behavior. I decided to make a usb boot stick. Checked the sha and got the same strange behavior. I googled my problem and no one seemed to have anything like it. There were a number of boot problems that were solved by changing boot settings. Unfortunately my machine didn't give me any such options, only boot order was able to be changed.

I reinstalled Linux Mint. Worked fine.

Next, I downloaded 20.04 server and installed. This worked fine. I installed a Gnome desktop on the server and got the same strange behavior.

It seems to me that my computer is allergic to 20.04.

Any suggestions? Thanks in advance.
↧

[ubuntu] Can't run cool-retro-term

May 26, 2020, 10:03 am
$
0
0
Hello.

So I recently wanted to run cool-retro-term on my Windows installation, but it's a Linux app.

So I went and installed Linux subsystem for Windows, Ubuntu 20.04 shell and Xming (I need an X-server, right?)

I compiled cool-retro-term, but, when I try to run it, this happens:

Code:
seal@mymachinename:/mnt/c/Users/myusername/coolretroterm/cool-retro-term$ ./cool-retro-term
qt.qpa.xcb: X server does not support XInput 2
failed to get the current screen resources
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-seal'
QQmlApplicationEngine failed to load component
qrc:/main.qml:137 Type TerminalContainer unavailable
qrc:/TerminalContainer.qml:23 Type PreprocessedTerminal unavailable
qrc:/PreprocessedTerminal.qml:97 Cannot assign to non-existent property "blinkingCursor"


Cannot load QML interface
seal@mymachinename:/mnt/c/Users/myusername/coolretroterm/cool-retro-term$
Please help or redirect me to a different forum if this one doesn't deal with Ubuntu on WSL.
↧
↧

[ubuntu] Ubuntu 20.04 Network installation failing using Foreman and internet repos

May 26, 2020, 12:06 pm
$
0
0
Greetings,

I am getting "No kernel modules were found" while trying to install Ubuntu 20.04 using Foreman & Internet repo. If I use same settings for 18.04 (foreman & internet repo), it works. I have attached error screenshot as well.

Please let me know if I am missing something or if Ubutnu 20.04 is not yet ready for network based installations. Also, I could not find netboot.tar.gz file for this release (as of mid-May 2020).

Hope to get some solution/workaround from those who are successfully able to install Ubuntu 20.04 using network install. :)

Cheers..

Attached Images
↧

[ubuntu] why amd64 and i386?

May 26, 2020, 12:25 pm
$
0
0
I have one machine with ubuntu 20.04 where all packages are installed as both amd64 and i386. On another machine only amd64 packages are installed.
Can I get rid of the i386 packages?
↧

Questions Aboout Failed mysql Installation (20.04)

May 26, 2020, 12:32 pm
$
0
0
This is a new installation (not an upgrade). The OS runs from a USB thumbdrive (32G). I installed mysql-client, and then tried to install mysql-server but the installation failed. Here's the error.log:

https://paste.ubuntu.com/p/zhVbd5n75r/

A couple of deviations are the /var and /tmp directories are links to directories on a harddrive (to avoid excessive read/write to the thumbdrive). The ownership and permissions of the linked-to directories are the same as original. Correction: /var was not linked!

From the error.log file:
Code:
2020-05-26T18:41:56.297387Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory.
Not sure why this comes up as the actual /tmp directory has permissions "drwxrwxrwt" with root:root ownership.

From the error.log file:
Code:
2020-05-26T18:41:06.571075Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
How do I turn it off? If I don't and successfully install with no root password, can I then run mysql as root with the command "mysql -u root"?

From the error.log file:
Code:
2020-05-26T18:41:55.732794Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
Is this a result of having /var as a linked directory (Correction: It's not)? I'd rather not, but I could create a couple of harddrive partitions and mount them on /var and /tmp.
↧
Viewing all 26379 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>