I am now running baloo 6.6 and it remains discreetly in the background.

@Thijs van Ulden Thanks for the hint, as long as I have been using KDE, I noticed yesterday for the first time that the process is so aggressive.

I’m using hstr since some years and it works perfect for me. https://github.com/dvorka/hstr

INOTIFY a GUI for monitor file changes. https://en.wikipedia.org/wiki/Inotify

@Dust0741 sometimes this can help -> in a linux console: ntfsfix -b -d /dev/sda1 oder ntfsfix -b -d /dev/sda2.

Lonewolf - https://flathub.org/apps/site.someones.Lonewolf

Progress - https://flathub.org/apps/io.github.smolblackcat.Progress

are some alternatives too.

Flatpaks require more storage space as all dependencies are combined in a flatpak. For me rather 2nd choice.

@eli04 Hast Du nicht gefragt, woher die Firma Deine Daten hat?

@sga ok, since you didn’t mention that before, that would be a possible source of error.

@sga I think you have to ask an admin of the university because a timeout is usually a problem on the server side.

This should work for all Nvidia user working with Plasma6 on Arch, Garuda etc:

Edit /etc/mkinitcpio.conf

MODULES=()

Change the Line and add the Nvidia Modules:

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

Save the File and create the initramfs:

sudo mkinitcpio -P

Now Add the Kernelflags to Grub: nano /etc/default/grub

There is a line like this:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet"

add this to the line:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1"

Now generate the new Grub config:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Reboot and have fun with wayland. Maybe you have to install: xorg-xwayland

without any logfile it’s difficult to say where the problem might lie.