Bug 747453

Summary:	spiceusbsrvd is added to the run level but not started
Product:	Red Hat Enterprise Linux 6	Reporter:	Cameron Meadors <cmeadors>
Component:	spice-usb-share	Assignee:	Uri Lublin <uril>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	acathrow, dblechte, mkrcmari, pvine
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-01 20:22:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Cameron Meadors 2011-10-19 20:36:50 UTC

Description of problem:

When I installed spice-usb-share I could not get usb share to work.  I discovered that the spiceusbsrvd service was not running.  Once I started it everything worked.  On further inspection chkconfig adds the service and defaults to on.  It should just start the service.  Otherwise it requires a reboot or a manual start.

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

spice-usb-share-4.9-9.el6.x86_64

How reproducible:
every install

Steps to Reproduce:
1.install spice-usb-share
2.try to use usb share
3.notice service state
  
Actual results:
not started

Expected results:
started on install

Additional info:

Comment 3 Uri Lublin 2011-12-13 10:59:36 UTC

Packaging guidelines explicitly tells packagers not to start services upon package installation.

From http://fedoraproject.org/wiki/Packaging/SysVInitScript#InitscriptScriptlets:

  Why don't we ...
    * start the service after installation?
  Installations can be in changeroots, in an installer context, or in other
  situations where you don't want the services started.

Comment 4 Cameron Meadors 2011-12-13 14:40:59 UTC

How is the user supposed to know that he needs to start the service?  I think this is bad choice in the guidelines as it does not satisfy the basic need of package: to deliver the software to the user so that he can use it.  Is there any mechanism to notify the user to start the service?

I will figure out where I should file an RFE to resolve the usability issues of this particular guideline.

Comment 5 Andrew Cathrow 2011-12-21 18:57:25 UTC

My preference is to autostart the service.
But given the fact that the use case we're servicing here is VDI and that's template driven i don't think we're going to suffer here.