protonscr

Black Desert: game window created Unmapped and off-screen on GNOME Wayland multi-monitor (borderless)

protonclosed appid 582660
ValveSoftware/Proton#10128 · opened 2026-09-07 by gmdias727 · updated 2026-09-07 · 1 comments · github · game page · search this game
Ggmdias727 2026-09-07 github

Compatibility Report

  • Name of the game with compatibility issues: Black Desert
  • Steam AppID of the game: 582660

Related tracking issue: #3620

System Information

  • GPU: Intel Arc A380 (DG2) [8086:56a5]
  • Video driver version: Mesa 26.1.8
  • Kernel version: 6.17.1? wait - 7.1.13-200.fc44.x86_64 (Fedora 44 Workstation)
  • Desktop: GNOME Shell / Mutter 50.4, session type Wayland (game via Xwayland + winex11.drv)
  • Link to full system information report as Gist: (not attached yet; can provide Steam Help → System Information + Runtime Diagnostics on request)
  • Proton version: Proton Experimental experimental-11.0-20260903b / prefix CURRENT_PREFIX_VERSION=11.0-100 / Wine wine-11.0
  • Steam Linux Runtime: SteamLinuxRuntime_4 (pressure-vessel)
  • Display layout:
    • HDMI-2 Samsung S24D332: [email protected] at logical position (0, 0) (not primary)
    • DP-1 LG Ultrawide 34": [email protected] at logical position (1920, 0) (primary)
    • Combined X11 desktop geometry observed: 4480×1080

I confirm:

  • [x] that I haven't found an existing compatibility report for this specific symptom (off-screen + Unmapped window). There is a general game thread in #3620.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

After getting past the Black Desert launcher, bin64/blackdesert64.exe starts and keeps running normally (high CPU, DXVK threads active, audio stream from blackdesert64.exe playing), but the game window is inaccessible in GNOME.

Inspection of the Xwayland window tree showed the top-level window existed with:

  • WM_NAME: Black Desert - <characterId>
  • WM_CLASS: steam_app_582660, steam_app_582660
  • size: 1920x1080
  • position: +-2366+-80 (outside the 4480×1080 desktop)
  • map_state: Unmapped
  • not present in _NET_CLIENT_LIST until manually mapped

So the process is healthy, but the Wine/X11 window is created (or left) unmapped and far off-screen, which makes it missing from normal GNOME overview / task switching behavior.

Game video settings at the time (Documents/Black Desert/GameOption.txt):

windowed = 2
width = 1920
height = 1080

(windowed = 2 is Black Desert borderless window mode.)

Relevant runtime details:

  • Proton launches BlackDesertLauncher.exe --steam, then the client blackdesert64.exe
  • Display driver in use: winex11.drv / winex11.so (not winewayland)
  • DISPLAY=:0, WAYLAND_DISPLAY=wayland-0
  • DXVK is active (dxvk-submit / dxvk-cs threads; renderD128 FDs open)
  • Steam overlay process attached to the game PID

Workaround that recovered the window for this session:

  1. Locate the X11 window named Black Desert - *
  2. XMoveResizeWindow to an on-screen position
  3. XMapRaised

After that, the window appeared in _NET_CLIENT_LIST and became viewable. Subsequent attempts to move it onto the primary ultrawide (x=1920) via plain X11 configure/_NET_MOVERESIZE_WINDOW were resisted (position snapped back), which may be a separate borderless/fullscreen-window interaction.

Reproduction

  1. Use GNOME on Wayland with two monitors arranged horizontally (secondary at x=0, primary ultrawide at x=1920).
  2. Launch Black Desert (582660) with Proton Experimental.
  3. Pass the launcher and enter the game client.
  4. Observe that the client process remains running (CPU/GPU/audio), but no usable game window is available in GNOME.
  5. Inspect X11 windows (Xwayland): find steam_app_582660 / Black Desert - ... at a large negative coordinate with map_state=Unmapped.

Expected: mapped, focusable window on a visible monitor (preferably the primary).
Actual: unmapped window parked off-screen; game continues running headlessly from the user's point of view.

Happy to attach a PROTON_LOG=1 log and Steam system information gist after the next reproduction.

Kkisak-valve maintainer 2026-09-07 github

Hello @gmdias727, as you've already noted, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-5573505798.

Proton versions

Launch options

Upstream links