pdflatex not found. Please select a different –pdf-engine or install pdflatex

If you use pandoc to generate a pdf file from a markdown file, you may have this warning message :

pdflatex not found. Please select a different –pdf-engine or install pdflatex

On Ubuntu 19.04, after an initial install using the distribution package manager, no pdf engine is installed.

Using the apt-file utility and searching for pdflatex, texlive-latex-base package includes it.
This package texlive-fonts-recommended will bring additional fonts.

To install it :


apt install textlive-latex-base texlive-fonts-recommended

To test the pdf output :


pandoc test.md -s -o test.pdf

Setting up a desktop notification in Ubuntu after login

The following actions have been tested successfully on Ubuntu 19.04

Setting a desktop notification in Ubuntu after login requires creating a Desktop application following the Freedesktop specifications.
All such applications run as a user must be located in $HOME/.config/autostart

The autostart folder may not exist.
If not :

mkdir -p $HOME/.config/autostart

As an example, this desktop application will be named welcome.desktop

Create this file as follows :


touch $HOME/.config/autostart/welcome.desktop

Add the following lines in it :

cat welcome.desktop

[Desktop Entry]
Type=Application
Exec=/home/$USERNAME/Tools/
welcome_msg.sh
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name=myscript
Comment=Startup Script

Create the bash script welcome_msg.sh that will display the notification message :

cat welcome_msg.sh

#!/usr/bin/env bash

notify-send “Good morning ${USERNAME^} !” “Did you check your backups ?”

Make sure that the Exec field in your welcome.desktop file points to your script.

Reboot your Ubuntu machine and log in. Your custom desktop notification will be displayed !

Further readings :

https://cloudkul.com/blog/display-notification-login-ubuntu/

XDG autostart specification

Different ways of autostarting applications in Linux

Desktop Application Autostart Specification

Python auto-completion in Vim with python-jedi on Ubuntu 19.04

python-jedi is a plugin available for Vim that features auto-completion for the Python programming language.
It is available as an Ubuntu package :


apt install vim-python-jedi

To enable it as a user :


vim-addons install python-jedi

or


vam install python-jedi

To start using it in Vim, the keyboard shortcut CTRL+Space is a good start for auto-completing.

Further readings :

jedi autocompletion library for VIM

VIM for development on Stackabuse

javaldx: Could not find a Java Runtime Environment! on Ubuntu 18.04.1

Running LibreOffice from the shell can display this message :

javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package libreoffice-java-common
is installed.
If it is already installed then try removing ~/.libreoffice/3/user/config/javasettings_Linux_*.xml
Warning: failed to read path from javaldx
func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26

This solution suggests installing libreoffice-base ubuntu package to fix it. It will also install libreoffice-java-common package while managing all the required dependencies.
Installing it removes this error message permanently On Ubuntu 18.04.1

NB : This solution works as well for Ubuntu 19.04

Ubuntu 17.10 as VirtualBox guest : missing vboxsf module

Running Ubuntu 17.10 as a VirtualBox guest works fine except for accessing files located on the host.
Only vboxguest and vboxvideo modules are available and loaded.
vboxsf module is missing.
Load the Guest Additions ISO image and let run the installer.

On a fresh new install, you may have this error :

Make sure to install the build-essential package :

apt install build-essential

One completed, reboot your system to make sure the right modules are loaded : vboxguest, vboxvideo, vboxsf

Once logged in, access to a directory located on your host may be denied.
Be sure that your user account is part of the vboxsf local group.
Add yourself :

usermod -aG vboxsf your_login

Log out and log in again. This should be good now