libretro / libretro/RetroArch

Desktop menu on Raspbian OS with labwc window manager unresponsive / hangs

Open
#17,775 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

When using labwc window manager on raspberry pi os the desktop menu becomes unresponsive / hangs if made fullscreen. When not in fullscreen it works as expected.

Expected behavior

Make desktop menu fullscreen and be able to interact with it.

Steps to reproduce the bug
  1. Activate labwc window manager in raspi-config if not default;
  2. Open retroarch desktop menu;
  3. Maximize it;
  4. Try to interact with the menu (select items, resize the window, navigate through items).
Version/Commit

Git b2ceb50

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Debian GNU / Linux 12 (bookworm) aarch64

Affected Cores

No response

Environment information

Window manager - labwc window manager with wayland backendGit

Relevant log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the RetroArch desktop menu hang on Debian 12 aarch64 with the labwc window manager and Wayland backend, comparing fullscreen or maximized behavior with windowed behavior. Trace the desktop menu and window-handling entry points involved in resizing and input; done means the fullscreen menu remains interactive and can be resized and navigated.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.