Bug 357940

Summary:	kde.xembedsniproxy: failed to claim ownership of Systray Manager
Product:	[Plasma] plasmashell	Reporter:	Raman Gupta <rocketraman>
Component:	XembedSNIProxy	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kde, rdieter
Priority:	NOR
Version First Reported In:	5.5.3
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Raman Gupta 2016-01-13 17:45:36 UTC

Logged in to KDE (5.5.3). xembedsniproxy crashed on startup as usual:

[ 2699.642842] xembedsniproxy[11209]: segfault at 10 ip 000056193c119881 sp 00007ffeb2faa5d0 error 4 in xembedsniproxy[56193c10b000+17000]

Then, as I usually do, I attempted to start xembedsniproxy manually, but got the following (new) error, and xembedsniproxy failed to start:

kde.xembedsniproxy: failed to claim ownership of Systray Manager

I updated from 5.5.1 to 5.5.3 and got this error. I never got this error before.

Subsequently, I had a crash in kf5-activities (https://retrace.fedoraproject.org/faf/reports/959669/) and in plasma-workspace (https://retrace.fedoraproject.org/faf/reports/939342/). After those crashes xembedsniproxy started working correctly.


Reproducible: Always

Comment 1 David Edmundson 2016-01-13 17:49:27 UTC

>kde.xembedsniproxy: failed to claim ownership of Systray Manager

That means another systray is running.
either another xembedsniproxy or just some other systemtray app.

Comment 2 Raman Gupta 2016-01-13 18:04:20 UTC

Thanks for the quick reply. Will check for that next time and update accordingly. All the various plasma, kde5, and xembedsniproxy crashes make it hard to understand exactly what is going on and when.