https://bugs.kde.org/show_bug.cgi?id=439346
Scott Beamer changed:
What|Removed |Added
CC||scott.bea...@comcast.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #10 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #1)
> Suspect this could be related:
> https://bugzilla.redhat.com/show_bug.cgi?id=1951580
> https://github.com/systemd/systemd/issues/18791
Whether it was or
https://bugs.kde.org/show_bug.cgi?id=439346
Nate Graham changed:
What|Removed |Added
Version Fixed In|5.23|5.22.4
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #9 from skierpage ---
(In reply to tagwerk19 from comment #8)
> ... If baloo can be run via systemd, does this open the possibility of using
> systemd cgroup settings to cap memory use? (Yes, thread drift, sorry...)
In Fedora 34, baloo is
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #8 from tagwer...@innerjoin.org ---
Chapeau!
... If baloo can be run via systemd, does this open the possibility of using
systemd cgroup settings to cap memory use? (Yes, thread drift, sorry...)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=439346
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=439346
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #6 from skierpage ---
Created attachment 140001
--> https://bugs.kde.org/attachment.cgi?id=140001=edit
diff of service generated from xdg file and kde-baloo.service
The
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #5 from skierpage ---
(In reply to tagwerk19 from comment #2)
> This is somehow a regression (as there wasn't an issue F33). If I remove the
> X-systemd-skip line, baloo starts up OK.
Yes I think that's it, so I was probably wrong to
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #4 from skierpage ---
(In reply to skierpage from comment #3)
> (In reply to tagwerk19 from comment #2)
> Many thanks for your suggestions!
>
> > If I remove the X-systemd-skip line, baloo starts up OK.
I commented out both
>
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #3 from skierpage ---
(In reply to tagwerk19 from comment #2)
Many thanks for your suggestions!
> If I remove the X-systemd-skip line, baloo starts up OK.
If I comment out both
X-GNOME-Autostart-enabled=true
and
X-systemd-skip=true
in
https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #2 from tagwer...@innerjoin.org ---
I notice in the
/etc/xdg/autostart/baloo_file.desktop
file there is a line
X-systemd-skip=true
Doesn't seem to bother Neon but maybe Neon "relies less" on systemd.
This is somehow a regression
https://bugs.kde.org/show_bug.cgi?id=439346
Rex Dieter changed:
What|Removed |Added
CC||rdie...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439346
tagwer...@innerjoin.org changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
14 matches
Mail list logo
