baloo daemon crashes unexpectedly

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
Vanitarium
Posts: 34
Joined: Wed Feb 03, 2021 4:35 am

baloo daemon crashes unexpectedly

#1 Post by Vanitarium »

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.14.5 info: latte-dock wm: kwin_x11 dm: SDDM 
           Distro: MX-19.4_kde_x64 patito feo March 31  2021 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TUXEDO product: TUXEDO Aura 15 Gen1 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: TUXEDO model: NL5xRU serial: <filter> UEFI: INSYDE v: 1.07.08TTR2 date: 03/18/2021 
Battery:   ID-1: BAT0 charge: 38.4 Wh condition: 46.3/48.3 Wh (96%) volts: 15.8/15.2 
           model: Notebook BAT type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP 
           arch: Zen family: 17 (23) model-id: 60 (96) stepping: 1 microcode: 8600106 
           L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31940 
           Speed: 1473 MHz min/max: 1400/2000 MHz boost: enabled Core speeds (MHz): 1: 1473 2: 1408 
           3: 1391 4: 1368 5: 1393 6: 1706 7: 1625 8: 1651 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Renoir vendor: CLEVO/KAPOK driver: amdgpu v: kernel bus ID: 05:00.0 
           chip ID: 1002:1636 
           Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.0-5mx-amd64 LLVM 11.0.1) v: 4.6 Mesa 20.3.4 
           direct render: Yes 
Audio:     Device-1: AMD vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus ID: 05:00.1 
           chip ID: 1002:1637 
           Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: CLEVO/KAPOK 
           driver: N/A bus ID: 05:00.5 chip ID: 1022:15e2 
           Device-3: AMD Family 17h HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel 
           bus ID: 05:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k5.10.0-5mx-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK 
           driver: r8169 v: kernel port: 2000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 bus ID: 03:00.0 
           chip ID: 8086:2723 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 585.01 GiB used: 22.64 GiB (3.9%) 
           ID-1: /dev/mmcblk0 model: ED4QT size: 119.25 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> scheme: GPT 
           ID-2: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 serial: <filter> rev: 1B2QGXA7 
           scheme: GPT 
Partition: ID-1: / raw size: 137.24 GiB size: 134.09 GiB (97.70%) used: 7.50 GiB (5.6%) fs: ext4 
           dev: /dev/nvme0n1p2 
           ID-2: /home raw size: 320.27 GiB size: 314.24 GiB (98.12%) used: 15.14 GiB (4.8%) 
           fs: ext4 dev: /dev/nvme0n1p4 
           ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 32.5 C mobo: N/A gpu: amdgpu temp: 31 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/bluemail.list 
           1: deb https://packages.bluemail.me/repos/debian/ ./
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ buster main contrib non-free
           2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ buster main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/testrepo/ buster test
           3: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           No active apt repos in: /etc/apt/sources.list.d/wavebox-stable.list 
Info:      Processes: 267 Uptime: 47m Memory: 30.74 GiB used: 2.14 GiB (7.0%) Init: SysVinit v: 2.93 
           runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
The baloo_files daemon crashes during use of KDE Plasma desktop and the crash report is here
baloo_file-20210527-135627.kcrash.txt
It appeared on the panel system tray and was not related to any file search activity by myself.
The bug report wizard replies with a comment that the report is not enough for developers to use.
When I run

Code: Select all

 balooctl start
it returns following error



Code: Select all

KCatalog being used without a Q*Application instance. Some translations won't work
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Baloo File Indexing has been disabled
What can I do then??
Help would be very welcome...
You do not have the required permissions to view the files attached to this post.
Last edited by Vanitarium on Thu May 27, 2021 10:01 am, edited 3 times in total.
User of TUXEDO AURA15v.1 laptop: AMD RYZEN 7 running MX Linux.Yunohost on Intel i3
Don't use Windows, tolerates macOS, loves MX Linux

User avatar
richb
Administrator
Posts: 10927
Joined: Wed Jul 12, 2006 2:17 pm

Re: baloo daemon crushes unexpected

#2 Post by richb »

For what it is worth you are not alone. Baloo often misbehaves for me, crashing and not responding to terminal commands. I have not found a solution. I use catfish for searches
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
Vanitarium
Posts: 34
Joined: Wed Feb 03, 2021 4:35 am

Re: baloo daemon crashes unexpectedly

#3 Post by Vanitarium »

Thanks @richb , I have searched files before in Dolphin and all was OK. I use catfish too and didn't know that baloo existed at all. Now I have learned that Dolphin finds using baloo!! Unfortunately one cannot remove baloo on its own, so I have disabled it as above. pretty bad for KDE to have such a bad daemon!!!
User of TUXEDO AURA15v.1 laptop: AMD RYZEN 7 running MX Linux.Yunohost on Intel i3
Don't use Windows, tolerates macOS, loves MX Linux

User avatar
richb
Administrator
Posts: 10927
Joined: Wed Jul 12, 2006 2:17 pm

Re: baloo daemon crashes unexpectedly

#4 Post by richb »

Hopefully they have made it more reliable in later KDE versions. When it works it is quite nice which is most of the time. You may want to explore some of the baloo terminal commands that can get it restarted after a crash. They are invoked with balooctl

Code: Select all

richb@mx:~
$ balooctl --help
Usage: balooctl [options] command status enable disable start stop restart suspend resume check index clear config monitor indexSize

Options:
  -f, --format <format>  Output format <json|simple|multiline (default)>.
                         Only applies to "balooctl status <file>"
  -v, --version          Displays version information.
  -h, --help             Displays this help.

Arguments:
  command                The command to execute
  status                 Print the status of the indexer
  enable                 Enable the file indexer
  disable                Disable the file indexer
  start                  Start the file indexer
  stop                   Stop the file indexer
  restart                Restart the file indexer
  suspend                Suspend the file indexer
  resume                 Resume the file indexer
  check                  Check for any unindexed files and index them
  index                  Index the specified files
  clear                  Forget the specified files
  config                 Modify the Baloo configuration
  monitor                Monitor the file indexer
  indexSize              Display the disk space used by index
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

Post Reply

Return to “MX KDE Official Release”