See https://invent.kde.org/system/kde-inotify-survey.
This daemon warns when apps are using all inotify watches and prompts the user to raise it; this can help users understand why Baloo in particular isn't working properly, and offers them a way to fix it
+1
Metadata Update from @ngompa: - Issue set to the milestone: Plasma 5.27 - Issue tagged with: experience, packaging
Metadata Update from @justinz: - Issue assigned to farchord
Package review request is here: https://bugzilla.redhat.com/show_bug.cgi?id=2173178
Package has been reviewed and it's going for testing: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3c5759ec7c (Rawhide)
https://bodhi.fedoraproject.org/updates/FEDORA-2023-9e969d4412 (F38)
https://bodhi.fedoraproject.org/updates/FEDORA-2023-aedfaccdfd (F37)
Let's include that by default. What should be the right component to add this as a Recommended dependency?
Metadata Update from @siosm: - Issue set to the milestone: None (was: Plasma 5.27)
We can either (or both) include it in the comps group (example: https://pagure.io/fedora-comps/pull-request/844) or directly add it as a (recommended) dependency to an existing package.
Added a request to add to the comps: https://pagure.io/fedora-comps/pull-request/846
Done in https://pagure.io/workstation-ostree-config/pull-request/385 & https://pagure.io/workstation-ostree-config/pull-request/386 for Kinoite
Metadata Update from @siosm: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Metadata Update from @siosm: - Issue tagged with: kinoite
Thanks so much, everyone!
What Fedora release will this change land in?
Thanks so much, everyone! What Fedora release will this change land in?
I believe all we did now is add it to the comps groups. I am not sure if there's anything else to be done as I'm unfamiliar with the next steps.
It's in the package repos right now for F37+. Kinoite F38+ users will get it with when they update. It will be included by default in new KDE Spin installations starting with F39.
If we want to have it installed automatically on existing systems, we should add a dependency to plasma-workspace for example.
Metadata Update from @siosm: - Issue set to the milestone: Fedora Linux 39
Thanks!
Metadata Update from @siosm: - Issue tagged with: meeting
Re-opening to make sure to talk about this in today's meeting.
Metadata Update from @siosm: - Issue status updated to: Open (was: Closed)
https://src.fedoraproject.org/rpms/plasma-workspace/pull-request/24
Metadata Update from @siosm: - Issue untagged with: meeting, packaging