My system:

kde4-config -v
Qt: 4.4.3
KDE: 4.1.3 (KDE 4.1.3) "release 8.13"
kde4-config: 1.0

OS = SLES 11.0

Unfortunately I am unable to upgrade the version of KDE4.

Some times when I lot out of a KDE4 X session using the the little red icon instead of landing on the GUI log in screen I end up on the green screen with just a log in prompt.

Any ideas why ?
Thank you.

fornews wrote:My system:

kde4-config -v
Qt: 4.4.3
KDE: 4.1.3 (KDE 4.1.3) "release 8.13"
kde4-config: 1.0

OS = SLES 11.0

Unfortunately I am unable to upgrade the version of KDE4.

Some times when I lot out of a KDE4 X session using the the little red icon instead of landing on the GUI log in screen I end up on the green screen with just a log in prompt.

Any ideas why ?
Thank you.

Some additional information...

After logging in via the green screen I can issue startx and get back to the desktop but the logout now only includes a Logout option and if selected I'm back to the green screen. I have to reboot the server to clear this up and be able to function.

Will I continue to fight issues with KDE4/Plasma ?
I'm wondering if I should try to revert back to KDE3 and wait for a stable KDE4/Plasma in SLES before trying again ?? Pretty frustrating and amazing the instability of this beast.

Try entering "Ctrl + Alt + F7" at this "Green" login screen. ( By the way, they are usually black... don't know why a virtual terminal would be green )

bcooksley wrote:Try entering "Ctrl + Alt + F7" at this "Green" login screen. ( By the way, they are usually black... don't know why a virtual terminal would be green )

Thank you for the response.

I guess my reference to "green screen" kind of shows my age

Any idea what might be causing this problem ?
I'd like to prevent this from happening if possible.
Though I appreciate the Ctrl Alt F7 information. I'll try that next time.

Again thank you.

The only possible reason I can think of is the usage of graphics drivers from NVidia or ATI, or your system has some other underlying problem such as overheating, etc.

bcooksley wrote:The only possible reason I can think of is the usage of graphics drivers from NVidia or ATI, or your system has some other underlying problem such as overheating, etc.

I've experienced this problem both in a VMWare client running on my lap top and on a server with out any VMWare present so I can't imagine this is HW related at all. Seems like a problem in the OS, KDE4, Plasma or is something else involved ?

A user logs out from a desktop and they would expect the graphic log in with a log in followed by the graphic desktop. What the users experiences is a command line log in prompt after logging off from the graphic desktop followed by a single command line prompt after the subsequent log in.

They can switch back to the graphical login screen with Ctrl + Alt + F7 correct?

In either case, it is a bug in the Novell packages. I have not been able to reproduce.

bcooksley wrote:They can switch back to the graphical login screen with Ctrl + Alt + F7 correct?

In either case, it is a bug in the Novell packages. I have not been able to reproduce.

Actually the Ctrl + Alt + F7 didn't appear to work. I'll try again the next time it occurs but you're right it is evasive to reproduce.
Once logged in you can execute startx and get back to the graphic screen but then when you log out you're back to the command line. The only way to break the cycle is to reboot.

Can you enlighten me as to why you think it is a SLES issue ? I don't disagree but knowing might help solve and be better prepared to point to a solution even if that solution is SLES 11.1

Again thank you!!

fornews wrote:

bcooksley wrote:They can switch back to the graphical login screen with Ctrl + Alt + F7 correct?

In either case, it is a bug in the Novell packages. I have not been able to reproduce.

Actually the Ctrl + Alt + F7 didn't appear to work. I'll try again the next time it occurs but you're right it is evasive to reproduce.
Once logged in you can execute startx and get back to the graphic screen but then when you log out you're back to the command line. The only way to break the cycle is to reboot.

Can you enlighten me as to why you think it is a SLES issue ? I don't disagree but knowing might help solve and be better prepared to point to a solution even if that solution is SLES 11.1

Again thank you!!

Try this to recreate..

When logged into the desktop open a konsole and execute 'shutdown now' or 'shutdown -r now' That's how I just made it break and while there I logged in as root and ran 'runlevel' which returned '1 S' so it's pushed me back to single user mode and is now stuck/hung.

The reason I think it is SLES related is because KDM should not stop because a user has logged out. It hasn't on any of the openSUSE releases I have used.

I have no idea why the system is hanging on shutdown, you may wish to check the main console ( Ctrl + Alt + F1 ) you may need to press "Esc" to display the information.

bcooksley wrote:The reason I think it is SLES related is because KDM should not stop because a user has logged out. It hasn't on any of the openSUSE releases I have used.

I have no idea why the system is hanging on shutdown, you may wish to check the main console ( Ctrl + Alt + F1 ) you may need to press "Esc" to display the information.

I received a response via the Novell forum to try 'shutdown -h now' as opposed to 'shutdown now' and 'shutdown -h now' does not appear to experience the problem I've seen with 'shutdown now'. I believe I have experienced this problem when using the 'lock/logout' button on the desktop so I wonder if 'turn off the computer' option uses 'shutdown now'

Where is that widget so I can check the details.

Turning off the computer is handled by KDM. The command it uses to shut the system down can be changed in System Settings > Advanced > Login Manager. If it is incorrect, then you will need to launch the module as root:

Code: Select all

kdesu kcmshell4 kdm

bcooksley wrote:Turning off the computer is handled by KDM. The command it uses to shut the system down can be changed in System Settings > Advanced > Login Manager. If it is incorrect, then you will need to launch the module as root:

Code: Select all

kdesu kcmshell4 kdm

Thank you.

Looks like it uses /sbin/halt which is a binary so would have to find the source to debug further.