Bug 54173 - up2dating to kdebase-2.2-9 breaks KDM
Summary: up2dating to kdebase-2.2-9 breaks KDM
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kdebase (Show other bugs)
(Show other bugs)
Version: roswell
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-30 10:48 UTC by Markku Kolkka
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-24 23:09:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Markku Kolkka 2001-09-30 10:48:47 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010809

Description of problem:
After using up2date to install the full set of updates to Roswell-2 KDM 
stops working. /var/log/messages contains the following error messages:
 Sep 30 11:24:44 localhost kdm_config[1092]: Cannot open config file
/usr/share/config/kdm/kdmrc
Sep 30 11:24:44 localhost kdm[1083]: Cannot open access control file
/usr/share/config/kdm/Xaccess, no XDMCP reqeusts will be granted
Sep 30 11:24:44 localhost kdm[1083]: cannot access servers file
/usr/share/config/kdm/Xservers
The directory /usr/share/config/kdm is empty.
There's a symbolic link /usr/share/config/kdm;3bb5e565 that points to
/etc/kde/kdm

Version-Release number of selected component (if applicable):
kdebase-2.2-9

How reproducible:
Always

Steps to Reproduce:
1. Install Roswell-2 as a KDE workstation
2. Run up2date under KDE and update everything
3. Reboot
	

Actual Results:  Text console with a login prompt

Expected Results:  KDM login screen

Additional info:
Note You need to log in before you can comment on or make changes to this bug.