https://bugs.kde.org/show_bug.cgi?id=515572
--- Comment #8 from Daniel <[email protected]> --- (In reply to tagwerk19 from comment #6) > ... > First question - You are excluding your home drive and not adding any other > folders for indexing? Yes. > Then giving an "index contents=false" command, which I think doesn't exist > but will be ignored together with am "only basic indexing=false", which > switched from filename/metadata indexing to full text. Right. In the meantime I found Baloo/Configuration in the KDE wiki. "index contents=false" doesn't exist. I've also changed: "only basic indexing=true" > I'm guessing you want to avoid automatic indexing (of anything, as you've > not given any folders to index) and rely on manual commands to index files. > That's an unusual setup. Thats the only way to get only the files indexed, which I wanted to be indexed. > Second question - Is "/home/sd/" your home directory (not an SD disk or > other external media?). If it is external media, can you say what filesystem > - in fact it's probably a good idea to let us know what filesystems you are > using anyway (ext4, btrfs, etc, etc) "/home/sd/" = $HOME This is "ext4" All media is stored on NAS, previously mounted with "cifs smb". > Third question - Does that happen just with .mkv files? or does the same > happen if you copy and index, say, a .pdf? It happens on any media, like MP4, MP3, WAV, JPG, JPEG, PNG, BMP, ICO, ... Specially on PDF. On PDF the service may hang. I've excluded ".PDF" in the exclude filters list first, now I exclude everything "exclude filters=*" > There are two "watch points": > > On some systems if you exclude $HOME without including any other folders, > you get it included by default (so you see it both excluded and included). > > Second point is if you have not included a folder for indexing and then > manually index one of the files in it. Baloo will "think" that the file no > longer needs to be indexed and remove the entry. That alone *should* not > leave you with a different set of results but maybe we've got more than one > strange thing happening here... I've found that the main problem is because of the smb shares. Inodes are changing on every restart of the system. Even DeviceIDs are not really fixed. I'm using NFS now, which is more stable, but still sometimes do change DeviceIDs. This causes the baloo index to contain corrupted data, because inodes and DeviceIDs stored with the media information do not fit after a restart of the system. I'm using a script now which checks the device IDs on system startup and which does a purge of the baloo index if it has been changed. I'm adding files to the index with the help of scripts added to the context menu of dolphin. Example for videos: --- script begin --- #!/bin/bash # Case-Insensitivity für Pattern-Matching aktivieren shopt -s nocasematch # Definiere die erlaubten Dateiendungen als Regex-Pattern # (Das pipe-Symbol | trennt die Formate) EXT_PATTERN='\.(mp4|mkv|avi)$' if [ $# -eq 0 ]; then echo "Keine Dateien oder Ordner übergeben." read -n 1 -s -r -p "Eine Taste drücken um weiterzufahren ..." exit 1 fi for item in "$@"; do if [ -f "$item" ]; then if [[ "$item" =~ $EXT_PATTERN ]]; then echo "Index für Datei: $item" balooctl clear "$item" balooctl index "$item" else echo "Überspringe: $item (kein unterstützter Medientyp)" fi elif [ -d "$item" ]; then echo "Index für Ordner: $item" balooctl clear "$item" find "$item" -regextype posix-extended -type f -iregex ".*$EXT_PATTERN" -exec balooctl clear {} + find "$item" -regextype posix-extended -type f -iregex ".*$EXT_PATTERN" -exec balooctl index {} + # find "$item" -regextype posix-extended -type f -iregex ".*$EXT_PATTERN" -print0 | while IFS= read -r -d '' file; do # balooctl clear "$file" # balooctl index "$file" #done echo "" balooctl status else echo "UNBEKANNT oder existiert nicht: $item" fi done read -n 1 -s -r -p "Eine Taste drücken um weiterzufahren ..." --- end of script --- As an alternative I've installed "nemo" on my Ubuntu KDE System. Nemo gets the media information from "mediainfo" and does not require indexing. It's much more reliable. -- You are receiving this mail because: You are watching all bug changes.
