MQTTX: Client wont start on ubuntu 22.04

Just did a clean install of mqttx via snap and I get this error (mqttx:4133837): Gtk-WARNING **: 14:16:29.157: Theme parsing error: gtk.css:1413:23: ‘font-feature-settings’ is not a valid property name

(mqttx:4133837): Gtk-WARNING **: 14:16:29.160: Theme parsing error: gtk.css:3286:25: ‘font-feature-settings’ is not a valid property name

(mqttx:4133837): Gtk-WARNING **: 14:16:29.161: Theme parsing error: gtk.css:3748:23: ‘font-feature-settings’ is not a valid property name /usr/share/libdrm/amdgpu.ids: No such file or directory (node:4133837) UnhandledPromiseRejectionWarning: DriverPackageNotInstalledError: SQLite package has not been found installed. Try to install it: npm install sqlite3 --save at new DriverPackageNotInstalledError (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/error/DriverPackageNotInstalledError.js:11:28) at SqliteDriver.loadDependencies (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/driver/sqlite/SqliteDriver.js:128:19) at new SqliteDriver (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/driver/sqlite/SqliteDriver.js:29:15) at DriverFactory.create (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/driver/DriverFactory.js:45:24) at new Connection (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/connection/Connection.js:54:59) at ConnectionManager.create (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/connection/ConnectionManager.js:57:26) at /snap/mqttx/31/resources/app.asar/node_modules/typeorm/index.js:219:66 at step (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/node_modules/tslib/tslib.js:143:27) at Object.next (/snap/mqttx/31/resources/app.asar/node_modules/typeorm/node_modules/tslib/tslib.js:124:57) at /snap/mqttx/31/resources/app.asar/node_modules/typeorm/node_modules/tslib/tslib.js:117:75 (Use mqttx --trace-warnings ... to show where the warning was created) (node:4133837) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:4133837) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.