Bug 359333

Summary: starting google chrome crashes xembedsniproxy
Product: [Plasma] plasmashell Reporter: Vadym Krevs <vkrevs>
Component: XembedSNIProxyAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol
Priority: NOR    
Version: 5.5.4   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Vadym Krevs 2016-02-12 21:13:12 UTC
openSUSE Leap 42.1 with latest plasma/frameworks from obs.

$ rpm -qf `which xembedsniproxy `
plasma5-workspace-5.5.4-166.1.x86_64

Login, and start google chrome. Xembedsniproxy crashes with the following stack trace:

Program received signal SIGSEGV, Segmentation fault.
0x000000000040fe0f in SNIProxy::getImageNonComposite() const ()
(gdb) bt
#0  0x000000000040fe0f in SNIProxy::getImageNonComposite() const ()                                                                                                                                                                          
#1  0x00000000004100d4 in SNIProxy::update() ()                                                                                                                                                                                              
#2  0x000000000040cf76 in FdoSelectionManager::nativeEventFilter(QByteArray const&, void*, long*) ()                                                                                                                                         
#3  0x00007f97038c0fc0 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=<optimized out>, eventType=..., message=message@entry=0x7f96f4003c40, result=result@entry=0x7ffddb092f18)                       
    at kernel/qabstracteventdispatcher.cpp:460                                                                                                                                                                                               
#4  0x00007f96fcd18044 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x11d3420, event=event@entry=0x7f96f4003c40) at qxcbconnection.cpp:1020                                                                      
#5  0x00007f96fcd1a01b in QXcbConnection::processXcbEvents() (this=0x11d3420) at qxcbconnection.cpp:1504                                                                                                                                     
#6  0x00007f97038f4ac6 in QObject::event(QEvent*) (this=0x11d3420, e=<optimized out>) at kernel/qobject.cpp:1239                                                                                                                             
#7  0x00007f97038c418d in QCoreApplication::notify(QObject*, QEvent*) (this=<optimized out>, receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1038                                                            
#8  0x00007f97038c3e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffddb093490, receiver=0x11d3420, event=event@entry=0x7f96f4003cc0) at kernel/qcoreapplication.cpp:965                                                 
#9  0x00007f97038c6057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x7f96f4003cc0, receiver=<optimized out>) at kernel/qcoreapplication.h:224                                                           
#10 0x00007f97038c6057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x11c2d70) at kernel/qcoreapplication.cpp:1593                            
#11 0x00007f97038c6608 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451                                                                 
#12 0x00007f970391b8f3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x1223bf0) at kernel/qeventdispatcher_glib.cpp:271                                                                                                     
#13 0x00007f96ffe7dc84 in g_main_context_dispatch (context=0x7f96f40016f0) at gmain.c:3122                                                                                                                                                   
#14 0x00007f96ffe7dc84 in g_main_context_dispatch (context=context@entry=0x7f96f40016f0) at gmain.c:3737                                                                                                                                     
#15 0x00007f96ffe7ded8 in g_main_context_iterate (context=context@entry=0x7f96f40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808                                                                
#16 0x00007f96ffe7df7c in g_main_context_iteration (context=0x7f96f40016f0, may_block=1) at gmain.c:3869                                                                                                                                     
#17 0x00007f970391ad6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x1225860, flags=...) at kernel/qeventdispatcher_glib.cpp:418                                                                     
#18 0x00007f97038c1d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffddb093420, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204                                                                  
#19 0x00007f97038c98f6 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229                                                                                                                                                    
#20 0x000000000040a9ca in main ()
(gdb) 


Reproducible: Always

Steps to Reproduce:
1. Login into KDE
2. open konsole, attach gdb to xembedconsole, continue
3. Click on google chrome icon


Actual Results:  
xembedsniproxy crashes

Expected Results:  
no crashes, dropbox, google chrome's icons are displayed normally in the system tray
Comment 1 David Edmundson 2016-02-15 17:00:31 UTC

*** This bug has been marked as a duplicate of bug 355463 ***