https://bugs.kde.org/show_bug.cgi?id=389697
Bug ID: 389697
Summary: Calling the elisa binary while it's also running makes
it crash
Product: elisa
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: dnico...@gmail.com
Target Milestone: ---
Running elisa and then trying to run another instance makes the first elisa
crash (and the second one never start).
This is what I get when trying to run another instance:
---
"Message recipient disconnected from message bus without replying"
---
This is what the original instance prints when it dies:
---
AbstractFileListing::emitNewFiles 501
AbstractFileListing::emitNewFiles 501
AbstractFileListing::emitNewFiles 501
AbstractFileListing::emitNewFiles 454
ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h,
line 351
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = elisa path = /home/januz/code/Elisa Music
Player/build/src pid = 9107
KCrash: Arguments: /home/januz/code/Elisa Music Player/build/src/elisa
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
Invalid write to eventfd: Bad file descriptor
Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post().
Aborting.
Unable to start Dr. Konqi
----
--
You are receiving this mail because:
You are watching all bug changes.
