https://bugs.kde.org/show_bug.cgi?id=435161
--- Comment #3 from tagwer...@innerjoin.org ---
Not sure whether this is related...
It's a glitch I get "every so often". When I've missed capturing it, I've not
found a way of reproducing it...
cd ~/Documents
mkdir temp
echo "Hello Penguin" > temp/file1.txt
balooshow -x temp/file1.txt
gave:
144da00000fc01 64513 1330592 temp/file1.txt
[/home/test/.kde/share/config/kdeglobals]
Mtime: 1617136526 2021-03-30T22:35:26
Ctime: 1617136526 2021-03-30T22:35:26
Cached properties:
Line Count: 158
Internal Info
Terms: 0 0.025 ... Mplain Mtext T5 T8 X20-158 activebackground activeblend
activeforeground backgroundalternate backgroundnormal ... widgetstyle window wm
File Name Terms: Fkdeglobals
XAttr Terms:
lineCount: 158
That is, the details of something else completely (a different file, indexed at
a different time). "Balooctl monitor" did not show "file1.txt" being indexed.
After a reboot I get the more expected:
144da00000fc01 64513 1330592 temp/file1.txt
[/home/test/Documents/temp/file1.txt]
Mtime: 1617270546 2021-04-01T11:49:06
Ctime: 1617270546 2021-04-01T11:49:06
Cached properties:
Line Count: 1
Internal Info
Terms: Mplain Mtext T5 T8 X20-1 hello penguin
File Name Terms: Ffile1 Ftxt
XAttr Terms:
lineCount: 1
I was hoping to be able to snapshot/clone the "confused" system, seemingly not
this time though :-(
It may be that if such a "confused" system is referencing a directory rather
than a file then you might get such an assert....
Neon Unstable
Plasma: 5.21.80
Frameworks: 5.81.0
Qt: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
