Archive

Archive for the ‘manjaro’ Category

[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.

Advertisements
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

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.

Categories: linux, manjaro, mongodb Tags: ,

[manjaro] open URLs with Firefox

December 18, 2017 Leave a comment

Problem
Under Manjaro I ran into a strange problem. Using Studio 3T (which is a GUI for MongoDB), if I click on a URL, it’s opened in Chrome. However, in Visual Studio Code for instance URLs are opened with Firefox. How to tell the system which browser to use?

Solution
I wrote to Studio 3T and they kindly answered me: “We don’t specify any browser but simply ask the OS to open the page. This might be a settings issue in the Manjaro Linux distro, which we don’t currently support. I hope this has not caused much inconvenience.

So, the problem is not with Studio 3T but it’s a Manjaro setting. After some research, I found the solution. Edit the file “~/.config/mimeapps.list” (first make a backup copy of it!) and identify the lines that start with “x-scheme-handler/http“. I made the following changes:

x-scheme-handler/http=firefox.desktop                                                                                                                       
x-scheme-handler/https=firefox.desktop

These two rows appear under another section too, so altogether I changed 4 lines. The string before “.desktop” is the name of the command that is used to start Firefox from the command-line. Thus, if you want to open the URLs with Palemoon for instance, you should write “palemoon.desktop“, etc.

When you save the file, changes are taken into account immediately.

(This is for Manjaro, using the XFCE graphical environment.)

Categories: firefox, manjaro Tags: , , ,

[manjaro] i686 is dead but still alive

November 26, 2017 Leave a comment

Problem
I have an old 32-bit laptop that I use for one thing only: it’s connected to my TV with a VGA cable and that’s how I watch movies. I have Manjaro on this laptop and it worked well until about two weeks ago. Since then I couldn’t update it, the repos returned a 404 error.

Solution
Today I dived in the problem and it turned out that Manjaro dropped the 32-bit support in November 2017.

However, some people still want to keep the i686 support alive. Here is the announcement of this unofficial 32-bit support.

The project also has a webpage: http://manjaro32.org/ .

Categories: manjaro Tags: ,

[manjaro] Make C# debugger work in Visual Studio Code

Problem
Under Manjaro / Arch you use Visual Studio Code with the C# extension. Everything works fine except the C# debugger.

Solution
I found the solution here: https://github.com/OmniSharp/omnisharp-vscode/issues/1323 . The debugger on Manjaro / Arch is not supported officially, so we need to do some tricks. In VS Code open the user settings and add this line:

"csharp.fallbackDebuggerLinuxRuntimeId": "ubuntu.16.04-x64"

Uninstall the C# extension, restart VS Code, and re-install the C# extension. Open a .cs file and the extension will download some packages, including the debugger for Ubuntu 16.04 (as we specified it in the settings).

However, the *.so files of the Ubuntu debugger rely on a specific version of the package “icu”.

$ cd ~/.vscode/extensions/ms-vscode.csharp-1.11.0/.debugger
$ find *.so -type f | xargs ldd 2> /dev/null | grep not\ found
        liblldb-3.6.so => not found
        libvsdebugeng.so => not found
        libvsbaseservices.so => not found
        libvsbaseservices.so => not found
        libicuuc.so.55 => not found
        libicui18n.so.55 => not found

The last 2 lines are interesting: we need version 55 of the package “icu“. “yaourt icu” revealed that I had version 59 installed, but version 55 can be installed too with “yaourt icu55“. The two versions can co-exist. When installed, restart VS Code and debugging should work now.

Credits
The solution was found at https://github.com/OmniSharp/omnisharp-vscode/issues/1323 . A big thanks for starquake.

Categories: csharp, manjaro Tags:

Record audio in good quality

April 13, 2017 Leave a comment

Problem
I wanted to create some simple tutorial videos using a screen recording software (with gtk-recordMyDesktop to be precise), but the audio quality was terrible. There was a constant white noise in the background. I could reduce the noise with Audacity but 1) I couldn’t eliminate the noise, 2) it distorted my voice, and 3) the audio became weaker.

Solution
I had a cheap headphone / microphone that was connected with a jack plug. I think there was also some inference that caused the noise. So I bought a USB headset (Logitech H390) and the damn noise is gone! It works very well for me.

I tried it under Manjaro and here is how to make it work. Plug it and start Audacity. Next to the microphone icon there is a dropdown list. Select your headset and try to record some audio.

Try “pavucontrol” too. Under the Recording tab I had to select “Headset H390 Analog Mono”. Talk in the microphone and the sound feedback line should be moving.

How to record audio with gtk-recordMyDesktop? Start “pavucontrol” and “gtk-recordMyDesktop” too. In gtk-recordMyDesktop, go to Advanced -> Sound tab. Next to the device name I had “DEFAULT”. Change it to “pulse” (without quotes). Start recording with gtk-recordMyDesktop. Now switch to pavucontrol and go the Recording tab. At the bottom select “Show: Applications”. Now recordmydesktop should appear. Next to it there is a dropdown menu where select “Headset H390 Analog Mono”. It should do the trick.