Posted onInsw-hw
,
archDisqus: Word count in article: 1.1kReading time ≈1 mins.
I use Joplin for note taking, and it’s a necessary software for me now. The Joplin data folder is in the NTFS driver so they are safe after I install Arch. It is known for a long time that Joplin does not allow (at least officially inside Joplin) the user to set a custom path for data storage.
Install from Discover (flatpak)
I first tried to install Joplin on Arch from the KDE Plasma’s Discover. I saw Joplin created a data folder (profile folder) at ~/.config/joplin-desktop.
Then I created a symbolink: I link ~/.config/joplin-desktop to the folder in the NTFS drive.
1
ln -s [TARGET] [LINK_NAME]
Before I use symbolink Joplin can start normally, however, after I use the link Joplin GUI no longer appear. Though I can see in the system monitor that Joplin is running, there is not even an error message popped up.
Install from AUR
I don’t know what cause the problem, but I can try to use other versions.
Thus, I tried to install Joplin from AUR. I didn’t managed to do that. Installation failed because it requires nodejs<23. I don’t understand, but I tried to install nodejs and saw the version is higher than 23. Well, I’d not bother with the versioning things. So, I gave up this way.
Install from AppImage
In fact, we don’t even need to “install”. Just make the file executable and double click, then it will run. And, importantly, it works with the symbolink profile folder.
just just pacman to install one and then the firefox display Chinese characters correctly.
Laggy and flickering external monitor
Desktop environment: KDE plasma.
My laptop has an Intel integrated GPU and a GTX 1050 GPU. At the arch linstallation step, I choose the “all open source” for GPU drivers.
Once I connected an external monitor to my laptop, the good news was that the monitor was recognized and showed graphics; while the bad news was that there was tearing or laggy on the external dispay. The first idea was to install the nvidia drivers.
I installed nvidianvidia-settings packages. After reboot, the external display was no longer laggy, but became flickering.
Nvidia Optimus
It seems a tool to make it easier to switch between integrated GPU and the descrete GPU. However, after installed, I found that it doesn’t support wayland. This gave me a hint that the problem might due to some incompatibility between Nvidia driver and wayland.
Although I later switched from wayland to xorg, I didn’t use it as I don’t understand its configurations. As long as now my external monitor works well, I don’t bother with it.
When I changed the panel from bottom to left vertical, the clock and date became very small, nearly not readable. After some exploration, I found that KDE Plasma offers a flexible way to customize the desktop panels.
I can create multiple panels on the desktop, and each panel can contain multiple widgets. The Clock is just a widget. So, I create an Application Menu Bar panel at the top, and move the clock widget to that panel.
Find “Keyboard - English (US) - English (US, intl., with dead keys)”
Auto mount NTFS disk
There are two storage drives on my lapto, one is used for OS, another is for data storage. Of course, both are originally used under Windows so they used NTFS file system. The one used for installing Arch OS has been formatted to ext4. The other one is not changed. After all, I don’t want to erase the data on it. Thus, I choose to cotinue use NTFS under Arch OS. Fortunately it’s not a big problem, Arch kernel already support NTFS file system.
use the following command to list available disks
1
lsblk -f
In my case, I see my unmounted disk is sda, and the largest partition is sda2, and we get the UUID of it. I decide to mount this device to /mnt/ntfsssd.
edit the file /etc/fstab, add the disk partition, save the file.
UUID=8E76D90B76D8F545: This is the unique identifier for your disk partition. Using the UUID is more reliable than using the device path (e.g., /dev/sda2).
/mnt/ntfsssd: The directory where the filesystem will be mounted. You must create this directory first if it doesn’t exist: sudo mkdir -p /mnt/ntfsssd.
ntfs3: This specifies the filesystem type.
defaults,uid=1000,gid=1000,windows_names: These are the mount options.
defaults: A standard set of options suitable for most cases.
uid=1000, gid=1000: These set the ownership of the mounted files to your user. NTFS doesn’t support standard Linux permissions, so this makes your user the owner, giving you full read/write access. You can find your specific uid and gid by running the id command in your terminal. 1000 is the standard for the first user created on most systems.
windows_names: This option prevents you from creating files with names or characters that are illegal on Windows, which is useful for cross-platform compatibility.
0 (dump): This disables the dump utility for this filesystem, which is standard for NTFS.
0 (pass): This tells the fsck utility not to check this filesystem for errors at boot time, as Linux’s fsck can’t repair NTFS partitions.
test if it works
1
sudo mount -a
After running the command, I get this hint:
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use ‘systemctl daemon-reload’ to reload.
The NTFS drive now works fine.
Manage AppImages
Although it might be a preferable way to install software on Arch by using pacman or yay (AUR), I still find that AppImage is a simple “ready to use” way.
I also firstly tried to install an AppImage manager from Discover, called Gear Lever. Unfortunately, it doesn’t work - adding AppImage files into Gear Lever always failed.
However, when I tried to run QQ AppImage file(downloaded from official site), AppImageLauncher didn’t managed to create a shortcut in the start menu, with an error message Failed to register AppImage in system via libappimage.
Show Caps Lock and Num Lock status
Although there is no on screen notification for status change of Caps lock and Num lock, there is a way to show the status by system tray. The System Tray widget has an entry Lock Keys Status. Set it to always shown or shown when relevant, then a status of lock keys will be shown in the system tray when enabled.