Bug 91706 - xfs freshening fails on preinstall script
Summary: xfs freshening fails on preinstall script
Status: CLOSED DUPLICATE of bug 91822
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: XFree86   
(Show other bugs)
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-27 14:17 UTC by Kaj J. Niemi
Modified: 2007-04-18 16:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:53:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Kaj J. Niemi 2003-05-27 14:17:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030509

Description of problem:
sudo rpm -Fvh XFree86-xfs-4.3.0-12.i386.rpm
useradd: user xfs exists
error: %pre(XFree86-xfs-4.3.0-12) scriptlet failed, exit status 9
error:   install: %pre scriptlet failed (2), skipping XFree86-xfs-4.3.0-12

Seems like preinstall contains the following which fails if the user already
exists returning an errorcode ...

/usr/sbin/useradd -c "X Font Server" -r -s $LOGINSHELL -u 43 -d /etc/X11/fs xfs

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

How reproducible:

Steps to Reproduce:
1. rpm -Fvh XFree86-xfs*

Actual Results:  Install process aborts

Expected Results:  Shouldn't abort even if user "xfs" exists already (which is
the case with most systems)

Additional info:

The following would probably prevent the error condition (from the top of my head):

/usr/sbin/useradd -c "X Font Server" -r -s $LOGINSHELL -u 43 -d /etc/X11/fs xfs
2> /dev/null || :

Comment 1 Mike A. Harris 2003-05-28 19:06:31 UTC

*** This bug has been marked as a duplicate of 91822 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:53:16 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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