You are not logged in.
i installed via archinstall script
at the end it gives an error: target not found plasma-wayland-session
error: failed to install packages to new root
This is not my first time installing
maybe because of the new KDE plasma 6.0.1
can someone tell me
thanks for the answer
P.S. updated via discovery
Invalid package file:
invalid or damaged package
Last edited by temmik (2024-03-07 08:39:10)
Offline
the package doesn't exist anymore and can be ignored. This is part of the standard plasma-workspace package now, archinstall needs to get updated.
Moving to Guided Installer
Offline
Just a heads up that the archinstall script will not complete installation correctly if the missing package is ignored. Selecting another profile option then installing plasma group afterwards is probably the best way to get around this.
Offline
It has been fixed, you could also partial update the archinstall script from the ISO until next month.
Offline
here is a specific answers, you need to install before installing:
pacman -Sy archinstall
After that, the installation will continue without errors
P.S. a new version arch install has been released and it was not in the iso file
The question can be closed
Last edited by temmik (2024-03-10 09:21:35)
Offline
You will also need to update the keyring.
pacman -Sy archlinux-keyring
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
after the above actions, the archlinux-keyring is updated automatically during installation
Offline
I just ran into this myself with the archinstall breaking with plasma-wayland-session, then found this post. I tried updating archinstall (and keyring) prior to installation, and it's still breaking.
Only thing odd I'm doing is installing with a lot of different desktops, as this is a vm I'm intending to play with for testing DE's anyways.
Offline
Ok, so damn me, I hadn't noticed the actual install of the updated archinstall and archlinux-keyring failed, so that's why I still got the error.
So then installing archlinux-keyring failed to upgrade, which left me scratching my head again, always something dumb with the keyring on arch! After some furious searching I found the link below to manually update the keyring, that then allowed me to install updated archinstall, that then allowed me to install kde cleanly now with plasma6.
Note for others should they run into this like me before arch team updates the busted installer.
## https://ostechnix.com/solve-error-requi … rch-linux/
pacman-key --init
pacman-key --populate archlinux
pacman-key --refresh-keys
## go get coffee/smoke/wait 5 min
pacman -Sy archinstall
archinstall -v ## should be 2.7.2-1 or later
## now run archinstall as normal
Offline
Ok, so damn me, I hadn't noticed the actual install of the updated archinstall and archlinux-keyring failed, so that's why I still got the error.
So then installing archlinux-keyring failed to upgrade, which left me scratching my head again, always something dumb with the keyring on arch! After some furious searching I found the link below to manually update the keyring, that then allowed me to install updated archinstall, that then allowed me to install kde cleanly now with plasma6.
Note for others should they run into this like me before arch team updates the busted installer.
## https://ostechnix.com/solve-error-requi … rch-linux/
pacman-key --init
pacman-key --populate archlinux
pacman-key --refresh-keys## go get coffee/smoke/wait 5 min
pacman -Sy archinstall
archinstall -v ## should be 2.7.2-1 or later
## now run archinstall as normal
This worked for my installation. Thank you!
Offline
the package doesn't exist anymore and can be ignored. This is part of the standard plasma-workspace package now, archinstall needs to get updated.
Moving to Guided Installer
I installed Arch Linux without archinstall script. I installed in traditional way.
I have installed plasma-workspace package. But I am still unable to login to wayland from SDDM.
Everytime I login from SDDM into Plasma Wayland session, the screen goes blank for 30 seconds and SDDM login screen is back.
If I switch to Plasma X11 session, then it is perfectly working fine.
I am missing out some important package. Here are all the packages I installed during installation.
Firstly using pacstrap, I installed
pacstrap /mnt base linux linux-lts linux-firmware btrfs-progs base-devel git man intel-ucode amd-ucode grub grub-btrfs efibootmgr snapper timeshift zsh zsh-completions zsh-autosuggestions lvm2 cryptsetup reflector bluez bluez-utils cups openssh networkmanager network-manager-applet xorg xdg-utils xdg-user-dirs linux-headers wayland vim nano sudo
Then, I installed all the open source video drivers.
sudo pacman -S xf86-video-qxl xf86-video-intel xf86-video-vesa xf86-video-ati xf86-video-amdgpu xf86-video-fbdev mesa-amber intel-media-driver vulkan-radeon vulkan-intel libva-mesa-driver mesa-vdpau xf86-video-nouveau
Then, I installed KDE Plasma packages excluding Discover package of KDE Plasma group
sudo pacman -S dolphin baloo-widgets dolphin-plugins ffmpegthumbs kdeconnect kdegraphics-thumbnailers plasma-desktop plasma-pa plasma-nm plasma-systemmonitor plasma-firewall plasma-browser-integration plasma-wayland-protocol plasma-workspace ark okular konsole gwenview kscreen bluedevil powerdevil power-profiles-daemon kdeplasma-addons xdg-desktop-portal-kde firefox kate breeze-gtk print-manager kde-gtk-config neofetch spectacle kaddressbook sddm sddm-kcm
Then, I enabled SDDM and tried to login into Plasma Wayland Session. But I couldn't login as I told earlier.
sudo systemctl enable --now sddm
Offline
And nothing of what you are talking about has no relation to this thread or the error within. Please don't hijack unrelated threads.
Make a new thread post details about your hardware and post the full output of
sudo journalctl -b
eglinfo -B #mesa-utls
when coming from a failed plasma session. Something I can tell you outright is that you most likely want to get rid of everything you installed in that second line except the vulkan packages and you want to switch to mesa instead of mesa-amber if your hardware is newer than ~15 years old -- should your hardware be ~15 years old that might well be the reason you can't run a Wayland session
Offline