https://bugs.kde.org/show_bug.cgi?id=421317
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #14 from Stefan Brüns ---
(In reply to tagwerk19 from comment #11)
> (In reply to Christoph Feck from comment #4)
> > From the backtrace, it looks like there is a text file larger than 2 GiB.
> > Qt only supports up to 2 GiB.
> Not sure
https://bugs.kde.org/show_bug.cgi?id=421317
Stefan Brüns changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #13 from Stefan Brüns ---
Git commit fd24c90c1e465324baa81a622f8767b62eef by Stefan Brüns.
Committed on 16/11/2023 at 04:18.
Pushed by bruns into branch 'kf5'.
[ExtractorProcess] Handle signal mangling by DrKonqi
DrKonqui catches the
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #12 from Stefan Brüns ---
Git commit 819cb757b5742372cf017fba84955178c1f1a7d1 by Stefan Brüns.
Committed on 14/11/2023 at 01:28.
Pushed by bruns into branch 'master'.
[ExtractorProcess] Handle signal mangling by DrKonqi
DrKonqui catches
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #11 from tagwer...@innerjoin.org ---
(In reply to Christoph Feck from comment #4)
> From the backtrace, it looks like there is a text file larger than 2 GiB. Qt
> only supports up to 2 GiB.
Not sure what Baloo would do with a 2GB file...
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #10 from Stefan Brüns ---
(In reply to Christoph Feck from comment #4)
> From the backtrace, it looks like there is a text file larger than 2 GiB. Qt
> only supports up to 2 GiB.
>
> I suggest to add incremental loading to the
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #9 from Stefan Brüns ---
On Tumbleweed, the pattern is set by installing the `systemd-coredump` package:
$> grep core_pattern /usr/lib/sysctl.d/50-coredump.conf
kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #8 from tagwer...@innerjoin.org ---
That explains a lot!
Is the "... depends on the kernel /proc/sys/kernel/core_pattern setting ..." a
distribution thing? I've never, as far as I remember, found files listed as
failed.
If this fixes
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #7 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/baloo/-/merge_requests/174
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421317
Stefan Brüns changed:
What|Removed |Added
CC||stefan.bruens@rwth-aachen.d
|
https://bugs.kde.org/show_bug.cgi?id=421317
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--
You are
https://bugs.kde.org/show_bug.cgi?id=421317
al F changed:
What|Removed |Added
CC||pub...@mellomrommet.no
Version|5.67.0
https://bugs.kde.org/show_bug.cgi?id=421317
Christoph Feck changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #3 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #2 from DaBler ---
(In reply to Stefan Brüns from comment #1)
> The extractor from KFileMetadata is crashing.
>
> 'balooctl failed' will tell which file causes the crash.
$ balooctl failed
All Files were indexed successfully
--
You are
https://bugs.kde.org/show_bug.cgi?id=421317
Stefan Brüns changed:
What|Removed |Added
Product|frameworks-baloo|frameworks-kfilemetadata
Resolution|---
17 matches
Mail list logo
