kdeinit5 crash every start up with crash pop up. But I'm not advance user or anything, I don't use kdeinit5 or know what it is. I asked this on Reddit KDE and opensuse, no one seems to know. Thanks. Operating System: openSUSE Tumbleweed 20181224 KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 Kernel Version: 4.19.11-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Application: kdeinit5 (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x00007f7910f4c08b in raise () from /lib64/libc.so.6 #7 0x00007f7910f354e9 in abort () from /lib64/libc.so.6 #8 0x00007f791136599d in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1901 #9 QMessageLogger::fatal (this=this@entry=0x7ffd64379220, msg=msg@entry=0x7f790c807938 "Fatal Error: Got cmd %d, while waiting for an answer!") at global/qlogging.cpp:887 #10 0x00007f790c73726f in KIO::SlaveBase::waitForAnswer (this=this@entry=0x7ffd643796e0, expected1=expected1@entry=84, expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7ffd64379294) at /usr/include/qt5/QtCore/qlogging.h:91 #11 0x00007f790c738495 in KIO::SlaveBase::canResume (this=0x7ffd643796e0, offset=12289) at /usr/src/debug/kio-5.53.0-1.1.x86_64/src/core/slavebase.cpp:997 #12 0x00007f790c690ad4 in FileProtocol::put (this=0x7ffd643796d0, url=..., _mode=-1, _flags=...) at /usr/src/debug/kio-5.53.0-1.1.x86_64/src/ioslaves/file/file.cpp:600 #13 0x00007f790c73d52b in KIO::SlaveBase::dispatch (this=0x7ffd643796e0, command=68, data=...) at /usr/src/debug/kio-5.53.0-1.1.x86_64/src/core/slavebase.cpp:1154 #14 0x00007f790c73dd36 in KIO::SlaveBase::dispatchLoop (this=0x7ffd643796e0) at /usr/src/debug/kio-5.53.0-1.1.x86_64/src/core/slavebase.cpp:324 #15 0x00007f790c68f109 in kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kio-5.53.0-1.1.x86_64/src/ioslaves/file/file.cpp:112 #16 0x0000560d97d37bf7 in launch (argc=4, _name=0x560d98cdccc8 "/usr/lib64/qt5/plugins/kf5/kio/file.so", args=<optimized out>, cwd=<optimized out>, envc=0, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x560d97d3b173 "0") at /usr/src/debug/kinit-5.53.0-1.1.x86_64/src/kdeinit/kinit.cpp:706 #17 0x0000560d97d38c2a in handle_launcher_request (sock=8, who=<optimized out>) at /usr/src/debug/kinit-5.53.0-1.1.x86_64/src/kdeinit/kinit.cpp:1146 #18 0x0000560d97d39548 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.53.0-1.1.x86_64/src/kdeinit/kinit.cpp:1339 #19 0x0000560d97d345b5 in main (argc=5, argv=<optimized out>) at /usr/src/debug/kinit-5.53.0-1.1.x86_64/src/kdeinit/kinit.cpp:1785 [Inferior 1 (process 12435) detached]
Interesting. It's asserting when loading a slave; probably the file slave from the trace. Given you have a separate prefix can you confirm that it's loading the write file.so KIO? and reopen.
I don't know what happen, but this problem is gone when I update my system simply with zypper dup. I guess it can be close now.
The problem is back for some reason. How do I "confirm that it's loading the write file.so KIO"? I don't have knowledge about this. Not sure if the report is the same but here: Application: kdeinit5 (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x00007f35a28d008b in raise () from /lib64/libc.so.6 #7 0x00007f35a28b94e9 in abort () from /lib64/libc.so.6 #8 0x00007f35a2ce999d in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1901 #9 QMessageLogger::fatal (this=this@entry=0x7ffd0e7e55a0, msg=msg@entry=0x7f359e18a7f8 "Fatal Error: Got cmd %d, while waiting for an answer!") at global/qlogging.cpp:887 #10 0x00007f359e0b954f in KIO::SlaveBase::waitForAnswer (this=this@entry=0x7ffd0e7e5a60, expected1=expected1@entry=84, expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7ffd0e7e5614) at /usr/include/qt5/QtCore/qlogging.h:91 #11 0x00007f359e0ba775 in KIO::SlaveBase::canResume (this=0x7ffd0e7e5a60, offset=12289) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:998 #12 0x00007f359e012ad4 in FileProtocol::put (this=0x7ffd0e7e5a50, url=..., _mode=-1, _flags=...) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/ioslaves/file/file.cpp:600 #13 0x00007f359e0bf80b in KIO::SlaveBase::dispatch (this=0x7ffd0e7e5a60, command=68, data=...) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:1155 #14 0x00007f359e0c0016 in KIO::SlaveBase::dispatchLoop (this=0x7ffd0e7e5a60) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:325 #15 0x00007f359e011109 in kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/ioslaves/file/file.cpp:112 #16 0x000055e3620dabf7 in launch (argc=4, _name=0x55e362c6ea78 "/usr/lib64/qt5/plugins/kf5/kio/file.so", args=<optimized out>, cwd=<optimized out>, envc=0, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x55e3620de173 "0") at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:706 #17 0x000055e3620dbc2a in handle_launcher_request (sock=8, who=<optimized out>) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1146 #18 0x000055e3620dc548 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1339 #19 0x000055e3620d75b5 in main (argc=5, argv=<optimized out>) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1785 [Inferior 1 (process 11126) detached]
*** Bug 403537 has been marked as a duplicate of this bug. ***
*** Bug 403551 has been marked as a duplicate of this bug. ***
As of March 18, 2019, the issue disappear, probably was fixed.
*** Bug 406365 has been marked as a duplicate of this bug. ***
Still an issue, given how many duplicates we're still seeing...
*** Bug 412821 has been marked as a duplicate of this bug. ***
From the other bug reports it seems that the bug is triggered when receiving a notification from KDE Connect, e.g. when you receive an sms on your phone and KDE Connect notifies you of it on the desktop.
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!