Thursday, September 3, 2026

How to Create a New User and Enable the Login Screen in Ubuntu

If your Xubuntu virtual machine boots directly to the desktop without showing a login screen, automatic login is probably enabled.

This guide shows how to create a new user called user1, set a password for the account, and disable automatic login so that Xubuntu displays the login screen whenever the VM starts.

Creating a New User in Xubuntu

1. Create the User

Open a Terminal and run:

sudo adduser user1

Follow the prompts to create the account. You will be asked to enter a password and some optional information about the user.

You can press Enter to skip optional information such as the full name, room number, and phone number.

2. Set or Change the Password for user1

If you need to set a password for user1 later, or simply want to change the existing password, run:

sudo passwd user1

You should see prompts similar to:

New password:
Retype new password:
passwd: password updated successfully

When entering a password in the Linux Terminal, nothing will appear on the screen. You will not see characters, dots, or asterisks while typing. This is normal behavior.

3. Give user1 Sudo Privileges (Optional)

By default, the new account does not necessarily have administrative privileges. If you want user1 to be able to execute commands using sudo, run:

sudo usermod -aG sudo user1

This step is optional. If user1 should remain a normal user without administrator privileges, you can skip it.

Enabling the Xubuntu Login Screen

4. Check the Display Manager

Xubuntu commonly uses LightDM to provide its graphical login screen. You can check which display manager is currently configured by running:

cat /etc/X11/default-display-manager

On a typical Xubuntu installation, the output should be:

/usr/sbin/lightdm

If you see /usr/sbin/lightdm, the following LightDM configuration steps apply to your system.

5. Check Whether Automatic Login Is Enabled

Search the LightDM configuration files for settings related to automatic login:

grep -R "autologin" /etc/lightdm/

You may find configuration similar to:

[Seat:*]
autologin-user=myuser
autologin-user-timeout=0

The important setting is:

autologin-user=myuser

This tells LightDM to automatically log in to the specified account instead of displaying the normal graphical login screen.

6. Disable Automatic Login

If the automatic-login configuration is located in /etc/lightdm/lightdm.conf, open the file using Nano:

sudo nano /etc/lightdm/lightdm.conf

Look for configuration similar to:

[Seat:*]
autologin-user=myuser
autologin-user-timeout=0

Comment out the automatic-login lines:

[Seat:*]
#autologin-user=myuser
#autologin-user-timeout=0

Alternatively, you can remove the automatic-login lines completely.

If the earlier grep command shows that the settings are stored in another file under /etc/lightdm/, edit that file instead.

When using Nano:

  • Press Ctrl+O to save the file.
  • Press Enter to confirm the filename.
  • Press Ctrl+X to exit Nano.

Testing the New User Account

7. Test user1 from the Terminal

Before rebooting the virtual machine, you can verify that the new account and password work correctly. Run:

su - user1

Enter the password that you configured for user1.

If authentication succeeds, the shell will switch to the new user's environment. You can verify the current username with:

whoami

The output should be:

user1

To return to your original account, run:

exit

Rebooting and Verifying the Login Screen

8. Reboot Xubuntu

After creating the user and disabling automatic login, reboot the virtual machine:

sudo reboot

When Xubuntu starts again, LightDM should display the graphical login screen instead of automatically opening the desktop.

You should now be able to select your existing account or user1 and log in using the corresponding password.

Quick Command Reference

# Create a new user
sudo adduser user1

# Set or change the user's password
sudo passwd user1

# Optional: give user1 sudo privileges
sudo usermod -aG sudo user1

# Check the current display manager
cat /etc/X11/default-display-manager

# Find LightDM automatic-login settings
grep -R "autologin" /etc/lightdm/

# Edit the main LightDM configuration
sudo nano /etc/lightdm/lightdm.conf

# Test the new account
su - user1

# Check the current username
whoami

# Reboot Xubuntu
sudo reboot

Conclusion

If Xubuntu boots directly to the desktop, automatic login is usually enabled in the display manager. Creating another user alone does not necessarily cause the login screen to appear.

After creating user1, setting its password, and disabling the autologin-user option in LightDM, the graphical login screen should appear whenever Xubuntu starts. You can then choose which account to use each time the virtual machine boots.

Read More

⚠️ Security Warning: Royal Cat (CAT) Crypto Token

Security Notice: Users who unexpectedly receive a cryptocurrency token named Royal Cat (CAT) should exercise caution.

An unfamiliar token appearing in your cryptocurrency wallet does not necessarily mean your wallet has been compromised, nor does it automatically prove that the token itself is fraudulent. However, unsolicited crypto tokens can sometimes be distributed as spam or used to encourage recipients to interact with suspicious websites, applications, or smart contracts.


⚠️ Why Royal Cat May Be Flagged as Suspicious

There can be multiple cryptocurrency assets using names such as Royal Cat and the ticker CAT. Cryptocurrency names and ticker symbols are not unique, which means the name alone cannot establish whether a particular token is legitimate.

You should be especially cautious if:

  • You never purchased or requested the Royal Cat token.
  • The token suddenly appeared in your wallet.
  • You do not recognize the sender or project.
  • The token directs you to an unfamiliar website.
  • You are asked to connect your wallet to claim, unlock, swap, or sell the token.
  • You are asked to approve an unfamiliar smart contract.
  • You are asked to sign a transaction you do not understand.
  • The token displays an apparent value but has unclear or unreliable liquidity.

🛡️ What Should You Do?

If an unknown Royal Cat token appears in your wallet, do not interact with it until you have independently verified its exact blockchain network and contract address.

As a precaution, avoid:

  • Clicking links promoted by the token.
  • Connecting your wallet to unfamiliar websites.
  • Approving unknown smart contracts.
  • Signing unexplained transactions or messages.
  • Entering your recovery phrase or private key on any website.

Important: Simply seeing an unsolicited token in your wallet generally does not require you to move your other cryptocurrency.

The greater risk can arise when a recipient is persuaded to interact with a malicious website, signature request, token approval, or smart contract.


🚨 Consider Reporting Royal Cat as Spam

If your wallet or cryptocurrency application provides a Report Spam, Mark as Spam, or Hide option, consider using it when Royal Cat appeared without your request or otherwise seems suspicious.

Reporting an unsolicited asset can help remove unwanted tokens from your wallet interface and may provide the platform with useful signals about potentially unwanted token distributions.

Reporting a token as spam is a precautionary security measure. It does not, by itself, establish that the token or its creators are fraudulent.


🔍 Check the Contract Address — Not Just the Name

Never identify a cryptocurrency solely by its name or ticker symbol.

Different smart contracts can use identical or very similar names such as Royal Cat or CAT. A legitimate project and an unrelated suspicious token could therefore appear to have the same name.

Before interacting with an unfamiliar cryptocurrency, verify:

  • The complete contract address.
  • The blockchain network where the token was issued.
  • Whether the contract source code is verified.
  • Whether the project's official sources identify the same contract.
  • Whether meaningful trading liquidity actually exists.
  • Whether reputable security services have identified contract risks.

🔐 Never Share Your Recovery Phrase

No legitimate token claim, wallet-support representative, exchange employee, or cryptocurrency project should require you to disclose your wallet's seed phrase, recovery phrase, or private key.

If a website associated with Royal Cat—or any other unexpected token—asks for this information, leave the website immediately.

Your recovery phrase can provide complete control over your wallet. Anyone who obtains it may be able to transfer your cryptocurrency without your permission.


✅ Recommended Action

⚠️ SECURITY RECOMMENDATION

If you did not intentionally acquire Royal Cat (CAT), avoid interacting with it, do not follow links associated with it, and consider reporting or hiding the token as spam until its exact contract can be independently verified.

Final Thoughts

Unexpected cryptocurrency should not automatically be treated as free money.

Receiving an unknown token can simply be unwanted blockchain spam, but unsolicited assets may also be designed to attract attention and encourage risky interactions.

The safest approach is simple: do not trust an unexpected token based on its name, displayed balance, or apparent value. Verify the contract independently before interacting with it.

When in doubt: don't click, don't connect, don't approve, and don't sign.


Disclaimer: This article is provided for general cybersecurity and educational purposes only. References to Royal Cat (CAT) describe precautions users may take when encountering an unsolicited or unverified token. The appearance of a token in a wallet, or reporting it as spam, does not by itself establish fraud or wrongdoing by any person or project. This article is not financial, investment, or legal advice.

Read More

Windows Partition Merge & WinRE Recovery Notes

Windows Partition Merge & WinRE Recovery Notes

This note documents the successful process used to merge the space from the old E: partition into C: while preserving and rebuilding the Windows Recovery Environment (WinRE).

Important: Partition operations can cause data loss if the wrong disk or partition is selected. Always verify partition numbers, sizes, and contents before deleting or changing anything.

Introduction: Why Windows Partition Merge Is Needed

Over time, a Windows disk can become inefficiently divided into multiple partitions. A common situation is that the system partition (C:) becomes nearly full while another partition, such as D: or E:, still has a large amount of unused space. A full C: drive can interfere with Windows updates, application installations, temporary files, virtual memory, and normal system operation.

In this case, the disk originally contained a relatively small C: partition of about 14 GB and a much larger E: partition of about 185 GB. Since the additional E: partition was no longer needed, the objective was to return its space to C: and create one much larger, more practical system partition.

Normally, this can be accomplished by deleting the unnecessary partition and extending C: into the resulting unallocated space. However, Windows can extend a partition only when the unallocated space is directly adjacent to the right side of that partition.

The original physical layout was:

[EFI] [MSR] [C:] [Recovery] [E:]

After E: was deallocated, the layout became:

[EFI] [MSR] [C:] [Recovery] [Unallocated Space]

The Windows Recovery Environment (WinRE) partition was therefore positioned between C: and the newly available space. Windows Disk Management cannot move this Recovery partition, so C: could not simply be extended into the large unallocated area.

The solution was to back up the existing WinRE files, remove the obstructing Recovery partition, extend C: into the available space, and then create a new Recovery partition at the end of the disk and restore WinRE.

The overall objective was:

BEFORE
[EFI] [MSR] [C: ~14 GB] [Recovery] [E: ~185 GB]

AFTER
[EFI] [MSR] [C: ~199 GB] [Recovery ~1 GB]

This arrangement gives the Windows system partition substantially more usable space while preserving the EFI boot partition, Microsoft Reserved partition, and a functional Windows Recovery Environment.

1. Original Layout

[EFI 100 MB] [MSR 16 MB] [C: ~14 GB] [Recovery 593 MB] [E: ~185 GB]

After E: was deallocated:

[EFI] [MSR] [C:] [Recovery 593 MB] [~185 GB Unallocated]

The 593 MB Recovery partition prevented C: from being extended because Windows requires unallocated space to be directly adjacent to the right side of C:.

2. Identify the Active WinRE Partition

reagentc /info

The important result was:

Windows RE status: Enabled
Windows RE location:
\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

DiskPart was used to confirm the partition:

diskpart
select disk 0
list partition

Partition 4 was confirmed as the 593 MB Recovery partition.

3. Mount the Existing Recovery Partition

diskpart
select disk 0
select partition 4
assign letter=R
exit

Verify the recovery files:

dir /a R:\Recovery\WindowsRE

The partition contained:

boot.sdi
ReAgent.xml
Winre.wim

Winre.wim was approximately 514 MB.

4. Back Up WinRE Before Deleting the Recovery Partition

Because C: initially had insufficient free space, a temporary partition was used to store the backup.

xcopy R:\Recovery\WindowsRE T:\WinRE_Backup\ /h /i /y

Verify hidden/system files with:

dir /a T:\WinRE_Backup
The /h option copies hidden and system files. A normal dir may report no files because these files retain their hidden/system attributes. Use dir /a.

5. Delete the Old Recovery Partition

First verify the partition carefully:

diskpart
select disk 0
select partition 4
detail partition

After confirming it was the 593 MB Recovery partition:

delete partition override

6. Make the Free Space Adjacent to C:

The temporary backup partition initially ended up between C: and the large unallocated region. The WinRE backup was therefore temporarily copied to C: after C: gained enough free space.

First extend C: into the immediately adjacent 593 MB:

diskpart
select volume C
extend
exit

Check free space:

fsutil volume diskfree C:

Copy the temporary WinRE backup to C:

mkdir C:\WinRE_Backup
xcopy T:\WinRE_Backup C:\WinRE_Backup\ /h /i /y
dir /a C:\WinRE_Backup

After verifying Winre.wim, delete the temporary T: partition:

diskpart
select volume T
detail volume
delete volume

7. Extend C: Across the Remaining Space

select volume C
extend
exit

C: grew from approximately 14 GB to approximately 199 GB.

8. Reserve About 1 GB for a New Recovery Partition

Shrink C: by 1 GB:

diskpart
select volume C
shrink desired=1024 minimum=1024

select disk 0
create partition primary
format quick fs=ntfs label="Windows RE tools"
assign letter=R
exit

The layout was now approximately:

[EFI] [MSR] [C: ~198.9 GB] [Windows RE tools ~1 GB]

9. Restore the WinRE Files

mkdir R:\Recovery
mkdir R:\Recovery\WindowsRE
xcopy C:\WinRE_Backup R:\Recovery\WindowsRE\ /h /i /y
dir /a R:\Recovery\WindowsRE

Verify that Winre.wim, boot.sdi, and ReAgent.xml are present.

10. Convert the New Partition to a Windows Recovery Partition

Verify the new ~1 GB partition number:

diskpart
select disk 0
list partition
select partition 4
detail partition

After confirming Partition 4 was the new 1023 MB Windows RE partition:

set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes=0x8000000000000001
exit

This changes the GPT partition type to the Windows Recovery partition type and applies the appropriate hidden/protected attributes.

11. Register and Enable WinRE

reagentc /setreimage /path R:\Recovery\WindowsRE
reagentc /enable
reagentc /info
Successful final result:
Windows RE status: Enabled
Windows RE location:
\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

12. Final Layout

[EFI 100 MB] [MSR 16 MB] [C: ~198.9 GB] [Recovery ~1 GB]
PartitionPurposeApprox. Size
EFIUEFI boot files100 MB
MSRMicrosoft Reserved Partition16 MB
C:Windows / main data partition~198.9 GB
RecoveryWindows Recovery Environment~1 GB

Final Cleanup

Before deleting the temporary backup, reboot Windows and verify:

reagentc /info

Confirm that WinRE remains Enabled and points to harddisk0\partition4\Recovery\WindowsRE.

After successful verification, the Recovery partition's temporary drive letter can be removed:

diskpart
select disk 0
select partition 4
remove letter=R
exit

Verify reagentc /info again. Only after WinRE remains enabled should the temporary backup be removed:

rmdir /s /q C:\WinRE_Backup
Key lesson: Drive letters such as P:, Q:, R:, or T: do not determine the physical position of a partition. DiskPart normally creates a new partition in available free space according to disk layout, so always check the graphical/physical partition order before relying on a temporary partition.
Read More