You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When removing the xochitl package the service that is running is run through /opt/bin/xochitl which means it's probably run with a rm2fb client (xochitl.service.d/toltec-wrapper.conf).
An issue arose with it when removing toltec completely (toltecctl uninstall) that xochitl held /opt and it couldn't be unmounted (device is busy).
Uninstalling xochitl package should restart the service on postremove so it's running through /usr/bin/xochitl and it releases any held files/whatever from /opt.
Discussed on discord. Hopefully it's clear and simple enough for me not to put "steps to reproduce".
The text was updated successfully, but these errors were encountered:
One thing to consider is that maybe it should be restarted only if it is running and/or enabled? I don't exactly know all the use cases here, whether it is a valid use case to have xochitl disabled when doing toltecctl uninstall and actually not wanting it to run afterwards? I presume it's like 1% of use cases but I know too little about the assumptions toltec makes here to know for sure.
Just adding this comment as a thought to consider. In any case if the service is actually running it should be restarted.
Describe the issue
When removing the
xochitl
package the service that is running is run through/opt/bin/xochitl
which means it's probably run with a rm2fb client (xochitl.service.d/toltec-wrapper.conf
).An issue arose with it when removing toltec completely (
toltecctl uninstall
) that xochitl held/opt
and it couldn't be unmounted (device is busy).Uninstalling
xochitl
package should restart the service onpostremove
so it's running through/usr/bin/xochitl
and it releases any held files/whatever from/opt
.Discussed on discord. Hopefully it's clear and simple enough for me not to put "steps to reproduce".
The text was updated successfully, but these errors were encountered: