You should use a syntax like the following:
Exec=sudo bash '/mnt/your-path/your-file.bash'
[...]
Terminal=true
TerminalOptions=
Not using exec as root
: sudo
at the beninning of the command line is enough.
a thoughtful use of digital
You should use a syntax like the following:
Exec=sudo bash '/mnt/your-path/your-file.bash'
[...]
Terminal=true
TerminalOptions=
Not using exec as root
: sudo
at the beninning of the command line is enough.
If your SSD has become slow, it could depend from the swap file: f.e. in fstab the ssd swap UUID could be wrong (after some partitions changes in your SSD).
You can fix this by giving to the swap partition the correct UUID.
The new KDE Plasma releases require a slight change in your svg files, if you have a radiant gradient (no problems instead with the linear ones).
You have to specify the radialGradient cx, cy and r, like in the following example:
<?xml version="1.0" standalone="no"?>
<svg viewBox="0 0 22 22" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<defs>
<radialGradient id="gradient" cx="0.50" cy="0.50" r="0.45">
<stop offset="0%" stop-color="#fbfbf0"></stop>
<stop offset="80%" stop-color="#bc5a1f"></stop>
</radialGradient>
</defs>
<g>
<path fill="url(#gradient)" d="M11 .008l3.4 6.888L22 8l-5.5 5.361 1.298 7.57L11 17.357l-6.798 3.574 1.298-7.57L0 8l7.6-1.104z" />
</g>
</svg>
Because a svg with this other following code won’t work (will be invisible)
<?xml version="1.0" standalone="no"?>
<svg viewBox="0 0 22 22" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<defs>
<radialGradient id="gradient">
<stop offset="0%" stop-color="#fbfbf0"></stop>
<stop offset="80%" stop-color="#bc5a1f"></stop>
</radialGradient>
</defs>
<g>
<path fill="url(#gradient)" d="M11 .008l3.4 6.888L22 8l-5.5 5.361 1.298 7.57L11 17.357l-6.798 3.574 1.298-7.57L0 8l7.6-1.104z" />
</g>
</svg>
Recently Ubuntu-based linux SO doesn’t remove automatically old kernels, with the command
sudo apt-get autoremove --purge
This because kernels, even automatically installed, are considered manually installed, and so they are not automatically removed.
To solve this, you should do beforehand this command
sudo apt-mark auto $(apt-mark showmanual | grep -E "^linux-([[:alpha:]]+-)+[[:digit:].]+-[^-]+(|-.+)$")
With this command you say that all kernels are automatically installed, and therefore the previuous command (sudo apt-get autoremove –purge) will work.
It could happen that a new kernel doesn’t work with your nvidia (geforce) grafical card. The problem could de the linux-modules, such as linux-modules-nvidia-460-5.8.0-53-generic.
You can check it by the following command
dpkg --list | egrep -i --color 'linux-image|linux-headers|linux-modules' | awk '{ print $2 }'
To solve this, if you find that the last kernel does’t have a matchintg nvidia module, you have to install manually that module
sudo apt-get install linux-modules-nvidia-460-5.8.0-53-generic
In Linux you can use ComposeKey, setting it for example (in System settings) as RightCtrl (the right-Ctrl key). RightCtrl is better than AltGr in Italian keyboard, to keep AltGr for some characters like ‘[‘, or ‘]’, or ‘@’, or ‘#’, otherwise unaccessible.
In that way, when you type 1) first RightCtrl 2) then ^ 3) then o, you will get ô. You don’t need to press simultaneously all the keys.
To sum up, the main simbols :
You could (but not necessarily) have problems (no sound at all) in Linux if you install timidity daemon. Therefore, to fix it, you should install only timidity, without timidity-daemon.
It’s a bug which affects only one user and not the whole graphical desktop, but only the “desktop” in a narrow sense.
A workaround can be to rename the .config folder (to something like .config.old) so that you can get anew your whole graphical desktop and then maybe you could copy (prudently) one by one your config files (from .config.old to the new .config folder).
To connect Plasma EventCalendar with a caldav, you must have Korganizer (with caldav sync) and PIM-routine working.
You can use a zsh script (let we call “rename-identical-files.bash”) with a code like the following
#! /bin/zsh -
zmodload zsh/stat || exit
typeset -A size_to_name
model_folder=${1?}
CDPATH= cd -P -- "$model_folder" || exit
for f in *(ND.); do
stat -LA size +size -- $f &&
size_to_name[$size]=$f &&
print -r "# File of size $size should be named ${(q)f}"
done
cd $OLDPWD || exit
for f in *(ND.); do
stat -LA size +size -- $f &&
(($+size_to_name[$size])) &&
[[ $f != $size_to_name[$size] ]] &&
print -r mv -i -- ${(qq)f} ${(qq)size_to_name[$size]}
done
#usage: that-script /model-folder-path
then you can go to the folder where you want rename the files and do this terminal command:
~/rename-identical-files.bash /path/to/model/folder
in this way, before executing the command, you can see what could happen afterwards. If it’s all ok, do the command:
~/rename-identical-files.bash /path/to/model/folder | sh