Posts Tagged ‘Ubuntu’
Linux Mint 20 Beta is Ready
Linux Mint announced the immediate BETA release of its upcoming version Linux Mint 20 “Ulyana”.
Scheduled for the end of June 2020, Linux Mint 20 promises plenty of new features in its primary three flavors XFCE, Cinnamon, and MATE.
This beta release is the pre-final version to iron out last-minute bugs and is available for download immediately.
Before you hit download, here are the upcoming changes in the Linux Mint 20 which you should check out now before your final experience with Linux Mint 20.
What’s New in Linux Mint 20
Linux Mint 20 is dropping support for 32-bit images officially and only to be available as a 64-bit image. That means the older computers will not be able to run the latest Linux Mint. But if you are having an older system setup running Linux 18.x, 19.x – they will continue to run but will not be getting security and other updates when support ends.
It is based on the current Ubuntu 20.04 LTS release and available with three desktop environment variants – Cinnamon, XFCE and MATE.
Linux Mint, Linux Mint Cinnamon, Linux Mint Editions, Linux Mint Mate, Linux Mint Releases, Linux Mint Upgrade
HandBrake 1.3.3 Open-Source Video Converter
Open-source and cross-platform HandBrake 1.3.3 video converter have been released today with several improvements and bug fixes.
This release improves support for MKV files by fixing an issue that made ISO 639-2/B language codes not to be set correctly, which affected Hebrew, Indonesian, Japanese, and Yiddish languages, and improves Intel QSV memory footprint and H.265 memory buffer size as needed by newer Intel Media SDK.
HandBrake 1.3.3 also adds better support for SSA (SubStation Alpha) subtitles by fixing a handling issue of overlapping imported SSA subtitles and improving support for out-of-order SSA subtitles. Also improved is Flatpak support, especially the building efficiency of the Intel QSV Flatpak plugin.
This release comes with support for the latest FFmpeg 4.2.3 open-source and cross-platform multimedia framework, which is needed for decoding and filters, as well as a new patch for improving the cross-compilation of the libdav1d AV1 decoding library included in FFmpeg 4.2 using GCC 10.x or later.
Among other noteworthy changes, HandBrake 1.3.3 improves support for video sources where the pixel format can’t be identified in a timely way, implements logging to identify where hardware support is disabled, and fixes an issue where full-range video files were identified as limited range after conversion when using filters.
Linux Video Converter Mkv To Mp4, Linux Video Converter Ubuntu
Flatpak Linux, Flatpak On Ubuntu
Build Debian Packages From Source
Debian and Debian-based systems like Ubuntu uses Advanced Package Tool, or APT in short, for installing, updating, upgrading and removing software from command line. Usually, the APT package manager stores the list of repositories in the file named /etc/apt/sources.list and in any file with the suffix .list under the directory /etc/apt/sources.list.d/. When we install a package, apt command retrieves the binary or pre-compiled version of the given package from these repositories. In addition to installing binary packages, APT can also lets you to download the source code of a package. So you can then add some features in the source, build the package from the source code, and finally install the modified version of the package. This guide explains how to build debian packages from source on Debian, Ubuntu and other APT-based systems like Linux Mint.
Why should we build a package from source?
There could be many reasons to build a package from source. Here are a few reasons I could think of now:
- Inspect the source code to find a bug.
- Add new features in the packages that aren’t being actively developed any longer.
- Install the most recent version of a package from source. Generally, the packages in the official repositories might be bit old.
- And more importantly – learn to build Debian packages from source.
Build Debian Package From Source Tarball, Build Debian Package From Tarball, Build Debian Packages, Build-essential Package Debian Install, Debian Build Package Install, How To Build Debian Packages, Ubuntu Build Debian Source Package
Fix Broken Packages in Ubuntu
How to Fix Broken Packages in Ubuntu
Apt, Ubuntu’s package manager, is among the most powerful and intuitive, but that doesn’t mean that things can’t go wrong. Occasionally, a package install goes wrong on Ubuntu, and you’re left to pick up the pieces. It’s a good thing Ubuntu’s package utilities, including Apt itself, have built-in functionality to help remedy the situation and get things back to normal.
These tips and tricks should help you get unstuck in most instances. They’re all fairly universal, but every situation is different, so keep that in mind when trying to debug your own situation.
Related: How to Fix Ubuntu Update Errors
With Apt/Apt-Get
Apt has a couple of flags that you can use in order to fix missing dependencies or packages that broke for one reason or another during install. A common use here would be installing a third-party .deb and finding that it had dependencies you didn’t know about. Those dependencies probably won’t be pulled in on their own, and dpkg
will complain that the package is missing in them. In any case, you can try these steps.

First, run an update to make sure that there aren’t newer versions of the required packages.
sudo apt update --fix-missing
Next, you can try forcing Apt to look for and correct any missing dependencies or broken packages. This will actually install any missing packages and repair existing installs.
sudo apt install -f
With DPKG
Another place where error can pop up in package installations is the configuration process. Behind the scenes, dpkg is taking care of this part, not Apt, so it would stand to reason that when a package fails during configuration, dpkg is the tool to turn to in order to fix it.

Start by trying to force dpkg to reconfigure any broken or partially configured packages.
sudo dpkg --configure -a
If that doesn’t solve the problem, you can take a more forceful approach. Start by listing any packages that dpkg marked as requiring a reinstall.
sudo dpkg -l | grep ^..r
You should see the problematic package(s) there. As long as there’s nothing that seems not to belong there, you can force-remove the broken packages.
sudo dpkg --remove --force-remove--reinstreq
When dpkg is done, try to clean up with Apt.
sudo apt clean sudo apt update
With any luck that’ll get you back to where you started. It won’t get you the broken packages that you tried to install, but at least Apt will be functional again.
Related: Ubuntu Software Center Not Working? Here Are the Fixes
Permanent DPKG Lock

There’s a less common issue with ridiculous dpkg locks preventing you from doing anything. Every time you try to use Apt or dpkg, you get an error saying another application already is … when it isn’t. It’s actually easy to delete the lock file preventing you from using Apt and get back to doing what you need to. Sometimes these lock files remain in place after an error occurs in an install, derailing the process and preventing the file from being removed automatically. In this case, you’ll need to do it yourself.
sudo rm /var/lib/apt/lists/lock
For good measure, delete the lock in cache.
sudo rm /var/cache/apt/archives/lock
Conclusion
Hopefully, one of these fixes worked for you, and you’re back working on Ubuntu normally. Remember that the best way to handle a totally out-of-hand situation is to try to return to the way it was before. Don’t try to power through and add more things to solve a breakage by adding more things, unless you know exactly what you’re doing. Chances are you’ll end up with a tangled mess of broken things that’ll be harder to sort out.
Install Paperwork on Ubuntu
Objective
The objective is to install Paperwork on Ubuntu 18.04 Bionic Beaver
Operating System and Software Versions
- Operating System: – Ubuntu 18.04
- Software: – Paperwork 1
Requirements
Privileged access to the operating system
Difficulty
MEDIUM
Conventions
- # – requires given linux commands to be executed with root privileges either directly as a root user or by use of
sudo
command - $ – given linux commands to be executed as a regular non-privileged user
Introduction
Paperwork is a note-taking and archiving alternative to Evernote, Microsoft OneNote, and Google Keep, with the advantage of being FOSS (Free and Open Source Software), meaning it that can be hosted on the user premises, which is a requirement for people and businesses worried about privacy.
Paperwork is comprised of collections
that contain notebooks
of notes
. Notes can be shared with other users. Tags can be assigned to notes that can also have documents attached to them. The user interface has translations to 23 languages. It’s also worth mentioning that there is an API that is useful for integration with other software.
The project web page mentions that version 2 is a major rewrite that is at an early development stage, meaning it’s not usable yet. While we wait for the shiny new version, we’ll cover how to have version 1 running on the latest Ubuntu LTS release.
Version 1 was released in 2014 and is written in the LEMP stack (Linux, Nginx, MySQL, PHP) using Laravel 4 framework and other Web technologies, like AngularJS and Bootstrap.
For this article we first tried to build a docker image, using the docker-compose file listed in the project’s Git repository, but the build is broken in multiple ways. We then reverted to the conventional form of installation, adapting the 16.04 manual for installing Paperwork in Ubuntu to version 18.04, and it proved to be a rather long, but easy sequence of steps to follow. The major setback is that 18.04 Bionic Beaver comes with a newer PHP (version 7.2) and the extension mcrypt
has been deprecated and moved to PEAR (a repository of PHP code) — but you will see that this difficulty can be easily overcome.
Before committing few hours to have your own instance running, it may be worth having a taste of Paperwork at a cloud-hosted provider, namely Sandstorm or Cloudron.
Once you’re ready to install Paperwork, notice that the steps below assume a clean installation of Ubuntu Server 18.04 Bionic Beaver. For Ubuntu Desktop the guide will be almost the same, except for the first step.
Instructions
Add Universe Repository
For Ubuntu Server, you have to add the Universe repository to install some packages (npm, nodejs, php-mbstring). Ubuntu Desktop already has the Universe repository enabled so this step can be skipped.
# add-apt-repository universe
Install package dependencies.
It will download 87.1 MB which will use 449 MB of disk space. Here we notice some differences from the set of packages required for 16.04.
# apt install wget git npm zip libmcrypt-dev mysql-server php-mysql nginx php-fpm curl php-cli php-gd nodejs php-xml php-mbstring php-pear php-dev
Install mcrypt
The mcrypt
PHP extension has long been abandoned and has been moved to PEAR. As it’s a dependency for Paperwork version 1, it needs to be installed with pecl.
sudo pecl channel-update pecl.php.net sudo pecl install mcrypt-1.0.1 (when asked, just press enter)
You also have to add extension mcrypt.so
to php.ini for both, the cli
and fpm
instances. Two methods are shown below. Notice that php-fpm will only load (and be aware of) mcrypt
after it’s reloaded in step 13. Adjust the below PHP version number where appropriate.
# sed -i.bak '927iextension=mcrypt.so' /etc/php/7.2/cli/php.ini # sed -i.bak '927iextension=mcrypt.so' /etc/php/7.2/fpm/php.ini
Or
# pico /etc/php/7.2/cli/php.ini # pico /etc/php/7.2/fpm/php.ini Add extension=mcrypt.so
Install composer
Composer is a dependency manager for PHP.
curl -sS https://getcomposer.org/installer | php sudo mv composer.phar /usr/local/bin/composer
Download Paperwork
Download Paperwork from GIT.
# cd /var/www/html/ # git clone -b 1 https://github.com/twostairs/paperwork.git
Function mcrypt_get_iv_size deprecated
Besides the entiremcrypt
extension, the functionmcrypt_get_iv_size
has also been deprecated. As a consequence, an error message will be thrown later into the user interface when the application is accessed by the browser. We must instruct PHP ignore it by adding a line to app/config/app.php.
# cd paperwork/frontend/ # sudo sed -i.bak '3ierror_reporting(E_ALL ^ E_DEPRECATED);' # app/config/app.php
Prepare the database
Create the database and a database user
# mysql DROP DATABASE IF EXISTS paperwork; CREATE DATABASE IF NOT EXISTS paperwork DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci; GRANT ALL PRIVILEGES ON paperwork.* TO 'paperwork'@'localhost' IDENTIFIED BY 'paperwork' WITH GRANT OPTION; FLUSH PRIVILEGES; quit
Populate the database
When asked, answer with “y”.
# php artisan migrate
Install PHP dependencies
Install PHP dependencies through composer.
# composer install
Install gulp and bower
Then install npm and bower dependencies.
sudo npm install -g gulp bower sudo npm install sudo bower install --allow-root sudo gulp
Change the ownership of files
Change the ownership of Paperwork directory to www-data
.
sudo chown www-data:www-data -R /var/www/html/
Nginx configuration
Edit or replace Nginx default site.
# pico /etc/nginx/sites-available/default
server {
listen 80;
# listen 443 ssl;
root /var/www/html/paperwork/frontend/public;
index index.php index.html index.htm;
server_name example.com;
# server_name example.com;
# ssl_certificate /etc/nginx/ssl/server.crt;
# ssl_certificate_key /etc/nginx/ssl/server.key;
location / {
try_files $uri $uri/ /index.php;
}
error_page 404 /404.html;
# pass the PHP scripts to FastCGI server listening on the php-fpm socket
location ~ .php$ {
try_files $uri =404;
fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
}
}
Restart services
Restart Nginx and PHP.
$ sudo service nginx restart $ sudo service php7.2-fpm restart
Access Paperwork
Now you can open Paperwork in your browser using localhost if the installation is local, or the IP address of the machine where it is installed. You should see a welcome page that initiates the setup wizard.
Run the Wizzard
First, the wizard checks that all dependencies and assets are in place. Then it sets the database connection (server, port, username, password, database). Next, it will ask for the definition of some system settings. And, finally, it will ask for the registration of the first user account.
Login
Login with the newly created user account, and happy note-taking!
Conclusion
Paperwork is being rewritten from scratch, with different technologies (mostly Javascript), and will be completely different than version 1. While we wait, version 1 can be installed in Ubuntu 18.04 Bionic Beaver by following a long, but easy sequence of commands to follow.
In the end, Paperwork is a great FOSS alternative to proprietary software that can be installed on the user premises. It has some interesting features and let us excited waiting for the next version.
Encrypt USB Drive on Ubuntu
Encryption is the best way to protect your important documents personal info and other credentials. Suppose, you have a USB pen drive and your all important data stored on it. In case you will lose your USB pen drive, all data stored on it will be lost. It will be in hands of some other person which will access your personal information and misuse it. So, the best solution to protect your data is to encrypt your USB pen drive with password.
Requirements
- Ubuntu 18.04 desktop installed on your system.
- A non-root user with sudo privileges.
Install Required Tools
First, you will need to install gnome-disk-utility and cryptsetup to your system. Cryptsetup is a utility for setting up encrypted filesystems with the help of Device Mapper and dm-crypt. You can install both tools with the following command:
sudo apt-get install gnome-disk-utility cryptsetup -y
Encrypt USB Drive
IMPORTANT: Before you proceed, back up all data that is on the USB Media as the data on the USB Media gets erased when the partition type is changed to an encrypted partition.
First, plug in your USB flash drive to the system. Next, launch the Disks utility from the Unity Dash. You should see USB drive in the left pane:
Next, umount the filesystem as shown below:
Next, click on the Format button as shown below:
Next, select encryption type, partition name and set your password as shown below:
Now, click on the Format button to encrypt the USB drive.
Access USB Drive
Your USB pen drive is now secure with a password. To test it, unplug and plug in USB drive again. You should be asked to input password to get access the partition as shown below:
Now, provide the password and click on the Connect button. You can access your USB pen drive.
Easy Encrypt Usb Drive, Easy Way To Encrypt Usb Drive, Encrypt Entire Usb Drive, Encrypt Usb Drive, Encrypt Usb Drive On Linux, Encrypt Usb Drive Ubuntu, How To Encrypt Usb Drive In Ubuntu
Malware Found on the Ubuntu Snap Store
Malware has been found hiding inside software on the Ubuntu Snap store.
A pair of (seemingly normal) apps hosted by the Canonical-backed app hub were discovered to contain a сryptocurrency miner disguised as the “systemd” daemon.
The affected apps also shipped an “init script” to auto-load the malicious code on boot and allow it to run in the background on affected systems.
Canonical says it has “removed all applications from this author pending further investigations” since learning of the flaw via a Github issue at the weekend.
Because the Snap Store doesn’t provide public facing install numbers for apps it holds it’s unclear how many Linux users have been affected by this “miner issue”, though it’s worth noting that both apps were only uploaded in late April.
Regardless of the exact figure it’s a given that many users will now be asking how this was allowed to happen in the first place.
Malware on Ubuntu Snap Store: Preventable?
The apps added a cryptocurrency mining script to users’ system without their knowledge
How it was possible for malware to find its way in to the Snap store and on to user’s systems?
The egregious code in question was first found by Github user ‘tarwirdur‘ in an app purporting to bea version of the popular 2048 game.
Curious as to why the app added a system start-up script they checked it out and saw it was for a crypto-currency miner tool.
This canny user then duly checked another app uploaded to the Snap store by the same developer. And guess what? They found it also contained the same ByteCoin mining script, linked to the same e-mail address.
This situation marks the first major “security” issue in the Snappy packaging system. But although unwelcome this particular fail is not necessarily as frightening as it sounds at first, nor is is necessarily a fault with the Snappy format.
All apps uploaded the Snap store undergo automatic testing to ensure that they work and install correctly for users on multiple Linux distros.
Both apps were uploaded as proprietary software so their code was not available to check
However, Snap apps are not checked line-by-linefor anything suspicious or out-of-the-ordinary. Therefore, under the current framework, there was simply no way to detect or prevent this “malware” from being bundled up with an app and made available on the Snap store.
Any theoretical pre-detection would’ve been hard to do given that both of the affected apps were uploaded as proprietary software. Their code was not available to check.
Badware
The crypto-currency miners in this instance can be considered malware because they weren’t mentioned in the store description and used system resources without permission or user knowledge for a task that wasn’t authorised.
That said, the mining scripts themselves don’t (seem to) do anything malicious to the system itself, e.g, harvest data, inject code, hijack browsers, etc.
Was this “malware” meant to be found?
It is possible that the app author in question wasn’t being intentionally malicious; given the lack of effort to disguise the malware (and the inclusion of a hardcoded email address mentioning a Ferrari) they may have been attempting to draw attention to a hole in the Snapcraft vetting model.
And if so, it’s worked.
Be Smart, And You’ll Stay Safe
Scared or worried about using Snap apps? Don’t be.
Although this bit of bundleware was distributed as a Snap it was not taking advantage of a Snap-specific flaw.
This issue stresses the importance of being cautious about where you install software from
The same Bytecoin miner could have be bundled up with an app and distributed through a PPA, an AppImage, an installer script shared on Github, and so on.
What this news does stress is the importance of being cautious about the kind of software you install, and the places you install it from.
Never assume that because an app is listed on a centralised app store like this Ubuntu one that it is free of issues or coming direct from the official maintainer.
Only ever install apps from sources, developers and repos that you trust. Where possible only use applications packaged by an official maintainer or a trusted community source.
Never idly install software from obscure sources, or run command scripts you haven’t vetted yourself.
And in the rare instance that you ever find something suspicious in a Linux app do what this awesome user did and let others know.
Ubuntu Introducing developer notifications for snap security updates
For some time, we’ve wanted a mechanism to alert snap publishers to security updates which affect their snaps. All the pieces have come together and we are now sending alerts via email. Stated more precisely, publishers who use ‘stage-packages’ in their snapcraft.yaml will now be alerted when Ubuntu Security Notices(USNs) have been issued for their staged packages. An example report looks like this:
In this report, multiple revisions are flagged because they are the current revision for the architecture by channel. The reference section aggregates links to the Ubuntu Security Notice website. Vendored code refers to code which is pulled directly from upstream sources, for example, code that is pulled directly from the project’s source code repository (e.g. Github).
As a snap publisher, you can opt-in to receiving these notifications by including a snap/manifest.yaml in your snap. The manifest will be generated for you in the following cases:
- snaps built with SNAPCRAFT_BUILD_INFO=1 will have a snap/manifest.yaml inserted into the snap before the ‘snapcraft pack’ step.
- any snaps built on Launchpad will have SNAPCRAFT_BUILD_INFO=1 set automatically.
Once a day, the service examines snaps that have manifest.yaml files for their currently published channels/tracks and checks whether USNs have been issued for the versions of the staged packages in the snap. If any snap revisions are affected, the tool will generate a report to send via email. By default, the report will be emailed to the publisher’s registered email address and the uploader’s registered email address. It is important to note that even when a snap includes a staged package containing a vulnerability, it does not mean that the snap is necessarily affected by the vulnerability. The developer will need to have a look at the vulnerability to determine whether and how the snap is affected. This service is therefore a one-time notification service and will not continue to nag the publisher about unfixed vulnerabilities. The service records the emails that have already been sent for USNs by revisions of the snap and will only send an email for a particular report once. The publisher will receive a new report only if something has changed in the report, for example, a new USN affects the snap or a new affected revision of the snap is published.
Since this is a new service, we would love to hear feedback. If you discover any issues or have any requests, please report them in the forum using the ‘store’ tag or at https://bugs.launchpad.net/review-tools/+filebug.
Snap In Ubuntu, Ubuntu Snap, Ubuntu Snap App, Ubuntu Snap Format, Ubuntu Snap Install, Ubuntu Snap Store, Ubuntu Snap Tool, Ubuntu Turn Off Snap, Ubuntu Window Snap Settings
How to upgrade to Ubuntu Linux 18.04
With Ubuntu 18.04 Linux, the next long-term support version, coming out shortly, it’s time to go over how to upgrade this popular Linux distribution.
First, keep in mind that this Ubuntu will not look or feel like the last few versions. That’s because Ubuntu is moving back to GNOME for its default desktop from Unity. The difference isn’t that big, but if you’re already comfortable with what you’re running, you may want to wait a while before switching over.
Eager to make the move? Well, before starting, you should backup your existing Ubuntu desktop. There are many ways to backup Ubuntu. My favorites for complete system backups are Ubuntu’s default Déjà Dup and CloneZilla. Whichever method you use, you should also check the restore to make certain your backup is good.
Next, if you want to do this from the GUI, take the following steps:
- Open the “Software & Updates” setting in System Settings.
- Select the third tab, called “Updates.”
- Set the “Notify me of a new Ubuntu version” dropdown menu to “For any new version.”
- Press Alt+F2 and type in “update-manager -cd” (without the quotes) into the command box.
- Update Manager should open up and tell you: New distribution release ‘18.04’ is available.
- If not, you can also use “/usr/lib/ubuntu-release-upgrader/check-new-release-gtk”.
-
- Click Upgrade and follow the on-screen instructions.
Long Term Support Versions Of Ubuntu, Ubuntu Long Term Support, Ubuntu Long Term Support Release, Ubuntu Long Term Support Schedule, Ubuntu Long Term Support Server, What Is Ubuntu Long Term Support
Ubuntu 18.04 LTS Review
The Ubuntu 18.04 release arrived at the end of April and plenty of news coverage was there to greet it.
Most major tech publications no longer carry reviews of Ubuntu, instead preferring to give readers with a punchy “overview”, with a blow-by-blow rundown of the key improvements or changes at hand.
So this post is less of a “review roundup” and more of a “overview roundup”.
The good news is that plenty of such posts appeared after the Bionic Beaver burrowed its way out on April 26, 2018.
And in this article we recap the best of them!
Ubuntu 18.04: Press Reaction
Ars Technica‘s Sean Gallagher treated readers to a “first look” at Ubuntu 18.04 (ahead of a more in-depth Ubuntu 18.04 review due for publication later in the month).
Alongside a well-stocked gallery of screenshots Gallagher shared his own thoughts on the release, writing: “Most of the major internal changes in 18.04 LTS are more important on the server side. But so far, as Ars’ primary day-to-day Linux desktop user, I’ve been really impressed with the snappiness and usability of this latest LTS desktop.”
Ubuntu Core Review, Ubuntu Review, Ubuntu Ultimate Review, Ubuntu User Review