Noob Install Issue

Support
1

I’m running Arch (Linux noob) and haven’t had any issues setting up my system that I’ve been running for six months now. When I try install joplin either cloning in or with an AUR helper I keep getting the same error. This is the output:

:: Checking for conflicts…
:: Checking for inner conflicts…
[Aur: 1] joplin-1.0.179-1

1 joplin (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a
:: Deleting (1/1): /home/greg/.cache/yay/joplin
:: Downloaded PKGBUILD (1/1): joplin
1 joplin (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
:: Parsing SRCINFO (1/1): joplin
==> Making package: joplin 1.0.179-1 (Thu Feb 13 21:50:17 2020)
==> Retrieving sources…
-> Found joplin.desktop
-> Found joplin-desktop.sh
-> Found joplin.sh
-> Downloading joplin-1.0.179.zip…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 123 0 123 0 0 266 0 --:–:-- --:–:-- --:–:-- 266
100 22.6M 0 22.6M 0 0 7902k 0 --:–:-- 0:00:02 --:–:-- 9464k
==> Validating source files with sha256sums…
joplin.desktop … Passed
joplin-desktop.sh … Passed
joplin.sh … Passed
joplin-1.0.179.zip … Passed
==> Making package: joplin 1.0.179-1 (Thu Feb 13 21:50:21 2020)
==> Checking runtime dependencies…
==> Checking buildtime dependencies…
==> Retrieving sources…
-> Found joplin.desktop
-> Found joplin-desktop.sh
-> Found joplin.sh
-> Found joplin-1.0.179.zip
==> Validating source files with sha256sums…
joplin.desktop … Passed
joplin-desktop.sh … Passed
joplin.sh … Passed
joplin-1.0.179.zip … Passed
==> Removing existing $srcdir/ directory…
==> Extracting sources…
-> Extracting joplin-1.0.179.zip with bsdtar
bsdtar: Failed to set default locale
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename … skipping.
bsdtar: Error exit delayed from previous errors.
==> ERROR: Failed to extract joplin-1.0.179.zip
Aborting…
Error making: joplin

When I check my locale output I get:

Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8

**I’ve checked everything on the Wiki and my locale appears to be properly generated (I’ve tried regenerating locale, export LC_ALL, as well as checking the config file, which on the Wiki are all potential errors but doesn’t seem to be an issue here). Again, I have been running this system for 6+ months and haven’t had any other package install issues, so I’m at a loss. I’m sure it’s probably a quick fix due to my user error, but need some help in identifying potential issues. **

2

We do not provide the AUR package. You will have to talk to the package maintainer.

However, the error above says that the extraction failed, apparently because the locale couldn’t be determined on your system. This seems more like an OS issue. Just because you haven’t experienced other issues doesn’t mean that your system is fine.

Let’s hope that the AUR package maintainer reads this topc. Unfortunately I can’t recall his username, otherwise I could have mentioned him here. Have a look at https://aur.archlinux.org/packages/joplin/

3

Okay, I really appreciate it! I even did a fresh install of the OS, so unless I replicated my user error, not sure how I’ll go about identifying the issue. I’ve at least tried all the various resolutions from

https://wiki.archlinux.org/index.php/locale

I guess the next step will be posting on the Arch forums, but prepared to get dragged.

4

Not necessarily. There are Arch Linux users here. And the maintainer of the package has also posted here before (I think).
I use only Linux without a DE (GUI) and I use npm install -g joplin to install the cli app.

5

The Arch Linux package repo is there https://github.com/alfredopalhares/joplin-pkgbuild

1 Like
6

I appreciate the reply! This is where I referenced originally, but when trying yay or cloning into git I got the same output that I posted above. Any suggestions on what I might be doing wrong?

7

We also do not provide yay packages.

How about you install node 10.16.x and then use npm install -g joplin to install the terminal client.

If you can’t use git, then your system is definitely broken somehow. I’m sorry, but how are we supposed to fix you OS issues?

8

I understand, and as I’ve acknowledged, I know it’s been a product of my user error, so I appreciate the assistance.

I discovered and resolved an issue with my locales (which as you said, was always present in my OS, just never arose from prior package installations).

I had to cleanup some of my own mess from prior installation attempts, but I have since successfully installed it! Thank you so much.

9

Mind sharing how you fixed it? Partially because I run Manjaro (an Arch based distro) and am just curious. And partially because it might help someone else if they run in to the same issue.

10

Sure, I’m not certain exactly how I created the issue to begin with, so there’s still some unknown, but I’ll share what I did.

I definitely did my initial locale-gen correctly during my Arch install (6 months ago). But at some point I must have messed it up, and had to go back to uncomment my locale in /etc/locale.gen and run locale-gen again. I also had to rm /usr/bin/joplin as there were still lingering files from my failed install attempts that even doing a cleanBuild install wouldn’t replace. Not sure if maybe an issue occurred when I first tried to use yay -S joplin or cloning into git. I might do a fresh install of the OS just to try replicate the issue sometime and can update you if I do.

1 Like