[Stable Update] 2024-02-21 - Kernels, KDE, VirtualBox, Calamares, ROCm, Firefox, Thunderbird

[nrw2000]

There are a lot of warnings like the ones below, and the update failed as a result. Does anyone know how to fix this?

Warning: npm: /usr/lib/node_modules/npm/node_modules/wrap-ansi/node_modules/strip-ansi/license already exists in filesystem
It has been backed up to /usr/lib/node_modules/npm/node_modules/wrap-ansi/node_modules/strip-ansi/license.old
Warning: npm: /usr/lib/node_modules/npm/node_modules/wrap-ansi/node_modules/strip-ansi/package.json already exists in filesystem
It has been backed up to /usr/lib/node_modules/npm/node_modules/wrap-ansi/node_modules/strip-ansi/package.json.old
Resolving dependencies...
Checking inter-conflicts...
Error: Failed to commit transaction: transaction not prepared

Found recommendations to execute sudo pacman -S npm --overwrite='*' here npm update error in arch · Issue #636 · nodesource/distributions · GitHub. Is this correct?

yes, sudo pacman -S npm --overwrite='*' fixed it

[BG405]

@linub

can i put it back?

If you wish, but as @Teo said, it’s useful for diagnostics … and AFAIK doesn’t affect start-up time.

@MrLavender

So it was impossible not to have it.

This is what confused me about @robbie-hatley 's post.

[linub]

if might be insufficient by itself and i won’t bother further with it:
https://wiki.archlinux.org/title/Silent_boot
Thanks
And @Teo

[jonnyabu]

@ManLuxer

export QT_QPA_PLATFORMTHEME=qt5ct

Awesome. Thanks for the info!

[infabo]

~/.profile no longer sourced

[tandrey]

Hi everyone!

I’m finishing the update using pacdiff. All files done except the last one: polkit-1.pacsave. I’ve read the known issues section but still confused since I don’t remember I’ve modified polkit-1 file before. Is it safe to just remove polkit-1.pacsave file as pacdiff suggests?

[Kobold]

@Aragorn

If you had updated with pacman instead of through the pamac GUI, then you would have seen the question to replace the package appear right at the top of the update process.

Well after i updated again with my PC now, i saw also the removal from this package, it was shown in the pamac GUI.

But the additional information about known issues and solution, was a little confusing for me.

Because i thought i had to manually deal with the replacement from bashrc-manjaro… i think it would be better if it not mentionend under know issues, when everything dealed automatically anyways.

[Aragorn]

@Kobold

i think it would be better if it not mentionend under know issues, when everything dealed automatically anyways.

Some people had modified their /etc/bash.bashrc, and in that case, they needed to know that those modifications were going to disappear.

[Fabby]

Have you tried Ctrl+Alt+F3 already as TTY1 now contains the last text outrput, TTY2 your current GUI and TTY3 and following are now the text consoles…

[Fabby]

Solution updated with #2. Thanks for letting us know!

P.S. Don’t forget to edit your /etc/skel/.bashrc file too!

[Fabby]

Indeed: /etc/.bash.bashrc is the system-wide one, so if you have multiple users, that’s the one to change so @robbie-hatley probably has a multi-user system just like mine…

[r0nin]

Help, help, my system is showing me the boot log!!!

[1efaf7d71a8637c6800a]

Thank you for the plymouth modification in this update. Everything went smoothly,
except:

after running pacdiff -s after the update and overwriting /etc/passwd with the pacnew, I could not use sudo anymore, nor log into gui or tty. I noticed my old one was in the first line with /bin/bash.
I had to get the Timeshifted file and copy it back to restore my system’s functionality! (copied the /etc/passwd and /etc/passwd- files back)
Before that I tried modifying the new one to /bin/bash in the first line but that didn’t work.
Noticed there is also the /etc/passwd- file that I didn’t modifly…

How should I go about it now? I don’t want to miss the advantages of the pacnew in the future.

@v4mp123

I now have a /etc/passwd.pacnew file with only one entry

root:x:0:0::/root:/usr/bin/bash

My old one has 42 lines.
I’ll keep my old config

Without my old config I can’t login …

Also

@notageek

found this in pacman.log

[ALPM] warning: directory permissions differ on /var/log/audit/
filesystem: 700  package: 755

[ALPM] warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750  package: 755

^ I got the same warnings while upgrading. How should I go about it? Change the permissions or ignore the warnings?

[Yochanan]

@notageek

[ALPM] warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750  package: 755

See my post here:

[Unstable Update] January 2024 Edition

Yes, it’s changed with polkit 124-1. Examples: This will take care of it once and for all: sudo chmod 0755 /usr/share/polkit-1/rules.d/

[MrLavender]

Has already been posted in this thread;

Question about passwd.pacnew

Hello everyone, I am currently looking at the .pacnew files after the update. A passwd.pacnew was created in which there is only one line: root:x:0:0::/root:/usr/bin/bash In my file it says at the beginning: root:x:0:0::/root:/bin/bash Just to be sure, I want to ask if I should change the line root:x:0:0::/root:/bin/bash to root:x:0:0::/root:/usr/bin/bash There is also a lot more text (40 lines in total) in my previous passwd file. I’d better leave them all, right? Bes…