Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

To: Nicholas D Steeves <nsteeves@gmail.com>
Cc: 942078@bugs.debian.org
Subject: Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f
From: Norbert Preining <norbert@preining.info>
Date: Wed, 23 Dec 2020 08:10:50 +0900
Message-id: <[🔎] X+J8+tsRQOaxO81U@burischnitzel.preining.info>
Reply-to: Norbert Preining <norbert@preining.info>, 942078@bugs.debian.org
In-reply-to: <157066160566.15955.3044056725605207934.reportbug@DigitalMercury.dynalias.net>
References: <157066160566.15955.3044056725605207934.reportbug@DigitalMercury.dynalias.net> <157066160566.15955.3044056725605207934.reportbug@DigitalMercury.dynalias.net>

Hi Nicholas,

On Wed, 09 Oct 2019, Nicholas D Steeves wrote:
> Version: 5.54.0-1
> Severity: serious
> Justification: poor experience will cause user to give up on baloo; worse than GNOME

Can you reproduce this with current frameworks 5.77 in unstable?

Does it always crash at the same file (jack_capture_90.mp3) or always in
different files?

Thanks

Norbert

--
PREINING Norbert                              https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Reply to:

Prev by Date: Processed: bug 974821 is forwarded to https://bugs.kde.org/show_bug.cgi?id=430721
Next by Date: kitinerary_20.08.3-2_amd64.changes ACCEPTED into unstable, unstable
Previous by thread: Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f
Next by thread: Bug#943462: [polkit-kde-agent-1] Fails to start with elogind
Index(es):
- Date
- Thread