Bug 477754

Summary: Baloo_file crash immediately after login
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Egor Kuznetsov <egor.kuznetsov.26>
Component: Baloo File DaemonAssignee: baloo-bugs-null
Status: RESOLVED DUPLICATE    
Severity: crash CC: bugseforuns, duha.bugs, natalie_clarius, tagwerk19
Priority: NOR Keywords: qt6
Version First Reported In: 5.246.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Baloo_file crash file

Description Egor Kuznetsov 2023-11-30 08:56:41 UTC
Created attachment 163640 [details]
Baloo_file crash file

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Every time (2 boots as minimum) when I login into system, baloo generate crash report with don't understandable error

STEPS TO REPRODUCE
1. Install KDE Neon Unstable
2. Login into system
3. Baloo_file generate crashreport

OBSERVED RESULT
Crash is happening

EXPECTED RESULT
Crash doesen't happening

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7,7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2023-11-30 21:29:13 UTC
Same on my neon unstable.
Comment 2 tagwerk19 2023-11-30 22:36:41 UTC
(In reply to Egor Kuznetsov from comment #0)
> Created attachment 163640 [details]
> Baloo_file crash file
#15 0x00007fc0ed6a5908 in qt_assert (assertion=assertion@entry=0x559d771799a0 "!filePath.endsWith(QLatin1Char('/'))",
An ASSERT can be pretty minimal, it would be nice if there was a Debug line giving the filePath in question...
Comment 3 tagwerk19 2023-12-22 14:27:23 UTC
Seems likely to be related to Bug 478854
Comment 4 duha.bugs 2024-02-12 16:07:35 UTC

*** This bug has been marked as a duplicate of bug 475115 ***