Created attachment 1187287 [details]
File: backtrace

Created attachment 1187288 [details]
File: cgroup

Created attachment 1187289 [details]
File: core_backtrace

Created attachment 1187290 [details]
File: dso_list

Created attachment 1187291 [details]
File: environ

Created attachment 1187292 [details]
File: exploitable

Created attachment 1187293 [details]
File: limits

Created attachment 1187294 [details]
File: maps

Created attachment 1187295 [details]
File: mountinfo

Created attachment 1187296 [details]
File: namespaces

Created attachment 1187297 [details]
File: open_fds

Created attachment 1187298 [details]
File: proc_pid_status

Created attachment 1187299 [details]
File: var_log_messages

*** ConfidentialBug 1387103 has been marked as a duplicate of this bug. ***

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Similar problem has been detected:

I found this after the first login on a freshly installed system (qemu-kvm | Fedora-KDE-Live-x86_64-26-20170420.n.0.iso)

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=e858e94c78f94e939b2bf0fe18785f3d;i=55b;b=af03f2e7bd4e43279a0d4207b5972adf;m=524905c;t=54e3f7676b123;x=433d4cc370d18f73
kernel:         4.11.0-0.rc6.git0.1.fc26.x86_64
package:        kactivitymanagerd-5.9.4-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            0

Similar problem has been detected:

Happened on first boot of a freshly installed Fedora 26 KDE system, installed to a KVM from Fedora-KDE-Live-x86_64-26-20170508.n.0.iso . Note that SDDM failed to start up at all, with some kind of kwin crash shown on the console; unsure if that's related or not.

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=fa44866444534362b2f8718a729f8e37;i=508;b=1de6959e3eb84101aeff180e52217d5a;m=2fb84e7;t=54f1d49c6ccf3;x=5fc7dd155678891b
kernel:         4.11.0-0.rc8.git0.1.fc26.x86_64
package:        kactivitymanagerd-5.9.5-1.fc26
reason:         kactivitymanagerd killed by signal 11
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            0

OK, so I'm pretty sure this crash happens on exit of initial-setup , which uses kwin as its window manager on the KDE spin (it can use various WMs, it has a list and it goes with the first that's actually available). I've now seen it happen three times in that situation. For me, when it happens, the system fails to reach the login screen as it should, but I can go to another TTY and log in and reboot from there, and on reboot, the login screen does appear and work.

I'm nominating this as at least a Beta freeze exception, as it prevents you reaching a working desktop when it happens. Not yet sure of the precise conditions under which it happens.

Here's some system logs of the initial-setup shutdown / kwin error / kactivitymanager crash sequence:

May 16 12:57:16 localhost-live.happyassassin.net initial-setup[1042]: writing the Initial Setup kickstart file /root/initial-setup-ks.cfg
May 16 12:57:16 localhost-live.happyassassin.net initial-setup[1042]: finished writing the Initial Setup kickstart file
May 16 12:57:16 localhost-live.happyassassin.net initial-setup[1042]: all changes have been applied
May 16 12:57:17 localhost-live.happyassassin.net kwin_x11[1039]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4666, resource id: 14680067, major code: 15 (QueryTree), minor code: 0
May 16 12:57:17 localhost-live.happyassassin.net initial-setup[1317]: Stopping the window manager (/usr/bin/kwin_x11)
May 16 12:57:17 localhost-live.happyassassin.net audit[1258]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 pid=1258 comm="kactivitymanage" exe="/usr/bin/kactivitymanagerd" sig=11 res=1
May 16 12:57:17 localhost-live.happyassassin.net kernel: kactivitymanage[1258]: segfault at 7f8b5ed1b650 ip 00007f8b481b29f1 sp 00007ffec91c51b8 error 4 in libQt5Sql.so.5.7.1[7f8b4819d000+49000]
May 16 12:57:17 localhost-live.happyassassin.net kactivitymanagerd[1258]: The X11 connection broke (error 1). Did the X11 server die?
May 16 12:57:17 localhost-live.happyassassin.net kglobalaccel5[1267]: The X11 connection broke (error 1). Did the X11 server die?
May 16 12:57:17 localhost-live.happyassassin.net org.a11y.Bus[1249]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":9"
May 16 12:57:17 localhost-live.happyassassin.net org.a11y.Bus[1249]:       after 41 requests (41 known processed) with 0 events remaining.
May 16 12:57:17 localhost-live.happyassassin.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-1319-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 12:57:17 localhost-live.happyassassin.net systemd[1]: Created slice system-systemd\x2dcoredump.slice.
May 16 12:57:17 localhost-live.happyassassin.net systemd[1]: Started Process Core Dump (PID 1319/UID 0).
May 16 12:57:17 localhost-live.happyassassin.net kwin_x11[1039]: The X11 connection broke: I/O error (code 1)
May 16 12:57:18 localhost-live.happyassassin.net systemd-coredump[1320]: Process 1258 (kactivitymanage) of user 0 dumped core.

Discussed at 2017-05-22 blocker review meeting: [1]. 

This bug was accepted as Freeze Exception: It would be good to get this fixed for Beta. However, if it starts to show up in more places, repropose as a blocker and we'll revisit it.

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-05-22

guessing this may be another symptom of long-standing sddm/xauth-related issue, bug #1370222

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.