[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #12 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #11) > ... but got nowhere ... I stumbled on this again (Bug 478854) I can reliably reproduce on neon-unstable; on newly-installed, as vanilla as possible, systems but

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 tagwer...@innerjoin.org changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #11 from tagwer...@innerjoin.org --- (In reply to Bernie Innocenti from comment #10) > ... 100% reproduce ... I remember having a go at building a "with a clean index" test and got nowhere. Chasing up what would happen if an inode was reused

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #10 from Bernie Innocenti --- Just to be clear: I could 100% reproduce the crash in baloo_file with these directory operations in my home: cd ~ mkdir foo <- CRASH! mv foo bar <- CRASH! chmod -x bar <- CRASH! -- You are

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #9 from Bug Janitor

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #8 from Bernie Innocenti --- On a tangential note, why didn't the autotests catch this regression? -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #7 from Bernie Innocenti --- I don't see how these asserts could have ever worked in the past. I traced back the pathnames, and the '/' is appended to all directories with normalizeTrailingSlash():

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #6 from Bernie Innocenti --- I'm able to trigger a similar assertion a different location by simply creating a new directory in my home: ... [Detaching after fork from child process 31519] QIBusPlatformInputContext: invalid portal bus.

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 Bernie Innocenti changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #5 from

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #4 from tagwer...@innerjoin.org --- Had to trim the list of terms in the previous post as the full list looked too much like spam. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

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

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #2 from Oded Arbel --- (In reply to Oded Arbel from comment #0) > Regardless, the > directory no longer exists - I think it was moved than deleted before baloo > got a chance to index it, but I don't think that is related to the problem.

[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp

https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #1 from Oded Arbel --- (In reply to Oded Arbel from comment #0) > Which means that `KInotify::moved` is emitted for both directories and > files, but `FileWatch::slotFileMoved` expects only files and enforces that > with an assert. Lookgin