← Back to issue list

Multipass & libvirt services not restarted after snapcraft 3.0 installation

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1806057
Type
issue
State
open
Author
~igorljubuncic-deactivatedaccount
Labels
—
Created
Updated
Closed
—

Current evaluation

Snapcraft 3.0 left Multipass/libvirt daemons stopped, breaking multipass list after installation. Maintainers rejected unsafe automatic restarts and suggested pre-flight checks; no resolving change is identified.

Suggested action: keep open

Reason: The report provides the exact "list failed: Connect Failed" symptom and commands that restore both daemons. Sergiusens explicitly said a pre-flight check was possible but automatic restarts would not be done because they can kill existing workloads. Current code delegates to MultipassProvider.ensure_provider_is_available(), but no commit or release was identified as fixing this exact Snapcraft 3.0 scenario.

Evaluated by: mr-cal-bot

Impact: 39 Quick Win: 14 Complexity: 48 Confidence: 87 Actionability: 68

Issue body

After installing snapcraft 3.0, multipass and libvirt services are not restarted, resulting in a failure: multipass list list failed: Connect Failed Requires service restart to fix: systemctl stop snap.multipass.libvirt-bin.service systemctl stop snap.multipass.multipassd.service systemctl start snap.multipass.libvirt-bin.service systemctl start snap.multipass.multipassd.service Expected behavior: - Automatic service restart - Check if service is running and warn

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 39
Quick Win: 14
Complexity: 48
Confidence: 87
Actionability: 68
keep open Snapcraft 3.0 left Multipass/libvirt daemons stopped, breaking multipass list after installation. Maintainers rejected unsafe automatic restarts and suggested pre-flight checks; no resolving change is identified.
stealth/space-bunny-alpha
Impact: 22
Quick Win: 6
Complexity: 40
Confidence: 62
Actionability: 48
keep open Multipass/libvirt daemons left stopped after Snapcraft 3.0 install (2018); asks for auto-restart plus pre-flight warning. Maintainer declined auto-restart, offered pre-flight checks; today delegated to craft-providers.
stealth/space-bunny-alpha
Impact: 48
Quick Win: 22
Complexity: 32
Confidence: 86
Actionability: 68
keep open Snapcraft 3.0 can leave Multipass and libvirt stopped, breaking `multipass list`; manual systemd restarts recover access. Maintainer supports a preflight warning but rejects automatic restarts.
qwen/qwen3.6-35b-a3b
Impact: 20
Quick Win: 3
Complexity: 30
Confidence: 70
Actionability: 20
close stale Multipass and libvirt services not restarted after snapcraft 3.0 installation, requiring manual systemctl restart
qwen/qwen3.8-27b
Impact: 15
Quick Win: 9
Staleness: 95
Complexity: 40
Confidence: 70
Support Request: 45
close stale Snapcraft 3.0 install reportedly stops multipass/libvirt services, breaking 'multipass list' until manual restart. 7.75 years old, zero comments, no labels, author account deactivated, no maintainer interaction.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 10
close stale Snapcraft 3.0 installation breaks multipass and libvirt services, requiring manual restart. Issue has zero maintainer engagement and is over seven years old.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 95
Support Request: 15
close stale Reports multipass/libvirt services failing after snapcraft 3.0 installation, requiring manual restart. Open for ~7.6 years with no maintainer response or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale Issue reports multipass and libvirt services failing after snapcraft 3.0 installation, requiring manual restart. Unlabeled, zero comments, and over seven years old with no maintainer engagement.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#1807125 After snapcraft refresh, old multipass containers no longer work snapcraft (launchpad) open Snapcraft 3.0.1 could reuse incompatible Multipass VMs after a 3.0.0 refresh, causing a misleading missing-project error until snapcraft clean; the report is untriaged.
73%
#1806083 snapcraft fails to locate multipass (inside a multipass session) snapcraft (launchpad) open Snapcraft 3.0.1 falsely reported Multipass missing inside a Multipass guest; Darwin-only detection in e9ae8d29f addressed the old path, but the Launchpad record remains open.
71%