Summary: | krunner telepathy integration crashes | ||
---|---|---|---|
Product: | [Unmaintained] telepathy | Reporter: | Jose Arthur Benetasso Villanova <jose.arthur> |
Component: | contact-runner | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andreas.davour, balthasar, james, rdieter, slartibart70, stefan.bruens, stephane, travneff, webdesigner |
Priority: | VHI | Keywords: | drkonqi |
Version: | git-latest | ||
Target Milestone: | Future | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jose Arthur Benetasso Villanova
2018-09-14 23:31:06 UTC
From konsole: KCrash: Attempting to start /usr/bin/krunner from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... [1] Exit 253 krunner [2]+ Stopped krunner dnf remove telepathy-qt5 solved this crash It's the telepathy applet, triaging there. Sorry, must be the "instant messaging" krunner plugin rather *** Bug 398212 has been marked as a duplicate of this bug. *** *** Bug 398824 has been marked as a duplicate of this bug. *** *** Bug 397933 has been marked as a duplicate of this bug. *** #9 Tp::RefCounted::deref (this=0x18) at /usr/include/telepathy-qt5/TelepathyQt/shared-ptr.h:90 #10 Tp::SharedPtr<Tp::AccountSet>::~SharedPtr (this=0x7ffff41ba8e0, __in_chrg=<optimized out>) at /usr/include/telepathy-qt5/TelepathyQt/shared-ptr.h:136 For me, this looks like a problem with TpQts homegrown shared pointer implementation. Tp::AccountSet inherits QObject and Tp::RefCounted, so the d pointer to the Tp::AccountSet apparently is already null when deref is called. *** Bug 400562 has been marked as a duplicate of this bug. *** *** Bug 400056 has been marked as a duplicate of this bug. *** *** Bug 401839 has been marked as a duplicate of this bug. *** *** Bug 401920 has been marked as a duplicate of this bug. *** *** Bug 402103 has been marked as a duplicate of this bug. *** *** Bug 402707 has been marked as a duplicate of this bug. *** *** Bug 407518 has been marked as a duplicate of this bug. *** *** Bug 410442 has been marked as a duplicate of this bug. *** *** Bug 427983 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 "REPORTED" when replying. Thank you! Hello. I can't remember if or how did I solved this, but I don't use telepathy anymore. You can close this issue. 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! |