@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!
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? 
The Package update Bro
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? 
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 
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
While doing the update:
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Package (6) Old Version New Version Net Change Download Size
extra/bluez 5.65-2 5.65-3 0.00 MiB
extra/bluez-libs 5.65-2 5.65-3 0.00 MiB
...
done
:: Processing package changes...
(1/6) upgrading bluez [############################################################################] 100%
warning: directory permissions differ on /etc/bluetooth/
filesystem: 755 package: 555
(2/6) upgrading bluez-libs [############################################################################] 100%
(3/6) upgrading gnupg [############################################################################] 100%
...
I got permission warning.
How do I recognize in that case and in general case:
does a package came with erroneously changed permission (bug)
OR
it was updated to proper/more suitable version of permissions
?
The permissions were changed purposely from 755 to 555, see the 5.65-3 commit.
You can follow up with:
sudo chmod -R 555 /etc/bluetooth/
2 Likes
Thanks, Mark!
OK, I think that my question above can’t have an answer when changes comes from package author: any changes in source code / building processes are a new feature/fix and could not be classified as bug or proper fix at the point of installation to a user machine, cause we have no new usage experience with that new version.
So I guess in general the usual user behavior should be to change permissions according to warnings of mentioned ones.
I’m I the only one getting 5.25.5, is it first available to the dev channel?
Since Sept. 1st, KDE 5.26 repo is enabled. Apart today, since then, 180 packets came in for preparing KDE 5.26. K stuff and plasma stuff get rewrited on a daily basis.
On the dev channel, 5.25.5 upgrade Is 98 packets. One packet came with an old number: Kconfig 5.96.
All is good and waiting for the big jump: 5.25.90.
[2022-09-07T18:46:58-0400] [ALPM] upgraded plasma-desktop (5.25.4.r9590.geb298689e-1 → 5.25.5.r9593.g7f1c5184d-1)
No, you’re not. Arch updated it yesterday and it’s available in both the Manjaro unstable and testing branches: Packages
[quote=“anon60794543, post:41, topic:119809”]
KDE 5.26 repo
[/quote
I assume you mean the kde-unstable repo? That is not related and is only meant for testing. Please do not report issues about it in this thread.