[Stable Update] 2023-05-07 - Kernels, KDE Gear 23.04.0, KDE Frameworks 5.105.0, Qt5, Firefox, Thunderbird

[cscs]

Dont use sudo with pamac.
Otherwise it looks like a partial upgrade or you have an odd package
(like here: Error Logging Into Plasma After Hard Reboot)
Sort your mirrors to be sure as well. ex;

sudo pacman-mirrors -f && sudo pacman -Syyu

[jonas.eberle]

Thank you. Will do and remember that.
It seems the upgrade uninstalled a number of KDE packages.

I did the KDE Plasma 5 steps from Install Desktop Environments - Manjaro and KDE is back now

[jeancf]

Can you please enable bootsplash on linux63?

> zgrep CONFIG_BOOTSPLASH /proc/config.gz
# CONFIG_BOOTSPLASH is not set

Thanks

[leledumbo]

I see, so this is not guaranteed to happen. OK, I’ll back that up and see if I experience the problem or not.

EDIT: yep, mine is safe.

[2Stoned]

I ran out of space in home and now it boots to a black screen and shows the mouse cursor. Tty2 and startx brings me to a completely black screen. I deleted some big folders, so there is enough space now, but it won’t show up sddm or the GUI. It happens with kernel 6.3, 6.2 and 5.15.

Wny ideas how to fix this?

[Mirdarthos]

@2Stoned

Wny ideas how to fix this?

Enter a chroot environment and run the sync again, this time with enough free space:

How to chroot

1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

2. Write/copy/dd the ISO to a USB thumb drive.

3. When done, boot with the above mentioned USB thumb drive into the live environment.

4. Once booted, open a terminal and enter the following command to enter the chroot encironment:

manjaro-chroot -a

5. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

Once successfully in the chroot environment, run the following to do a complete sync/update:

pamac upgrade && pamac upgrade --aur --devel || echo -e '\033[0;91mThere was an error upgrading the system. AUR packages not upgraded.\e[0m'

This will update your system and ONLY if that was successful update any AUR packages.

a Reminder: While use of the AUR is possible, it’s neither recommended nor supported.

I recommend pamac instead of pacman, especially for newcomers as pamac was developed by Manajaro (developers) for Manjaro and just takes care of more thing than pacman.

[wael]

I can not run Spyder anymore
in the terminal i got this last line:

pkg_resources.DistributionNotFound: The ‘astroid<=2.17.0-dev0,>=2.15.4’ distribution was not found and is required by pylint

I still have astroid 2.15.2. How can i update to astroid 2.15.4 ?
Thanks

[2Stoned]

OK, it appears that the update itself went fine. My chrooted pamac said “nothing to do”. So, I tried to restore my time shift backup instead, which brings back SDDM, but now I cannot login. I type in my password and hit enter. Thereafter, SDDM freezes. I can still move the mouse cursor but cannot click anything.

Can I somehow circumvent SDDM / repair SDDM / see if Plasma is running fine or SDDM is hanging and just not loading KDE?

[julikaiba]

For me xfce4-pulseaudio-plugin kept crashing instantly until i downgraded it to the previous version.

[1efaf7d71a8637c6800a]

I recommend pamac instead of pacman, especially for newcomers as pamac was developed by Manajaro (developers) for Manjaro and just takes care of more thing[s] than pacman.

Does it have the same commands, like for instance sudo pacman -Syyu equals sudo pamac -Syyu ?
And are you the only one who recommends pamac over pacman from tty?
I did pacman updates from tty and got few bugs except the slide back desktop effect which confuses front and back then and when when I switched Activities.
I recommend force re-installing video-nvidia after every update.

[hasezoey]

as a update, i had updated everything except amd-ucode, and it was fine, then upgraded the bios version (ASUS b550f from 2803 to 3002) and it ran fine, then installed the update for amd-ucode and it also runs fine now

[shnplr]

Hi, After this update crc start fails with message ‘internal error: virtiofsd died unexpectedly’. systemctl status libvirtd.service shows as no longer active. Linux419. Reverted back to snapshot and its fine.

[cscs]

Not the same.
pamac uses ‘regular phrases’ like install.
pamac also has some bugs about grabbing packages from the AUR at the moment … and some other quirks. AFAIK theres not any reason to recommend pamac over pacman besides that ‘easiness’.
(in fact myself and some others much prefer, and choose, to use pacman exclusively)
Someone once said ‘pamac does extra things’ … I still dont have any evidence for what they were referring to. Most automation that pamac does (like automatically changing mirrors) is not required, many people deactivate, and are often a source of breakage.
All of that is not to tell folks what they should use … just that I dont see any reason to avoid pacman if you are comfortable with it.

[tsuki]

It APPEARS that the default kernel gets changed automatically to 6.2? For whatever reason, my system won’t run the 6.2 kernel. Luckily, it runs 6.1 okay.

[cscs]

@tsuki

It APPEARS that the default kernel gets changed automatically to 6.2

I find that unlikely considering that is not the normal functioning structure, though avilable at one time, as well as petitions to implement it, ie: Proposal to streamline/simplify kernel updates and management for users

[parahaps]

This update broke tpm2 unlocking of luks disks on sdboot, again. This also broke a couple of updates ago, but a revert to cryptsetup, pushed in an update, fixed it.

It results in: “systemd-cryptsetup[441]: TPM2 support is not installed.” on boot.

The breaking change seems to be an incompatibility between systemd-252 and cryptsetup-2.6.1-3.2. See:

Breaking change in cryptsetup 2.6.1-3

I just installed the latest stable updates on my laptop and found that my LUKS unlock with TPM2 was broken. Took me a while to track it down but I finally narrowed it down to just the cryptsetup 2.6.1-3 package – by downgrading to 2.6.1-1 the automatic unlock works again. I strongly suspect that it’s related to this change, but I’m not certain the best route to get it reported to the upstream – I’ve heard that arch folks tend to turn away reports from manjaro users. Anyone have suggestions w…

[Mirdarthos]

No, as @cscs said, they’re not the same.

As he/she/it also said, someone once said, which I believe is me, "that it does more things, which I believe was me. That is why I have always and will always recommended pamac. It was even recommended to use pamac in many of the update announcements, by no one other than the great @philm himself. And regardless whether it’s considered good practise or not, it’s the way things is.

You can find more information about pamac if you RTFM:

man pamac

@cscs

AFAIK theres not any reason to recommend pamac over pacman besides that ‘easiness’.

And that’s why I recommend it, especially to newcomers - it’s less daunting.

@cscs

pamac also has some bugs about grabbing packages from the AUR at the moment … and some other quirks.

Never experienced anything of the sort.

@cscs

I still dont have any evidence for what they were referring to.

I have. When using pacman a lot more human intervention was necessary for some things. No, I don’t remember which things.

@cscs

if you are comfortable with it

Which most people aren’t. And that’s why I have the disclaimer:

I recommend pamac instead of pacman, especially for newcomers as pamac was developed by Manajaro (developers) for Manjaro and just takes care of more thing than pacman.

And since Manjaro attracts a lot of newcomers, people that have no experience with Linux or the CLI, it’s likely to stay that way.

And as I have it, most people only end up on the Forum when something breaks and they need help. Heck, that was why I came here originally. So most people are at least newcomers to Manjaro, most to Linux. So I’d say they’re newcomers.

[cscs]

These 2 are from today alone…

Unable to uninstall pipewire

i try to do pamac remove pipewire-pulse but it says Preparing… Checking dependencies… Error: Failed to prepare transaction: could not satisfy dependencies: removing pipewire-pulse breaks dependency ‘pipewire-pulse’ required by manjaro-pipewire removing pipewire-pulse breaks dependency ‘pulseaudio’ required by pulseaudio-ctl how do i remove pipewire?

Have Pamac perform AUR updates only for packages already installed from AUR

Pamac’s AUR update feature has caused a significant number of problems due to it overwriting existing packages from the repositories. I can’t really think of an upside for this feature, besides allowing a smooth transition for packages removed from the official repositories, which is less important IMO. There’s even a highly-viewed guide about how this feature is problematic. Correct me if I am wrong, but it should not be too difficult for Pamac to run an additional check on AUR updates to make…

pacman has none of these issues, or any other one I (or you) can point to … aside from ‘confusing syntax’.
Once again … folks should use what they want. I just dont understand fear-mongering around pacman.

[Mirdarthos]

I don’t have any specific posts, quotes or anything like that. Maybe I’m just more careful since I’ve used Ubuntu in the past, so I know it’s not Windows. And I prefer the CLI for stuff like this, so I might just be more careful, I don’t know.

@cscs

folks should use what they want.

Indeed. But that won’t stop me from making a recommendation. And I’ve had this conversation before, that’s why I put that disclaimer along with my recommendation.

You’ll notice I don’t answer to support requests regarding anything to do with sound, since I can’t use sound, so don’t have experience with it. I don’t wish to make people scared about pacman, or Linux, I just make my recommendations based on personal experience and conviction.

And I gave my reasons already.