Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionCameron 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:
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.
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.
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.