Sorry for double posting but we got something interesting from upstream:
https://github.com/snapcore/snapd/pull/7956

I can take care of fixing the packaging if we all agree this is the way to go.

Not sure where this is headed but by suggestion of the people on Snapcraft's forums, I've opened a bug report: https://bugs.launchpad.net/snapd/+bug/1858303

In T139#2870, @kc2bez wrote:

In T139#2869, @The_LoudSpeaker wrote:

I'd say we give the users an option to enable snaps using the "Welcome Center" and let them know that it will cost approx 50MB.

Having the option to enable it in the "Welcome Center" won't be any different from the experience that is provided now. The user will still have to logout/login for the menu etc. to work properly.

I've asked on Snapcraft's forum if there's a way to achieve the same behavior without seeding a snap: https://forum.snapcraft.io/t/snapd-required-dependencies-to-start/14904

In T139#2863, @kc2bez wrote:

In T139#2852, @gsilvapt wrote:

More curious data: Fresh install, since it might not have any snaps installed, systemctl status snapd returns the following (inactive): https://paste.ubuntu.com/p/z5F8bZ24yM/

Immediately after installing the core snap, it returns that is now active - perhaps that's why we can start applications from the terminal.

So sounds like if we want snaps to appear "normal" we need to seed one so that the daemon starts out of the box.

More curious data: Fresh install, since it might not have any snaps installed, systemctl status snapd returns the following (inactive): https://paste.ubuntu.com/p/z5F8bZ24yM/

In T139#2848, @wxl wrote:

Could someone fire up a VM and try installing the core snap first and then some other one and make sure it works?

Then comes the next question: if it does, how the heck do we seed a snap or make it a meta depend?????????????

In T139#2842, @wxl wrote:

@gsilvapt Good job! So now the next question is whether or not this is actually a problem with LXQt or a problem with Lubuntu (or rather LXQt but specifically in combination to the rest of our system). To test this, it would be best to check and see what happens in Debian, since it's going to be the closest to what we have. Using Debian testing or stable would be the best bet with the LXQt desktop environment installed. Probably best to check them both.

Hey guys,