Bug 165863

Summary: Session manager starts wrong / no window manager, ignores some preferences
Product: [Unmaintained] ksmserver Reporter: Georg Greve <greve>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Plasma Appletsrc, as requiested

Description Georg Greve 2008-07-06 15:36:49 UTC 
Version:            (using KDE 4.0.83)
Installed from:    Debian testing/unstable Packages
Compiler:          Debian GNU/Linux (experimental), version 4:4.0.84-1 
OS:                Linux

This is the second half of the problem initially reported in http://bugs.kde.org/show_bug.cgi?id=163218 - the missing window decorations. Digging a bit deeper, I could reproduce this with KDE 4.1-beta2 and it seems to be an issue with the session management.

During the first login, KDE 4.1 starts with metacity instead of kwin.

This is despite kwin having been selected as window manager in the session settings.

On second login, no window manager gets started. Neither metacity nor kwin are running.

Opening a shell and doing "kwin --replace &" starts kwin and all runs normally from there on. Note: The option "--replace" is necessary, or it says there is a window manager running, although I cannot find one in the process list. 

If I can provide more information to help you track down the problem, please let me know.
Comment 1 Georg Greve 2008-07-06 16:07:58 UTC 
One additional bit of information: The compiz window manager was running, but there were no window decorations, which is why it looked like it wasn't running.
Comment 2 Georg Greve 2008-07-07 20:20:00 UTC 
Created attachment 25908 [details]
Plasma Appletsrc, as requiested
Comment 3 Georg Greve 2008-07-07 20:23:23 UTC 
My apologies, wrong bug. Hadn't noticed that Bugzilla had jumped to next bug after submitting comments for previous one.
Comment 4 Dario Andres 2009-02-05 22:57:00 UTC 
Can you still reproduce this bug with a recent KDE installation ? 
It sounds like an installation bug to me
Thanks
Comment 5 Lubos Lunak 2009-11-23 20:14:15 UTC 
No response.