[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 --- Comment #10 from Ahmad Samir --- >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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added CC||szots...@gmail.com --- Comment #9 from Ahmad Samir --- *** Bug 412821 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added Ever confirmed|1 |0 Resolution|FIXED |--- Status|RESOLVED|REPORTED CC||a.samir...@gmail.com --- Comment #8 from Ahmad Samir --- Still an issue, given how many duplicates we're still seeing... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added CC||elxr...@gmail.com --- Comment #7 from Ahmad Samir --- *** Bug 406365 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Andy Great changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Andy Great --- As of March 18, 2019, the issue disappear, probably was fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Christoph Feck changed: What|Removed |Added CC||ade...@gmail.com --- Comment #5 from Christoph Feck --- *** Bug 403551 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Christoph Feck changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com --- Comment #4 from Christoph Feck --- *** Bug 403537 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Andy Great changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #3 from Andy Great --- 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 0x7f35a28d008b in raise () from /lib64/libc.so.6 #7 0x7f35a28b94e9 in abort () from /lib64/libc.so.6 #8 0x7f35a2ce999d in qt_message_fatal (context=..., message=...) 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 0x7f359e0b954f 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 0x7f359e0ba775 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 0x7f359e012ad4 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 0x7f359e0bf80b 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 0x7f359e0c0016 in KIO::SlaveBase::dispatchLoop (this=0x7ffd0e7e5a60) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:325 #15 0x7f359e011109 in kdemain (argc=, argv=) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/ioslaves/file/file.cpp:112 #16 0x55e3620dabf7 in launch (argc=4, _name=0x55e362c6ea78 "/usr/lib64/qt5/plugins/kf5/kio/file.so", args=, cwd=, envc=0, envs=, 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 0x55e3620dbc2a in handle_launcher_request (sock=8, who=) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1146 #18 0x55e3620dc548 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1339 #19 0x55e3620d75b5 in main (argc=5, argv=) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1785 [Inferior 1 (process 11126) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 David Edmundson changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 --- Comment #2 from Andy Great --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- 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. -- You are receiving this mail because: You are watching all bug changes.
