Psychotechnopath's questions

Today I created a link to a folder, like so:

Then, I looked up the location of the original icon (See the red M below the link I just created). Then I right clicked the "Link to MEGA", and clicked on the icon.

I navigated to the original icon location, and changed the "Link to MEGA" icon (The plain Ubuntu folder) to the original MEGA icon, like so:

As is seen in the screenshot this seems to be working fine! However, when I then drag and drop this Link to the Desktop folder, the icon does not display properly on my desktop (As is seen below (Excuse me for my crappy paint skills haha)

Does anyone know why this is happening and how do I fix it?

What is the most elegant way to create desktop shortcuts (e.g. to folders, applications, or documents) in Ubuntu 20.04?

I am trying to install MegaSync on my new ubuntu 20.04 installation =). They already have a version out for ubuntu 20.04. (See https://mega.nz/sync). However, when I try to install it with sudo dpkg -i megasync-xUbuntu_20.04_amd64.deb I get a big list of dependency errors. It seems to me Megasync is missing some packages. However when I open the software updater it says there are no new updates that need to be done. I am not so experienced with Ubuntu yet so any help would be greatly appreciated.

Selecting previously unselected package megasync.
(Reading database ... 195014 files and directories currently installed.)
Preparing to unpack megasync-xUbuntu_20.04_amd64.deb ...
Unpacking megasync (4.3.1-15.1) ...
dpkg: dependency problems prevent configuration of megasync:
 megasync depends on libc-ares2 (>= 1.7.4); however:
  Package libc-ares2 is not installed.
 megasync depends on libcrypto++6; however:
  Package libcrypto++6 is not installed.
 megasync depends on libmediainfo0v5 (>= 0.7.56); however:
  Package libmediainfo0v5 is not installed.
 megasync depends on libqt5core5a (>= 5.12.2); however:
  Package libqt5core5a is not installed.
 megasync depends on libqt5dbus5 (>= 5.0.2); however:
  Package libqt5dbus5 is not installed.
 megasync depends on libqt5gui5 (>= 5.8.0) | libqt5gui5-gles (>= 5.8.0); however:
  Package libqt5gui5 is not installed.
  Package libqt5gui5-gles is not installed.
 megasync depends on libqt5network5 (>= 5.1.0); however:
  Package libqt5network5 is not installed.
 megasync depends on libqt5svg5 (>= 5.6.0~beta); however:
  Package libqt5svg5 is not installed.
 megasync depends on libqt5widgets5 (>= 5.11.0~rc1); however:
  Package libqt5widgets5 is not installed.
 megasync depends on libzen0v5 (>= 0.4.31-2~); however:
  Package libzen0v5 is not installed.

dpkg: error processing package megasync (--install):
 dependency problems - leaving unconfigured
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu2) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
 megasync

I'm experiencing a very strange issue. I have a new system, with two drives:

• A samsung 970 plus m.2 SSD
• A samgung 860 evo regular SSD

I've installed windows on the samsung 970 drive. And I wanted to install Ubuntu on the samsung 860 drive. I did this, with a flash-drive Ubuntu 18.04.4 installation, with MBR as partition scheme.

However, when I use an MBR partition scheme I need to enable CSM (compatability support mode) in my UEFI BIOS, every time I want to boot Ubuntu.So I tought; let's reinstall ubuntu, but with a GPT partition scheme, so I do not need the CSM-mode.

When I launch the Ubuntu installer; I can see my drive with windows, and the empty SSD (Sorry for the crappy pictures):

As you can see I created a ext4 Partition table on the /dev/sda device; which corresponds to my samgung 860 SSD. Then, I select /dev/sda (Samsung SSD 860 (500.1GB) As the Device for boot loader installation, and I select the dev/sda1 location in the menu above as the place where to install Ubuntu. Ubuntu then starts installing in the regular way.

Now comes the strange part. When the installer is finished and I reboot my PC, I can only acces Grub through my samsung 970 ssd. The bios does not show me the 860 SSD, only an option which says "Ubuntu on samsung 970". When I select that option, I get grub, and I am able to start up Ubuntu. However, Ubuntu does not seem to reside on the 970 drive but in fact on the 860 drive. It seems that only the bootloader is installed on the 970??

Can anybody explain me what has happened here? Am I making a thinking mistake somewhere?

I used to prevent these kinds of issues by simply disconnecting the sata-cables of SSD's I was not currently using. But with the new M.2 SSD's (which are deeply embedded in the mainboard, below my graphics card and a heatsink), this is no easy job.

What I would like is two completely seperate systems on two seperate drives.

I am experiencing weird behavior on a desktop PC with an ASUS X570-F ROG-strix gaming motherboard with the AMD Ryzen 9 3900X (which has no integrated graphics).

I've recently upgraded my hardware, and when I try to boot from an USB-stick which previously worked fine, I do get GRUB. When I then select the option "Try Ubuntu", it seems to crash; I get this (rather uninformative) screen:

I have already tried numerous solutions, but I am out of ideas. Thing I've tried:

• Different USB sticks. Problem persists.
• Different Ubuntu versions (Version 18.04.4 LTS, Version 19.10). Problem persists

I am using RUFUS to create a bootable .iso file on my USB-stick. When I try these USB-sticks in my laptop, I can use the option to Try Ubuntu. It then loads a live version of Ubuntu.

The specs of my new PC:

AMD Ryzen 9 3900X
Gigabyte NVIDIA 2070 RTX
32 GB of 3600 MHz G.Skill RAM
ASUS X570-F ROG-strix gaming motherboard
Samsung 970 Evo plus M.2 SSD 500 GB with windows installed
Samsung 860 Evo 500 GB with nothing on it (Ideally I want to install Ubuntu on this SSD).

I am out of ideas! Any help or tips would be greatly appreciated

I am experiencing some trouble with my graphical card (Sometimes my GPU crashes and I have to reboot my PC). I suspect it might have something to do with a faulty driver that is chrashing. While looking into my drivers in Ubuntu, I noticed a lot are available:

What are the differences between all these drivers, which one should I pick and why?

I am asking this because my GPU keeps crashing (Also on windows), therefore I might need another driver than the default one. Trying to automate this process with sudo ubuntu-drivers autoinstall throws the following error:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-driver-435 : Depends: libnvidia-gl-435 (= 435.21-0ubuntu0.18.04.2) but it is not going to be installed
                     Depends: nvidia-dkms-435 (= 435.21-0ubuntu0.18.04.2) but it is not going to be installed
                     Depends: xserver-xorg-video-nvidia-435 (= 435.21-0ubuntu0.18.04.2) but it is not going to be installed
                     Depends: libnvidia-cfg1-435 (= 435.21-0ubuntu0.18.04.2) but it is not going to be installed
                     Depends: libnvidia-ifr1-435 (= 435.21-0ubuntu0.18.04.2) but it is not going to be installed
                     Depends: libnvidia-fbc1-435 (= 435.21-0ubuntu0.18.04.2) but it is not going to be installed
                     Recommends: libnvidia-decode-435:i386 (= 435.21-0ubuntu0.18.04.2)
                     Recommends: libnvidia-encode-435:i386 (= 435.21-0ubuntu0.18.04.2)
                     Recommends: libnvidia-ifr1-435:i386 (= 435.21-0ubuntu0.18.04.2)
                     Recommends: libnvidia-fbc1-435:i386 (= 435.21-0ubuntu0.18.04.2)
E: Unable to correct problems, you have held broken packages.

I was trying to clone the OS + files on my 500GB HDD to a 250GB SSD. To achieve this, I followed the steps in This question. In step 3, I shrunk the partition of my original HDD to 43GB (The smallest possible), which seemed about right since it did not contain vast amounts of data/programs. In step 8, I was told to re-install GRUB. I did this for the original HDD, by following This link.

However, after resizing and copying, nor my original HDD or my new SSD boots up. The original HDD does show the purple Ubuntu loading image, but gives some strange text afterwards (See picture below). The SSD does not boot at all (But I also didn't try to re-install GRUB here).

When I open Gparted from a flash-drive with Ubuntu again, all the partitions seem to be intact. Also, after restarting the HDD many times, I was able to get into some kind of basic linux terminal by pressing ctrl + alt + F2. I was unable to install a repair-bootloader from there, it said I did not have enough space (Probably because I resized my partition to the smallest possible size).

With some basic cd ls and pwd commands I was able to check if my files are intact, and that seems to be the case.

How can I fix the issue, and make ubuntu boot normally again?

I am trying to clone my whole Ubuntu OS to a new SSD. I was following This video. To check to which disk I had to clone, I ran the lsblk command.

According to this, It seems that sda is my current HDD, and sdb is my current SSD. I then tried to run the following command: dd if =/dev/sda of=/dev/sdb. But when I did this, it ran for a while and then gave me an error, that the sdb drive does not have sufficient memory. What I suspect has happened is that the dd command tried to clone my entire mounted volume on the HDD (So the whole 495GB, including empty space) to my 250GB SSD. This is not what I meant to do, so now my question is:

How do I clone my Ubuntu OS + relevant files, but not empty space to my new SSD?

(BTW I've already re-formatted my SSD after my failed attempt to clone)