Bug 145871

Summary:	pcmcia starts on boot after update
Product:	[Fedora] Fedora	Reporter:	Jeff Moe (jebba) <moe>
Component:	pcmcia-cs	Assignee:	Dave Jones <davej>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	notting, pfrields
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-01-23 00:19:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Moe (jebba) 2005-01-22 22:03:52 UTC

Description of problem:
After an update of pcmcia-cs it starts on boot, even when the previous
version was set to not start on boot. So if pcmcia-cs is installed,
but not in use, a user who thinks they have it disabled will have it
re-enabled at boot when they upgrade.

Version-Release number of selected component (if applicable):
pcmcia-cs-3.2.7-2.1 and earlier

How reproducible:
Get an older version of pcmcia-cs, turn it off on boot, upgrade.

Steps to Reproduce:
1.
rpm -U --oldpackage pcmcia-cs-[old version]

2.
chkconfig --del pcmcia

3.
rpm -U pcmcia-cs-3.2.7-2.1

4.
chkconfig --list | grep pcmcia    [shows pcmcia on]


Actual results:
pcmcia is set to start on boot.

Expected results:
pcmcia is left at it's previous setting to not start on reboot.
Apache, for example, honors it's previous setting.

Additional info:
Similar to recently fixed cups bug: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145629

Comment 1 Dave Jones 2005-01-23 00:19:19 UTC

use chkconfig pcmcia off instead of step 2.