https://bugs.kde.org/show_bug.cgi?id=526922
--- Comment #8 from [email protected] --- (In reply to tagwerk19 from comment #7) > The original report was for FreeBSD. > > There's been a wave of reports for Linux, see Bug 524392 and a solution > https://invent.kde.org/frameworks/baloo/-/merge_requests/331 > You can do a "quick test" and see whether you still have crashes after > restarting baloo? > $ systemctl restart --user kde-baloo > > Alas I don't know how much if this can be taken over to the FreeBSD > environment. > > > ... Systemd Service Environment: Add > > Environment="QT_QPA_PLATFORM=offscreen" upstream to > > /usr/lib/systemd/user/kde-baloo.service ... > Beware, this will stop Baloo from checking whether the system is in use or > idle. If the system is idle, it processes its indexing queue more quickly. > You'll stop getting crashes but indexing will be slower. > > > ... 3. Ordering Dependency: Add After=plasma-workspace.target or > > After=graphical-session.target in kde-baloo.service to avoid starting > > concurrently before the display environment is exported ... > I think that's what the patch is doing. > > Arch was caught very quickly by the bug, it should pick up the patch > similarly quickly. (Not setting as Resolved, Duplicate as I don't know > whether the FreeBSD issue is the same). Sorry, my mistake. I just searched for similar bug and not saw the correct plataform. But the cause may be the startup race? From what I saw, the first session (wayland-0) is started by the login manager, and the user session uses wayland-1 (not sure if this can change), and the baloo uses QT engine which crashs wihout a proper graphical session. -- You are receiving this mail because: You are watching all bug changes.
