[plasmashell] [Bug 409652] xembedsniproxy segmentation faults in FdoSelectionManager::init when logging into Plasma on X after running scap-workbench remediation script

2019-10-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=409652

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/pla
   ||sma-workspace/741441765601c
   ||00cb84ecb7fa7b38e69d185f51a
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||5.17.1

--- Comment #3 from Nate Graham  ---
Git commit 741441765601c00cb84ecb7fa7b38e69d185f51a by Nate Graham, on behalf
of Konrad Materka.
Committed on 10/10/2019 at 14:42.
Pushed by ngraham into branch 'Plasma/5.17'.

[XembedSNIProxy] Do not crash on null pointer

Summary:
XCB may return null pointer as a response. Add a check to prevent
segmentation fault.
FIXED-IN: 5.17.1

Test Plan: It is hard to reproduce, but the reason of the segmentation fault is
pretty obvious, thanks to the debug dump from bug 409652

Reviewers: #plasma_workspaces, #plasma, davidedmundson

Reviewed By: #plasma_workspaces, #plasma, davidedmundson

Subscribers: ngraham, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D24514

M  +11   -11   xembed-sni-proxy/fdoselectionmanager.cpp
M  +2-3xembed-sni-proxy/fdoselectionmanager.h

https://commits.kde.org/plasma-workspace/741441765601c00cb84ecb7fa7b38e69d185f51a

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 409652] xembedsniproxy segmentation faults in FdoSelectionManager::init when logging into Plasma on X after running scap-workbench remediation script

2019-10-09 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=409652

Konrad Materka  changed:

   What|Removed |Added

 CC||kmate...@wp.pl

--- Comment #2 from Konrad Materka  ---
Patch:
https://phabricator.kde.org/D24514

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 409652] xembedsniproxy segmentation faults in FdoSelectionManager::init when logging into Plasma on X after running scap-workbench remediation script

2019-07-25 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=409652

Matt Fagnani  changed:

   What|Removed |Added

Version|5.15.5  |5.16.2

--- Comment #1 from Matt Fagnani  ---
Qt Version: 5.12.4
Frameworks Version: 5.59.0
Operating System: Linux 5.3.0-0.rc1.git1.1.fc31.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:

I booted into the Fedora Rawhide/31 KDE Plasma spin image
Fedora-KDE-Live-x86_64-Rawhide-20190724.n.0.iso at
https://koji.fedoraproject.org/koji/buildinfo?buildID=1319740

I ran sudo dnf install x*amd* kwin*way* pla*way*
kwayland-integration-5.16.2-1.fc31.x86_64 
kwin-wayland-5.16.2-1.fc31.x86_64 
plasma-workspace-wayland-5.16.2-2.fc31.x86_64 
xorg-x11-drv-amdgpu-19.0.1-1.fc31.x86_64  
xorg-x11-server-Xwayland-1.20.5-5.fc31.x86_64 

I logged out of Plasma. I switched to VT2 then I ran sudo systemctl restart
sddm. Plasma on X logged in automatically but Plasma froze on the splash
screen. I ran sudo systemctl stop sddm in VT2. xembedsniproxy from
plasma-workspace-5.16.2 had a segmentation fault in FdoSelectionManager::init
at
/usr/src/debug/plasma-workspace-5.16.2-2.fc31.x86_64/xembed-sni-proxy/fdoselectionmanager.cpp:69
69  if (reply->present) {

The crash had a similar trace using coredumpctl gdb as I reported before. The
pointer reply was null so reply->present looks like a null pointer dereference.
I'm unsure if the xembedsniproxy crash happened right before or after I ran
startplasmacompositor & from VT2 based on the journal. Plasma on Wayland
started, but drkonqi showed a segmentation fault in plasmashell which I
reported in bug 410211. I installed the plasma-workspaces and qt5-qtbase
debugging rpms. 

(gdb) thread apply all bt full

Thread 2 (Thread 0x7f1a4c646700 (LWP 3717)):
#0  0x7f1a5cbed79f in poll () from /lib64/libc.so.6
No symbol table info available.
#1  0x7f1a5b8202ee in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#2  0x7f1a5b820423 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#3  0x7f1a5d180bb5 in QEventDispatcherGlib::processEvents
(this=0x7f1a440018e0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
d = 0x7f1a44005250
canWait = true
savedFlags = {i = 0}
result = 
#4  0x7f1a5d12a9db in QEventLoop::exec (this=this@entry=0x7f1a4c645d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
d = 0x7f1a440065f0
locker = {val = 94273122388240}
ref = 
app = 
#5  0x7f1a5cf83625 in QThread::exec (this=this@entry=0x7f1a5da82060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
d = 0x55bdabf8c8a0
locker = {val = 94273122388240}
--Type  for more, q to quit, c to continue without paging--c
eventLoop = { = {_vptr.QObject = 0x7f1a5d3dba28 , static staticMetaObject = {d = {superdata = 0x0, stringdata =
0x7f1a5d2cb300 , data = 0x7f1a5d2cb1e0
, static_metacall = 0x7f1a5d15dfc0
,
relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x7f1a440065f0},
static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f1a5d2ce220
, data = 0x7f1a5d2cb420 ,
static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static
staticMetaObject = {d = {superdata = 0x7f1a5d3d3fe0
, stringdata = 0x7f1a5d2c56a0
, data = 0x7f1a5d2c5640
, static_metacall = 0x7f1a5d12a6f0
,
relatedMetaObjects = 0x0, extradata = 0x0}}}
returnCode = 
#6  0x7f1a5d9fef4a in QDBusConnectionManager::run (this=0x7f1a5da82060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
locker = 
#7  0x7f1a5cf84776 in QThreadPrivate::start (arg=0x7f1a5da82060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
thr = 0x7f1a5da82060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>
data = 
__clframe = {__cancel_routine = 0x7f1a5cf83eb0
, __cancel_arg = 0x7f1a5da82060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>, __do_it = 1,
__cancel_type = }
#8  0x7f1a5cad84e2 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#9  0x7f1a5cbf8333 in clone () from /lib64/libc.so.6
No symbol table info available.

Thread 1 (Thread 0x7f1a5d98bc80 (LWP 3468)):
#0  FdoSelectionManager::init (this=0x7ffda0c272b0) at
/usr/src/debug/plasma-workspace-5.16.2-2.fc31.x86_64/xembed-sni-proxy/fdoselectionmanager.cpp:69
c = 0x55bdabee0c00
reply = 0x0
#1  0x7f1a5d162576 in QtPrivate::QSlotObjectBase::call (a=0x7ffda0c26e90,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject

[plasmashell] [Bug 409652] xembedsniproxy segmentation faults in FdoSelectionManager::init when logging into Plasma on X after running scap-workbench remediation script

2019-07-25 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=409652

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

-- 
You are receiving this mail because:
You are watching all bug changes.