18 Dec
2019
18 Dec
'19
11:25 p.m.
On Wednesday 18 December 2019, deloptes wrote:
E. Liddell wrote:
I think
it's an amarok problem because it's the only program affected.
I have amarok's engine as alsa. When I turn off pulseaudio amarok doesn't work
regardless of the engine I choose.
I installed Clementine and it works fine.
Something happened to somewhere that only affects amarok.
It may be a pclos exclusive problem.
At this point, I'm lost.
Kate
On Wed, 18 Dec 2019 02:02:33 -0500
"BorgLabs - Kate Draven"
<borglabs4(a)gmail.com> wrote:
look in the message
Invalid write to eventfd: Bad file descriptor - could be even something
outside PA.
And yes there is a lot that PA provides and ALSO does not.
No, it does not work wrong - especially the 12.2-4+deb10u1 is very good.
A recent update seems to be causing amarok to
crash when I attempt to
play a song. I get the usual signal 11 stuff of the gui. From the
commadline I get
[kcrash] TDECrash: Application 'amarokapp' crashing...
Invalid write to eventfd: Bad file descriptor
Code should not be reached at pulsecore/fdsem.c:199, function
pa_fdsem_post(). Aborting.
[kcrash] Unable to start Dr. Konqi
Any idea as to what might be causing this? It's happening on all pclos
boxes.
Well, the error message is bubbling up from pulseaudio, so either amaroK
is
passing it the wrong thing, or pulse has a bug. So, the first question
is, do you
actually need any functionality pulseaudio provides and alsa doesn't? If
not, I would kill it—it's just one more thing that can go wrong on your
system. You might still want to file a bug against
amaroK, though. If you do, it
would be a good idea to include the exact version of pulseaudio that's
causing the problem, and check with your distro to see if they're using
any patches that might affect fdsem.c
Most important is the way to reproduce.
I do not use amarok personally - my father does all the time - with PA.
Never complained so far.
---------------------------------------------------------------------