Linux/i3: 4.16.0 client-side window chrome causes duplicate title bars and redundant window controls

[dusatvoj]

Search before asking

• I had searched in the issues and found no similar issues.

Operating System

Linux

Operating System Version

Arch Linux (rolling release), X11, i3wm

It happens on the web browser too?

No, it just happens on the Desktop app

Rocket.Chat Desktop App Version

4.16.0

Arch package:

rocketchat-client-bin 4.16.0-1

Rocket.Chat Server Version

Describe the bug

Since upgrading to Rocket.Chat Desktop 4.16.0, the new Linux client-side window chrome conflicts with window-manager-managed decorations on i3.

Rocket.Chat now renders its own title bar / TopBar and minimize, maximize and close controls inside the application window.

At the same time, i3 still manages the normal X11 window and renders its own window title bar.

The result is two stacked title bars:

1. the normal i3 window-manager title bar
2. an additional Rocket.Chat title bar / TopBar below it, including client-side window controls

This is a regression from the previous Linux behavior, where Rocket.Chat behaved as a regular WM-managed X11 application and did not render Windows-style window controls itself.

The problem is particularly visible with tiling window managers, where window decorations and window management are intentionally handled by the WM.

How to Reproduce

1. Run Linux with X11 and i3wm.
2. Install/start Rocket.Chat Desktop 4.16.0.
3. Use the sidebar navigation layout.
4. Open the main Rocket.Chat window.
5. Observe the normal i3 title bar.
6. Observe an additional Rocket.Chat title bar / TopBar directly below it, together with minimize/maximize/close controls.

The X11 window itself is otherwise a normal application window:

WM_CLASS(STRING) = "rocket-chat", "rocket-chat"
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL

[subhranshudash13-dotcom]

Hi @dusatvoj — I’d like to work on this issue. I traced the regression to the Linux window chrome changes in #3450: rootWindow.ts sets titleBarStyle: 'hidden' for Linux but never sets frame: false, while Shell/index.tsx still renders the custom WindowControls on Linux, resulting in duplicate decorations under i3.

My initial approach would be to make the custom Linux chrome opt-out, following the existing persisted setting pattern used by isTransparentWindowEnabled, allowing users to fall back to native WM decorations.
Would this approach make sense or theres something more specific u are looking for.

[dusatvoj]

I'm okay with whatever way. I just don't want to patch it. I'm okay with the auto opt-out as the manual mode.

Thank you for it.