Forem: Jakariya Abbas

How to Clean Paru's Local Repository and Stop Removed Packages from Showing Up During Upgrades

Jakariya Abbas — Thu, 05 Jun 2025 08:10:47 +0000

If you're using Paru as your AUR helper and have a local repository set up, you might have noticed something odd: even after uninstalling a package, it still shows up when you run paru -Syu.

This happens because the package still exists in your local repository database. Paru thinks it's something you still want to track or upgrade.

In this guide, we’ll walk through how to properly clean up your local repo so Paru stops suggesting updates for packages you've already removed.

Why This Happens

Paru doesn't just check installed packages. If you've built packages into your local repository, it also checks the repository database when deciding what to upgrade.

So even if you uninstall a package, if its metadata is still in the local repo, Paru will include it in upgrade suggestions.

Step 1: Remove the Package from the Local Repo Database

If a package is no longer installed but still being suggested during an upgrade, remove its entry from the local repository database:

paru -Ld <package-name>

For example, if you previously added package-bin:

paru -Ld package-bin

This removes the package entry from the local repo database, but keeps the actual package file on disk.

Step 2: Remove the Package File Too (Optional)

If you want to remove the package file as well (to save space or avoid clutter), use:

paru -Ldd <package-name>

This removes both the database entry and the package file (.pkg.tar.zst).

Step 3: Clean Paru’s Build Cache (Optional)

Over time, Paru’s cache can build up with downloaded and compiled package files. You can clear that cache like this:

paru -Scc

You’ll be asked to confirm—say yes to both prompts if you want to fully clear everything. This helps avoid rebuild issues and keeps things tidy.

(Alternative) Manually Remove the Package from a Repo Database

If you’re managing a local repo manually (outside of Paru), you can use the repo-remove tool:

repo-remove /path/to/localrepo.db.tar.gz <package-name>

Just replace the path with your actual .db.tar.gz repo file.

Quick Summary

What You Want to Do	Command
Remove package from local DB	`paru -Ld package-name`
Remove from DB + delete file	`paru -Ldd package-name`
Clear Paru build cache	`paru -Scc`
Manually remove from repo DB	`repo-remove yourrepo.db package-name`

After cleaning things up, run paru -Syu again. You should only see packages that are actually installed and relevant.

Keeping your local repo clean makes managing AUR packages a lot easier—and avoids confusion when you're updating your system.

How to Partition Using GParted Live

Jakariya Abbas — Wed, 14 May 2025 05:09:23 +0000

When working with Linux systems, managing disk partitions can be an essential task—especially if you want to create space for sharing files between Linux and Windows. One of the most useful tools for partitioning is GParted Live, a bootable tool that allows you to resize, move, or create new partitions safely.

In this short guide, we’ll walk through how to shrink an existing /home partition (formatted as ext4) and use the freed space to create a new exFAT partition, ideal for cross-platform compatibility.

What You’ll Need

GParted Live ISO: Download here.
A USB drive or CD to boot GParted Live.
Backup of important data (always recommended before changing partitions).

Step 1: Boot Into GParted Live

Burn the GParted Live ISO to a USB stick or CD.
Reboot your computer and boot from the USB/CD.
Follow the startup prompts to load into the GParted interface.

Step 2: Shrink the `/home` ext4 Partition

In GParted, locate the ext4 partition labeled as /home.
Right-click the partition and select Resize/Move.
In the resize window, drag the slider to reduce the partition size and leave unallocated space.
Click Resize/Move to confirm.

Step 3: Create a New exFAT Partition

Right-click the newly unallocated space and choose New.
For the file system type, select exFAT from the dropdown list.
Give the partition a label (optional) and click Add.

Note: If exFAT doesn’t appear, GParted may be missing exFAT support. In that case, you can format the partition later using mkfs.exfat on your main Linux system (install with sudo apt install exfatprogs on Debian/Ubuntu).

Step 4: Apply Changes

Click the green checkmark button in the toolbar to apply all operations.
GParted will now perform the resize and format actions. This may take several minutes.
Once completed, close GParted and shut down the system.

Step 5: Reboot and Verify

Remove the GParted Live USB/CD and boot back into your normal operating system. You should now see a smaller /home partition and a new exFAT partition ready to use.

Using GParted Live is one of the safest and most flexible ways to manage disk partitions. Whether you’re resizing Linux partitions or creating file systems for cross-platform use, GParted gives you full control with a clean graphical interface.

Partitioning can be risky if not done carefully, so always make sure to back up your data before making changes.

Happy partitioning!

MongoDB vs PostgreSQL: Which One Should You Choose?

Jakariya Abbas — Thu, 24 Apr 2025 05:34:01 +0000

MongoDB and PostgreSQL are two of the most popular open-source database systems available today. While they both store and manage data efficiently, they cater to different needs depending on their design philosophies and strengths. This article provides a detailed comparison between MongoDB and PostgreSQL to help you determine which is more suitable for your project.

Data Model and Schema

MongoDB is a NoSQL, document-oriented database that stores data in flexible, JSON-like documents (BSON). It is schema-less, which makes it ideal for rapidly evolving applications and use cases involving unstructured or semi-structured data.

PostgreSQL, on the other hand, is a traditional relational database management system (RDBMS). It stores data in structured tables with predefined schemas. This makes it perfect for applications that rely on strict data consistency and complex relationships.

Performance and Scalability

MongoDB is designed for horizontal scalability. It can handle large-scale applications that require high throughput and low latency, especially when dealing with massive volumes of data that change frequently. Its flexibility in schema design also makes it well-suited for agile development environments.

PostgreSQL provides robust performance for complex queries and transactional operations. It excels in vertical scaling and is highly optimized for read-heavy workloads that require structured querying. While it supports horizontal scaling, it often requires additional configuration and tools to do so effectively.

ACID Compliance and Transactions

MongoDB offers ACID compliance at the document level and supports multi-document transactions since version 4.0. However, its transactional capabilities are not as mature or deeply integrated as those in traditional RDBMS systems.

PostgreSQL is fully ACID-compliant and supports advanced transaction management features. It is a strong choice for applications that require strict data integrity and consistency, such as financial systems or enterprise resource planning (ERP) platforms.

Query Language and Features

MongoDB uses a JavaScript-like query language. It is intuitive for developers familiar with JSON and supports powerful aggregation pipelines. However, it does not support traditional SQL JOIN operations.

PostgreSQL uses SQL, which is standardized and widely adopted. It supports complex queries, JOINs, window functions, subqueries, and more. This makes it especially suitable for data analysis, reporting, and applications that rely on complex querying.

Security and Compliance

MongoDB includes essential security features such as authentication, role-based access control, and encryption. However, some advanced features may require additional configuration.

PostgreSQL provides a robust set of security tools out-of-the-box, including SSL/TLS encryption, role-based access, and row-level security. These features make it well-suited for applications that need to comply with stringent data regulations.

Use Cases

MongoDB is ideal for content management systems, IoT platforms, real-time analytics, and other applications where the data model changes frequently or is not strictly structured.

PostgreSQL shines in use cases that demand data accuracy, consistency, and advanced querying capabilities. Examples include banking systems, government databases, and analytics-heavy applications.

Summary Comparison

Feature	MongoDB	PostgreSQL
Type	NoSQL Document Store	Relational Database (RDBMS)
Schema	Flexible (Schema-less)	Fixed (Schema-based)
Scalability	Horizontal (Sharding)	Vertical (Scaling Up)
Transactions	Limited ACID Support	Full ACID Compliance
Query Language	JavaScript-like (BSON)	SQL
Best For	Unstructured, Dynamic Data	Structured Data, Complex Queries

Final Thoughts

Both MongoDB and PostgreSQL are powerful tools, but their suitability depends on the specific needs of your application. MongoDB offers flexibility and speed for unstructured data and rapid development. PostgreSQL provides reliability, strong transactional support, and advanced features for complex queries and data integrity.

Evaluate your application's requirements carefully to choose the right database engine. For rapidly evolving data structures, MongoDB is a great fit. For high levels of data accuracy and complex reporting, PostgreSQL stands out as the preferred choice.

How to Create and Use userChrome.css in Firefox

Jakariya Abbas — Sat, 05 Apr 2025 19:00:18 +0000

Firefox allows interface customization using a file called userChrome.css. This file can change how Firefox looks by applying custom CSS to its interface. Below is a simple guide to set it up, using "hiding the tab bar" as an example.

Step 1: Enable Custom Stylesheets

Open Firefox and go to about:config.
Search for: toolkit.legacyUserProfileCustomizations.stylesheets
Set it to true by double-clicking.

Step 2: Open Your Profile Folder

Go to about:support in the address bar.
Find the Profile Folder row.
Click Open Folder.

Step 3: Create the `userChrome.css` File

Inside your profile folder, create a folder named chrome (if it doesn’t already exist).
Inside the chrome folder, create a file named userChrome.css.

Step 4: Add Custom CSS

Open userChrome.css in a text editor and add your custom styles.

Example: Hide the tab bar

#TabsToolbar {
    visibility: collapse;
}

Save the file after editing.

Step 5: Restart Firefox

Close and reopen Firefox to see the changes take effect.

Notes

You can add more CSS rules to customize other parts of Firefox.
Hiding the tab bar works best if you use a tab manager extension (like Sidebery or Tree Style Tab) or only use one tab.

Troubleshoot Your Last Boot Crash on Linux

Jakariya Abbas — Wed, 26 Mar 2025 10:04:50 +0000

When your Linux system crashes, understanding the cause is crucial for troubleshooting. The journalctl command helps you analyze system logs, including crash reports. This guide explains how to use journalctl to check why your system crashed in the last boot.

Step 1: View Logs from the Previous Boot

To check logs from the last boot, use the following command:

journalctl -b -1

Here, -b -1 means "show logs from the previous boot." If you want logs from two boots ago, use -b -2, and so on.

Step 2: Filter Logs for Errors

To see only errors from the last boot, run:

journalctl -b -1 -p 3

The -p 3 option filters logs by priority, showing only errors (priority 3) and higher (critical and alert messages).

Step 3: Check Kernel Logs

Kernel messages often contain information about crashes. To see only kernel logs from the last boot, use:

journalctl -k -b -1

Step 4: Identify the Crash Reason with Systemd Logs

To find if systemd recorded any failures, run:

journalctl -b -1 -u systemd-coredump

The systemd-coredump service logs crash dumps of applications, which can help pinpoint the issue.

Step 5: Analyze Segmentation Faults and Core Dumps

If a program caused a segmentation fault, you can check:

journalctl -b -1 | grep 'segfault'

For core dump analysis, run:

coredumpctl list

To inspect a specific core dump:

coredumpctl info <PID>

Replace <PID> with the process ID from the coredumpctl list output.

Step 6: Check Power or Hardware Issues

If you suspect power failures or hardware issues, look for messages related to abrupt shutdowns:

journalctl -b -1 | grep -i 'power off'

To check for disk errors:

journalctl -b -1 | grep -i 'I/O error'

By using journalctl, you can investigate the cause of a system crash and take appropriate action. If logs indicate software issues, updating or reinstalling the package may help. If hardware failures are detected, consider checking system components.

These easy steps will help you effectively diagnose and resolve crashes in Linux. For more details on journal logs and troubleshooting in Linux, visit ArchWiki:

How to Open Windows .url Files in Arch Linux Using a Bash Script

Jakariya Abbas — Wed, 19 Mar 2025 08:53:22 +0000

Windows .url files store web shortcuts. If you have .url files and want to open them in Linux, follow this tutorial to create a Bash script that does it automatically.

Step 1: Create the Script File

First, open a terminal and create a new script file:

nano open-url

This command opens the Nano text editor so you can write the script.

Step 2: Write the Bash Script

Copy and paste the following code into Nano:

#!/bin/bash

# Check if a file is provided
if [[ -z "$1" ]]; then
    echo "Usage: $0 <file.url>"
    exit 1
fi

# Check if the file exists
if [[ ! -f "$1" ]]; then
    echo "Error: File '$1' not found!"
    exit 1
fi

# Extract URL from the .url file
url=$(grep '^URL=' "$1" | cut -d'=' -f2)

# Check if URL was found
if [[ -z "$url" ]]; then
    echo "Error: No URL found in '$1'"
    exit 1
fi

# Open the URL in the default browser
xdg-open "$url"

After pasting the script, save the file by pressing:

CTRL + X → Y → Enter

Step 3: Make the Script Executable

Now, run this command to give the script permission to execute:

chmod +x open-url

Step 4: Make It a System Command

To use this script from anywhere in the terminal, move it to /usr/local/bin:

sudo mv open-url /usr/local/bin/open-url

Now, you can open any .url file like this:

open-url myshortcut.url

Protip: You can set this as a default application/command to open .url files when clicked.

Conclusion

With this simple script, you can easily open Windows .url files in Arch Linux. It checks if the file exists, extracts the URL, and opens it in your default browser using xdg-open.

Setup fingerprint login on Arch Linux with LightDM

Jakariya Abbas — Wed, 26 Feb 2025 13:39:39 +0000

1. Check Your Fingerprint Reader

Make sure your fingerprint reader is supported. You can check your device with:

lsusb

Then look up your reader on list of supported devices or the list of unsupported devices.
Note: The list of supported devices is not updated frequently and may be incomplete. It is recommended to test your device before making any conclusions.

2. Install the Needed Packages

Open a terminal and install fprintd (it will also install libfprint):

sudo pacman -S fprintd

3. Enroll Your Fingerprint

Run this command in your terminal (replace yourusername if needed):

fprintd-enroll

Follow the on-screen instructions to swipe your finger until it says enrollment is complete.

4. Configure PAM for LightDM

Edit the LightDM PAM file to allow fingerprint login:

sudo nano /etc/pam.d/lightdm

At the top of the file, add this line (before any other “auth” lines):

auth    sufficient   pam_fprintd.so

Then save and close the file.

5. Restart LightDM

Restart LightDM to apply the changes:

sudo systemctl restart lightdm

Restrict Fingerprint Enrollment (Optional)

By default, any user can enroll new fingerprints without authentication. You can change this behavior using polkit rules.

1. Locate the Polkit Configuration Files

Polkit configuration files are stored in two locations:

/etc/polkit-1/rules.d/  
/usr/share/polkit-1/rules.d/

Note: Do not modify files in /usr/share/polkit-1/rules.d/ directly, as they may be overwritten during updates. Instead, copy them to /etc/polkit-1/rules.d/ and edit them there.

2. Restrict Enrollment to Root Only

To allow only the root user to enroll fingerprints, create a new rule file:

sudo nano /etc/polkit-1/rules.d/50-net.reactivated.fprint.device.enroll.rules

Add the following content:

polkit.addRule(function (action, subject) {
  if (action.id == "net.reactivated.fprint.device.enroll") {
    return subject.user == "root" ? polkit.Result.YES : polkit.Result.NO;
  }
});

Save the file and exit.

3. Apply Changes

No reboot is required, but you may need to restart the polkit service for changes to take effect:

sudo systemctl restart polkit

Now, only the root user can enroll new fingerprints.

This simple setup should allow you to log in using your fingerprint. Enjoy your new login method!

Effortless GitHub SSH Authentication on Arch Linux (XFCE) using GNOME Keyring (GPG Agent)

Jakariya Abbas — Thu, 20 Feb 2025 09:03:11 +0000

Enhance your workflow with secure, password-free GitHub authentication on Arch Linux. This guide walks you through setting up SSH keys and seamlessly integrating GNOME Keyring for a hassle-free experience on XFCE.

Part 1: Setting Up SSH with GitHub

Step 1: Generate an SSH Key

Run the following command to generate a new SSH key:

ssh-keygen -t ed25519 -C "user@arch.linux"

-t ed25519: Uses the secure Ed25519 algorithm.
-C "user@arch.linux": Labels the key with your email.

Follow the prompts to save the key (default location: ~/.ssh/id_ed25519).

Step 2: Start the SSH Agent

To manage SSH keys in memory, start the SSH agent:

eval "$(ssh-agent -s)"

Step 3: Add Your SSH Key to the Agent

ssh-add ~/.ssh/id_ed25519

Step 4: Copy and Add Your Public Key to GitHub

cat ~/.ssh/id_ed25519.pub

Copy the output and go to GitHub → Settings → SSH and GPG keys → New SSH Key, paste it, and save.

Step 5: Test Your SSH Connection

ssh -T git@github.com

A successful connection returns a GitHub welcome message.

Step 6: Configure SSH (Optional)

To avoid manually specifying the SSH key, create a configuration file:

touch ~/.ssh/config
nano ~/.ssh/config

Add:

Host github.com  
  IdentityFile ~/.ssh/id_ed25519  
  AddKeysToAgent yes

Save and exit.

Step 7: Re-Test SSH Connection

Run:

ssh -T git@github.com

Your SSH setup is now complete!

Part 2: Enabling GNOME Keyring for Passwordless SSH on Arch XFCE

To have your SSH keys unlocked automatically at login, configure GNOME Keyring.

Step 1: Disable XFCE's Default SSH Agent

Run:

xfconf-query --channel xfce4-session --property /startup/ssh-agent/enabled --create --type bool --set false

Step 2: Install GNOME Keyring

Using an AUR helper like paru:

paru -S gnome-keyring seahorse

This provides gpg-agent, which will act as your SSH agent.

Step 3: Set the SSH_AUTH_SOCK Environment Variable

The SSH_AUTH_SOCK environment variable tells SSH tools where to find the authentication agent. Since GPG agent is being used as the SSH agent, this variable must point to its socket:

export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)

To make this change persistent across reboots, add this line to your ~/.bashrc or ~/.zshrc file.

Step 5: Add Your SSH Key to the Agent

Now that GPG agent is running with SSH support, add your SSH key:

ssh-add ~/.ssh/id_ed25519

If your key has a passphrase, you will be prompted.
The passphrase will be cached according to GPG agent settings.

Step 7: Verify the Key Is Loaded

To confirm that your key has been added successfully, run:

ssh-add -l

If your key is listed, it means GPG agent is managing it correctly.
If no keys appear, ensure that GPG agent is running and SSH_AUTH_SOCK is set correctly.

Your SSH keys are now managed by GNOME Keyring (GPG Agent), providing a secure and consistent authentication experience. 🎉

Forem: Jakariya Abbas

How to Clean Paru's Local Repository and Stop Removed Packages from Showing Up During Upgrades

Why This Happens

Step 1: Remove the Package from the Local Repo Database

Step 2: Remove the Package File Too (Optional)

Step 3: Clean Paru’s Build Cache (Optional)

(Alternative) Manually Remove the Package from a Repo Database

Quick Summary

How to Partition Using GParted Live

What You’ll Need

Step 1: Boot Into GParted Live

Step 2: Shrink the /home ext4 Partition

Step 3: Create a New exFAT Partition

Step 4: Apply Changes

Step 5: Reboot and Verify

MongoDB vs PostgreSQL: Which One Should You Choose?

Data Model and Schema

Performance and Scalability

ACID Compliance and Transactions

Query Language and Features

Security and Compliance

Use Cases

Summary Comparison

Final Thoughts

How to Create and Use userChrome.css in Firefox

Step 1: Enable Custom Stylesheets

Step 2: Open Your Profile Folder

Step 3: Create the userChrome.css File

Step 4: Add Custom CSS

Step 5: Restart Firefox

Notes

Troubleshoot Your Last Boot Crash on Linux

Step 1: View Logs from the Previous Boot

Step 2: Filter Logs for Errors

Step 3: Check Kernel Logs

Step 4: Identify the Crash Reason with Systemd Logs

Step 5: Analyze Segmentation Faults and Core Dumps

Step 6: Check Power or Hardware Issues

How to Open Windows .url Files in Arch Linux Using a Bash Script

Step 1: Create the Script File

Step 2: Write the Bash Script

Step 3: Make the Script Executable

Step 4: Make It a System Command

Conclusion

Setup fingerprint login on Arch Linux with LightDM

1. Check Your Fingerprint Reader

2. Install the Needed Packages

3. Enroll Your Fingerprint

4. Configure PAM for LightDM

5. Restart LightDM

Restrict Fingerprint Enrollment (Optional)

1. Locate the Polkit Configuration Files

2. Restrict Enrollment to Root Only

3. Apply Changes

Effortless GitHub SSH Authentication on Arch Linux (XFCE) using GNOME Keyring (GPG Agent)

Part 1: Setting Up SSH with GitHub

Step 1: Generate an SSH Key

Step 2: Start the SSH Agent

Step 3: Add Your SSH Key to the Agent

Step 4: Copy and Add Your Public Key to GitHub

Step 5: Test Your SSH Connection

Step 6: Configure SSH (Optional)

Step 7: Re-Test SSH Connection

Part 2: Enabling GNOME Keyring for Passwordless SSH on Arch XFCE

Step 1: Disable XFCE's Default SSH Agent

Step 2: Install GNOME Keyring

Step 3: Set the SSH_AUTH_SOCK Environment Variable

Step 5: Add Your SSH Key to the Agent

Step 7: Verify the Key Is Loaded

Step 2: Shrink the `/home` ext4 Partition

Step 3: Create the `userChrome.css` File