Created attachment 119872 [details] Backtrace Running "git svn rebase" crashes reproducibly with the following error message when using kwallet as an authentication backend: $ git svn rebase org.kde.kwindowsystem: Could not find any platform plugin Current branch master is up to date. error: git-svn died of signal 11 The command is executed properly and commits are also added to the local git clone. But when cleaning up afterwards the git-svn script produces a segfault. STEPS TO REPRODUCE 1. Clone a git repository from an SVN server and set kwallet as password storage backed. 2. Run "git svn rebase" 3. Observe the crash OBSERVED RESULT Calling "git svn rebase" will now always generate a segfault: [ 6470.589903] git-svn[1291]: segfault at 7f25e8ab8f80 ip 00007f25e897a3e6 sp 00007ffd8c670d70 error 4 in libKF5CoreAddons.so.5.50.0[7f25e8972000+5e000] [ 6470.589908] Code: f8 ff 74 06 f0 83 2f 01 74 7a 48 8b 7b 08 8b 07 85 c0 0f 84 92 00 00 00 83 f8 ff 74 0a f0 83 2f 01 0f 84 25 02 00 00 48 8b 03 <8b> 10 85 d2 74 24 83 fa ff 74 06 f0 83 28 01 74 19 48 8b 7d 00 48 [ 6470.590013] audit: type=1701 audit(1536562099.754:82): auid=1000 uid=1000 gid=100 ses=6 pid=1291 comm="git-svn" exe="/usr/bin/perl" sig=11 res=1 Additional info on used Arch package versions: * git 2.21.0-1 * perl 5.28.2-1 * kcoreaddons 5.57.0-1 * kwallet 5.57.0-1 * qt5-base 5.12.3-2 ADDITIONAL INFORMATION Original Arch Linux Bug report: https://bugs.archlinux.org/task/60005
I suspect some kind of race condition during shutdown, where the global-static tries to delete an already-deleted KAboutData in the registry. I'm having trouble reproducing but I also don't have git-svn setup for kwallet. Based on the platform plugin message I've tried various settings of the environment variable QT_QPA_PLATFORM (xcb, minimal, eglfs) but that hasn't helped me reproduce either.
The problem certainly isn't in KAboutData. The issue is that something calls exit(); the "org.kde.kwindowsystem: Could not find any platform plugin" message might be related. I suggest to report this issue to the bug tracker of your distribution.
(In reply to Christoph Feck from comment #2) > I suggest to report this issue to the bug tracker of your distribution. This has gone throught downstream already. I have no idea what we are supposed to do about this TBH, this is reproducible in a plain Plasma session with unmodified KDE and svn packages. You just need a very specific setup to reproduce it.
Also reproducible in Tumbleweed, so definitely not a downstream problem.
I second reproducibility in Tumbleweed, with the following backtrace: #0 0x00007ffff659061c in std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x7ffff73a81c0) at /usr/include/qt5/QtCore/qrefcount.h:65 #1 QAtomicOps<int>::load<int> (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #2 QBasicAtomicInteger<int>::load (this=0x7ffff73a81c0) at /usr/include/qt5/QtCore/qbasicatomic.h:103 #3 QtPrivate::RefCount::deref (this=0x7ffff73a81c0) at /usr/include/qt5/QtCore/qrefcount.h:66 #4 QString::~QString (this=<optimized out>, this=<optimized out>) at /usr/include/qt5/QtCore/qstring.h:1133 #5 KAboutData::Private::~Private (this=<optimized out>, this=<optimized out>) at /usr/src/debug/kcoreaddons-5.60.0-1.1.x86_64/src/lib/kaboutdata.cpp:460 #6 KAboutData::~KAboutData (this=<optimized out>, this=<optimized out>) at /usr/src/debug/kcoreaddons-5.60.0-1.1.x86_64/src/lib/kaboutdata.cpp:581 #7 0x00007ffff65908cd in (anonymous namespace)::Q_QGS_s_registry::innerFunction()::Holder::~Holder() () at /usr/src/debug/kcoreaddons-5.60.0-1.1.x86_64/src/lib/kaboutdata.cpp:1033 #8 0x00007ffff7c69500 in __run_exit_handlers () from /lib64/libc.so.6 #9 0x00007ffff7c6963c in exit () from /lib64/libc.so.6 #10 0x000055555558c446 in main ()
Which application is crashing? This information is missing in all backtraces.
(In reply to Christoph Feck from comment #6) > Which application is crashing? This information is missing in all backtraces. "Core was generated by `/usr/bin/perl /usr/lib/git-core/git-svn rebase'."
*** Bug 411590 has been marked as a duplicate of this bug. ***
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!