Hi people
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.
Cheers to all,
Kate
On Wed, 18 Dec 2019 02:02:33 -0500 "BorgLabs - Kate Draven" borglabs4@gmail.com wrote:
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
E. Liddell
E. Liddell wrote:
On Wed, 18 Dec 2019 02:02:33 -0500 "BorgLabs - Kate Draven" borglabs4@gmail.com wrote:
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.
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.
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.
On Wednesday 18 December 2019, deloptes wrote:
E. Liddell wrote:
On Wed, 18 Dec 2019 02:02:33 -0500 "BorgLabs - Kate Draven"
borglabs4@gmail.com wrote:
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.
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.
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.
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 Wednesday, 18 December 2019, 23:26:17 GMT, BorgLabs - Kate Draven borglabs4@gmail.com wrote:
On Wednesday 18 December 2019, deloptes wrote:
E. Liddell wrote:
On Wed, 18 Dec 2019 02:02:33 -0500 "BorgLabs - Kate Draven"
borglabs4@gmail.com wrote:
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.
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.
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.
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
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: trinity-users@lists.pearsoncomputing.net Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
| | | | trinity-users@lists.pearsoncomputing.net
|
|
|
I'm having the same issue with Amarok, I don't know what has caused it, I have had too many updates to say which could have been the offending update. Just of note, if you are running "intel" graphics that use i915 driver and 5.4.x kernel you may get some font corruption if still using GDM to login, easiest "fix" is to go to pcc >> boot, and change the display manager to TDM Alie
On Thursday 19 December 2019, alistair izzard via trinity-users wrote:
On Wednesday, 18 December 2019, 23:26:17 GMT, BorgLabs - Kate Dravenborglabs4@gmail.com wrote:
On Wednesday 18 December 2019, deloptes wrote:
E. Liddell wrote:
On Wed, 18 Dec 2019 02:02:33 -0500 "BorgLabs - Kate Draven"
borglabs4@gmail.com wrote:
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.
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.
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.
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
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: trinity-users@lists.pearsoncomputing.net Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
trinity-users@lists.pearsoncomputing.net
I'm having the same issue with Amarok, I don't know what has caused it, I have had too many updates to say which could have been the offending update. Just of note, if you are running "intel" graphics that use i915 driver and 5.4.x kernel you may get some font corruption if still using GDM to login, easiest "fix" is to go to pcc >> boot, and change the display manager to TDM Alie
I have an ati and use tdm be default. All is good save for the amarok stuff.
Thanks Ali and Happy Christmas.
Kate
On Thursday, 19 December 2019, 15:10:15 GMT, BorgLabs - Kate Draven borglabs4@gmail.com wrote:
On Thursday 19 December 2019, alistair izzard via trinity-users wrote:
On Wednesday, 18 December 2019, 23:26:17 GMT, BorgLabs - Kate Draven borglabs4@gmail.com wrote:
On Wednesday 18 December 2019, deloptes wrote:
E. Liddell wrote:
On Wed, 18 Dec 2019 02:02:33 -0500 "BorgLabs - Kate Draven"
borglabs4@gmail.com wrote:
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.
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.
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.
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
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: trinity-users@lists.pearsoncomputing.net Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
trinity-users@lists.pearsoncomputing.net
I'm having the same issue with Amarok, I don't know what has caused it, I have had too many updates to say which could have been the offending update. Just of note, if you are running "intel" graphics that use i915 driver and 5.4.x kernel you may get some font corruption if still using GDM to login, easiest "fix" is to go to pcc >> boot, and change the display manager to TDM Alie
I have an ati and use tdm be default. All is good save for the amarok stuff.
Thanks Ali and Happy Christmas.
Kate
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: trinity-users@lists.pearsoncomputing.net Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
| | | | trinity-users@lists.pearsoncomputing.net
|
|
|
Merry Christmas Kate and a wonderful New Year, yeah I have no issues with ATI / NVidia :)
On 12/18/2019 01:13 PM, deloptes wrote:
look in the message Invalid write to eventfd: Bad file descriptor - could be even something outside PA.
Agreed, this is bad-Juju.
"eventfd Bad file descriptor" likely means the 64-bit value contained in the eventfd has been trampled by another memory problem resulting in Undefined Behavior. It is likely an Amarok problem as the virtual address space for the process should keep Amarok walled off from the rest of the processes. That doesn't mean that PA can't be going haywire and causing the problem if Amarok and PA are communicated over the descriptor (or other parts of TDE), but my bet is Amarok is the source of the problem.
Grab a strace of Amarok when the issue occurs and post that will the bug-report. That should identify exactly what is failing if it is something that is hard to reproduce.
-
alistair izzard via trinity-users -
BorgLabs - Kate Draven -
David C. Rankin -
deloptes -
E. Liddell