Bug 1280018

Created attachment 1092380 [details]
File: backtrace

Created attachment 1092381 [details]
File: cgroup

Created attachment 1092382 [details]
File: core_backtrace

Created attachment 1092383 [details]
File: dso_list

Created attachment 1092384 [details]
File: environ

Created attachment 1092385 [details]
File: exploitable

Created attachment 1092386 [details]
File: limits

Created attachment 1092387 [details]
File: maps

Created attachment 1092388 [details]
File: mountinfo

Created attachment 1092389 [details]
File: open_fds

Created attachment 1092390 [details]
File: proc_pid_status

Created attachment 1092391 [details]
File: var_log_messages

Another user experienced a similar problem:

Just login from sddm. The issue occurs right after kde's startup

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/xembedsniproxy
crash_function: SNIProxy::SNIProxy
executable:     /usr/bin/xembedsniproxy
global_pid:     2799
kernel:         4.2.6-300.fc23.x86_64
package:        plasma-workspace-5.4.3-3.fc23
reason:         xembedsniproxy killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

I experienced a similar problem. Just login from sddm. The issue occurs right after kde's startup

- reason: xembedsniproxy killed by SIGSEGV
- package: plasma-workspace-5.4.3-3.fc23
- kernel: 4.2.6-300.fc23.x86_64

Another user experienced a similar problem:

Start KDE plasma workspace and run any application.
Sometimes all environmnet "freeze". Frozen environment can be restart only by Ctrl-Alt-Backspace or pkill kde in neighbour console (Ctrl-Alt-F3, login, use pkill). 

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/xembedsniproxy
crash_function: SNIProxy::SNIProxy
executable:     /usr/bin/xembedsniproxy
global_pid:     1407
kernel:         4.2.5-300.fc23.i686+PAE
package:        plasma-workspace-5.4.3-2.fc23
reason:         xembedsniproxy killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

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

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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.