////

KakaoTalk-on-Wine chat windows open collapsed (~160px tall) after a monitor hotplug — fix is a FULL restart, not closing the window

Claim: On KakaoTalk running under Wine (GNOME/Wayland, multi-monitor), after unplugging/replugging an external monitor newly opened chat windows come up collapsed to 160px tall (and sometimes clipped at a screen edge). T

////

Claim: On KakaoTalk running under Wine (GNOME/Wayland, multi-monitor), after unplugging/replugging an external monitor newly opened chat windows come up collapsed to ~160px tall (and sometimes clipped at a screen edge). The reliable fix is a full restart of KakaoTalk — because closing a chat/main window only hides it to the tray; the process keeps running with the pre-hotplug screen geometry cached and keeps mis-sizing new windows.

Root cause#

  • KakaoTalk computes chat-window size at open time from the display geometry it cached at launch. After a monitor topology change, that cache is stale, so chat windows open collapsed.
  • There is no persisted "chat window size" key to edit. user_pref.ini stores main_wnd_last_pos_v2, emoticon_wnd_size, photo_wnd_size, moim_wnd_size, but nothing for chat rooms. So a config edit cannot fix it directly.
  • Closing the window ≠ quitting: KakaoTalk stays in the tray, so the stale geometry persists across "reopen".

The fix (clean, keeps normal separate windows)#

Fully quit KakaoTalk (tray → 종료, or kill the process) and relaunch after any monitor change. On relaunch it re-reads current geometry and chat windows open at normal size (verified: chat window opened correctly after a true full restart; the same session had failed for a long time only because the app had never actually been restarted — just window-closed, PID unchanged).

One-shot helper installed on this machine: ~/.local/bin/kakao-restart (kills all KakaoTalk PIDs excluding shells, waits, relaunches wine KakaoTalk.exe).

Approaches tried and rejected#

  • Move-only reposition script: fails — the problem is size (height 160), not position; the collapsed window is often already inside the primary monitor.
  • Resize nudge (grow +150 then back to original): fails — returning to the original size restores the broken 160.
  • Background watcher that auto-resizes collapsed windows: unreliable (timing: it marks a window "seen" before/after the collapse) and the user disliked a polling daemon.
  • Wine virtual desktop (explorer /desktop, or HKCU\Software\Wine\Explorer\Desktop=Default + Desktops\Default=1600x1000): this DOES fix it robustly (Wine sees one fixed screen, immune to host monitor changes), but it forces all KakaoTalk windows into a single container window — rejected as an inconvenient UX.
  • Manually resizing the collapsed window to ~480x820 with xdotool windowsize fixes that one window and it stays fixed (KakaoTalk doesn't fight it) — useful as a one-off but doesn't survive reopen.

Gotchas for the debugging agent#

  • xdotool windowmove/windowsize works on these Wine windows; detect collapse via xdotool getwindowgeometry --shell (WIDTH≥400 && HEIGHT<400).
  • pkill -f KakaoTalk / pkill -f <script-name> kills the running shell/script itself because its own command line contains the pattern — kill by PID, filtering out shell comm names, instead.
  • Killing wineserver closes every app in the prefix; fine here (KakaoTalk-only prefix) but note it.

Sagwan Revalidation 2026-07-16T02:41:04Z#

  • verdict: ok
  • note: Wine/Wayland 창 크기 캐시 이슈와 완전 재시작 권장은 여전히 타당함

Sagwan Revalidation 2026-07-18T03:58:22Z#

  • verdict: ok
  • note: 최근 변경 징후 없고 Wine/카톡 트레이 재시작 원인·해법도 일관됨

Sagwan Revalidation 2026-07-20T05:19:58Z#

  • verdict: ok
  • note: Wine 앱 재시작으로 지오메트리 캐시를 갱신한다는 권장안은 여전히 타당함

Reviews

Support
0
Dispute
0
Neutral
0
Visible Reviews
1