Bug 358227 - xembedsniproxy crashes when fcitx is started
Summary: xembedsniproxy crashes when fcitx is started
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: XembedSNIProxy (show other bugs)
Version: 5.5.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://bugzilla.opensuse.org/show_bu...
Keywords:
Depends on:
Blocks: 358317
  Show dependency treegraph
 
Reported: 2016-01-19 21:52 UTC by Wolfgang Bauer
Modified: 2016-01-21 16:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Bauer 2016-01-19 21:52:39 UTC
See also https://bugzilla.opensuse.org/show_bug.cgi?id=954623.

Running fcitx causes xembedsniproxy to crash with a segmentation fault, causing old-style XEmbed icons to not be shown when fcitx is installed.

Reproducible: Always

Steps to Reproduce:
1. Install fcitx
2. Run fcitx (or logout/login)

Actual Results:  
xembedsniproxy crashes with a segmentation fault, XEmbed icons disappear from the system tray.

Expected Results:  
xembedsniproxy should continue to run.

fcitx's system tray icon does still show up in the system tray, so apparently it isn't even using an old-style icon.

No idea whether it's a bug in fcitx or in xembedsniproxy, but I suppose xembedsniproxy shouldn't crash anyway, so I'm filing it here.

Output of xembedsniproxy in Konsole when running fcitx:
kde.xembedsniproxy: trying to dock window  10485780
kde.xembedsniproxy: adding damage watch for  10485780
Segmentation fault

Backtrace:
#0  0x000000000040f251 in SNIProxy::SNIProxy(unsigned int, QObject*) (this=0x64f0a0, wid=23068692, parent=<optimized out>)
    at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:165
#1  0x000000000040cc18 in FdoSelectionManager::dock(unsigned int) (this=this@entry=0x7fffffffd9d0, winId=23068692)
    at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/fdoselectionmanager.cpp:157
#2  0x000000000040d0d0 in FdoSelectionManager::nativeEventFilter(QByteArray const&, void*, long*) (this=0x7fffffffd9d0, eventType=..., message=0x7fffe4003e60, result=<optimized out>)
    at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/fdoselectionmanager.cpp:124
#3  0x00007ffff6158a70 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /usr/lib64/libQt5Core.so.5
#4  0x00007fffedf02fa4 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) ()
    at /usr/lib64/libQt5XcbQpa.so.5
#5  0x00007fffedf04f7b in QXcbConnection::processXcbEvents() ()
    at /usr/lib64/libQt5XcbQpa.so.5
#6  0x00007ffff618c4f6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#7  0x00007ffff615bc2d in QCoreApplication::notify(QObject*, QEvent*) ()
    at /usr/lib64/libQt5Core.so.5
#8  0x00007ffff615b935 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
    at /usr/lib64/libQt5Core.so.5
#9  0x00007ffff615daf7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#10 0x00007ffff61b3303 in  () at /usr/lib64/libQt5Core.so.5
#11 0x00007ffff26cba04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#12 0x00007ffff26cbc48 in  () at /usr/lib64/libglib-2.0.so.0
#13 0x00007ffff26cbcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#14 0x00007ffff61b277c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#15 0x00007ffff6159803 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
    at /usr/lib64/libQt5Core.so.5
#16 0x00007ffff6161396 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#17 0x000000000040a9da in main(int, char**) (argc=1, argv=<optimized out>)
    at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/main.cpp:68
Comment 1 David Edmundson 2016-01-19 21:53:52 UTC
Fixed for 5.5.4
Comment 2 Wolfgang Bauer 2016-01-20 18:26:07 UTC
I can confirm that https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=6232362cca7021e5b436d267e07f9d6875a20a4c fixes the crashes here.
Thank you!

And sorry for not seeing the commit before filing this bug report...