Okt 29 08:04:41 HP rtkit-daemon: Successfully limited resources. Okt 29 08:04:41 HP systemd: Started RealtimeKit Scheduling Policy Service. Okt 29 08:04:41 HP rtkit-daemon: Successfully dropped privileges. Okt 29 08:04:41 HP rtkit-daemon: Successfully called chroot. Okt 29 08:04:41 HP dbus-daemon: Successfully activated service '1' Okt 29 08:04:41 HP systemd: Starting RealtimeKit Scheduling Policy Service. Okt 29 08:04:41 HP dbus-daemon: Activating via systemd: service name='1' unit='rvice' requested by ':1.62' (uid=1000 pid=7156 comm="/usr/bin/pulseaudio -daemonize=no -log-target> Okt 29 08:04:41 HP kscreen_backend_launcher: kscreen.xrandr: XRandR::setConfig done!
What is baloo file extractor update#
Okt 29 08:04:41 HP kscreen_backend_launcher: kscreen.xrandr: XRandROutput 66 update Okt 29 08:04:41 HP kscreen_backend_launcher: kscreen.xrandr: Result: 0 I have not experienced this behavior on Manjaro before on any DE, so I am wondering what I can do about this. I noticed this first after uninstalling amd-ucode and rebooting (I have Intel CPU). I was just installing Manjaro KDE from Manjaro GNOME using Architect iso. The fans ramp up and stay up there for maybe 5 - 10 minutes, but eventually this behavior only lasts for few minutes.
htop shows between 90 - 98% CPU usage on baloo_file_extractor. For the last two boots, this baloo_file_extractor has been hitting my CPU rather hard for quite some time.
0 kommentar(er)
