https://bugs.kde.org/show_bug.cgi?id=393478
Tobias Deiminger <haxti...@posteo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |haxti...@posteo.de
--- Comment #11 from Tobias Deiminger <haxti...@posteo.de> ---
I can reproduce the bug and will have a look into it. Someone closed libpulses
eventfd(2), while libpulse continues to write to it. A write to the already
closed fd in pa_fdsem_post then triggers assertion. I modified pulseaudio to
get a bit more debug info:
$ strace -e close ./okular 2>&1
[...]
close(19) = 0
close(15) = 0 # who is doing that? and why?
close(15) = 0
close(15) = 0
close(19) = 0
close(21) = 0
[...]
Invalid write to eventfd: fd=15, r=-1, errno=9 # pa_fdsem_post tried writing
fd 15, too late, already closed
I think next thing to check is where the close happened. Could be okular, Qt,
or pulseaudio itself.
--
You are receiving this mail because:
You are watching all bug changes.
