Archive

Archive for the ‘manjaro’ Category

[manjaro] change window buttons layout

August 18, 2019 Leave a comment

Problem
On my desktop I have a Manjaro that I installed years ago. It’s a rolling release distro, meaning I get all the updates, but the graphical interface is not always updated. For instance, I installed a new Manjaro on a laptop, and Manjaro looks much better on my laptop than on my old desktop.
On a newly installed Manjaro, the window buttons are on the right side, but on my desktop they are on the left. How could I unify them and move the buttons to the right?

Solution
I found the solution in this video: https://www.youtube.com/watch?v=yVfHDyWcgSA . In short: start the Settings Editor, select xfwm4 on the left, edit “button layout”, and provide the string “O|SHMC” (without quotes).

ASUS VivoBook S530F: how to install the Windows 10 drivers?

Problem
I got a new laptop at my workplace, an ASUS VivoBook S530F. I wanted to make a dual-boot system with Windows 10 and Manjaro. First, I installed Windows 10 on it. For creating a bootable USB stick, I followed this guide (I used gparted). Windows 10 installed successfully but I had no wifi. Fine, let’s install the drivers from the included DVD. Some drivers went up, but the installation of the wifi driver terminated with a DLL error. This error was produced by a file called pnputil.exe. Hmm… OK, then let’s connect an Ethernet cable. Oh, but this slim laptop has no Ethernet connection! Using another machine, I downloaded the wifi driver from the ASUS home page, I could install it, but nothing happened. The wifi was still dead.

Solution
It turned out that the file pnputil.exe is part of the Windows and you can find it in the C:\Windows\System32 folder. On the DVD there were about 18 copies of this file and by comparing their sizes, there were at least 3 different versions. On the official DVD! Congratulations!

So I copied the content of the DVD to the hard drive and overwrote all instances of pnputil.exe with the one from the System32 folder. Then I launched the installation wizard and it installed all the drivers without any DLL error message.

Update: Installing Manjaro
After Windows 10, I installed Manjaro in a separate partition. Under Windows 10 I downloaded the Manjaro ISO and wrote it on a USB stick with Rufus in dd mode. During the installation I created a swap partition and a root partition. Here I got a warning that an EFI partition is necessary. The Windows 10 installer created a FAT32 partition of size 100 MB. I selected this partition and specified it to be mounted under /boot/efi. The installer flagged it automatically as “esp”. Then the installation went on without any problem and my wifi card was recognized out-of-the-box.

Categories: manjaro, windows 10 Tags: , ,

browse your fonts easily

October 13, 2018 Leave a comment

Problem
I wanted to create a captioned image with Gimp and for this I was looking for a nice font. Under Manjaro I installed the package “aur/ttf-google-fonts-opinionated-git” and thus I got hundreds of fonts. How to visualize and browse them easily?

Solution
FontManager can do exactly this. Install the package “aur/fontmanager.app” and launch the app. with the command FontManager. It looks similar to this:

On the left side click on a font, then use the down arrow to run through the fonts.

Categories: linux, manjaro Tags: , , ,

maximize a window

October 13, 2018 Leave a comment

In Manjaro (XFCE) it’s “Alt+F10”. In Windows it’s “Super key + up arrow”.

In Manjaro, you can find and edit all window manager shortcut keys from Menu → Settings Manager → Window Manager → Keyboard tab.

Originally, I wanted to figure out how to maximize a VS Code window (reddit question here).

[manjaro] edit PKGBUILD and install a package

March 30, 2018 Leave a comment

Problem
You try to install a package with “yaourt pkg_name” but the installation fails. How to edit the PKGBUILD file manually and then install the package?

Solution

$ cd /tmp
$ yaourt -G pkg_name
$ cd pkg_name
# modify the file PKGBUILD with your favourite text editor
$ makepkg -i

Where “pkg_name” is the name of the package you want to install.

Categories: manjaro Tags: , ,

[manjaro] installation fails, unknown public key

January 17, 2018 Leave a comment

Problem
I couldn’t update a package due to the following error:

==> Validating source files with sha256sums...
    gcc-7.2.1-20171224.tar.xz ... Passed
    gcc-7.2.1-20171224.tar.xz.sig ... Skipped
    isl-0.18.tar.bz2 ... Passed
==> Verifying source file signatures with gpg...
    gcc-7.2.1-20171224.tar.xz ... FAILED (unknown public key BBE43771487328A9)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build mingw-w64-gcc.
==> Restart building mingw-w64-gcc ? [y/N]
==> --------------------------------------
==> ==> ERROR: unable to update

Solution
I asked this on reddit and /u/SuperGrip kindly provided the solution:

This is a common issue when an apps key is not included in the ArchLinux Keyring, to solve this issue you can add the key manually by running the following command: gpg --recv BBE43771487328A9

For further information check the package comments on the AUR site. https://aur.archlinux.org/packages/mingw-w64-gcc/

Categories: manjaro Tags: , , , ,

[mongo] Upgrade to version 3.6, 4.0, 4.2

January 1, 2018 1 comment

Problem
Under Manjaro, my MongoDB 3.4 was upgraded to version 3.6 and it stopped working. Great!

Solution
In the log file I found this error: “IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details.

Visiting the link in the error message, it was suggested to execute a DB command in the mongo shell. But the Mongo server was not willing to start, thus I couldn’t connect to it with the Mongo shell!

So I downgraded to version 3.4 just to be able to start the Mongo shell and execute the command “db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )“. Now I upgraded MongoDB to version 3.6 and it started happily.

Update (20190911)
Today I wanted to update MongoDB 3.6 to MongoDB 4.2 under Manjaro. The package manager contained a binary package that I could install easily but when I started it, the shell was version 4.2 but the server was still version 3.6! A few hours later I figured out that the problem was caused by the old server (v3.6) that was still running when I updated MongoDB. So the winning strategy was the following:

  • Remove 4.2 and put back 3.6. Start the mongo shell to see that everything works.
  • Stop the mongo server: “systemctl stop mongodb“.
  • Update to version 4.0 (using a binary package), start the server (“systemctl start mongodb“) and launch the mongo shell to verify that everything is OK.
  • In the mongo shell issue the command “db.adminCommand( { setFeatureCompatibilityVersion: "4.0" } )“.
  • Now we can move on to version 4.2. Stop the mongo server: “systemctl stop mongodb“.
  • Update to version 4.2 (using a binary package), start the server and launch the mongo shell to verify that everything is OK.
  • In the mongo shell issue the command “db.adminCommand( { setFeatureCompatibilityVersion: "4.2" } )“.

When you start / stop the server with systemctl, you’ll have to wait a few seconds to see its effect. You can verify the status of the server with “systemctl status mongodb“. It’s highly recommended that you install a binary package. Installing from source takes several hours even on a decent machine.

List of installed mongo packages: “pacman -Q | grep mongo“. When you want to upgrade, it’ll show you what packages to remove.

Categories: linux, manjaro, mongodb Tags: , ,