No Window Manager in second X Server with SuSE 9.3
Hi all! I run an Athlon PC, using SuSE 9.3. My graphics card is a Matrox G 450 (AGP, 32 MB) with the "mga" driver. I have two TFTs connected to it with a traditional Dual-Head setup (independent KDE workspaces with different configurations, no Xinerama). With this setup (no hardware changes !), in SuSE 9.1 I could start a new session as another user, overlaying my current one, and it was fully functional. After the upgrade to SuSE 9.3, such a new session does not have a Window manager running, so the windows lack their borders and title line, and all window manager functions (resize, move, ...) are impossible to do. Is this a known effect, is there some setting needed in 9.3 which was implicit in 9.1, or anything else I can do to make this work again? Just in case someone is curious: I typically have long-running graphic applications, so I can not start them from "screen", but I want to give my wife access to her account with her own KDE and applications when I make a longer break, so I really need two different X sessions for different users, the second one hiding the first until the second terminates. Thanks for hints, Jörg -- Joerg Bruehe - persoenliche Aeusserung / speaking only for himself mailto:joerg.bruehe@web.de
It sounds like you are running twm. Simply click on the X screen and a context menu should show up. including resize/move/ and xterm :) When having an xterm you can start the WM of your choise. re, wh Joerg Bruehe wrote:
Hi all!
I run an Athlon PC, using SuSE 9.3. My graphics card is a Matrox G 450 (AGP, 32 MB) with the "mga" driver. I have two TFTs connected to it with a traditional Dual-Head setup (independent KDE workspaces with different configurations, no Xinerama).
With this setup (no hardware changes !), in SuSE 9.1 I could start a new session as another user, overlaying my current one, and it was fully functional.
After the upgrade to SuSE 9.3, such a new session does not have a Window manager running, so the windows lack their borders and title line, and all window manager functions (resize, move, ...) are impossible to do.
Is this a known effect, is there some setting needed in 9.3 which was implicit in 9.1, or anything else I can do to make this work again?
Just in case someone is curious: I typically have long-running graphic applications, so I can not start them from "screen", but I want to give my wife access to her account with her own KDE and applications when I make a longer break, so I really need two different X sessions for different users, the second one hiding the first until the second terminates.
Thanks for hints, Jörg
Hi Walter, all! walter harms wrote:
Joerg Bruehe wrote:
[[...]]
I run an Athlon PC, using SuSE 9.3. My graphics card is a Matrox G 450 (AGP, 32 MB) with the "mga" driver. I have two TFTs connected to it with a traditional Dual-Head setup (independent KDE workspaces with different configurations, no Xinerama).
With this setup (no hardware changes !), in SuSE 9.1 I could start a new session as another user, overlaying my current one, and it was fully functional.
I should have written explicitly: This second session also uses KDE.
After the upgrade to SuSE 9.3, such a new session does not have a Window manager running, [[...]]
It sounds like you are running twm. Simply click on the X screen and a context menu should show up. including resize/move/ and xterm :)
When having an xterm you can start the WM of your choise.
Well, both the old and the new session are KDE sessions, so twm should not be involved AFAIK. Can I start a WM for an existing KDE session ? I always thought 1) the WM needs to be started before the X applications, and 2) KDE has an integrated WM. But given that this second session has access to some KDE elements, its WM really seems to be a separate entity. I will give this a try on my next attempt, thanks. Jörg -- Joerg Bruehe - persoenliche Aeusserung / speaking only for himself mailto:joerg.bruehe@web.de
you did not say a work about kda, ntl, you can simply stop kwm (?) and start an other windowmanager, of cause it will be different to kwm but still a WM. most WM kan be stop during an ongoing session and an other wm started, only applicatation that need certain features of the former wm will stop working. re, wh Joerg Bruehe wrote:
Hi Walter, all!
walter harms wrote:
Joerg Bruehe wrote:
[[...]]
I run an Athlon PC, using SuSE 9.3. My graphics card is a Matrox G 450 (AGP, 32 MB) with the "mga" driver. I have two TFTs connected to it with a traditional Dual-Head setup (independent KDE workspaces with different configurations, no Xinerama).
With this setup (no hardware changes !), in SuSE 9.1 I could start a new session as another user, overlaying my current one, and it was fully functional.
I should have written explicitly: This second session also uses KDE.
After the upgrade to SuSE 9.3, such a new session does not have a Window manager running, [[...]]
It sounds like you are running twm. Simply click on the X screen and a context menu should show up. including resize/move/ and xterm :)
When having an xterm you can start the WM of your choise.
Well, both the old and the new session are KDE sessions, so twm should not be involved AFAIK.
Can I start a WM for an existing KDE session ? I always thought 1) the WM needs to be started before the X applications, and 2) KDE has an integrated WM. But given that this second session has access to some KDE elements, its WM really seems to be a separate entity.
I will give this a try on my next attempt, thanks.
Jörg
participants (2)
-
Joerg Bruehe -
walter harms