How to start Manjaro KDE?

Today, I download and installed latest Manjaro KDE(manjaro-kde-23.1.4-240406-linux66) to my laptop.

How ever, I cannot do anything. I think Manjaro Linux is most difficult OS.
thank you.

# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (2) linux66-6.6.26-1  xorg-xwayland-23.2.6-0

Total Installed Size:  137.50 MiB
Net Upgrade Size:       -0.05 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring                                     [####################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
# pacman-key --init
/usr/bin/pacman-key: line 31: /usr/share/makepkg/util/message.sh: No such file or directory
/usr/bin/pacman-key: line 32: /usr/share/makepkg/util/parseopts.sh: No such file or directory
/usr/bin/pacman-key: line 631: parseopts: command not found

6.6.25-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Apr  4 20:32:38 UTC 2024 x86_64 GNU/Linux

Check the ISO used for errors.

If you want to automate the check use a the [manjaro-iso-downloader] or the python script [root tip] [Utility Script] Using python to download and verify a Manjaro ISO

2 Likes

Did you verify the downloaded .ISO?

@linux-aarhus You beat me to it!

I checked it.

 Get-FileHash -Algorithm SHA256 .\manjaro-kde-23.1.4-240406-linux66.iso

Algorithm       Hash                                                                   Path
---------       ----                                                                   ----
SHA256          31872DED447254E4531B6877F8894300B7A96E5D39A9E7B806498DB033EC9BCA

31872ded447254e4531b6877f8894300b7a96e5d39a9e7b806498db033ec9bca  manjaro-kde-23.1.4-240406-linux66.iso

I think it have not an error.

thank you!

Install something that is more appropriate to your skill level then.

And why you can’t do anything? How and where did you installed it?

You can also use pamac GUI from taskbar>settings>add/remove software, to update your stuff.

Maybe refresh your mirrors first with:

sudo pacman-mirrors --fasttrack

Thanks for grateful and constructive advice!
Then , Which os do you think?

I installed my laptop by USB.
And updated mirrors, but it still doen’t work.

Did you used pamac GUI or Terminal?

Maybe your USB Stick has a problem? How did you created it?

Did you used a custom installation? Maybe you did a mistake while installing?

I created in Steam Forum a noob guide (FAQ inclusive), how to install Linux and which Linux OS you may want… its maybe worth for you to look into:

I use pamac on Teminal.
I do not think my USB stick has probrem. I created by Rufus.
And not custom install.
Thank you for your guide. I will read it.

1 Like

When you think that Manjaro is so difficult why you use Terminal, when you don’t have too?

The GUI is right there…

Because GUI is only a simple message.

I decide delete latest manjaro on my laptop.
I appreciate your assistance.

Apparently:

Edit:

Then Arch would be a complete nightmare and Gentoo would be that nightmare come to life.

Are you trying to run Manjaro in WSL or did you just use Powershell to verify the ISO?

If you are, please acknowledge that we provide no support for Microsoft WSL.

Use [ventoy] to make the stick bootable then drop the ISO file onto the stick.

Boot the stick → select the manjaro ISO → select use grub mode

That had me confused as well. I find e.g.

sha256sum -c manjaro-kde-23.1.3-240113-linux66.iso.sha256

works just fine. Can always add --ignore-missing as an option in case of the sha* file containing multiple checksums, such as is the case with Linux Mint.

I don’t know about the Windows/WSL side of things.

At least with Ventoy, the above method can be used to verify the .ISO on the actual stick, as well. Just have the sha* file in the same directory for simplicity.

I only verify the iso. Because my linux machine don’t work now.

I used to use Manjaro Linux xfce on the same machine, but it would not boot properly due to grub corruption.

I tried to install a new kde version on the same machine, but I could not repair the keyring in any way.

Did you made a clean installation? All old and unused partitions was removed on the disk?

Did you installed with legacy boot or in Uefi mode? Did you deactivated fast boot in bios?

warning: Public keyring not found; have you run ‘pacman-key --init’?
downloading required keys…
error: keyring is not writable

Whats that about? Did you run the command? With sudo.

clean install for / , /boot/efi partition. but /home did not full clean.
And UEFI mode , secure and fast boot mode desabled.

I do not know how to fix this message. yes, I had with on root user.

I wrote top of this thread, after finished install, I try to sudo pacman -Syu but appear this error.

# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (2) linux66-6.6.26-1 xorg-xwayland-23.2.6-0

Total Installed Size: 137.50 MiB
Net Upgrade Size: -0.05 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring [####################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

next, I tried this command pacman-key --init.

# pacman-key --init
/usr/bin/pacman-key: line 31: /usr/share/makepkg/util/message.sh: No such file or directory
/usr/bin/pacman-key: line 32: /usr/share/makepkg/util/parseopts.sh: No such file or directory
/usr/bin/pacman-key: line 631: parseopts: command not found

It is over.

Could be Rufus messing up the ISO. Would not surprise me. Had it happen with many old USB tools. Has happened zero times with Ventoy.

I too, would recommend using a Ventoy USB. The following information describes how to create one in Linux - but you can also make one in Windows - the relevant information is on the Ventoy site.

Ventoy USB

Using a Ventoy USB allows to boot any bootable ISO you choose; all from one USB. The beauty of using Ventoy is that nothing else is needed.

Boot with a Ventoy USB, and ISO files are automatically listed in the Ventoy menu, and can be booted directly. A 32GB (minimum) capacity USB should allow ample space to store several ISOs of your choice.

Ventoy is available from the official Manjaro extra repository:

sudo pacman -S ventoy

Type ventoy (without arguments) to see usage information:

Usage:  Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX  
 CMD:  
  -i  install Ventoy to sdX (fails if disk already installed with Ventoy)  
  -I  force install Ventoy to sdX (no matter if installed or not)  
  -u  update Ventoy in sdX  
  -l  list Ventoy information in sdX  
  
 OPTION: (optional)  
  -r SIZE_MB  preserve some space at the bottom of the disk (only for install)  
  -s/-S       enable/disable secure boot support (default is enabled)  
  -g          use GPT partition style, default is MBR (only for install)  
  -L          Label of the 1st exfat partition (default is Ventoy)  
  -n          try non-destructive installation (only for install)

Write the Ventoy system to an empty USB drive;
use /dev/sdX to target the device itself (not a partition).

This is the command I might normally use:

sudo sh ventoy -i -r 100 -S -g -L VOLUME /dev/sdX
  • Substitute VOLUME for a volume label name to use.
  • Substitute /dev/sdX for the location of your USB device.
  • Preserve some space on the target device (example allows 100mb).

See also: Ventoy (GitHub);

I hope this is helpful. Cheers.