Repository: tauri
Issue: [bug] Unable to set x or y window position on Ubuntu production builds / bundle
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

We have a Retail POS application which has two windows. 1 main `POS` window and a customer facing `Cart` window. On MacOS, dev and prod builds, setting position for the second window is easy and is working by doing something like this onMount (Were using SvelteKit as our frontend):

```ts
const monitors = await availableMonitors() // get all available monitors

// The cart monitor is the first monitor that has a non-zero x position (monitor facing the customer)
// As this indicates that the monitor is not the primary monitor

let cartMonitor: Monitor | undefined = monitors.find((monitor) => monitor.position.x > 0)

if (!cartMonitor) {
  console.warn("No monitor with x pos greater than 0 detected")
  cartMonitor = monitors[1] // Fallback to selecting the second monitor
}

console.log("Cart monitor detected: ", cartMonitor)

new WebviewWindow("cart", {
  url: "/cart",
  title: "Cart",
  height: cartMonitor.size.height,
  width: cartMonitor.size.width,
  x: cartMonitor.position.x,
  y: cartMonitor.position.y,
})
```

With this, the second window correctly positions to the second monitor. 

The problem is however for Ubuntu, it only works for `dev` mode but not for `production builds`. The 2nd window just doesn't want to move. Even if you do something like

`await appWindow.setPosition(new LogicalPosition(1920, 0));`

It only works on `dev` but again not on `prod builds`. The windows just stays on the first monitor. Has anyone encountered this issue as well on ubuntu and how were you able to address this? (Using Ubuntu 22.04.2 LTS)

### Reproduction

1. Clone the reproduction repo: `git clone https://github.com/dreilacadin/ubuntu-tauri.git`
2. Run `yarn install` or however you'd like to install the dependencies.
3. Make sure to connect a secondary monitor or display.
4. Run `yarn tauri dev`, hopefully you would see that in dev mode, the cart window spawns to the correct secondary monitor.
5. Run `yarn tauri build` to build the production bundle.
6. Install the bundle in your Ubuntu machine.
7. Run the `ubuntu-tauri` app, check if the `Cart` window does indeed stay in your primary monitor.

### Expected behavior

The main window should, as expected, spawn in the primary monitor, then another window (cart) window should spawn to the secondary monitor.

Expected - (Works in Dev mode):

![IMG_1962](https://github.com/tauri-apps/tauri/assets/38705944/f63b0c40-7240-4631-ac6c-2d0534bdcca2)

What happens in `prod builds / bundle`. It stays on the first monitor:
![IMG_1961](https://github.com/tauri-apps/tauri/assets/38705944/6a2e1bcb-bf9b-4339-bc36-96f0b8f6e994)


### Platform and versions

```text
[✔] Environment
    - OS: Ubuntu 22.04 X64
    ✔ webkit2gtk-4.0: 2.38.6
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.65.0 (897e37553 2022-11-02)
    ✔ Cargo: 1.65.0 (4bc8f24d3 2022-10-20)
    ✔ rustup: 1.25.1 (bb60b1e89 2022-07-12)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 16.20.0
    - yarn: 1.22.19
    - npm: 8.19.4

[-] Packages
    - tauri [RUST]: 1.4.1
    - tauri-build [RUST]: 1.4.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.4.0
    - @tauri-apps/cli [NPM]: 1.4.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../build
    - devPath: http://localhost:5173/
    - framework: Svelte
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

We know for a fact that it is indeed possible to move the `Cart` window into the secondary monitor by "dragging" the `Cart` window, however, for our users that open this application a number of times throughout the day, this becomes very tedious, hence us raising this issue.