On 13/01/2024 22:37, Valerio Vanni wrote:
Il 13/01/2024 16:20, Max Nikulin ha scritto:
And this is one with a --lastchannel launch:
lrwx------ 1 valerio valerio 64 12 gen 20.52 34 ->
/dev/dvb/adapter0/frontend0
lsof for the same process may be more informative, but currently it
does not matter. Perhaps, opening devices in /dev/dvb, kaffeine does
not set the O_CLOEXEC flag for open(2) (or does not call fcntl with
FD_CLOEXEC). As a result, file descriptors leak to spawned processes.
I suggest to reach a community more close to kaffeine (or maybe baloo)
developers and ask if it could be improved.
In my system baloo is disabled.
Which package does tags.so belong to in your case?
I believe you that file indexer is disabled, but some components may
still be called for reasons unclear for me. Maybe they do something
useful. Leaking of file descriptors to child processes is not uncommon
issue. Ideally both sides should take measures to avoid it, but to
mitigate it is enough that any party handle file descriptors with care.
However it is just my guess, maybe actual cause of the issue with
tags.so is completely different.
P.S. Years ago KDE developers decided to remove controls that allowed to
disable file indexer. Otherwise nobody would use it since previous
version caused enough troubles. Fortunately that times have gone.
