Created attachment 1393096 [details]
File: backtrace

Created attachment 1393097 [details]
File: cgroup

Created attachment 1393098 [details]
File: core_backtrace

Created attachment 1393099 [details]
File: cpuinfo

Created attachment 1393100 [details]
File: dso_list

Created attachment 1393101 [details]
File: environ

Created attachment 1393102 [details]
File: limits

Created attachment 1393103 [details]
File: maps

Created attachment 1393104 [details]
File: mountinfo

Created attachment 1393105 [details]
File: open_fds

Created attachment 1393106 [details]
File: proc_pid_status

Similar problem has been detected:

I'm not 100% sure.

Here's the sequence of events for my activity today:
* boot Fedora 27 Cinnamon virtual machine in VirtualBox 5.2.6 r120293 and log in
* run updates from dnfdragora, including a kernel update; don't know what updated *from*, but updated *to* 4.14.16-300.fc27.x86_64.
* reboot
* try pressing control-alt-t to open a terminal, find no action occurring
* open terminal via clicking on Icon on taskbar to check that the terminal application starts correctly via GUI; it started.
* suspect somehow wrong key bindings, open menu, type in 'keyboard' to look for an application that should show the keys as I press them; open 'Virtual Keyboard'
* 'Virtual Keyboard' does not show what keys are pressed on the keyboard. It appears to only be an interface to simulate button presses via the mouse
* Closed the virtual keyboard and then opened the only other application found via searching the menu for 'keyboard', the 'Keyboard' configuration application
* Layout appears to be compatible with my keyboard
* look through Keybindings to find 'Launch terminal', notice it's set for 'Ctrl+Alt+T', which I had pressed.
* Go back to started terminal, note it says 'Tilix'; type 'tilix' into command line and press enter; a new Tilix terminal window was created, then closed it.
* Create new custom shortcut, configure for name 'Launch Tilix', command 'tilix' and set its keybinding to 'Ctrl+Alt+T'; overriding the 'Launch terminal' shortcut's keybinding
* close the keyboard applications.
* Insert VirtualBox Guest Additions CD
* Attempt to install, notice that it had complained of some missing packages; installed the packages with 'dnf'
* Attempt to install (again), and it succeeds.
* reboot
* I then receive this error from the problem reporter.
* There were also SELinux issues indicating that ld.so.cache could not have 'map' action performed upon them by many background daemons that started. The file had incorrect type associations. I resolved that issue through the troubleshooter interface. This may (?) be related.


reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/csd-keyboard
crash_function: XGetWindowProperty
executable:     /usr/libexec/csd-keyboard
journald_cursor: s=97edd3e6e73c4499b68a80fdda2d0b31;i=345da;b=330e627dc5cf47efb5037534d9424ce3;m=70807a9;t=564bc439aa87f;x=b69c16094c3dc1b
kernel:         4.14.16-300.fc27.x86_64
package:        cinnamon-settings-daemon-3.6.1-1.fc27
reason:         csd-keyboard killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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

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

Similar problem has been detected:

Occured during boot, after login, but before any apps manually started.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/csd-keyboard
crash_function: XGetWindowProperty
executable:     /usr/libexec/csd-keyboard
journald_cursor: s=756794f981b5485e8f1bdad9d2c72fdb;i=d7fb;b=794720f488f6478983f21d991436295d;m=3086bed;t=5661c02264e6c;x=73a9a6401398504
kernel:         4.15.4-300.fc27.x86_64
package:        cinnamon-settings-daemon-3.6.1-1.fc27
reason:         csd-keyboard killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

System boot. Login, baamm

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/csd-keyboard
crash_function: XGetWindowProperty
executable:     /usr/libexec/csd-keyboard
journald_cursor: s=2ea17128e4414e679bc2fe212bfbf9cc;i=f5971;b=e3859ae55f41481b9558cd387d5287d1;m=2eb0b35;t=5666943884f10;x=c33b83d527e8b82c
kernel:         4.15.4-300.fc27.x86_64
package:        cinnamon-settings-daemon-3.6.1-1.fc27
reason:         csd-keyboard killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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

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

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

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

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

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

Similar problem has been detected:

Login to user (cinnamon) desktop. After logging out from other user desktop.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/csd-keyboard
crash_function: XGetWindowProperty
executable:     /usr/libexec/csd-keyboard
journald_cursor: s=e1eed83f57934e3a9cfc431fba3802c7;i=32ffc3;b=f0b266a3775e499a812e1a5199eefaf0;m=465cbe896;t=56e492948656a;x=d4fa7173dc4fbf2a
kernel:         4.16.13-200.fc27.x86_64
package:        cinnamon-settings-daemon-3.6.2-1.fc27
reason:         csd-keyboard killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Switch user (via icon on system tray), login. Error occurred while/after starting desktop. 
Even though error refers to keyboard, it seems functional as I am typing this...
Maybe related. Sometimes after being idle for a while, I need to login, but keyboard no longer functions.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/csd-keyboard
crash_function: XGetWindowProperty
executable:     /usr/libexec/csd-keyboard
journald_cursor: s=e1eed83f57934e3a9cfc431fba3802c7;i=3631b0;b=1e5b06b487414cb69c4261dd13ada0ab;m=1dd83a253;t=570b6aa51a83f;x=3c9dc55bb7773886
kernel:         4.17.3-100.fc27.x86_64
package:        cinnamon-settings-daemon-3.8.3-1.fc27
reason:         csd-keyboard killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

*** Bug 1650869 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.