Red Hat Bugzilla – Bug 74556
KDE login/unlock fails for nisplus users when RedHat 7.0 was installed with GNOME default desktop
Last modified: 2015-01-07 19:00:39 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.17-21mdk i686)
Description of problem:
When RedHat 7.0 was installed with GNOME default desktop, KDE login and KDE
unlock screen fails for nisplus users.
Everything works well for local user, tested only as 'root'
Everything works well for all users, including nisplus users, when using GNOME
desktop (the one selected at installation time).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install RedHat 7.0, select GNOME as the default desktop
2.Configure to use nisplus for users
3.GNOME login: login nisplus user, select KDE desktop
4.Lock the screen
5.unlock the screen => ALWAYS FAILS
6.Ctrl+Alt+F2 to switch to virtual terminal
7.login root and kill KDE screen lock process
8.Ctrl+At+F7 to switch to KDE, the screen is unlocked
Actual Results: I must kill the KDE screen lock using virtual terminal or
remote login from other host.
BUG: pam setup only for GNOME,
Workaround: to fix all the problems,
I should copy the GNOME file into the KDE file.
% cp /etc/pam.d/gdm /etc/pam.d/kde
Expected Results: Should work
The problem is critical when switching default desktop from GNOME to KDE (file
/etc/sysconfig/desktop:DESKTOP="KDE" + reboot).
nisplus users login always fails.
Workaroung switch desktop to GNOME from a virtual terminal and reboot
This is actually a bug in the /etc/pam.d/kde file, from kdebase.
Forgot to change owner, sorry.
This bug is reported against old release of Red Hat Linux or Fedora Core
that is no longer supported. Chances are that it has been already fixed in
newer Fedora Core release. If you still experience the problem with
current release of Fedora Core, please update the Version field (you may
need to switch Product to Fedora Core first) in the bug report and put it
back to NEW state.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
If this issue is still present in a current Fedora Core release, please
open a new bug with the relevant information.
Closing as CANTFIX.