https://bugs.kde.org/show_bug.cgi?id=355463
--- Comment #33 from Kai Krakow <k...@kaishome.de> ---
Crash(In reply to David Edmundson from comment #32)
> Rather than writing fancy scripts to work around it, can someone give me a
> backtrace of where there's now a crash.
Crash is still there:
$ equery b /usr/bin/xembedsniproxy
* Searching for /usr/bin/xembedsniproxy ...
kde-plasma/plasma-workspace-5.6.0 (/usr/bin/xembedsniproxy)
$ coredumpctl dump xembedsniproxy
PID: 1892 (xembedsniproxy)
UID: 500 (kakra)
GID: 500 (kakra)
Signal: 11 (SEGV)
Timestamp: Di 2016-03-22 23:24:30 CET (42min ago)
Command Line: /usr/bin/xembedsniproxy
Executable: /usr/bin/xembedsniproxy
Control Group: /user.slice/user-500.slice/session-c1.scope
Unit: session-c1.scope
Slice: user-500.slice
Session: c1
Owner UID: 500 (kakra)
Boot ID: fb9754500d82444ca9b6b57fc3270282
Machine ID: 121b87ca633e8ac0016656680000001b
Hostname: jupiter.sol.local
Coredump:
/var/lib/systemd/coredump/core.xembedsniproxy.500.fb9754500d82444ca9b6b57fc3270282.1892.1458685470000000000000.lz4
Message: Process 1892 (xembedsniproxy) of user 500 dumped core.
Stack trace of thread 1892:
#0 0x000000000040bcbc _ZNK8SNIProxy20getImageNonCompositeEv
(xembedsniproxy)
#1 0x000000000040bf97 _ZN8SNIProxy6updateEv (xembedsniproxy)
#2 0x0000000000408f49
_ZN19FdoSelectionManager17nativeEventFilterERK10QByteArrayPvPl (xembedsniproxy)
#3 0x0000003bc104b30c
_ZN24QAbstractEventDispatcher17filterNativeEventERK10QByteArrayPvPl
(libQt5Core.so.5)
#4 0x00007f59204fc7a5
_ZN14QXcbConnection14handleXcbEventEP19xcb_generic_event_t (libQt5XcbQpa.so.5)
#5 0x00007f59204fe8cb _ZN14QXcbConnection16processXcbEventsEv
(libQt5XcbQpa.so.5)
#6 0x0000003bc107682a _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5)
#7 0x0000003bc104d895
_ZN16QCoreApplication6notifyEP7QObjectP6QEvent (libQt5Core.so.5)
#8 0x0000003bc104d55d
_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent (libQt5Core.so.5)
#9 0x0000003bc1050323
_ZN16QCoreApplication9sendEventEP7QObjectP6QEvent (libQt5Core.so.5)
#10 0x0000003bc109ae33 postEventSourceDispatch
(libQt5Core.so.5)
#11 0x0000003e57a49c9d g_main_dispatch (libglib-2.0.so.0)
#12 0x0000003e57a49f80 g_main_context_iterate
(libglib-2.0.so.0)
#13 0x0000003e57a4a02c g_main_context_iteration
(libglib-2.0.so.0)
#14 0x0000003bc109aea7
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#15 0x0000003bc104c17a
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#16 0x0000003bc105354c _ZN16QCoreApplication4execEv
(libQt5Core.so.5)
#17 0x000000000040638e main (xembedsniproxy)
#18 0x00000031e5620850 __libc_start_main (libc.so.6)
#19 0x0000000000406539 _start (xembedsniproxy)
Stack trace of thread 1900:
#0 0x00000031e56dfd7d poll (libc.so.6)
#1 0x00000031e7e0aac2 poll (libxcb.so.1)
#2 0x00000031e7e0c72f xcb_wait_for_event (libxcb.so.1)
#3 0x00007f59204fec89 _ZN15QXcbEventReader3runEv
(libQt5XcbQpa.so.5)
#4 0x0000003bc0ea04a2 _ZN14QThreadPrivate5startEPv
(libQt5Core.so.5)
#5 0x00000031e5e07324 start_thread (libpthread.so.0)
#6 0x00000031e56e8b9d __clone (libc.so.6)
Refusing to dump core to tty.
--
You are receiving this mail because:
You are watching all bug changes.
