https://bugs.kde.org/show_bug.cgi?id=356325
            Bug ID: 356325
           Summary: Each KDE session manager session save between sessions
                    produces one additional input for xembedsniproxy in
                    ksmserverrc
           Product: plasmashell
           Version: master
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: grave
          Priority: NOR
         Component: XembedSNIProxy
          Assignee: plasma-b...@kde.org
          Reporter: hra...@post.sk

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.

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

Reply via email to