Torsdag 09 juni 2005 23:29 skrev Black, Alain: Hi Alan, - thank you for your VERY prompt reaction :-) - No, usually I cannot telnet into the machine while hung at the blue screen. - The /etc/sysconfig/displaymanager indeed is correct with DISPLAYMANAGER = "kdm" and windowmanager is correct too. This was the first thing I checked myself... Yes, they've been modified recently. By the profile manager, I think. BTW this profile manager is active, but all profiles are deleted, only one is active - the current odd one. I've attached the two files to this reply. In displaymanager, I never get to see the defined greeting string, which I find very odd. Best regards, Verner

Verner,

Can you telnet/ssh into the machine from another computer when it's hung at the blue screen?

Check your /etc/sysconfig/windowmanager and /etc/sysconfig/displaymanager.

For KDE windowmanager should have: DEFAULT_WM="kde"

And displaymanager should contain: DISPLAYMANAGER="kdm"

The only times I've had a similar experience is when those got changed to a different window manager, twm or something similar.

Also, check the dates on those files to ensure that they haven't been updated anytime recently.

-Alain.

-----Original Message----- From: Verner Kjærsgaard [mailto:vk@os-academy.dk] Sent: Thursday, June 09, 2005 2:14 PM To: suse-kde@suse.com Subject: [suse-kde] Odd KDM behaving, all users listed, profiles

Hi list,

- I've ended up in a mess, now hear this...

My SuSE9.3/KDE plain vanilla used to work like a breeze - with profiles and all. Somehow, while setting up the ThinkPad to work in a temporarily new wireless environment, I landed at this scenario:

a) I edit /etc/inittab into runlevel 3. This causes a (as expected) textmode boot-up from where I can log in and to "startx". All is normal and life is good. However, if I (in textmode) fire up "mc", I get the most strange linedrawing characters. I.e., "mc" is useable, but looks very odd.

b) I edit /etc/inittab or YAST into runlevel 5. Reboot. Now I get KDM with a list of ALL users and systemusers (from /etc/passwd I think) listed. If lucky, with a working keyboard and I can log in. But, alas, only to a blue background with a very primitive Xterm - that doesn't respond to the keypad. I cannot do CTRL-ALT-F1/F2 etc., to get a shell. I cannot do anything - only switch off the machine. This leaves the runlevel set to 5, so a rescue CD is in order. Once fixed I'm back in scenario a).

Question: where does KDM get its list of users from, where is (if any) its configuration file? How to get back normal life again?

And, oh, thank you in advance and sorry for this long writing!

-- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy www.os-academy.dk Denmark +45 56964223 +45 2014 5551 ------------------------------

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

-- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy www.os-academy.dk Denmark +45 56964223 +45 2014 5551 ------------------------------ ## Path: Desktop/Display manager ## Description: ## Type: string(kdm,xdm,gdm,wdm,console) ## Default: "" # # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console). # all changes in this file require a restart of the displaymanager # DISPLAYMANAGER="kdm" ## Type: yesno ## Default: no # # Allow remote access to your display manager (xdm/kdm). Please note # that a modified kdm or xdm configuration, e.g. by KDE control center # will not be changed. # DISPLAYMANAGER_REMOTE_ACCESS="no" ## Type: yesno ## Default: no # # Allow remote access of the user root to your display manager # DISPLAYMANAGER_ROOT_LOGIN_REMOTE="no" ## Type: yesno ## Default: yes # # let the displaymanager start a local Xserver # set to "no" for remote-access only # set to "no" on architectures without any Xserver (e.g. s390/s390x) # DISPLAYMANAGER_STARTS_XSERVER="yes" ## Type: yesno ## Default: no ## Config: xdm # # Tcp port 6000 of Xserver. When set to "no" (default) Xserver is # started with "-nolisten tcp". Only set this to "yes" if you really # need to. Use ssh X11 port forwarding whenever possible. # DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no" ## Path: Desktop/Display manager ## Description: settings to generate a proper displaymanager config ## Type: list(root,all,none,local,auto) ## Default: auto ## Config: kdm3 # # KDM_SHUTDOWN determines who will be able to shutdown the # system in kdm. Valid values are: "root", "all", "none", "local", "auto" # KDM_SHUTDOWN="auto" ## Type: string ## Default: # # space separated list of users for which icons should be shown in KDM # if empty, then take system defaults # KDM_USERS="vk" ## Type: string ## Default: # # Special greeting words in kdm # KDM_GREETSTRING="Open Source Academy IBM/SuSE9.3" ## Type: string ## Default: # # Define the user whom should get logged in without request # DISPLAYMANAGER_AUTOLOGIN="" ## Type: yesno ## Default: no # # Allow all users to login without password, but ask for the user # DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" ## Type: string ## Default: SUSE # # Define the theme to be used by kdm. If empty, the traditional login # window is used (which lacks some features) # DISPLAYMANAGER_KDM_THEME="SUSE" ## Path: Desktop/Window manager ## Description: ## Type: string(kde,fvwm,gnome,windowmaker) ## Default: kde ## Config: profiles,kde,susewm # # Here you can set the default window manager (kde, fvwm, ...) # changes here require at least a re-login DEFAULT_WM="kde" ## Type: yesno ## Default: yes # # install the SuSE extension for new users # (theme and additional functions) # INSTALL_DESKTOP_EXTENSIONS="yes" ## Type: string ## Default: ## Path: Desktop ## Description: default mouse cursor theme # # Name of mouse cursor theme for X11. Possible themes can be found # in /usr/X11R6/lib/X11/icons/ # X_MOUSE_CURSOR="crystalwhite" ## Type: boolean ## Default: true ## Path: Desktop ## Description: create XDG menus for other windowmanagers ## (black, flux, openbox) # # Should SuSEconfig create XDG menus for other windowmanagers # like blackbox, fluxbox, openbox? # Possible values are lowercase "true" or "false". # CREATE_XDG_MENUS="true" ## Path: Desktop ## Description: prepare global sycoca database for faster first startup ## Type: list(yes,initial,no) ## Default: initial # # building a global sycoca database, which can be used at first user # login in KDE # KDE_BUILD_GLOBAL_SYCOCA="initial" ## Type: yesno ## Default: yes # # To disable IPv6 support within KDE. It might solve large timeouts due to # broken servers which claim to have IPv6 support, but do not respond. # KDE_USE_IPV6="yes" ## Type: yesno ## Default: yes # # IDN support can get disabled to avoid DNS phishing for example. # KDE_USE_IDN="yes"

Torsdag 09 juni 2005 23:29 skrev Black, Alain: Hi Alain and list, - correction to my answer: - I cannot telnet nor ssh into the machine - which I normally can, the firewall in the machine is OFF, so no problem here. - I'll try right away to change the "vk" to "". Remember, this (booting into level 5) may crash my machine, forcing me to do a rescue and all, it may take some time to come back to the list... - I didn't setup the users. It's only me (vk) and no more. It's just that KDM lists all systemusers too... - I have to get up very early in the morning to fly to Copenhagen, so I'll sign off now, - this being the reason for not replying to any postings that may come hereafter. - I will, however try the "vk" -> "" trick right now. If I'm not back in a few minutes, the list will know why :-) - again, thanks to all. Best regards, Verner

Verner,

Can you telnet/ssh into the machine from another computer when it's hung at the blue screen?

Check your /etc/sysconfig/windowmanager and /etc/sysconfig/displaymanager.

For KDE windowmanager should have: DEFAULT_WM="kde"

And displaymanager should contain: DISPLAYMANAGER="kdm"

The only times I've had a similar experience is when those got changed to a different window manager, twm or something similar.

Also, check the dates on those files to ensure that they haven't been updated anytime recently.

-Alain.

-----Original Message----- From: Verner Kjærsgaard [mailto:vk@os-academy.dk] Sent: Thursday, June 09, 2005 2:14 PM To: suse-kde@suse.com Subject: [suse-kde] Odd KDM behaving, all users listed, profiles

Hi list,

- I've ended up in a mess, now hear this...

My SuSE9.3/KDE plain vanilla used to work like a breeze - with profiles and all. Somehow, while setting up the ThinkPad to work in a temporarily new wireless environment, I landed at this scenario:

a) I edit /etc/inittab into runlevel 3. This causes a (as expected) textmode boot-up from where I can log in and to "startx". All is normal and life is good. However, if I (in textmode) fire up "mc", I get the most strange linedrawing characters. I.e., "mc" is useable, but looks very odd.

b) I edit /etc/inittab or YAST into runlevel 5. Reboot. Now I get KDM with a list of ALL users and systemusers (from /etc/passwd I think) listed. If lucky, with a working keyboard and I can log in. But, alas, only to a blue background with a very primitive Xterm - that doesn't respond to the keypad. I cannot do CTRL-ALT-F1/F2 etc., to get a shell. I cannot do anything - only switch off the machine. This leaves the runlevel set to 5, so a rescue CD is in order. Once fixed I'm back in scenario a).

Question: where does KDM get its list of users from, where is (if any) its configuration file? How to get back normal life again?

And, oh, thank you in advance and sorry for this long writing!

-- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy www.os-academy.dk Denmark +45 56964223 +45 2014 5551 ------------------------------

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

-- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy www.os-academy.dk Denmark +45 56964223 +45 2014 5551 ------------------------------