https://bugs.kde.org/show_bug.cgi?id=401637
Bug ID: 401637
Summary: KDE crash handler conflicts with RPCS3
Product: frameworks-kcrash
Version: 5.52.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: billy65...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
My guess is that with KDE Frameworks 5.52, KCrash's behaviour was changed so
that it was injected into ALL Qt applications under a KDE session, rather than
just KDE specific ones.
With the KDE crash handler present, RPCS3 crashes very early on when booting
most games, whereas with it absent, everything works perfectly fine.
The crash produces output similar to this
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = rpcs3 path = /usr/bin pid = 50951
KCrash: Arguments: /usr/bin/rpcs3
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
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
Re-raising signal for core dump handling.
Bad Run
1. run RPCS3
2. boot a game
3. it crashes
Good Run
1. run RPCS3 with KDE_DEBUG=1
2. boot a game
3. it runs perfectly
EXPECTED RESULT
presence of KCrash shouldn't affect the runtime behaviour of RPCS3.
SOFTWARE/OS VERSIONS
Linux: 4.19.5
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2
GCC Version: 8.2.1
ADDITIONAL INFORMATION:
RPCS3 issue: https://github.com/RPCS3/rpcs3/issues/5324
Additionally, the official AppImages provided by RPCS3 does not exhibit the
issue - my guess is largely because it bundles its own older Qt
--
You are receiving this mail because:
You are watching all bug changes.
