Bug 1537282
| Summary: | [abrt] kactivitymanagerd: QXcbConnection::processXcbEvents(): kactivitymanagerd killed by SIGSEGV | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | D. Stimits <stimits> |
| Component: | kactivitymanagerd | Assignee: | Daniel Vrátil <me> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | a.abbashamedani1371, afarrag, allan.poulsen, alvin, arepallig, a.thiaville, code, cornosier, dabbill, dap78, dennis.schridde, detonadorx, drz.se.generacio, edirenaldi20011, emanoel171, eugenemah, extras-qa, f.alexander.wilms, fukidid, garrett.mitchener, gcarmin, ger.sultanov, gos01363, gtwilliams, hanspetersorge, hitori.gm, hunkdvj, igiwatson, iliketurtlesbro, jacek.radzikowski, juha.heljoranta, juliux.pigface, LailahFSF, Larry, leshy, leskop, linuxhippy, me, m.k.wadee, mustafa1024m, nick, ogldelphi, oliver, pavel.raur.pr, rajivranjan, rdieter, recalcitrantowl, renatusbertonis, rhopp, rkudyba, rozzo, samuel_lee_1991, samuelyogi, sean, simon, smichal, soveks, spichka21, ssabcew, stealthcipher, stimits, strelok5771, sungdh86, tcarlin, thanosk, tonipallitur, vasyukv, vedran |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/facf4b838008b1d5acc9e5d69dfc0ebfb5ab505f | ||
| Whiteboard: | abrt_hash:89b1c207601eae60d69d158ee2f8633438bdad35; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1347859 | Environment: | |
| Last Closed: | 2018-11-30 20:18:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
D. Stimits
2018-01-22 20:24:54 UTC
*** Bug 1537345 has been marked as a duplicate of this bug. *** Similar problem has been detected: I signed in to KDE Plasma reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=d7542d1d9a4040a591f228ed04ca9b57;i=2a37b3;b=27904925343d4875abe88b32da6d0beb;m=4aa5c4c5;t=5637380814bd1;x=81c0dfbf9f42fe6c kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: after trying kde-plasma I logged into xfce4 again, when kactivitymanagerd crashed. why did it try to start up after all? reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=dbd28263a3d54c78a1d672869c619a1c;i=179a8;b=30e47af7ba59492bacedf68d58a2efbf;m=2d0dca3d;t=56380990d1864;x=95786aaa3fa29c52 kernel: 4.14.13-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 (In reply to Clemens Eisserer from comment #3) > Similar problem has been detected: > > after trying kde-plasma I logged into xfce4 again, when kactivitymanagerd > crashed. > why did it try to start up after all? ... In my case I've briefly seen a crash during logout, but since the desktop is closing I could never do anything about it until logging back in. I believe your crash was during logout from KDE, but the crash report tool told you about it during login because it isn't running (or is in the process of stopping) at the moment of crash. could be, I once logged out of a broken session - next time the dialog appeared. (In reply to Clemens Eisserer from comment #5) > could be, I once logged out of a broken session - next time the dialog > appeared. I just verified this. What I did was start gnome-abrt, clear all warnings, and verify "/var/spool/abrt/" was empty. Then I logged out. I looked at "/var/spool/abrt/" and there are the crash reports. So exiting KDE is a reliable trigger. Reports visible on start-up are just delayed visibility of an event which already occurred. *** Bug 1541909 has been marked as a duplicate of this bug. *** *** Bug 1542637 has been marked as a duplicate of this bug. *** *** Bug 1544018 has been marked as a duplicate of this bug. *** *** Bug 1544110 has been marked as a duplicate of this bug. *** *** Bug 1544156 has been marked as a duplicate of this bug. *** *** Bug 1544262 has been marked as a duplicate of this bug. *** *** Bug 1544292 has been marked as a duplicate of this bug. *** Similar problem has been detected: started the system when I was notified of this crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=e5f649b5941f438298f85a602100c562;i=868;b=cd0178b54b1d41f186c6eff7bb4bc928;m=27901b6;t=5651d50b2c059;x=2603b7307e88b94 kernel: 4.14.18-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: 5 3 type: CCpp uid: 1000 Similar problem has been detected: brefore shutdown I switcht to runlevel 3, at the next boot I got this crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=e5f649b5941f438298f85a602100c562;i=1203;b=550fe5fcc1774ebebe2e6518e6a22a06;m=1fe76474;t=5651d81bd4ce7;x=33153e99eb8d2ce2 kernel: 4.14.18-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: 5 3 type: CCpp uid: 1000 I have noticed a number of applications are momentarily listed as crashed during logout if the applications have not been manually closed. A big example is konsole. What I see is a pattern that logging out is for whatever reason causing crashes instead of normal shutdown of applications. I believe someone will need to trace how exiting a session for logout deals with running applications. Normally there will be no note until logging back in...in cases where the crash is actually visible during logout the crash app ends too quickly to see the details until logging back in. *** Bug 1546199 has been marked as a duplicate of this bug. *** *** Bug 1548186 has been marked as a duplicate of this bug. *** Similar problem has been detected: kactivitymanagerd crashed after update kernel 4.15.4, reboot and login session reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=ca8ca2ba7181409889635ea09baca302;i=14092;b=178a8fb5b1fe4b17b3ff719198b8cfb5;m=3304c897;t=565ec06682c67;x=91380f02c728c841 kernel: 4.15.3-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1549962 has been marked as a duplicate of this bug. *** *** Bug 1550563 has been marked as a duplicate of this bug. *** Similar problem has been detected: typical kde crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd journald_cursor: s=e5f649b5941f438298f85a602100c562;i=359cd;b=81688820ea7a4ee088f35633a0207ca5;m=2d0dd1e;t=5662aff4bdff0;x=404a3a2f4249f9e7 kernel: 4.15.4-300.fc27.x86_64 package: kactivitymanagerd-5.11.5-1.fc27 reason: kactivitymanagerd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1551184 has been marked as a duplicate of this bug. *** *** Bug 1551694 has been marked as a duplicate of this bug. *** *** Bug 1553298 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |