Bug 235169 - SCIM conf file removed on update
SCIM conf file removed on update
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: scim (Show other bugs)
6
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jens Petersen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-04 03:03 EDT by LuYu
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-19 01:20:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description LuYu 2007-04-04 03:03:14 EDT
Description of problem:
After a yum update, the scim.conf file in /etc/X11/xinit/xinput.d/ gets deleted
(probably by another package).  After the file is deleted, scim does not run
when the desktop is started.  The problem can be fixed with a forced reinstall
of the scim package which replaces the file.  Nothing else in the scim package
appears to be affected.

Version-Release number of selected component (if applicable):
FC6, but I remember this problem occurring on earlier versions of Fedora.


How reproducible:
Probably very, but I am not going to reinstall and do another yum update to find
out.

Steps to Reproduce:
1.Install Fedora Core 6
2.run: yum -y update
3.file (/etc/X11/xinit/xinput.d/scim.conf) is missing
  
Actual results:
file (/etc/X11/xinit/xinput.d/scim.conf) is missing

Expected results:
file (/etc/X11/xinit/xinput.d/scim.conf) should not be missing

Additional info:
Comment 1 Jens Petersen 2007-04-10 21:42:23 EDT
Do you have the yum.log files from you updated?

It is the first time for me hear of this problem.
Comment 2 Jens Petersen 2007-04-10 21:46:59 EDT
Can you please attach the output of "rpm -qa | sort"?
Comment 3 Jens Petersen 2007-07-19 01:20:26 EDT
Closing for now for lack of response/information.

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