Ricardo Abreu
Ricardo Abreu
Meanwhile, [this](https://doc.qt.io/qt-5/qobject.html#deleteLater) mentions the requirements for the objects to actually be deleted in an event loop. Maybe they are not fulfilled in the test... TBC
The issue remains: ``` $ multipass_tests --gtest_filter=SSHFSMount* [...] ERROR: 4 leaked mock objects found at program exit. Expectations on a mock object are verified when the object is destructed. Leaking...
One other thing, is this represented in Jira somehow?
Hey @Sploder12, is this ready for another look?
Hey @tobe2098, just to clarify the signals, we do have [custom handling](https://github.com/canonical/multipass/blob/c10bd66dbe318a62746daaf53078cb5603aec960/src/daemon/daemon_main.cpp#L52-L51) for SIGINT (SIGKILL can't be handled).
I could reproduce with `snap install --edge multipass` too.
Could not reproduce here, FWIW. What does `echo $HOME` say for you?
And `echo $SNAP_REAL_HOME`? This is where we get the user's home: https://github.com/canonical/multipass/blob/43b8b9af177c3090ab6565e5154a687b7853b012/src/client/cli/cmd/launch.cpp#L138-L150
Puzzling. You're saying that those vars have the right values in `snap run --shell multipass`, right? Not sure what mechanism could be causing Multipass to see something else.
Perhaps adding `snapcraft` to the msg would be enough for now. However, future remote addition/removal would make the message outdated again. To streamline things, if we find it would make...