Bug 356325

Summary:	Each KDE session manager session save between sessions produces one additional input for xembedsniproxy in ksmserverrc
Product:	[Plasma] plasmashell	Reporter:	Peter K. <peter.krutel>
Component:	XembedSNIProxy	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	claudioantonio.morales11, kde
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Peter K. 2015-12-05 23:02:16 UTC

Using openSUSE Leap 42.1 64bit.
When KDE session is saved (manuallly or automatically at logout), to .config/ksmserverrc is added one additional entry for xembedsniproxy. Empty session starts with one xembedsniproxy process
setup 2302 2205 0 22:40 ? 00:00:00 /usr/bin/xembedsniproxy
After saving session, logout and login back we see
setup 2302 2205 0 22:40 ? 00:00:00 /usr/bin/xembedsniproxy
setup 2307 2205 0 22:40 ? 00:00:00 /usr/bin/xembedsniproxy -session 101751ea1a41a0000144926951100000017930005_1449269813_757803

In .config/session there is no file entry xembedsniproxy_101751ea1a41a0000144926951100000017930005_1449269813_757803

When in this state is session saved again, after logout and login we can see 3 xembedsniproxy processes. One without parameter and 2 with "-session" parameter. In .config/session there is no file entry starting with xembedsniproxy.

This behaviour is big problem, when user configured automatic session save on logout. In my case I had after ca 1 moth of Linux usage ca 100 xembedsniproxy processes at session start and it caused various problems in system - KDE applications cannot be started, kdeinit5 randomly crashed after login, VirtualBox said there is HW support for 3D display acceleration.

Reproducible: Always

Steps to Reproduce:
1. Save KDE session (manually or automatic save on logout)
2. Logout and login back
3. Again save KDE session (manually or automatic save on logout)

Actual Results:
Number of xembedsniproxy processes grows. From some point in time system has various problems (KDe applications do not start, kdeinit5 randomly crashed after login, VirtualBox said there is HW support for 3D display acceleration)

Expected Results:
KDE session save will include only one xembedsniproxy entry. After start there will be only one xembedsniproxy process - same behaviour as if empty session is started.

Comment 1 Peter K. 2015-12-05 23:06:02 UTC

One correction as for VirtualBox - it declared, there is NO HW support for 3D display acceleration.

Comment 2 David Edmundson 2015-12-05 23:59:01 UTC

Can you confirm your version number of Plasma

Comment 3 Peter K. 2015-12-06 01:05:06 UTC

Yast shows me plasma-framework 5.16.0-3.1 . If this is not required info, please write me help, how do get Plasma version.

Comment 4 Claudio Morales 2015-12-06 07:21:34 UTC

I can confirm I have this same issue too. I'm using openSUSE Leap 42.1

Comment 5 Peter K. 2015-12-06 13:34:25 UTC

Repeated comment in order to set bug status to UNCONFIRMED.
Yast shows me plasma-framework 5.16.0-3.1 . If this is not required info, please write me help, how do get Plasma version.

Comment 6 David Edmundson 2015-12-06 13:37:55 UTC

kinfocenter -> "KDE Plasma Version"

Comment 7 Peter K. 2015-12-06 13:46:10 UTC

kinfocenter -> "KDE Plasma Version" - 5.4.3

Comment 8 David Edmundson 2015-12-06 14:02:32 UTC

That doesn't contain xembedsniproxy.

The first official release of Plasma with xembedsniproxy is 5.5 which is out next week.
(which btw, doesn't have this bug)

I have a feeling your distribution has randomly grabbed unreleased software and started including it without asking. I can't do anything with that.