Sure:
root@vm1:~# systemctl list-units | grep maas
run-snapd-ns-maas.mnt.mount loaded active mounted /run/snapd/ns/maas.mnt
snap-maas-36363.mount loaded active mounted Mount unit for maas, revision 36363
snap.maas.pebble.service loaded active running Service for snap application maas.pebble
root@vm1:~# snap remove maas
maas removed
root@vm1:~# systemctl list-units | grep maas
root@vm1:~# dpkg -l | grep maas
root@vm1:~# apt list --installed | grep maas
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
root@vm1:~# which maas
/usr/local/bin/maas
root@vm1:/usr/local/bin# apt update
Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:4 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:5 https://ppa.launchpadcontent.net/maas/3.5/ubuntu jammy InRelease
Fetched 257 kB in 1s (470 kB/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
3 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
root@vm1:/usr/local/bin# apt install snapd lxd lxd-client python3-lxc python3-openstackclient
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package lxd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package ‘lxd’ has no installation candidate
E: Unable to locate package lxd-client
root@vm1:/usr/local/bin# snap install maas
maas (3.5/stable) 3.5.0-16308-g.c799a1080 from Canonical✓ installed
postgresql is allready there
root@vm1:~# tail -n 1 /etc/postgresql/14/main/pg_hba.conf
host maas_db maas_user 0/0 md5
seting up for variables:
root@vm1:~# MAAS_DBUSER=“maas_user”
MAAS_DBPASS=“maas_dbpass_679”
MAAS_DBNAME=“mass_db”
HOSTNAME=“localhost”
maas init region+rack --database-uri postgres://maas:password@localhost/maasdb
Error: argument COMMAND: invalid choice: ‘init’ (choose from ‘help’, ‘nodes’, ‘node’, ‘machines’, ‘machine’, ‘allocate’, ‘deploy’, ‘commission’, ‘release’, ‘abort’, ‘mark-fixed’, ‘mark-broken’, ‘power-off’, ‘power-on’, ‘ssh’, ‘devices’, ‘device’, ‘controllers’, ‘controller’, ‘fabrics’, ‘fabric’, ‘vlans’, ‘vlan’, ‘subnets’, ‘subnet’, ‘spaces’, ‘space’, ‘files’, ‘tags’, ‘users’, ‘login’, ‘logout’, ‘switch’, ‘profiles’, ‘shell’)
but if i use the full path … magic happend 
/snap/bin/maas init region+rack --database-uri root@vm1:/snap/bin# /snap/bin/maas init region+rack --database-uri “postgres://maas_user:maas_dbpass_679@localhost/mass_db”
MAAS URL [default=http://10.100.131.17:5240/MAAS]:
MAAS has been set up.
If you want to configure external authentication or use
MAAS with Canonical RBAC, please run
sudo maas configauth
To create admins when not using external authentication, run
sudo maas createadmin
To enable TLS for secured communication, please run
sudo maas config-tls enable
Blockquote
Sow it’s look like solved but strand are the old bins in /usr/local/bin/maas