Dear Friends,
I installed razor-qt (0.4.0) on top of kubuntu (11.10, kde 4. as I wanted to try a lightweight desktop. When I logout from a kde sessio and log into razor-qt kwin session, clicking firefox causes logout from the session. It is a vice-versa process as well. It was taking place when kde was 4.7.4 and upgrading razor-qt to 0.4.1 did not solve the inconvenience.

I have posted it here with the perception that kwin handles logout and shutdown behavior. The report was filed in razor-qt google groups as well. It may also be related to firefox -kde package as other softwares does not cause this behavior.

If you open Konsole, and run "firefox" does the logout occur?
Also, what graphics card does your system have?

Finally - how abrupt is the logout? Is it instantaneous or does it take a few moments to log you out?

Sounds like FF crashes X11, check /var/log/Xorg.0.log

This would be an X11 bug.
It's likely in the GPU driver module, resp. MESA (ie. OpenGL) and caused by the parallel OpenGL usage by KWin and FF .. or your homepage uses flash

-> Suspend compositing before running FF (SHIFT+Alt+F12, given kglobalaccel is up) or disable HW acceleration in FF
You can also try the XRender acceleration of KWin (if 2 parallel GL contexts crash your X11 regardless of the actual client)

To bcooksley

The logout is abrupt/ instantaneous.
Logout also took place when command firefox was issued in krunner (Alt+F2).
Can you advise about how to check for graphics card?

To lubeking,
Homepage is "about:startpage" shipped with OS. To me, with limited knowledge, flash does not seem to be a part of it.
/var/log/Xorg.0.log does not show crash events, again to my limited knowledge.
I can post the full log, resisting owing to its length. Kindly advise.

Checking other possibilities in the meantime.

Please do post the /var/log/Xorg.0.log as well as /var/log/Xorg.0.log.old
A pastebin site such as http://paste.kde.org can be used to do this.

The log of Xorg.0.log is in the following link
http://paste.kde.org/432200/
and that of the Xorg.0.log.old is in the following link
http://paste.kde.org/432206/
and that of Xorg.1.log is at the
http://paste.kde.org/432212/

Disabling hardware acceleration from firefox did not work. I was still logged out.

It turns out to be the problem only with firefox and other applications work nicely. Once I was logged out from kde and switched to razor and then I was not logged out after clicking the icon.

"boring" - either X doesn't crash or (unlikely) doesn't log it
It's proably rather whatever keeps this session up (what is probably not kdeinit)
-> do you happen to know what that is?

Does it also happen if
* you run firefox from eg. konsole (by typing "firefox" and pressing enter)
* you have suspended compositing before (Shift+Alt+F12)
* you use another GTK+ theme (which one do you btw. use, oxygen?)

Side question: can you "kwin --replace&" w/o being logged out?

The only relevant line I can see in that X output is a note saying the Power button is being pressed, after which it begins to shutdown. This is odd indeed.

The process responsible for keeping the session up is usually ksmserver. However it should cause Dr Konqi to launch - so X should not close immediately.

Running firefox from konsole again kicked me out.
Composition is already suspended. I can post snapshot of "Desktop Effects/Systemsettings". Kindly advise.
I did not change themes and liked the defaults very much.

To the side question: Doing "kwin --replace&" led to logging out as well.

> I did not change themes and liked the defaults very much.
It was sth. you should test, not a debate about aesthetics - the theme pot. causes a segfault, leading to the "logout"

I sounds like firefox crashes KWin - however it does such.
Anyway, if restarting the WM quits the session, the session has a pretty weird setup.
-> Where did you obtain the session script so one can inspect it?
-> You need a session where you can just change the WM w/o exiting the session.
-> crashing KWin should provide you some debug output that allows to figure how your firefox manages to take it down -
iIf that is the case after all... (usually crashes occur in the compositor, resp. the GL librabry/driver - but not w/o compositing)

Come on luebking (Sorry for mistyping your name earlier)

Kindly tell me how to give you what you want. I am a chemist by education and deal with acids, bases, salt, etc.
Computers are self taught subject and I do not know the nitty gritty details of it.

@thakur: Under a KDE 4 session, please post the output of "pstree" as well as the output of "ps aux" from Konsole.

pstree log
http://paste.kde.org/434672/

ps aux
http://paste.kde.org/434678/

Errr... what Ben actually *meant* (yet didn't say was to do that under the qt-razor session you run when launching FF causes a logout.

Also there's likely sth. like /usr/bin/startrazor (just like /usr/bin/startkde) or so, what starts your crashy session.
This is the most interesting file since it will tell us why the session depends on the windowmanager.

However: since you apparently can run FF under a "normal" KDE session, this either means FF has no impact on KWin OR kwin crashes and restarts whenever you launch FF under a normal KDE session.
In the latter case you'd get a "kwin just crashed" dialog where the "developer information" would be very relevant here.

PS: i don't care about typos =)

/usr/bin/startrazor content

http://paste.kde.org/434756/

I do not get "kwin just crashed" dialogue.

The description of the problem is that after changing session from kde to razor-qt (or vice versa), starting firefox causes logout. Afterwards it runs peacefully in either environment. Also if it log me out from kde and I log into razor (or vice versa), firefox runs smoothly.

Kindly let me know if further clarification is needed.