My Tauri and frontend (Quasar) browsers are conflicting

[gloomy sequoia]

My Tauri and frontend (Quasar) browsers are conflicting:
'Warn Waiting for your frontend dev server to start on http://localhost:1420/'

The tauri.config.json DevPath seems to be the problem:
No matter the URL I set DevPath to I get the above error.

If I set it to the same as the frontend URL it bombs out with:
"Finished dev [unoptimized + debuginfo] target(s) in 23.49s
/home/kenahaagner/dev/quasar-project/src-tauri/target/debug/pow: symbol lookup error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE"

In the "Integrate into Existing Project" docs, it mentions that:
"What is the URL of your dev server?
This can be either a URL or a file path that Tauri will load during development.
For the project example in this guide, this is http://localhost:3000. Note that it may be something different (or even a directory) if you're using a different framework."
I can use a directory which, I would guess would be the best for MPDA.
I've tried using UI, as explained in the "HTML, CSS, and JavaScript" section,
but this can't be found.
I've also tried "../dist" as indicated in Configuration, but here the macro panicks mentioning the "distDir" not being found but giving the line number of the DevPath.

[arctic bane]

What's weird here is why it waits for your frontend at all, since you've set it to be ../dist

It should be the same as your frontend URL, the long error you got is a step in the right direction about libc_pthread

Did you install all dependencies? Because by the looks of it what's happening is that you're missing a dependency or it's broken

[gloomy sequoia]

The frontend (Quasar) loads no problem but then the Tauri kicks in and bombs out. Sorry, the ../dist here was the last config I tested - the frontend goes to localhost 9000 regardless of what I set DevPath to

I'll keep on checking dependencies - thank you

[arctic bane]

The frontend app has its own config for what it's gonna use. What you set in tauri.conf.json tells Tauri what you have set it to in the frontend app. So if you set 9000 in Quasar then that's what you should inform Tauri that you've selected in Quasar

Once you manage to get an error about your dependency like you did above it suggests Tauri found the frontend and has started compiling, which based on the failure indicates there's a dependency issue

You can try running cargo build in the src-tauri directory, if that doesn't succeed then you gotta fix your system

[gloomy sequoia]

Will do thanks Simon

[gloomy sequoia]

Resolved:
Encountered the root hassle to be the same problems on Ubuntu 22.04 with GTK - reinstalled onto Windows 10 and good to go