[Stable Update] 2024-01-13 - Kernels, Systemd, Qt5, Mesa, Dbus, Firefox, Thunderbird

[philm]

@j77h

Looks like mkinitcpio-37.2 got downgraded to mkinitcpio-37.1 a few minutes ago.

correct, as we are working on this issue: Mkinitcpio update 37.2-1 break the System

[Aragorn]

@Teo

Generally, if /boot is mounted in fstab, commenting it there and rebooting and it wont be seen anymore and you will not be able to boot. You will have to create /boot if not already there, copy the stuff from old boot and copy grub on that partition.

Strictly speaking, that’s not true. The /boot directory and the EFI partition are both only accessed by maintenance utilities such as grub-install, update-grub and mkinitcpio.

The system itself does not access either /boot or /boot/efi during the boot process.

• In the event of a legacy BIOS boot, the BIOS reads the MBR, which loads the first stage of GRUB, and GRUB itself will then either read the raw blocks of the /boot partition (on MSDOS-style partitioned drives) or of the unformatted bios_grub partition (on GPT-style partitioned drives) in order to load its intermediary stage. This intermediary stage then contains a filesystem driver and will then mount the /boot partition as its own root partition. Upon manually or automatically choosing a GRUB menu entry, the compressed kernel image and the initramfs are read into RAM and decompressed. From that point onward, /boot is no longer being accessed by the system.

• In the event of a native UEFI boot, the UEFI reads the chosen or default EFI executable into RAM and executes it. The UEFI-native version of GRUB installs such an executable in the EFI system partition — both in /boot/efi/EFI/boot and in /boot/efi/EFI/manjaro — and from there on, GRUB will, by way of a filesystem driver, mount /boot as its own root filesystem and load the (chosen or default) compressed kernel image and the initramfs into memory. Once again, as soon as the kernel image is decompressed and begins booting, it no longer accesses either the ESP or the /boot directory.

[Stonith]

For 2. VNC output only 4:3 and cut off:

Uninstalling Krfb, deleting the config file (/home/user/.config/krfbc) and reinstalling the package solved this issue…

Still no clue about the Steam display issue though.

[Kobold]

@soundofthunder

I suspect it might be certificate related.

The error just vanished 20min ago, before it also appeares on my my second device.
Maybe it was a server issue.

I also think it was mainly related to AUR.

Thanks anyways.

[ButterflyMelissa]

I always do, so I can see there the fails pop up, I remove quiet and splash…good luck

[v4mp123]

Hey, I have mkinitcpo 37.2-1 installed. And my system boots.
Just a silly question I know → should I downgrade just to be save?
Or should I don’t touch something which seems to be fine

Thanks in advance.

Edit:
I have found my answer:

[Testing Update] 2024-01-11 - Kernels, Mesa, Dbus, Firefox, Thunderbird

Before anyone asks: If you have no issues with 37.2-1, then there’s nothing to do.

[soundofthunder]

@Kobold

Maybe it was a server issue … mainly related to AUR.

That was always likely. Though I since found Failed to synchronize AUR database (albeit a year old) which might have been related.

@Kobold

The error just vanished 20min ago

As if by magic!

[Kobold]

@soundofthunder

As if by magic!

Exactly, its also not the first time i had saw this error.

[linub]

i ended up keeping it,update went fine.

[LA-MJ]

Your use of “original” is confusing.

My suggestion: “Original” file is the one in the old package version. The “current” file is the original modified by the user or some util. The pacnew is then… well the file in the new package version.

[Stonith]

The Steam client had an update yesterday.
Since that the display issue is also gone.

[soundofthunder]

@LA-MJ

Your use of “original” is confusing.

Only to you, it seems. In context, the original is that which is to be modified; the file in situ; and the new file – the .pacnew – contains the new information.

[andreas85]

@soundofthunder

@LA-MJ

Your use of “original” is confusing.

Only to you, it seems.

You could think of that

• old original file → The default file that would exist if it was current and never changed by the user.
• local file → The file that was on this PC immediately before the update
• suggested file → This is the suggestion to switch to after its changes have been reviewed

I don’t mean to say that my suggestions are the best. Choosing good names can help prevent misunderstandings.

[haha]

After applying this update, xfwm4 freezes a minute after logging in and starting Firefox. If I’m lucky, I can login in with Ctrl-Alt-F2 and run pkill -9 xfwm4 and then Ctrl-Alt-F7 to get an unfrozen terminal. Sometimes I am not lucky and the system freezes and requires a hard power cycle.

Can you help me localize this behavior? I am not sure what commands to run to test this.

[philm]

I’ve now updated mkinitcpio to 37.2-1.6, which fixes the extramodules situation and also kms hook for kernels older than 5.17.

[D.Dave]

@philm

mkinitcpio 37.2-1.6

Did anyone update mkinitcpio to 37.2-1.6? On 2024-01-16 I received an update to 37.1-4 and has worked fine.

EDIT: I installed it, rebooted, and everything is ok.

[1efaf7d71a8637c6800a]

Yeah I noticed sleep, in my case, auto hybrid-sleep, issues with KDE (no more display output after waking up) before this update so I hope the issue will be wiped after this update.

[wael]

@philm @Yochanan do you have any tips for me to fix the problem? i still can’t install the update
Thanks in advance

[Yochanan]

Please create a Support topic if you need further assistance.

[fupalynx]

was this fix already?

I updated to mkinitcpio 37.2-1.6 and the next day my pc wouldn’t pass the boot screen so I had to downgrade it

is it safe to update again?