It’s a known issue with Gedit 47.0 and will be addressed with 48.0. See my upstream issue:
Indeed. See:
4 Likes
when running the update, i see a lot of ruby packages being replaced with extra/ruby. should i worry or is that fine?
1 Like
Another user had the same behaviour:
1 Like
Thank you for the clarification. The change makes more sense now 
2 posts were merged into an existing topic: Any plans to finally push Plasma 6.1 at least to testing?
I still facing a lot of crashes with this update as I had with 08/aug/2024, just saved a snapshot and rolled back to the 29/jul/2024 witch is the must stable for my machine for a while. Waiting for the next update
Which kernel are you using? mhwd-kernel -li
with the 29/jul/024 release I’m using the 6.9
with the 08/aug/2024 and 20/aug/2024 I was using the 6.10 once the 6.9 was EoL.
I tested 6,6 and 6,1. no important difference.
I can’t confirm, due to the lack of knowledge where the issue is, but I have the impression that the issue might be related more to plasma. It has more chances to crash if I let the system in idle, there is no log available on KSystemlog after hard reboot to support in the analysis.
Just a thought: is it the same with x11 vs. Wayland?
There could be various causes for frequent crashes, which might be hardware related but since it’s more stable with previous releases, this doesn’t seem all that likely.
May be better to start a new thread on this (if you haven’t already).
in general I keep as much default as possible from Manjaro, so I only use Wayland.
I was under the impression that the default on kde/plasma would still be X11
Perhaps you have one of those hardware setups which might still run better on X11.
It is, but one can always choose to use Wayland. I myself have transitioned from X11 to Wayland about a month ago — for both my desktop session and for sddm — and even though there are some Wayland-specific Plasma bugs, I’m quite satisfied with it. 
Ran into issue with vagrant update and the vagrant-libvirt plugin (bigdecimal dependency version mismatch). Stumbled upon someone else online with the same issue; leaving link to their helpful solution here:
Vagrant Error after Updates – Stuff I'm Up To
And for those that don’t like random links:
VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin install vagrant-libvirt
Post upgrade, some CLion projects could not find all the headers. Solved by adding the line below to CMakeLists.txt and rebuilding the project. After the first (re)build, the line can be removed.
include_directories(SYSTEM ./src)
A post was split to a new topic: Realtek RTL8852BE intermittent issues
I have some problem with last update.
All gnome extensions became very unstable : system monitor doesn’t display anything, presspaper manager is shown as empty, close/expand button are not always displayed in the topbar when the windows is maximize (unite), some closed apps stay displayed in the dash.
Also the screen turn black after 30s instead of 5min. The password form is not always displayed on lockscreen (but still work if typed blindly)…
It seems there is a little problem with gnome update…
I am on the latest release and am running GNOME and I did not experience this problem. I presume you haven’t been maintaining incompatible extensions and orphans?
1 Like
8 posts were split to a new topic: File conflicts were detected
I recently found a git repo with a PKGBUILD arch gitlab; this might be what you and I need. I still plan to build Mesa from source to benefit from processor optimizations, but I haven’t had time to test it yet.
UPD. I installed and used this version for a few days. No issues noticed.
1 Like
Im experience system freezes since this stable update, i think something is buggy with Flatpak Nvidia Drivers 