https://bugs.kde.org/show_bug.cgi?id=500665
--- Comment #26 from postix <pos...@posteo.eu> --- > Are you using the Paragon NTFS drivers or the older FUSE ntfs-3g drivers? mount says /dev/sda1 on /media/foo type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) /dev/sdb1 on /media/bar type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) ntfs-3g is installed and if I see it correctly openSUSE does not offer the newer Paragon NTFS driver > If you search for one of the files on your NTFS drives with "balooctl -i > one-of-your-files.txt", possibly balooctl6, do you get just the one hit? For a few files I've tried I only got a single hit with `baloosearch -i myfile` > Have a look as see whether Baloo is running under systemd, specifically the > systemd unit file that limits RAM useage to 500 MB. You can see with > "systemctl status --user kde-baloo" and you want to look at the "Memory:" > line. There's no memory line for me. > Are you watching the content indexing "as it happens" with a "balooctl > monitor" in a separate window, again balooctl may be balooctl6 Nope, I am not. -- You are receiving this mail because: You are watching all bug changes.
