I'll add to what was said by others, but about [I] and [No]
When building there is a cache. Sometimes you remove make dependencies, which removes the program but keeps a copy in cache. (There are other ways to remove a program and still keep it in cache)
[I] means it will clen build all installed packages and use the cache for those that are not installed but were present.
[No] means it will leave installed packages untouched but will rebuild those that are in cache before reinstalling them.
Hope that solves it. And as said before - in 99.99% cases None is good enough.
USB 1 and 2 use a set of 4 pins. It can only use those 4pins to transmit data.
USB 3 uses 9 pins : the 4 original pins and 5 more pins. It is backwards compatible with USB 1 and 2 because it can only use those four pins instead of the full array.
USB-C, however, uses 24 pins (2*12 pins to be exact). However, what makes no sense, is when using a USB-A to USB-C cable it does work only in one direction : from USB-A to USB-C.
But rest assured, you are not alone onnthis issue. I've had it, even when I did not want to tranfer data but just power : it does not work, whether on Windows or Linux...
There was a point in time where every byte of data saved was important : when transferring to a floppy disk, when uploading/downloading via 56.6K / 128K / 256K.
Now that we live in a world where a 128Gb pendrive is worth 12€, a 1Tb hard drive is less than 50€ and internet speeds go almost at 1Gbps... the default archive manager is sufficient.
Okay first question is : is MATE absolutely necessary ?
If not, I would advise you to switch to a distro that uses GNOME or KDE. I'd go for Zorin OS which is really perfect for anyone beginning on Linux.
In any case, I have a solution that should work no matter the device. It requires you to have libinput and libinput-gestures installed (rather than fusuma which I found buggy and laggy)
This is no help, I know, but... OpenSuSE behaves weirdly. On my old laptop every distro would work, exception made for SuSE who wouldn't even boot from LiveCD.
You can switch desktops horizontally with three or four fingers
You can only switch desktops vertically with three fingers
By default, four fingers vertical opens present windows or something like that
To be able to use four fingers swipe up, you need to disable present windows first.
Go to settings > workspace behaviour > desktop effects and unclick desktop grid and present windows (in the hope that you have no use for them)
Then you need to install evemu and libinput-gestures (if you're on Arch, it's in the pacman repo and the AUR respectively)
Once you have it installed, run in your terminal evemu-record. It will list all of your devices. Shut down the program with Ctrl + C and look at the event for your keyboard. Once this is done note it down.
Create a new file
nano sendkey.sh
Copy the content of this code in the new file but replace EVDEVICE=/dev/input/event4 with your keyboard.
#!/bin/bash
# sendkey.sh
EVDEVICE=/dev/input/event4
for key in $@; do
evemu-event $EVDEVICE --type EV_KEY --code KEY_$key --value 1 --sync
done
# reverse order
for key in $@; do
evemu-event $EVDEVICE --type EV_KEY --code KEY_$key --value 0 --sync
done
Ctrl +O then CTRL + X to save then quit nano. Once it is done run this command : chmod +x sendkey.sh then open the gestures app and start mapping away. The interface is very intuitive. What you want to do is click on the little + at the top bar then select the motion you want to bind (in your case swipe + up + 4 fingers) and in the command at the bottom you write /home/YOURUSERNAME/sendkey.sh LEFTMETA W
And there it is. You can map pretty any keybind to any event with this. Hope this helps.
I'll add to what was said by others, but about [I] and [No]
When building there is a cache. Sometimes you remove make dependencies, which removes the program but keeps a copy in cache. (There are other ways to remove a program and still keep it in cache)
[I] means it will clen build all installed packages and use the cache for those that are not installed but were present.
[No] means it will leave installed packages untouched but will rebuild those that are in cache before reinstalling them.
Hope that solves it. And as said before - in 99.99% cases None is good enough.