Doing "kwin --replace&" led to logging out as well from razorqt. Doing the same from kde did not cause the logout.

regarding the script:

"great" - it executes one process, likely a binary
-> "file `which razor-session`" - if that says sth. about ASCII you can paste it as well, but

regarding your explanations:

Do you mean you run two sessions at the very same time and launching FF in that case causes one of the sessions to quit?
Probably while FF runs under the other session as well?

I will execute the file command later, as I am at home now and the computer is at my office. Tomorrow is a tentative Indian holiday.

About the explaination: I can choose "plasma-desktop" or "razorqt;kwin" session at the login screen. Only one session run at a time and I lave to logout to switch between the two. When I swich session, I log out of it and then choose other session at the kdm login screen and when I start firefox for the first time, after session switch from one to other, I got logged out abruptly.

I am facing another stupid problem now. In between these debugging steps, most probably "kwin --replace&" completely screwed up the look of firefox and it does not looks like native kde application. Earlier it look non-native application on razor only now it looks hopeless on kde session also. Can you suggest few tricks to restore the polished look of kde integration.

the firefox look is determined by the .gtkrc config file and the hint which file(s) to use is provided by some environment variable GTK2_RC_FILES.
this has nothing to do with restarting kwin, but may mean that your session environment is screwed, ie. the env is not present when launchingbFF
this is context dependent. -> open konsole and "env | grep -i gtk", see whether there is such variable and try to start FF from konsole (not by clicking somewhere and not by krunner either)
if there's such variable and FF looks as expected, i can't help you, since i don't know how your sessions get screwed.
if there's such variable and it includes some file in a .kde subpath, but FF looks wrong, run "kcmshell4 gtk" or use gtk-chtheme to change the theme.
also be aware that ff supports it's own themes and for the constant version bumping yiu might just have been using the oxygen ff theme, which then got flagged out of date...

file `which razor-session`
gives the following output

ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

Firefox look is now back to polished one after fresh booting.

@luebking: I am not getting the meaning of "sth." often used by you.

The output of ps commands under razor will be posted soon. Should I attempt to run razor with openbox WM? After reading their website, as it might be better optimised solution. For this installing openbox from Muon should do the way to go. I am just asking for opinions as I am witnessing funny thigs and I want my productive environment to sustain.

"sth." likely means "something".

ps tree and ps aux under razor in this paste-bin

http://paste.kde.org/435260/

a) if you run "pkill razor-panel" or "pkill razor-runner" that will likely log you out as well?

b) what's more important is however "only after the first switch", because it sounds like the sessions share a resource/process, ie. one process isn't taken down with the logout but should. Can you logout of the razor session, switch to VT1 (ctrl+alt+f1), login there, "pstree > pstree.interim; ps -Af > ps.interim", exit, switch back to X11 (ctrl+alt+f7), login and post/attach ps*.interim files

c) if you actually just want to run kde w/o plasma & krunner you could simply do so by overriding the services in ~/.kde/share/autostart/ - ask on in case of interest

d) i assume switching between eg. GNOME, FluxBox, XFCE or LXDE and KDE does not cause this?

PS: sorry for using abbr.s

Answers
a) No and No. Razor-panel restarted itself immediately or just blinked.
b) http://paste.kde.org/436010/
c) I liked kubuntu-low-fat-settings but it looked aweful. Please tell me ways to disable krunner and plasma. If it leads to distasteful experience, I can revert back.
d) I have run Lubuntu-desktop on Kubuntu and do not remember such weird behavior. I can not say surely about other combinations but I read a lot of tutorials about such simple hacks where I never read rants (trol) against the articles.

I read regularly that KDE developers are trying a lot of optimisation these days, kwin, plasma, pim, neopmuk. I have a feeling that, theoretically, one should be able to rum good desktop under 100 MB requirement. I am always on for thin system. More from Less for More is a regularly discussed busines model in India. Somebody can try to optimise a plasma-lite solution after we have functional variants plasma-desktop, plasma-netbook, plasma-active. Why can't we have a polished functional system with low resources? Or is it that I an unaware of such initiative.

thakur wrote:b) http://paste.kde.org/436010/

The razor session is still running at this time, did you actually log out before obtaining the pstree

thakur wrote:c) I liked kubuntu-low-fat-settings but it looked aweful. Please tell me ways to disable krunner and plasma. If it leads to distasteful experience, I can revert back.

add several files to ~/.kde/share/autostart:

--- snip plasma-desktop.desktop ---
[Desktop Entry]
Exec=plasma-desktop
Hidden=true
Name=Plasma Desktop Workspace
OnlyShowIn=KDE;
Type=Service
X-DBUS-StartupType=none
X-KDE-StartupNotify=false
X-KDE-autostart-phase=BaseDesktop
--- /snip ---

--- snip plasma-netbook.desktop --------
[Desktop Entry]
Exec=plasma-netbook
Hidden=true
Name=Plasma Netbook Workspace
OnlyShowIn=KDE;
Type=Service
X-DBUS-StartupType=none
X-KDE-StartupNotify=false
X-KDE-autostart-phase=BaseDesktop
-------- /snip ----------

--- snip krunner.desktop --------
[Desktop Entry]
Exec=krunner
Hidden=true
Name=Command Runner
OnlyShowIn=KDE;
Type=Service
X-DBUS-StartupType=none
X-KDE-StartupNotify=false
X-KDE-autostart-phase=BaseDesktop
---------- /snip -------------------

--- snip razor-desktop.desktop --------
[Desktop Entry]
Exec=razor-desktop
X-DBUS-StartupType=wait
Name=Razor Desktop
Type=Service
X-KDE-StartupNotify=false
OnlyShowIn=KDE;
X-KDE-autostart-phase=0
--- /snip -----------

--- snip razor-panel.desktop --------
[Desktop Entry]
Exec=razor-panel
#X-DBUS-StartupType=wait #probably not
Name=Razor Panel
Type=Service
X-KDE-StartupNotify=false
OnlyShowIn=KDE;
X-KDE-autostart-phase=0
--- /snip -----------

--- snip razor-runner.desktop --------
[Desktop Entry]
Exec=razor-runner
Name=Razor Desktop
Type=Service
X-KDE-StartupNotify=false
OnlyShowIn=KDE;
X-KDE-autostart-phase=0
--- /snip -----------


behavior is obviously controlled by the Hidden flag, so adding that to the razor files and commenting it in the plasma files will switch the behavior.

Sorry,

Could not read the fine print and, yes, razor desktop was running then.

Will post the correct output as soon as possible.

Too many logs

pstree and ps logs from razor-logout
http://paste.kde.org/437162/

pstree and ps logs from razor-logout (abrupt logout after starting firefox)
http://paste.kde.org/437168/

pstree and ps logs from kde logout processes
http://paste.kde.org/437174/

Hope they serve some purpose.

I also tried running razor with openbox but this problem was not resolved.

In case my old friends are still keeping track.

The latest addition to the detail and a request.

The logout after launching firefox after change session from kde to razor or vice-versa does not take place if "restart X server" commad is issued in the login screen. May be kdm is involved here!!!
Is there a way I can make it automated in some script?

Sorry, your last message fell off the table
There's no difference between the pstrees of normal and post-crash logout, but it looks wrong to me that nepomukserver is still running (because if you log out your session processes should do as well) - i'd have to test whether this occurs here, but suggest trying to
- logout (into a crash prone state)
- enter VT1, login, "pkill nepomukserver", exit
- login
- start firefox -> still crashes?

After long time (I am learning to live with the problem)

pkill neopmukserver from VT1 in crash prone stage led me to reenter credentials in the login window. then aftewards firefox did not logged me out. I could not repeat it successively.

I am stating it from memory that "restart xserver" was working in a more robust manner.