FS#50011 - [snapd] snapd doesn't do a systemctl daemon-reload after install

Attached to Project: Community Packages
Opened by Alexander Pavel (SuperIce97) - Sunday, 10 July 2016, 22:37 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 11 July 2016, 00:34 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Snapd should do a "systemctl daemon-reload" after install so that systemctl can see the snapd.socket. If a fresh install is done on a system, a user will not be able to load snapd.socket unless he/she runs the reload or reboot ths computer


Additional info:
2.0.10


Steps to reproduce:
Do a fresh install of snapd on a system and try to do "systemctl start snapd.socket". It will fail. Run "systemctl daemon-reload" and then "systemctl start snapd.socket" and it will succeed.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 11 July 2016, 00:34 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is an administrator task left up to the administrator.

Loading...