Bug 1461661

Created attachment 1287911 [details]
File: backtrace

Created attachment 1287912 [details]
File: cgroup

Created attachment 1287913 [details]
File: core_backtrace

Created attachment 1287914 [details]
File: cpuinfo

Created attachment 1287915 [details]
File: dso_list

Created attachment 1287916 [details]
File: environ

Created attachment 1287917 [details]
File: exploitable

Created attachment 1287918 [details]
File: limits

Created attachment 1287919 [details]
File: maps

Created attachment 1287920 [details]
File: open_fds

Created attachment 1287921 [details]
File: proc_pid_status

Created attachment 1287922 [details]
File: var_log_messages

Similar problem has been detected:

This crash occurs every time I log out of KDE Plasma (but not if I just reboot or power off).

reporter:       libreport-2.9.1
backtrace_rating: 3
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=22003801544d48fabb755644e73832e6;i=4273;b=c4176feefc96422695b6f4ff3a8fdb6d;m=17cf8887;t=5527ef8fbd4f0;x=2388b8ec210b570e
kernel:         4.11.6-300.fc26.x86_64
package:        kactivitymanagerd-5.10.1-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

When the session started 

reporter:       libreport-2.9.1
backtrace_rating: 3
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=e0b39b6252694472a3a9b31965092dcb;i=cf6;b=4de80ba8be4a42ce8a16509073fccd71;m=2f1ef7eb;t=55295c0093fc5;x=4f8b8b6c407155fc
kernel:         4.11.6-300.fc26.x86_64
package:        kactivitymanagerd-5.10.1-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Similar problem has been detected:

Occurs as a notification after boot sometimes.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=dd0e3beb6b704df7a3f40f6c7a6b1d98;i=167c;b=061d4950fccf45a29c0f646e27b4818c;m=fa85cfb;t=553a6c93e2fac;x=d89335b7d06b0914
kernel:         4.11.6-301.fc26.x86_64
package:        kactivitymanagerd-5.10.1-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

After I update to Fedora 26, the gnome wayland with the teamviewer and kactivitymanagerd was crashed

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=c2c975b179f34c6ea489b6b3e6838659;i=dea5;b=28c45389859144bcba2a45e60cb52628;m=4438019;t=5544e0b7f6768;x=ec5ec6be93161982
kernel:         4.11.9-300.fc26.x86_64
package:        kactivitymanagerd-5.10.1-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

login after power off

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=47ecbea39ead43c8b3958e9cb12c6a8f;i=11695a;b=39248daad4594e85bf2002aa8326e5a5;m=baf5abfd4;t=5549058c58eb5;x=4da30e29e24fb989
kernel:         4.11.9-300.fc26.x86_64
package:        kactivitymanagerd-5.10.1-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Running the command 'kactivitymanagerd stop' on KDE logout stops the crashes.

*** Bug 1514596 has been marked as a duplicate of this bug. ***

*** Bug 1516957 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Starten von "The Long Dark" auf Steam

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=103295e53dba4202a43addebbfb26c60;i=c2c5;b=bce642ba53cb4754a438b2f9ce4c3436;m=15a1f191;t=55f5a46dead1d;x=2140e60b02270d68
kernel:         4.13.16-200.fc26.x86_64
package:        kactivitymanagerd-5.10.5-1.fc26
reason:         kactivitymanagerd killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

after reboot (new kernel)

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=62aceecc1daa4e85ab079ff61fab4210;i=126bf9;b=94d9b072ab2e4261b30b0ff8dcad1c7b;m=552589feb;t=56098cbba5d78;x=5b481df8091dd17
kernel:         4.14.4-200.fc26.x86_64
package:        kactivitymanagerd-5.10.5-1.fc26
reason:         kactivitymanagerd killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

*** Bug 1530388 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I just logged in and this was the second crashing application I saw (after qlipper).

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: QXcbConnection::processXcbEvents
executable:     /usr/bin/kactivitymanagerd
journald_cursor: s=b1fe2774a12a4dd08fc0c8aa46661419;i=9ed1;b=93ed394bbe494deea6b5c87c68915e1b;m=98dcc0964;t=5637ec2d89f5b;x=75dd2089ffa998a5
kernel:         4.14.13-200.fc26.x86_64
package:        kactivitymanagerd-5.10.5-1.fc26
reason:         kactivitymanagerd killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1544560 has been marked as a duplicate of this bug. ***

*** Bug 1546310 has been marked as a duplicate of this bug. ***

*** Bug 1548351 has been marked as a duplicate of this bug. ***

*** Bug 1573134 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.