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

[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…

[Armag67]

Hooray, you saved my day. I’ve been struggling for months to apply a dark theme to my qt5 applications in Xfce. Following your advice, I moved these four lines from .profile to .bash_profile

export EDITOR=/usr/bin/nano
export QT_QPA_PLATFORMTHEME=qt5ct
export QT_AUTO_SCREEN_SCALE_FACTOR=0
export GTK2_RC_FILES="$HOME/.gtkrc-2.0"

And everything works correctly in the dark theme (except for baobab which mysteriously remains in the light theme).

Edit: there is no mystery, baobab requires gtk4 which is not supported by Xfce…

[Buncho]

I get a black screen during device inactive

[linux-aarhus]

@JMHoffmann

An issue I had is using sd-boot+ukify+kernel-install+sbctl is that the sbctl hook in /etc/initcpio/post/ is broken. I had to fully comment it out. kernel-install has its own sbctl hook to sign a uki.

That is an unsupported use-case

I know because I have a similar construct with a laptop - boot using a signed efi-stub

[philm]

@Olli

fakeroot is a primary security issue and other distros use it also while updating-processes but they delete it after finishing.

Can you point me to one of these distributions and how they do it?

@MrLavender

You never explicitly installed it because previously fakeroot was automatically installed as a dependency of pacman. So it was impossible not to have it. It is now a dependency of both pacman-contrib and base-devel (which is a requirement for building AUR packages on Manjaro.).

Yep, in the past we bundled pacman-contrib into the pacman package: [pkg-upd] 6.0.2-17 (69072048) · Commits · Packages / Core / pacman · GitLab

[notageek]

@Yochanan

See my post here:

Yes, edited my post and linked the page yesterday

@linub

do new ISOs come with Pipewire as default?

yes

@1efaf7d71a8637c6800a

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

for polkit, you have to change as Yochanan stated
for audit is not clear to me, if I change or not the result of

ls -al /var/log/audit/

is same…

[kwacorn]

After applying pacdiff changes I appear to have lost the users and can only login as root.

I applied the updates to my two less critical systems, an old Intel based desktop system and and old AMD based netbook. They rebooted fine and I was able to do graphical login as normal then check for changes using pacdiff -s. As I had made no changes to any of the files for which there was a *.pacnew I overwrote all the files. There were no *.pacsave files afterwards, I do not know if there should be.

However on rebooting I appear to have the Plymouth problems and cannot login as any user except root on a TTY (Ctrl+Alt+Fn), which seems a similar the above problem:

@1efaf7d71a8637c6800a

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 am continuing to investigate, though guidance welcome, but I thought it best to report the issues now.

[LA-MJ]

@kwacorn

As I had made no changes to any of the files for which there was a *.pacnew I overwrote all the files. There were no *.pacsave files afterwards, I do not know if there should be.

I guess this is a lesson and you should not be doing that. Measure first, cut later

[anon51566685]

@kwacorn

I am continuing to investigate

There’s nothing to investigate. You overwrote all users in passwd instead of merging changes.

[JohnML]

i just have overwritten the existing passwd with passwd.pacnew and my Manjaro didn’t start any more only blinking courser. I now restore a backup and remove passwd.pacnew.

Are we the only ones with this severe issue? But i hope i missed something?!

Solution as allways: i am the ■■■■■. only update the one line at the beginning of passwd !!!

[gefri]

Attention with new Remmina v1.4.34
There seems to be an authentication bug with RDP connecting to MS servers, especially via connection brokers / RDP gateways.
The previous v1.4.33 is ok.