Bug 166598

Summary: leading comma on ksmserverrc restartCommand on multiscreen
Product: [Unmaintained] ksmserver Reporter: eini <a-einstein>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED FIXED    
Severity: normal CC: hans.ullrich
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description eini 2008-07-15 09:19:35 UTC 
Version:           3.5.9 (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages
OS:                Linux

By saving sessions for Multiple Screens, ksmserver corrupts the ksmserverrc for the second screen (or more; never tested more then two).
It writes a leading comma where it shouldn't be:
restartCommand1=,kwin,....
instead of correct
restartCommand1=kwin,....

This prevents kwin from starting which makes the whole screen unusable.
Comment 1 eini 2008-07-15 21:25:11 UTC 
It seems that all KDE-components which are started on screen 0.1 without a Path provide a restart command with a leading comma.
Some additional entrys from my ksmserverrc:

restartCommand1=,kwin,-session,1076696e69000121614714300000128250000_1216149417_33795,-display,:0.1
restartCommand2=kwin,-session,1076696e69000121614714300000128250001_1216149417_25958,-display,:0.0
restartCommand3=/usr/bin/kde4,nepomukserver,-session,1076696e69000121614714300000128250008_1216149417_7096,-display,:0
restartCommand4=/usr/bin/kblueplugd,-session,1076696e69000121614714400000128250015_1216149417_7401
restartCommand5=,konqueror,-session,1076696e69000121614940700000128250034_1216149417_7540,-display,:0.1
Comment 2 Lubos Lunak 2008-07-24 11:41:13 UTC 
Your kdebase is too old for kdelibs.
Comment 3 Lubos Lunak 2008-07-24 11:41:55 UTC 
SVN commit 837226 by lunakl:

The KDE_FULL_SESSION property is always on root window of screen 0.
BUG: 166598



 M  +2 -2      kapplication.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=837226
Comment 4 Lubos Lunak 2008-08-07 13:19:44 UTC 
*** Bug 168590 has been marked as a duplicate of this bug. ***