Bug 496283

Summary:	baloo_file
Product:	[KDE Neon] neon	Reporter:	Dav84 <davm00>
Component:	general	Assignee:	Neon Bugs <neon-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	carlosd.kde, christoph, jr, neon-bugs
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	baloo_file error baloo file-20241114-151803.kcrash attachment-172271-0.html baloo_file-20241115-112024.kcrash

Description Dav84 2024-11-14 21:33:46 UTC

Created attachment 175828 [details]
baloo_file error

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.2.3
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION
Hi, sorry to insist on this baloo_file issue, it is not a constant, but something must be causing this error, I think it is Dolphin that causes this error or I don't know if it is something deeper... in the system, I will attach the kcrash file as the error report shows, maybe they can find the problem...

Comment 1 Carlos De Maine 2024-11-14 23:45:21 UTC

Comment on attachment 175828 [details]
baloo_file error

could you please attach another trace with debuginfod enabled ??

Comment 2 Dav84 2024-11-14 23:52:04 UTC

Created attachment 175831 [details]
baloo file-20241114-151803.kcrash

This is what I generated, I don't know if it could be useful.

Comment 3 Carlos De Maine 2024-11-15 02:18:53 UTC

`Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal]`
somewhere down the line you opted to not download the debuginfod files.

maybe you could recreate the crash if it's reproducible and make sure that drkonqi is enabled/allowed to download those debuginfod symbols??

Comment 4 Dav84 2024-11-15 02:33:12 UTC

Created attachment 175834 [details]
attachment-172271-0.html

In fact when I try to download the debug symbols it gives me an error and does not let me do the download so I saved the kcrash file and the truth is that I am not very expert on this subject and that's why I like KDE is very stable but that error appeared overnight and I know it does not seriously affect the system but I have read several users with the same problem with that file baloo_file and is not a constant error personally usually happens to me being in dolphin but I do not know if dolphin is the cause or is something else ...

Comment 5 Dav84 2024-11-15 20:58:09 UTC

Created attachment 175853 [details]
baloo_file-20241115-112024.kcrash

I don't know if this file can help you, I think I managed to download the debugging files, I'm going to attach the kcrash file.

Comment 6 Christoph Cullmann 2025-06-23 18:18:16 UTC

Fixed with 

commit 27a5e70abe6479dee045f5ed8412c55fc1d87243
Author: Méven Car <meven@kde.org>
Date:   Wed Jan 15 18:35:47 2025 +0100

    MetadataMover::updateMetadata: tolerate path ending with /
    
    Since KInotify can return path ending with '/', instead of asserting,
    sanitize the input data by chopping the end /.
    
    SENTRY: BALOO-1H4

in KF6.