[Unstable Update] 2022-08-19 - Kernels, LibreOffice, KDE Frameworks, AMDVLK, Qemu, KDE-git, Haskell, Python

now kate provides both kate & kwrite, so win-win

2 Likes

13 posts were split to a new topic: Issues with GRUB on the unstable branch

:information_source: Changes with Back In Time packages as of 1.3.2-3

  • backintime has been renamed to backintime-qt
  • backintime-cli has been renamed to backintime

After replacing backintime-cli with backintime, you will need to install backintime-qt manually if you want the Qt frontend installed again.

We we’re able to isolate the restart and shutdown issue. In Arch (June 1st ISO), the splash screen message on Kernel 5.19.3 (restart only) was about network and mirrors list refresh. We are not using Ethernet, turn it OFF in the BIOS removes the bug.

All is good now.

pacman -Qii linux60
Name : linux60
Version : 6.0.0rc2-1
Description : The Linux60 kernel and modules
Architecture : x86_64
URL : https://www.kernel.org/
Licenses : GPL2
Groups : None

After steam package replaced steam-manjaro, I had to mark the former as explicitly installed, since it was marked as orphan.

@clmbtti See testing note:

I’m aware of that. My point is that the new package wasn’t set as ex·plic·it·ly installed as it was steam-manjaro.

The name is not my point!

Seems like an anomaly; mine is explicitly installed.

1 Like

Thanks, @Jaypee. I appreciate your kindness for checking it out.

In other news, networkmanager 1.40 has reached us.

@Yochanan out of curiosity, does manjaro ship its kernels with Multipath TCP enabled?

Yes.

1 Like

For the grub update do I need to boot iso to do:
grub-install …?

What grub update? :wink:

The Package update Bro :wink:

There is no package update. See Packages | manjaro

1 Like

@pheiduck is referring to the recent Arch update of grub:

Upgrading grub (2:2.06.r322.gd9b4638c5-1 -> 2:2.06.r322.gd9b4638c5-3)...
:: To use the new features provided in this GRUB update, it is recommended
   to install it to the MBR or UEFI. Due to potential configuration
   incompatibilities, it is advised to run both, installation and generation
   of configuration:
     $ grub-install ...
     $ grub-mkconfig -o /boot/grub/grub.cfg
1 Like

Shouldn’t it be # ? Installing GRUB as a regular user doesn’t seem correct.
Or do GRUB developers Arch packagers run everything as root? :rofl:

Yes, I’m aware. We have our own grub package, we do not import Arch’s.

Ah, that explains why r322 landed here when it was still at Testing on Arch :+1:

I know that, but good to know we’re not backporting this…
Or have to do it later. When grub (the new version / updated pkg) is stable enough.

If you’d followed this thread, you’d have noticed this split-off:

We had that change as well - it’s been rolled back.

2 Likes